Ad Widget

Collapse

Nodata trigger going off on JVM uptime

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • mdobrinin
    Junior Member
    • Oct 2012
    • 7
    #1

    Nodata trigger going off on JVM uptime

    Hello,

    I have a JVM uptime JMX check stored as DELTA. This is monitored over a proxy every 30 seconds. The proxy is an active proxy and I made sure in the log that it is sending every 30 seconds.


    Code:
    28446:20121023:132855.568
In send_data_to_server ...
28446:20121023:132925.833
In send_data_to_server ...


    The trigger goes off on the item when it is set to DELTA, but not when the trigger is referencing an AS-IS version. The server is receiving data:

    Code:
    2012.Oct.23 15:44:39	30077
2012.Oct.23 15:44:09	30150
2012.Oct.23 15:43:39	30034
2012.Oct.23 15:43:09	30078
2012.Oct.23 15:42:39	29926
2012.Oct.23 15:42:10	29225
2012.Oct.23 15:41:40	30082
2012.Oct.23 15:41:10	30082
2012.Oct.23 15:40:40	30089
2012.Oct.23 15:40:10	30190
2012.Oct.23 15:39:40	30018
    However, the trigger is still going off:
    Code:
    23 Oct 2012 15:44:09	ProxyJMXTest is not reachable	OK	High	51s	No
23 Oct 2012 15:43:00	ProxyJMXTest is not reachable	PROBLEM	High	1m 9s	No	
23 Oct 2012 15:42:10	ProxyJMXTest is not reachable	OK	High	50s	No	
23 Oct 2012 15:42:31	ProxyJMXTest is not reachable	PROBLEM	High	21s	No	
23 Oct 2012 15:41:40	ProxyJMXTest is not reachable	OK	High	51s	No	
23 Oct 2012 15:42:00	ProxyJMXTest is not reachable	PROBLEM	High	20s	No	
23 Oct 2012 15:41:10	ProxyJMXTest is not reachable	OK	High	50s	No	
23 Oct 2012 15:41:30	ProxyJMXTest is not reachable	PROBLEM	High	20s	No	
23 Oct 2012 15:40:40	ProxyJMXTest is not reachable	OK	High	50s	No	
23 Oct 2012 15:41:00	ProxyJMXTest is not reachable	PROBLEM	High	20s	No	
23 Oct 2012 15:40:10	ProxyJMXTest is not reachable	OK	High	50s	No	
23 Oct 2012 15:40:30	ProxyJMXTest is not reachable	PROBLEM	High	20s	No	
23 Oct 2012 15:39:40	ProxyJMXTest is not reachable	OK	High	50s	No	
23 Oct 2012 15:40:00	ProxyJMXTest is not reachable	PROBLEM	High	20s	No	
23 Oct 2012 15:39:09	ProxyJMXTest is not reachable	OK	High	51s	No	
23 Oct 2012 15:39:30	ProxyJMXTest is not reachable	PROBLEM	High	21s	No
    The trigger:
    Code:
    {HOSTNAME} is not reachable - {JMX Generic:jmx["java.lang:type=Runtime","Uptime"].nodata(45)}=1
    The item:
    name=JVM Uptime Delta
    key=jmx["java.lang:type=Runtime","Uptime"]
    update interval=30
    store value=Delta (simple change)
    Last edited by mdobrinin; 23-10-2012, 23:43.
    Tags: None
    • BDiE8VNy
      Senior Member
      • Apr 2010
      • 680
      #2
      I have had a similar problem. Increasing the value of the nodata() trigger function for the corresponding item solved the issue in my case.

        Comment

        Previous template Next
        Working...