Return
-
Title
Spotlight Data Collection and Alarms -
Description
An alarm is only raised when information necessary to trigger that alarm becomes available. How does this work?
-
Resolution
There are a number of factors that determine when an alarm should be raised, when to display information for which the alarm was raised and when the information should be stored in the Playback database.
Spotlight's data collection schedules determine how often the Diagnostic Server checks and collects data from servers being monitored for a particular metric. This can be done within the Backgroud schedules wizard. Data can be collected at regular intervals of a minimum of one minute. It therefore means that a metric for example, 'Blocking' must therefore be happening for at least 1 minute before the statistics can be collected and stored within the Playback database.Here is an example of how it works. For the first alarm, the data is only displayed on the console and not stored in the Playback database. If say an alarm is raised and displayed for blocking after 9 seconds of it occuring and blocking persist for another one minute, the schedule will be triggered at the 69th second when another alarm will be fired possibly with a different colour. It is only then that the statistics will be collectored and stored in the Playback database. It is after this happens that you can view the staticstics in the history browser or during playback. Otherwise, if blocking stops after say about 50 secs, you won't be able to see the information during replay. It will only be highlighted on the console.