Fundamentals for deployment & configuration : fundamentals & monaco example
✅ ITSM integration & SLO Quality of Service : itsm-integration-with-slo & monaco-template
Dashboarding Dynatrace Simply Smarter : slo-simply-smarter with monaco template
Goal : be alerting immediatly on application and/or frontend services if there is a risk to miss the SLO.
- Create SLO for main application or main frontend services (but not for all)
- Add SLO alert on fast burn rate
- Create Alerting Profile on SLO alert
- Add ITSM notification without delay
Monaco template for slo and itsm intgeration here
Goal : be alerting if the problem is persistant and not fix after X minutes.
- Create an alerting profile with X min delay (for example > 60 min)
- Add ITSM Integration based on this alerting profile.
-
Configure Maintenance Windows to disable the notification of the ITSM integration.
For example, if you know that your application will not be used during Bank Hollidays, create a maintenance window to avoid the alertApplication Low TrafficYou can do that easily with monaco template (example for French banck hollidays) -
Don't modify the thresholds (expecpt may be Disk threshold and specific needs in particular cases), but leave Davis to deal with his baseline
-
Create the SLO to take advantage of the real time Burn Rate alerts.
- SLO for real time alert => Specific SLO for main application or frontend service (as described above) click here
- SLO filtered by MZ => You can use the Simply Smarter with the SLO smarters which have been configured globaly by tenant and can be filtered by MZ : click here
Problems seen by Dynatrace for an application :
Notification send to the ITSM for this application (Alert based on SLO burn rate)
- Youtube : Observability clinic : SLO
- Youtube : Boost your Service Desk integration with SLO
- Tools : sla-uptime