Ad Widget

Collapse

Delay on the just added external check Item

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • d2718nis
    Junior Member
    • Oct 2018
    • 5

    #1

    Delay on the just added external check Item

    Hey everyone.


    I tried to find the answer on my question here and in other places, but it doesn't seem that someone else is interested in this. Hope it's not my searching skills being poor (:

    I've noticed that the external check Item is not checked right after you add or enable it. Moreover it seems to me it bases on the update interval somehow. For example I have an external check at the Template with an update interval of 10 minutes. Then I add a Host based on this Template, the first value from the check will appear no sooner than 8 minutes after. It's not the 10 minutes though, so it is a bit confusing.

    On the other hand, I have a simple check with update interval of 30 seconds. It is checked in about a minute after I add a Host. Maybe it is related to the check type? I tried to search for a related setting both at the frontend (Administration -> General -> Other -> "Refresh unsupported items" option doesn't seem to have any impact on this) and the zabbix_server.conf, but was unlucky to find one. I also know that there should be an option to force check the Item since version 4.0 as stated at this feature request https://support.zabbix.com/browse/ZBXNEXT-4426 so that might be an option for me.


    Am I missing something? Your help would be appreciated, thanks a lot!
    Last edited by d2718nis; 20-10-2018, 11:22.
  • samsaint
    Junior Member
    • Oct 2018
    • 1

    #2
    Okay, I tried looking a lot about this issue of yours. Even I'm caught in a rut. I'll be glad if anyone can fix this issue of ours. Thanks.

    Regards,
    TechyHost
    Last edited by samsaint; 21-10-2018, 14:02.

    Comment

    • d2718nis
      Junior Member
      • Oct 2018
      • 5

      #3
      FYI I found out something interesting at the Check now documentation page

      The check must be present in configuration cache in order to get executed; for more information see CacheUpdateFrequency. Before executing the check, the configuration cache is not updated, thus very recent changes to item/discovery rule configuration will not be picked up. Therefore, it is also not possible to check for a new value for an item/rule that has been created just now.
      Although it won't fix the original problem with 8+ minutes delay because the default value for this setting is 60 (seconds), it could still be useful for better understanding on how it works and also if you need some checks with smaller delays to be updated quickly.
      Last edited by d2718nis; 21-10-2018, 11:07.

      Comment

      Working...