Adjusting the timestamp of data from Zabbix agents

[ktt]

I'm using Zabbix to monitor certain test data, for which I'm using Zabbix agent's user parameters. Those work generally fine.

However, there is one remote test site, for which it is not possible to have real-time monitoring. The remote site can't be connected from Internet and itself, it can send data to my Zabbix host only once per hour.

I would like to feed this data to Zabbix then once per hour, so that I could see from graphs, how test data has behaved in past - of course there is one hour delay in updating graphs.

Is there any way to feed data to Zabbix SQL tables afterwards, and to adjust data timestamps to reflect the real situation? If I feed the data manually using my own PHP scripts, is there risk that Zabbix "normal" data gathering would get confused?

[Semiadmin]

Hi, ktt.
Use zabbix_sender with options -i and -T

https://www.zabbix.com/documentation/3.2/manpages/zabbix_sender

[kloczek]

I would like to feed this data to Zabbix then once per hour, so that I could see from graphs, how test data has behaved in past - of course there is one hour delay in updating graphs.

Add proxy in the same segment of the network and agent will be able to push all data to the proxy. When connection from/to the server will be possible using passive/active proxy all data will be pushed to the server. With such approach none of the time stamp data needs to be adjusted.

[ktt]

Add proxy in the same segment of the network and agent will be able to push all data to the proxy. When connection from/to the server will be possible using passive/active proxy all data will be pushed to the server. With such approach none of the time stamp data needs to be adjusted.

Thank you! I did not realize, that proxy can store the data during connection breaks. I already tested the proxy and it fulfills this need neatly.

[kloczek]

Thank you! I did not realize, that proxy can store the data during connection breaks. I already tested the proxy and it fulfills this need neatly.

Proxy by default keeps last 1 hour of data and its cyclic buffer can be extended to 24h.
It is normal practice extending this buffer for example before major upgrade of the server.
Proxy buffer is as well is fundamental part of the zabbix stack HA.
For example even if man srv DB will be trashed and will be restored from backup not older that proxies cyclic buffer window after restoring srv<>prx connections all gaps in history* data will be restored from data buffered on the proxies.
In other words proxy with own buffer of all monitoring data is essential part of the stack making it fault tolerant.