Paused sensor writes 0% coverage in historical data
Modified on 2025-06-10 22:48:23 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Important: We no longer maintain this article. The information might be out of date.
I want to create a availability report of our servers with a script out of the historical data.
Sometimes we have to set the state of a sensor to paused.
The problem is that the sensor writes 0% coverage in the historical data while he is paused. Is there any way to skip or remove these wrong entries? Is there a way to correct this wrongdoing in the settings?
Best regards.
Article Comments
Hi,
currently it is not possible to remove the 0% Coverage from the tables. The only way would do some post-export processing and removing the data from the exported data.
Best regards
Oct, 2015 - Permalink
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Hi,
currently it is not possible to remove the 0% Coverage from the tables. The only way would do some post-export processing and removing the data from the exported data.
Best regards
Oct, 2015 - Permalink