Table: datadog_service_level_objective - Query Datadog Service Level Objectives using SQL

A Service Level Objective (SLO) in Datadog is a target that a service aims to achieve over a given period. It quantifies the long-term performance of a service in terms of its availability or response time. SLOs are typically used to set expectations for service performance and to measure whether those expectations are being met.

Table Usage Guide

The datadog_service_level_objective table provides insights into Service Level Objectives within Datadog. As an SRE or DevOps engineer, explore SLO-specific details through this table, including thresholds, timeframes, and associated metadata. Utilize it to uncover information about SLOs, such as those that are not meeting their targets, the historical performance of SLOs, and the verification of SLO configurations.

Examples

Basic info

Explore which service level objectives have been set up in your Datadog account and when they were created. This can assist in understanding what performance metrics are being monitored and by whom, aiding in the overall management and optimization of your services.

select
  name,
  type,
  thresholds,
  created_at,
  creator_email
from
  datadog_service_level_objective;

select
  name,
  type,
  thresholds,
  created_at,
  creator_email
from
  datadog_service_level_objective;

List metric type SLOs

Explore which service level objectives (SLOs) are based on metrics in your Datadog account. This can help you assess the performance of specific services or systems over time.

select
  name,
  type,
  created_at,
  monitor_ids
from
  datadog_service_level_objective
where
  type = 'metric';

select
  name,
  type,
  created_at,
  monitor_ids
from
  datadog_service_level_objective
where
  type = 'metric';

List SLOs that are type monitor and have thresholds set to 2.5 9's over 7 days

Identify service level objectives (SLOs) that are classified as 'monitor' type and have specific thresholds set. This can be useful in managing and monitoring system performance over a week.

select
  name,
  type,
  thresholds,
  created_at
from
  datadog_service_level_objective
where
  type = 'monitor'
  and thresholds @> '[{"target":99.5,"target_display":"99.5","timeframe":"7d"}]' :: jsonb;

Error: The corresponding SQLite query is unavailable.

Schema for datadog_service_level_objective

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form, e.g. connection_name.
configured_alert_ids	jsonb		Get the IDs of SLO monitors that reference this SLO.
created_at	timestamp with time zone		Timestamp of the SLO creation.
creator_email	text		Email of the creator.
description	jsonb		Description of the SLO.
groups	jsonb		A list of (up to 20) monitor groups that narrow the scope of a monitor service level objective.
id	text	=	ID of the SLO.
modified_at	timestamp with time zone		Last timestamp when the monitor was edited.
monitor_ids	jsonb		A list of monitor ids that defines the scope of a monitor service level objective.
monitor_tags	jsonb		If monitors that are associated with SLO have tags they will show here.
name	text		Name of the SLO.
query	jsonb		The Metric based SLOs use queries to determine the state. Shows associated query.
tags	jsonb		Tags associated with SLO.
thresholds	jsonb		Thresholds that are set for the SLOs.
type	text		The type of the SLO. For more information about type, see https://docs.datadoghq.com/monitors/service_level_objectives/.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- datadog

You can pass the configuration to the command with the --config argument:

steampipe_export_datadog --config '<your_config>' datadog_service_level_objective