used to compare the number of Status messages across Status nodes to understand the potential discrepancies and odd behaviour of messages being inserted in the past in a given pubsub topic.
The following tables are available in https://superset.bi.status.im/superset/sqllab/ `telemetry` database:
### `missingMessages`
This table contains the list of missing messages, and in which storenode the messages was identified to be missing. The `msgStatus` column indicates the possible scenarios in which a message can be considered missing:
-`does_not_exist`. The message is not stored in the storenode's db
-`unknown`. It was not possible to retrieve information about this message. The store node was likely not available during the time the query to verify the message status was done.
### `storeNodeUnavailable`
This table records timestamps on which a specific storenode was not available. This information should be used along with data from https://kibana.infra.status.im/ and https://grafana.infra.status.im/ to determine the reason why the storenode was not available.