Ad Widget

Collapse

high delay problems shows in dashobard

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • propusgemini@gmail.com
    Senior Member
    • Mar 2018
    • 108
    #1

    high delay problems shows in dashobard

    Hi,
    i have a problem with the dashboard.



    non-pinging hosts are not shown in the dashobard immediatly but after a very lot time from the trigger's event.

    ICMPING losts at 19:55Click image for larger version Name: effective ping.JPG Views: 0 Size: 58.9 KB ID: 425013


    On dashboard 2 hours after....

    Click image for larger version Name: on dashboard.JPG Views: 0 Size: 17.0 KB ID: 425014




    TRIGGER:

    Click image for larger version Name: trigger.JPG Views: 0 Size: 47.5 KB ID: 425015


    Dashboard setting:

    Click image for larger version Name: dashobard setting.JPG Views: 0 Size: 56.2 KB ID: 425016

    System and my pollingstarters in zabbix config is set to 5

    Click image for larger version Name: Systems Pollersping 5.JPG Views: 0 Size: 28.5 KB ID: 425017


    any ideas?

    Thank you very much
    Fab

    Tags: None
    • propusgemini@gmail.com
      Senior Member
      • Mar 2018
      • 108
      #2
      Originally posted by cyber
      It is normal, if you calculate based on last 60th value.. I suppose if you ping once in 2 minutes, then this 60th value is 2h ago..
      last (<sec|#num>,<time_shift>)
      The most recent value. sec (ignored, equals #1) or #num (optional) - the Nth most recent value
      time_shift (optional) - evaluation point is moved the number of seconds back in time      		 Supported value types: float, int, str, text, log

      Take note that #num works differently here than with many other functions.
      For example:
      last() is always equal to last(#1)
      last(#3) - third most recent value (not three latest values)

      Zabbix does not guarantee exact order of values if more than two values exist within one second in history.

      The #num parameter is supported since Zabbix 1.6.2.
      The time_shift parameter is supported since Zabbix 1.8.2.
      Nothing to say... only excuse me i am a newbie

        Comment

        • cyber
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2006
          • 4807
          #3
          It is normal, if you calculate based on last 60th value.. I suppose if you ping once in 2 minutes, then this 60th value is 2h ago..
          last (,)
          The most recent value. sec (ignored, equals #1) or #num (optional) - the Nth most recent value
          time_shift (optional) - evaluation point is moved the number of seconds back in time          		 Supported value types: float, int, str, text, log
          Take note that #num works differently here than with many other functions.
          For example:
          last() is always equal to last(#1)
          last(#3) - third most recent value (not three latest values)
          Zabbix does not guarantee exact order of values if more than two values exist within one second in history.
          The #num parameter is supported since Zabbix 1.6.2.
          The time_shift parameter is supported since Zabbix 1.8.2.

            Comment

            Previous template Next
            Working...