Odd issue with very low icmppingsec's
I have a 60 item to monitor the icmppingsec. The bype is Numeric (float) and values are stored as is.
What I did was install zabbix-proxy 2.0.3 on a machine, then I installed zabbix-agent on it aswell.
This is the debug value that the proxy is getting from the agent:
{
"host":"xyz",
"key":"icmppingsec",
"clock":1353609614,
"ns":810372070,
"value":"0.000037"}],
This trigger is getting triggered though. Could it be because the value above is so low?
{xyz:icmppingsec.sum(300)}=0
The last data values on the graph are showing mostly 0, even though I can see the above data being sent to the server.
What I did was install zabbix-proxy 2.0.3 on a machine, then I installed zabbix-agent on it aswell.
This is the debug value that the proxy is getting from the agent:
{
"host":"xyz",
"key":"icmppingsec",
"clock":1353609614,
"ns":810372070,
"value":"0.000037"}],
This trigger is getting triggered though. Could it be because the value above is so low?
{xyz:icmppingsec.sum(300)}=0
The last data values on the graph are showing mostly 0, even though I can see the above data being sent to the server.