Problem with screens (diff between config and monitoring)

[ORi]

Hi all,

So for Zabbix has been an awesome experience for me. It has been really helpful in identifying issues before they occur. So I must start with a thank you toward the developers!

I do have a problem with the screens feature in zabbix 2.0. I made a graph which is monitoring the cpu load and memory usage of our Windows Server machines (zabbix agent). I made a calculated item for the memory usage "(total - free) / total * 100) to show it in percentage. Then I can fit CPU usage and Mem Usage on the same percentage graph. The graphs are working ok, but when I combine the graphs into a screen I have the following issue.

- The screen is looking OK in the configuration section.

img_config_Screen.jpg:

- The screen is not looking OK in the monitoring section.

img_monitoring_Screen.jpg:

As to why there is a different I have no idea. It's regarding exactly the same data and configuration! And the graphs individually also work fine.

Do you guys have any idea? Could it be linked to the calculated item? Or could it be a bug?

[ORi]

Nobody else has this problem?

[eskytthe]

Did a test on the 2.0 Zabbix Appliance, with a very simple calc item. No problem with graphs.

Maybe a problem with your calc item?. Try some test with it - more simple func or make a new one or ....

Br
Erik

[ORi]

With graphs it's working fine. As soon as I make a screen of the graph it's not displaying. Instead of showing the value it's showing '0'.

I'm pretty sure this is a bug. Because how else can be explained that in 'design mode' the screen shows correctly. But when I look at the screen from the monitoring page, it shows the calculated item as '0'. Must be a bug in the way calculated items are shown on a screen (not graph, there it works)

[richlv]

check the time period scrollbar at the top of the page. you are looking at data for a different period.

[ORi]

The screenshots have different timespans, but I checked always over the last hour/day. So it's not that.

However, the issue seems to have resolved by itself. I didn't do anything other than rebooting the server during the weekend. That's the only assumption I can make.

In any case, thanks for your feedback and interest.

Another huge zabbix fan here ;-)