Ad Widget

Collapse

Discovery interval not "respected"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • OliWasTaken
    Junior Member
    • Nov 2021
    • 2

    #1

    Discovery interval not "respected"

    Hi All,

    I have a Discovery Rule that should run every 15 minutes, however this seems to not be "respected", the last time it ran was 23 minutes ago (and still waiting as of right now), and the time before that was 27 minutes.

    Is the interval set on the rule more of a "do not run again within X duration, but can be ran whenever after that" or is there a configuration setting is missed?

    Thanks for reading!
  • niveastn
    Member
    • Oct 2021
    • 82

    #2
    Hi Oli!

    What is your discovery configuration and what is your zabbix version?
    The discovery interval is the period it is going to collect the data for discovery, not when the data is going to return (for instance, if you have an odbc discovery, the discovery can run each 15min, but if the query in the discovery run takes 20 minutes to run + zabbix takes 10 minutes to process your data (This is only an example. If it takes this long, something is seriously worng with your server/database), your discovery is going to take 30 minutes.
    Well, hope you could understand and let us know how is your discovery so we can help you better (:

    Comment

    • OliWasTaken
      Junior Member
      • Nov 2021
      • 2

      #3
      Hi!

      I am on Zabbix 5.0, on CentOS 7 with a MySQL database.

      My Discovery configuration is simply scanning 10.0.1.1-254 for zabbix-agents and checking for "system.uname", every 15minutes. If I'm understanding you correctly, it finishes the discovery run, then sends the data to the discovery action to be processed, and not "find one > action one > find one > action one" etc?

      Let me bump the loglevel up and check how long the discovery run is actually taking itself. I don't think a simple scan of a single port in a /24 would take ~15 minutes though.

      Cheers!

      Comment

      • ceinmart
        Junior Member
        • Nov 2012
        • 28

        #4
        Hi,
        I'm using zabbix 6.2.7 and get into the same problem .
        My discover rule , to check few ports is set to ran in 6h hours.
        However I'm noticed they aren't running.

        Running this SQL over my zabbix database I can see the last time they ran was 4 days ago...

        select *,FROM_UNIXTIME(lastup) from dservices d
        where d.ip = '172.215.1.1'​

        any tips?

        Comment

        • GTs
          Junior Member
          • Mar 2023
          • 2

          #5
          hello, it is not related this problem, but could you told me, I need it only send out message if ICMP ping fail equal to 5min or more. how can i make it? i am using this triger ​but not working, alert comes out in 30 second

          Comment

          Working...