Copyright © TIBCO Software Inc. All Rights Reserved |
The MM server can monitor key performance indicators provided in the metric charts and tables, and generate notifications (alerts) when a specified condition is met.See Working with Panels and Panes for some examples of charts and tables.Alert conditions are met by comparing a specified metric value with a reference value. The reference value can be a constant, or it can be another value in the same pane. As an example of a constant reference, you can configure an alert to trigger when the number of deadlocked threads exceeds a certain number. As an example of a reference that is another value in a pane, you could configure an alert to trigger when Used memory exceeds 95% of Max memory.Each alert has an alert level (critical, warning, and normal), and a configurable message. Messages use the Java Message Format syntax. You can, as desired, set up three alerts of different severity for the same metric, using different threshold values.Alerts are viewable in the System Alerts pane of the Cluster Overview. See Cluster Overview for an example.The presence of alerts can also be used to define the health level value for any monitored entity. See Configuring Health Metric Rules.
Ensure that condition settings in different alerts do not overlap with each other, so that it is clear which alert to use in all cases.See Alert Configuration Reference for more details on the settings referenced in this procedure.
As with any procedure that changes files, ensure the emonitor project is backed up before you edit its CDD file.
1.
2. Open the MM.cdd in the Cluster Deployment Descriptor editor and select the Agent Classes tab
3. Select mm-class (Monitoring & Management) > Alert Configurations.
4. Click Add or select an existing alert configuration.
6.
7. If you have finished configuration, start the emonitor project using the modified CDD file. This starts the MM server. See Starting MM Server and Logging On to the Console.
Copyright © TIBCO Software Inc. All Rights Reserved |