Advanced Configuration
The SLA_CONFIGURATION configuration table supports the following options:
| Parameter | Description | Default Value | Values |
|---|---|---|---|
autoConfirmation | Automatically confirm generated alerts. | false | true - generated alerts are automatically confirmedfalse - generated alerts require manual intervention |
redirectAlertAddress | Email address to overwrite all target email addresses (for development and test environments, for example). | ||
historyRetention | Time SLA alert history is kept, in days. | 7 | |
showRuleAfterDeadLineTime | After how many hours should the monitor roll over the rule to the next occurrence. | 12 | |
statusBarLinkOverwrite | Allow an alternative hyperlink from the bar. | ||
disablePredictedAlert | Suppress the PredictedAlert to be sent out. | false | true,false |
disableHalfMissedAlert | Suppress the HalfMissedAlert to be sent out. | false | true,false |
disableMissedAlert | Suppress the MissedAlert to be sent out. | false | true,false |
showOriginalPredictionColumn | Display an additional column containing the initial predicted end time. | false | true,false |
showRuleTagsColumn | Display an additional column containing the rule tags of an SLA rule. | false | true,false |
SLA Rule Definition Monitor Processes
SLA_Monitor- Started automatically at first use
- Keeps track of potential processes and makes calculations
- Sends out alerts
- Restarts once a day
SLA_Maintenance- Truncates history
- Ensures consistency
Troubleshooting
Component writes logging to <install_dir>/j2ee/cluster/server1/log/extensionpoints/GLOBAL.Sla.log
Dynamic trace is available with custom.sla_analysis=debug, you submit System_DynamicTrace with trace string custom.sla_analysis=debug.