7 SLOs to get started with using Dynatrace

As an industry, we are gaining more experience in defining the right SLOs (Service Level Objectives) for your critical services.
In this session, we have Brian Chandler walking us through the Top 7 SLOs that he has set up for organizations over the past few months. Watch this session and learn how to set up SLOs for Service and Service Request Availability, Service Request Performance, Synthetic and Synthetic Test Step Availability, Real User Monitoring, and Infrastructure Capacity using #Dynatrace.
Chapter List:
Intro - 00:00
What you will learn today - 01:30
Dynatrace SLO UI Updates - 02:40
Basic Service Availability - 06:35
Single Request Availability - 13:54
Service Request Response Time SLO - 24:26
Synthetic Test SLO - 34:35
Synthetic Test Step SLO - 39:49
Real User Monitoring SLO - 44:45
Infrastructure Capacity SLO - 47:38
Dashboarding SLOs - 53:30

[@AlienAndrew51]

Really wish it was easier to work with like GCP monitoring SLO engine. It should be as easy as saying less than or greater than a certain percentage and automatically doing the percentage without custom metrics. Or at least more default SLO's out of the box for the big three cloud services.

[@patcadelina]

Hi @grabnerandi, in the SLO Wizard, the metric expression for Service-level availability uses `splitBy`. In the Single Request Availablity demo `sum` was used instead. What is the difference and when should you use one over the other?

[@FreFreTube]

Looks great, but I'm missing the possibility to {}use wildcards on some parts of the URI that you want to "group" as one endpoint. In Europe endpoints quite often start with the following /{language}/GetInforFromOrder/{UUID}. If I want to create an SLO for /GetInfoFromOrder I need to create one rule for each language of that endpoint?

[@grabnerandi]

Hi. There are multiple options you have. In Dynatrace you can specify request name patterns where you can exactly specify that a part of the URL should be treated as a category or whatever you call it. In that case you then get all incoming requests automatically grouped and therefore your metrics are also as you like it.

[@kucera_jan]

Hello. Why are we using the "count" unit again? Some metrics only have auto+avg

[@grabnerandi]

Hi. The "Count" aggregate should be available for ALL metrics as it really gives you the number of metric points for that metric in the selected timeframe. I