Advanced SLA Configuration

Note: This topic refers mainly to "Jobs," but what it describes also applies to Workflows.

The SLA_CONFIGURATION configuration table lets you edit the following options.

Name	Description	Default Value	Values
`autoConfirmation`	If this entry is set to `false` (or not present), and the Auto Confirm checkbox for a generated Alert is not checked, the Alert will require manual intervention. If this is set to `true`, generated Alerts are automatically confirmed.	`false`	`true`, `false`
`redirectAlertAddress`	If you enter an email address here, it will override all other target email addresses in the SLA Extension. This can be useful in development and test environments.
`historyRetention`	The number of days the SLA Alert history is kept.	`7`
`showRuleAfterDeadLineTime`	The number of hours the SLA Extension should wait after a monitored Job finishes or misses, before it starts monitoring the next execution of the Job.	`12`
`disablePredictedAlert`	If this is set to `true`, Alerts of type `PredictedAlert` are suppressed.	`false`	`true`, `false`
`disableHalfMissedAlert`	If this is set to `true`, Alerts of type `HalfMissedAlert` are suppressed.	`false`	`true`, `false`
`disableMissedAlert`	If this is set to `true`, Alerts of type `MissedAlert` are suppressed.	`false`	`true`, `false`
`disableFinishedAlert`	If this is set to `true`, Alerts of type `Finished` are suppressed.	`false`	`true`, `false`

SLA Job Definitions

The SLA Extension uses the following Job Definitions.

SLA_Monitor keeps track of Jobs, makes calculations, and sends out Alerts. You must submit it once when you start using the SLA Extension, but after that it automatically restarts once a day.
SLA_Maintenance truncates the SLA history and ensures consistency. Do not submit this Job Definition manually.

To generate a dynamic trace, submit the System_DynamicTrace Job Definition with the Trace String field set to custom.sla_analysis=debug.