Ad Widget

Collapse

How to get notification for not supported items

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kaib
    Junior Member
    • May 2021
    • 3

    #1

    How to get notification for not supported items

    Hi everyone,

    I've created an item to monitor a webpage with:
    Code:
    web.page.regexp[xx.xx.xx.xx,index.html,80,"HTTP/1.1 200 OK",,1]
    to check whether "HTTP/1.1 200 OK" is found. Also implemented a corresponding trigger:
    Code:
    {host:web.page.regexp[xx.xx.xx.xx,index.html,80,"HTTP/1.1 200 OK",,1].last()}<>1
    The idea was to be able to tell whether the page is available or not, and to be notified when it's not. Turns out when it can't reach the page, because the host is not available, the item status turns to "Not supported". And I don't get any notification because the trigger won't take.
    I've enabled the Internal Action "Report not supported items", but I still don't get any notification. Any ideas why this is not working?

    Any other ideas to implement such a scenario are welcome as well!
    Last edited by kaib; 11-05-2021, 21:50.
  • eithor
    Member
    • May 2020
    • 50

    #2
    For the general issue of triggering on unsupported items I have made a template that I put on all hosts with a "Zabbix internal" item with key "zabbix[host,,items_unsupported]", checking every 1min. This will give a number of unsupported items on that host. I then have a trigger in the same template with the following logic:

    {Zabbix host item status:zabbix[host,,items_unsupported].last()}>0 and
    {Zabbix host item status:zabbix[host,,items_unsupported].count(10m,0,gt)}>7

    This will trigger if the last value is at least 1 unsupported item and the count of checks-with-unsupported-items is more than 7 last 10min on that host.

    Comment

    • kaib
      Junior Member
      • May 2021
      • 3

      #3
      Ok, that works great! Thank you for that! But how do you figure then out which the unsupported item is?

      Comment

      • eithor
        Member
        • May 2020
        • 50

        #4
        If you manually want a list of unsupported items on a host, you will find them on the Configurations->your host->items page where you change the "State" dropdown to not-supported and choose Apply. A little trick: if you then remove the host selected in the Hosts box and choose apply, you will see it for all your hosts.

        Comment

        • SergeiChechev
          Junior Member
          • May 2021
          • 8

          #5
          Could you help?
          At the moment, I get an alert on a trigger every time at the same time
          avg(/zabbix_server/zabbix[items_unsupported],10m)>100
          At the same time, I don’t observe any activity on hosts and in monitoring, the value of inaccessible is ~110
          I filter the request as you specify, I get all unsupported items, only in the amount of ~250
          When the trigger resolves and the value becomes ~90, I re-filter and get the same value of 250
          How else can I find unsupported items?
          And how can I check what zabbix[item_unsuppported] returns?, zabbix_get does not work, because this is an internal check

          Comment

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

            #6
            There are "internal actions" what you can use to report every time item or LLD rule turns to not supported state...

            Comment

            • SergeiChechev
              Junior Member
              • May 2021
              • 8

              #7
              Thanks for your reply
              But I can't determine which specific items become unsupported?, the filter doesn't help

              Comment

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

                #8
                You will get name of item or LLD rule with it... You can define the message by yourself and include all needed things, host, item name, key ... There should be some of those internal actions by default IIRC... Just in disabled state.

                Comment

                • dimir
                  Zabbix developer
                  • Apr 2011
                  • 1080

                  #9
                  Originally posted by SergeiChechev
                  Could you help?
                  At the moment, I get an alert on a trigger every time at the same time
                  avg(/zabbix_server/zabbix[items_unsupported],10m)>100
                  At the same time, I don’t observe any activity on hosts and in monitoring, the value of inaccessible is ~110
                  I filter the request as you specify, I get all unsupported items, only in the amount of ~250
                  When the trigger resolves and the value becomes ~90, I re-filter and get the same value of 250
                  How else can I find unsupported items?
                  And how can I check what zabbix[item_unsuppported] returns?, zabbix_get does not work, because this is an internal check
                  zabbix[items_nsupported] only counts enabled items. I guess bigger part of your unspported items are disabled

                  Comment

                  • dimir
                    Zabbix developer
                    • Apr 2011
                    • 1080

                    #10
                    Originally posted by SergeiChechev
                    Thanks for your reply
                    But I can't determine which specific items become unsupported?, the filter doesn't help
                    An internal action can let you know which item exactly became unsupported



                    How to set it up

                    Comment

                    Working...