Configure and monitor service-level objectives with Dynatrace

The list of defined service-level objectives (SLOs) within a Dynatrace monitoring environment shows important information such as current status and error budget, as well as details about error budget, target, warning, the number of open problems out of the total number of problems for the SLO entity selector, and the timeframe during which the SLO is to be evaluated.

By default, each SLO is evaluated according to its defined timeframe, but for what-if analyses with different timeframes and for a retrospective view, you can temporarily switch to the global timeframe. timeframe

Configure a service-level objective

To configure a new service-level objective, you can either use the SLO wizard to select from a set of Dynatrace preconfigured templates for common use cases, or create your own SLO definitions.

Use the SLO wizard to select and configure templates

Dynatrace offers preconfigured templates out of the box for some of the primary monitoring domains.

  • Service-level availability SLO, where service-level availability is measured by dividing the number of successful service calls by the total number of service calls
  • User experience SLO, which is based on the Apdex measurement, representing the percentage of users who are SATISFIED out of the total number of users who are using a web or mobile application
  • Mobile crash-free users SLO, which measures the percentage of crash-free users within your mobile applications
  • Synthetic availability SLO, which represents the percentage of successful synthetic tests related to the total number of executed tests

For more information on the use cases, see Configuration examples of service-level objective definitions.

To use a preconfigured template, go to the SLOs page, select Add new SLO, and step through the SLO wizard as described below.

  1. Select your indicators.

Select the desired SLO (Service-level availability, User experience, Mobile crash-free users, or Synthetic availability) and (optionally) configure the SLI metrics you want to add to your SLO.

  1. Define a filter.

Select a fine-grained filter for the specific service you are interested in.

The filter definition is consistent with the Dynatrace REST API query syntax. You can use filters on management zone ID/name, tags, entity name/ID/type, health state, or a combination of these.
For more information on the filters, see Entity Selector.

Note: After entering your filter, you must validate it by selecting Preview before you can continue.

  • If the filter value is correct, you get a list of matching entities for the respective filter after selecting Preview.
  • If the filter value is incorrect, you won't be able to continue the setup after selecting Preview.

The definition of a service-level objective represents a top-level element within the main menu of each monitoring environment.

  1. Set your target.

Set the target percentage (Error) and the warning percentage (Warning), as well as the timeframe. To specify a timeframe, use the timeframe selector syntax. Select the question mark in the Dynatrace timeframe selector for a syntax guide.

Note: The warning percentage has to be between 100% and your SLO target percentage in order to be effective. For example, if your SLO target percentage is 99.00%, you need to set your warning percentage between 99.00% and 100% to get an early warning (as indicated by a yellow state).

  1. Review your changes.

After you complete the previous steps, the wizard displays a summary of your SLO (name, metrics, target, warning, filter, and timeframe) and a preview showing the status and the error budget of the SLO based on your selections.

  1. Select Save to save your configuration.

Create your own service-level objective definition

To set up your own service-level objective

  1. In the Dynatrace menu, go to Settings > Cloud Automation > Definition.
  2. Select Add new SLO.
  3. Enter the SLO details.

Note: If you enter a filter parameter, you can validate it by selecting Preview:

  • If the filter value is correct, you get a list of matching entities for the filter.
  • If the filter value is incorrect, you won't be able to save your configuration.
  1. After entering the SLO details, you can select Evaluate SLO to get a preview of the SLO status and error budget based on your selections.
  2. Select Save changes to save your configuration.

After you complete the setup, the newly created service-level objective appears on the SLOs page.

You can always edit your SLO by selecting Actions > Edit SLO on the SLOs page. actions

To see a normalized error budget (ranging from 0% to 100%) for all SLOs, go to Settings > Cloud Automation > Setup and enable Normalize error budget.

Pin SLOs to your dashboard

After you define your objectives, you can add the SLOs to your dashboard to visualize their current status along with the remaining error budgets.

There are two ways to add SLOs to your dashboard.

By default, the SLO tile evaluates the SLO timeframe instead of the selected global timeframe, which is shown by the small filter icon in the upper-right corner of the SLO tile. To compare between the global timeframe and the SLO timeframe, you can also override the used timeframe within the tile configuration.

Show data in the Data explorer

To query and chart metrics, go to the service-level objective you want and select Actions > Show data in Data explorer. For more information on how to use the Data explorer, see Data explorer.


  • The Data explorer shows metric keys; it doesn't show transformations or filters.
  • For SLOs consisting of two metrics (numerator and denominator), the Data explorer shows only the numerator.

Analyze problems

If there are any open problems associated with an SLO, the value in the Open/total problems column for the SLO is marked with a red warning symbol. Select the value to display the Problems page filtered by the respective entity selector. For more information on how to analyze problems, see Problem detection and analysis.

Davis alerting

Davis provides quick notifications on anomalies detected, along with actionable root causes. If your SLO has turned red, this is most likely because Davis has already raised a problem for the underlying metrics, showing you the root cause.