greatcare / pm2-zabbix

A Node.js PM2 monitoring tool for Zabbix.
MIT License
87 stars 60 forks source link

Graph-Discrepency-LatestData vs Graph prototype #30

Closed ang3lwitch closed 5 years ago

ang3lwitch commented 6 years ago

So, I have used pm2-zabbix for about 1 year, works great. Thanks for that.

It came to my attention from a developer in that the following visuals are troublesome.

If, for instance a particular application, "pm2-api_app" climbs in memory usage pm2-zabbix does do its job, sends an alert and from "Monitoring->Latest-Data->Host-Pm2-app it shows proper spikes/triggers in graph.

If I were to select same host and go right to graphs, bypassing "Latest Data" The graph is not to the same scale and does not show the correct memory usage, meaning much lower than that of "Latest Data"

I understand that graph prototype may not have the trigger lines in it, that is fine. I just would like to know why the discrepancy happens from the graph prototype vs latest data graph for the same application's memory check.

Thanks

dcdamien commented 5 years ago

Hi @ang3lwitch, thank you for reporting this issue. Unfortunately I'm not able to reproduce problem you've described.

This is how it looks on our instance on example item, I don't see any difference:

graphs:

image

latest data:

image

dcdamien commented 5 years ago

I'm going to close the issue. Feel free to reopen if required.