Hi there,
the timestamp of the latest data in probably all overviews seems to be taken from the latest data stored in the database.
Depending on the overview (latest data) this is ok.
But when processing data/items with item value preprocessing e.g. Throttling Discard unchanged with heartbeat this leads to misinformation about the real latest check timestamp.
In Monitoring->Latest Data -> Last Check it should display the timestamp of the last check and not from the database, as this may lead to questioning the update intervall, if the item update intervall is set to a shorter
value than the heartbeat.
I know, that this is probabyl not easy to change.
the timestamp of the latest data in probably all overviews seems to be taken from the latest data stored in the database.
Depending on the overview (latest data) this is ok.
But when processing data/items with item value preprocessing e.g. Throttling Discard unchanged with heartbeat this leads to misinformation about the real latest check timestamp.
In Monitoring->Latest Data -> Last Check it should display the timestamp of the last check and not from the database, as this may lead to questioning the update intervall, if the item update intervall is set to a shorter
value than the heartbeat.
I know, that this is probabyl not easy to change.