Configure Keyed Alarms
Some alarms in Spotlight can be configured with keys that allow you to apply different thresholds to each key in an alarm. A key is a unique value that identifies a particular row in a collection. For example, database name is the key for the Databases alarms.
The following alarms can be configured with keys:
- Backup - Days Since Last Full Backup
- Backup - Hours Since Last Differential Backup
- Backup - Minutes Since Last Log Backup
- Command - Long Running Command
- CPU - Individual CPU Usage
- Cubes - Days Since Last Processed
- Cubes - Unprocessed
- Custom Counters
- Databases - Data File Group Space Used
- Databases - Dynamic Data File Group Growths Remaining
- Databases - Dynamic Log File Growths Remaining
- Databases - Log File Space Used
- Databases - Log Flush Wait Time
- Databases - Unavailable
- Diagnostic Server - Alarm Action Failure
- Diagnostic Server - Alarm Evaluation Failure
- Diagnostic Server - Collection Execution Failure
- Diagnostic Server - Email Service
- Diagnostic Server - Spotlight Playback
- Disks - Percentage Used
- File - Exceeded Set Size
- Locks - Blocked Processes
- Log Shipping - Primary Backup Job
- Log Shipping - Secondary Job
- Log Shipping - Secondary Latency
- Mirroring - State
- Mirroring - Unrestored Log
- Mirroring - Unsent Log
- Monitored Server - Alarm Action Failure
- Monitored Server - Alarm Evaluation Failure
- Monitored Server - Collection Execution Failure
- Monitored Server - Secondary Connection Failure
- Network - Percentage Bandwidth
- Paging - Disk Activity
- Paging - File Collision
- Services - Service Not Running
- SQL - Long Running SQL
- SQL Agent - Jobs Failed
- SQL Agent - Long Running Jobs
Scenario
The standard backup schedule for your databases is weekly but you have one particular database that gets backed up monthly. You need to stop Spotlight from raising an alarm against this particular database. You configure a specific threshold for that database and set it to alarm when the database has not been backed up for 30 days. |
To add keys to alarms
-
Click Configure | Alarms.
- Select a connection to configure. To apply the configuration to all connections, select Default Settings.
-
Select an alarm.
Scenario: Select Databases - Days Since Last Backup.
- Select Override the default settings for the alarm.
- Click Add.
-
Select or type the Key value - the key you want to add the alarm to.
Scenario: Select the name of the database that gets backed up monthly.
- Adjust the thresholds for each severity using the colored bar or severity table. Note, if the alarm does not have thresholds then select a severity from the Severity list.
Scenario: In the Severity table, for the High severity, enter 30 in the Start column.
Tip: You can use keys to configure alarms to ignore certain values. See "Configure an Alarm to Ignore Certain Values" (page 1) for more information.
Related Topics
Configure Alarms (page 1)
Alarms Dialog (page 1)
Alarms Ribbon Group (page 1)