Spectrum Report Manager (SRM) reporting 100% up and down in Availability reports even though it is known these models had down and up time.
Possible root cause is missing events from the Archive Manager (DDM) database.
All events are first logged to the SpectroSERVER (SS) database. Then they are passed to the Archive Manager to be logged in the DDM database. After they are successfully passed to the DDM database, they are removed from the SS database.
The events that are logged in the DDM database are then passed to the SRM system to be logged in the reporting database. Jasper uses these events in the reporting database for the availability and other reports.
If the ArchMgr is down or having issues logging events from the SS, you will see the "Locally Stored Events" field in the SpectroSERVER Control -> Event Information subview in the Information tab of the VNM model increase. When the ArchMgr comes back up, these events are passed to the ArchMgr to be stored in the DDM database.
By default, Spectrum will only keep 20,000 "Locally Stored Events" in the SS database. This is the "Max Log Size" field seen in the Event Information subview. If there are more than 20,000 events, the oldest events are purged from the SS database and the "Events Purged" field is incremented. These purged event do not get logged into the DDM database therefore they do not get logged into the reporting database.
Release : Any
Component : Spectrum Reporting
Check the "Locally Stored Events" and "Max Log Size" fields in the Event Information subview for values greater than zero. This is an indication of issues logging events into the DDM database.
Make sure the Archive Manager is up and running and there are no errors in the $SPECROOT/SS/DDM/ARCHMGR.OUT file.
Contact Spectrum Support if assistance is needed.