Hi,
we have Zabbix v6 in production environment.
I am looking at PostgreSQL database metric "pgsql.wal.write" from https://git.zabbix.com/projects/AP/r...Frelease%2F6.0
and from SQL it does the difference between current WAL file and 0/00000000. According to this calculation metric should always increase, because there are more and more bytes from beginning.
But from my system metric I see the following graph:
From graph it is obvious that metric does not increases all the time (like expected if metric is in bytes).
It looks like this metric is not measured in bytes, but something like "bytes per some time", it looks to me this metric is "bytes per second", so the graph in my case is showing "MB/s" (mega bytes per second and not only mega bytes).
Is this defect in measurement metric? Currently it reports the metric is in "bytes", but it looks like it is "bytes per second".
we have Zabbix v6 in production environment.
I am looking at PostgreSQL database metric "pgsql.wal.write" from https://git.zabbix.com/projects/AP/r...Frelease%2F6.0
and from SQL it does the difference between current WAL file and 0/00000000. According to this calculation metric should always increase, because there are more and more bytes from beginning.
But from my system metric I see the following graph:
From graph it is obvious that metric does not increases all the time (like expected if metric is in bytes).
It looks like this metric is not measured in bytes, but something like "bytes per some time", it looks to me this metric is "bytes per second", so the graph in my case is showing "MB/s" (mega bytes per second and not only mega bytes).
Is this defect in measurement metric? Currently it reports the metric is in "bytes", but it looks like it is "bytes per second".
Comment