Ad Widget

Collapse

TrueNAS - no trigger or alert when ZFS pool is above defined percentage value.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • beriapl
    Junior Member
    • Jun 2020
    • 7

    #1

    TrueNAS - no trigger or alert when ZFS pool is above defined percentage value.

    I successfully set up monitoring for my TrueNAS by official SNMP integration/template from zabbix.
    However, I have a strange issue with alerts about ZFS pool usage - they are not generated, and I have no idea why.
    I have zabbix 7.0.6 and I'm using TrueNAS CORE by SNMP.

    There is a trigger definition using two macros:
    {$ZPOOL.PUSED.MAX.WARN} - value 80
    {$ZPOOL.PUSED.MAX.CRIT} - value 90

    All values are watched properly, but my zpool is currently at 99.32 usage and I never got any alert on the zabbix.





  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4811

    #2
    How much free space you still have?
    If you look here https://www.zabbix.com/integrations/truenas, then it says "2 conditions have to match"...
    Two conditions should match:
    1. The first condition - utilization of the space should be above {$ZPOOL.PUSED.MAX.CRIT:"{#POOLNAME}"}%.
    2. The second condition - the pool free space is less than {$ZPOOL.FREE.MIN.CRIT:"{#POOLNAME}"}
    by default free space is set to 5G...
    So if you still have more thatn 5G of gree space there... full condition is not matched.. only half..

    Comment

    • beriapl
      Junior Member
      • Jun 2020
      • 7

      #3
      Ok, I've got like 200GB free space left, but is there any way to remove that condition and base only on %?

      ZFS do not work well if it is more than 80%

      That's actual alert on TrueNAS: Space usage for pool "backup" is 96%. Optimal pool performance requires used space remain below 80%.

      Comment

      • cyber
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Dec 2006
        • 4811

        #4
        Remove part of the trigger condition ...

        Comment

        Working...