Ad Widget

Collapse

Discovery interval stuck on default value

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MattNorman
    Junior Member
    • Oct 2023
    • 1

    #1

    Discovery interval stuck on default value

    I am currently testing Zabbix as a possible replacement solution for my company.

    I have added one of our F5 load balancers and the default discovery interval for pools is 1 hour. I changed this to 5 minutes however it is still only running every 1 hour.

    Do I have to delete the host and add it again for it to use the amended value from the template?

    Is it also possible to set different trigger thresholds at a host level? Once I add my vCenter appliance, I will need to have different trigger values for datastores depending on their total capacity.
  • petervs
    Junior Member
    • Jun 2024
    • 3

    #2
    Hi,

    I have the same issue with the F5 Big-IP SNMP v5 template.
    All the "Latest check" values are 1h interval, while the "Item prototypes" are configured at 5m..

    When i manually create the Item, the 5 min interval is working fine.

    Comment

    • Markku
      Senior Member
      Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
      • Sep 2018
      • 1781

      #3
      When you open the item prototype configuration, you will see that there is a preprocessing step that discards unchanged values, with heartbeat interval of 1 hour. So, even if Zabbix retrieves the value every 5 minutes, it only stores the value once an hour if the value is not changing.

      Markku

      Comment

      • petervs
        Junior Member
        • Jun 2024
        • 3

        #4
        Originally posted by Markku
        When you open the item prototype configuration, you will see that there is a preprocessing step that discards unchanged values, with heartbeat interval of 1 hour. So, even if Zabbix retrieves the value every 5 minutes, it only stores the value once an hour if the value is not changing.

        Markku
        Hello Markku,

        That was indeed the issue/solution.
        Now it's working the way I want it.

        Thank you!

        Comment

        Working...