Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Discovery, Poller, Unix Agent

    Description

      Hey there,

      we would be happy to have a ZOL integration. An agent that could read the pools and collect the status of the pools and then display them as a status indicator.

       

      We run some storages with ZOL and would be very happy about such a feature!

       

       

      Attachments

        Activity

          [OBS-3249] ZFS on Linux

          Data is not exposed vi snmp so this would need a unix agent modification to identify and pull out requisite data.   As Adam Sarkozi above indicated a bare minimum would be health status.   But to be able to track arc stats and other metrics pulled from /sys/modules/zfs/parameters.     

          Top of my head some items would be:

           

          l2arc size

          l2arc low memory aborts

          arc size  (relation to 'c' total size) 

          arc hits

          arc misses

          demand hits

          demand miss

          prefetch hits

          prefetch miss

           

          basically the stats you can get from arc_summary but something that can be recorded/graphed over time.

            

          # arc_summary
           ------------------------------------------------------------------------
          ZFS Subsystem Report                            Fri Feb 11 11:32:07 2022
          Linux 5.4.0-89-generic                                0.8.3-1ubuntu12.12
          Machine: loki (x86_64)                                0.8.3-1ubuntu12.12ARC status:                                                      HEALTHY
                  Memory throttle count:                                         0ARC size (current):                                   100.1 %   64.0 GiB
                  Target size (adaptive):                       100.0 %   64.0 GiB
                  Min size (hard limit):                          4.6 %    3.0 GiB
                  Max size (high water):                           21:1   64.0 GiB
                  Most Frequently Used (MFU) cache size:         96.3 %   47.7 GiB
                  Most Recently Used (MRU) cache size:            3.7 %    1.8 GiB
                  Metadata cache size (hard limit):              75.0 %   48.0 GiB
                  Metadata cache size (current):                 44.8 %   21.5 GiB
                  Dnode cache size (hard limit):                 10.0 %    4.8 GiB
                  Dnode cache size (current):                   143.5 %    6.9 GiBARC hash breakdown:
                  Elements max:                                              20.9M
                  Elements current:                              84.9 %      17.7M
                  Collisions:                                                 1.7G
                  Chain max:                                                    12
                  Chains:                                                     4.8MARC misc:
                  Deleted:                                                    3.2G
                  Mutex misses:                                             485.7k
                  Eviction skips:                                           248.0MARC total accesses (hits + misses):                                19.1G
                  Cache hit ratio:                               84.6 %      16.1G
                  Cache miss ratio:                              15.4 %       2.9G
                  Actual hit ratio (MFU + MRU hits):             83.7 %      16.0G
                  Data demand efficiency:                        93.2 %       7.5G
                  Data prefetch efficiency:                      11.0 %       2.6GCache hits by cache type:
                  Most frequently used (MFU):                    60.7 %       9.8G
                  Most recently used (MRU):                      38.2 %       6.2G
                  Most frequently used (MFU) ghost:               0.2 %      26.5M
                  Most recently used (MRU) ghost:                 0.7 %     116.9M
                  Anonymously used:                               0.2 %      37.2MCache hits by data type:
                  Demand data:                                   43.4 %       7.0G
                  Demand prefetch data:                           1.7 %     280.0M
                  Demand metadata:                               53.7 %       8.7G
                  Demand prefetch metadata:                       1.2 %     199.0MCache misses by data type:
                  Demand data:                                   17.3 %     506.5M
                  Demand prefetch data:                          77.6 %       2.3G
                  Demand metadata:                                1.8 %      51.6M
                  Demand prefetch metadata:                       3.3 %      97.9MDMU prefetch efficiency:                                            4.7G
                  Hit ratio:                                     41.9 %       2.0G
                  Miss ratio:                                    58.1 %       2.8GL2ARC status:                                                    HEALTHY
                  Low memory aborts:                                          3.9k
                  Free on write:                                               618
                  R/W clashes:                                                   0
                  Bad checksums:                                                 0
                  I/O errors:                                                    0L2ARC size (adaptive):                                         385.6 GiB
                  Compressed:                                    19.4 %   74.7 GiB
                  Header size:                                    0.3 %    1.1 GiBL2ARC breakdown:                                                    2.9G
                  Hit ratio:                                      1.7 %      49.3M
                  Miss ratio:                                    98.3 %       2.9G
                  Feeds:                                                      8.6ML2ARC writes:
                  Writes sent:                                    100 %    2.0 MiBL2ARC evicts:
                  Lock retries:                                                  0
                  Upon reading:                                                  0
           
          
          

           

           

          u7K5VtKqFn Steve Costaras added a comment - Data is not exposed vi snmp so this would need a unix agent modification to identify and pull out requisite data.   As Adam Sarkozi above indicated a bare minimum would be health status.   But to be able to track arc stats and other metrics pulled from /sys/modules/zfs/parameters.      Top of my head some items would be:   l2arc size l2arc low memory aborts arc size  (relation to 'c' total size)  arc hits arc misses demand hits demand miss prefetch hits prefetch miss   basically the stats you can get from arc_summary but something that can be recorded/graphed over time.    # arc_summary ------------------------------------------------------------------------ ZFS Subsystem Report                            Fri Feb 11 11 : 32 : 07 2022 Linux 5.4 . 0 - 89 -generic                                 0.8 . 3 -1ubuntu12. 12 Machine: loki (x86_64)                                 0.8 . 3 -1ubuntu12.12ARC status:                                                      HEALTHY         Memory throttle count:                                         0ARC size (current):                                   100.1 %   64.0 GiB         Target size (adaptive):                       100.0 %   64.0 GiB         Min size (hard limit):                           4.6 %     3.0 GiB         Max size (high water):                           21 : 1   64.0 GiB         Most Frequently Used (MFU) cache size:         96.3 %   47.7 GiB         Most Recently Used (MRU) cache size:             3.7 %     1.8 GiB         Metadata cache size (hard limit):               75.0 %   48.0 GiB         Metadata cache size (current):                 44.8 %   21.5 GiB         Dnode cache size (hard limit):                 10.0 %     4.8 GiB         Dnode cache size (current):                   143.5 %     6.9 GiBARC hash breakdown:         Elements max:                                               20 .9M         Elements current:                               84.9 %       17 .7M         Collisions:                                                 1 .7G         Chain max:                                                     12         Chains:                                                     4 .8MARC misc:         Deleted:                                                     3 .2G         Mutex misses:                                             485 .7k         Eviction skips:                                           248 .0MARC total accesses (hits + misses):                                 19 .1G         Cache hit ratio:                               84.6 %       16 .1G         Cache miss ratio:                               15.4 %       2 .9G         Actual hit ratio (MFU + MRU hits):             83.7 %       16 .0G         Data demand efficiency:                         93.2 %       7 .5G         Data prefetch efficiency:                       11.0 %       2 .6GCache hits by cache type:         Most frequently used (MFU):                     60.7 %       9 .8G         Most recently used (MRU):                       38.2 %       6 .2G         Most frequently used (MFU) ghost:               0.2 %       26 .5M         Most recently used (MRU) ghost:                 0.7 %     116 .9M         Anonymously used:                               0.2 %       37 .2MCache hits by data type:         Demand data:                                   43.4 %       7 .0G         Demand prefetch data:                           1.7 %     280 .0M         Demand metadata:                               53.7 %       8 .7G         Demand prefetch metadata:                       1.2 %     199 .0MCache misses by data type:         Demand data:                                   17.3 %     506 .5M         Demand prefetch data:                           77.6 %       2 .3G         Demand metadata:                                 1.8 %       51 .6M         Demand prefetch metadata:                       3.3 %       97 .9MDMU prefetch efficiency:                                             4 .7G         Hit ratio:                                     41.9 %       2 .0G         Miss ratio:                                     58.1 %       2 .8GL2ARC status:                                                    HEALTHY         Low memory aborts:                                           3 .9k         Free on write:                                               618         R/W clashes:                                                   0         Bad checksums:                                                 0         I/O errors:                                                    0L2ARC size (adaptive):                                         385.6 GiB         Compressed:                                     19.4 %   74.7 GiB         Header size:                                     0.3 %     1.1 GiBL2ARC breakdown:                                                     2 .9G         Hit ratio:                                       1.7 %       49 .3M         Miss ratio:                                     98.3 %       2 .9G         Feeds:                                                       8 .6ML2ARC writes:         Writes sent:                                     100 %     2.0 MiBL2ARC evicts:         Lock retries:                                                   0         Upon reading:                                                   0      

          Hi Richard Kucera, we have not received the additional information requested earlier from you in this issue 'Hey there,

          we would be happy to have a ZOL integration. An agent that could read the pools and collect the status of the pools and then display them as a status indicator.

           

          We run some storages with ZOL and would be very happy about such a feature!

           

           '!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Richard Kucera, we have not received the additional information requested earlier from you in this issue 'Hey there, we would be happy to have a ZOL integration. An agent that could read the pools and collect the status of the pools and then display them as a status indicator.   We run some storages with ZOL and would be very happy about such a feature!    '! Issues without your response will be closed within 2 weeks.

          Hello,

          Can we get an Unix agent solution to this problem?
          A simple status with pool name and status like FreeNAS status indicator as the attached image of the sender of the ticket.

          Possible output from Linux:
          root@pbstest: ~ # zpool list -o name, health
          NAME HEALTH
          MirrorTest DEGRADED
          PoolTest SUSPENDED
          TestZFS ONLINE

          Thanks in advance

          sarada Adam Sarkozi added a comment - Hello, Can we get an Unix agent solution to this problem? A simple status with pool name and status like FreeNAS status indicator as the attached image of the sender of the ticket. Possible output from Linux: root@pbstest: ~ # zpool list -o name, health NAME HEALTH MirrorTest DEGRADED PoolTest SUSPENDED TestZFS ONLINE Thanks in advance

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          Note, this comment is added automatically.

          landy Mike Stupalov added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

          People

            landy Mike Stupalov
            kuhner Richard Kucera
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: