One of the main functions available within IBM Tivoli Storage Resource Manager for Databases is the ability to alert you to storage-related events that occur within your database environment. Once you have defined the events or conditions for which you want to be alerted, you can let IBM Tivoli Storage Resource Manager monitor your RDBMS storage resources so that you don't have to.
IBM Tivoli Storage Resource Manager provides you with a number options for defining who gets notified when an alert occurs and how that notification is delivered. The choice of which alert mechanism to use will most likely depend upon the severity of the event that triggers the alert.
The available alert mechanisms are:
Alert Mechanism |
Allows you to: |
SNMP Trap |
Interface with the frameworks that might already be in use within your environment. |
TEC Event |
Check this box to send the alert to the Tivoli Event Console (TEC). The TEC administrator can write correlation and automation rules to analyze IBM Tivoli Storage Resource Manager events and perform responses such as send further notification, create or update trouble tickets, run programs, and so forth. |
Upon Log In to Tivoli SRM GUI |
Receive a list of alerts that are targeted for you every time you log in to IBM Tivoli Storage Resource Manager. |
Windows or Unix Event log |
Write out alert messages to the OS log. If you already have an administrator monitoring OS logs, this is an easy way to have all of your priority messages centralized for quick notification and viewing. |
Run Scripts |
Define an action that should be performed automatically when a storage-related condition/event occurs within an RDBMS storage environment. |
EMAIL or Pager |
Receive and email or page when a specific type of alert is triggered. IBM Tivoli Storage Resource Manager can send this type of notification to you, the storage administrator, and/or the violating user. This is very useful for high priority events such as running out of free space or imminent disk failure. |
You can select the following sub nodes within the Alerting node to create an alert: