# This is an example yaml template that can be used to define a service's SLIs and SLOs as code, # which will be visible in Datadog # Once you update and complete this yaml template, please add it to your service's repository # # Please be sure to edit/update each attribute to your applications specifications # # If an attribute requires specific values, all possibilities will be listed as a comment above it. # If you are unsure what metrics your service supports or should be logging, please refer to the # README for instructions on how to generate a list of all supported metrics for your service. # Below is the minimal yaml required for an SLO/SLI configuration business_unit: devops service: devops-portal slos: - short_name: test-slo-converter-slo-1 name: test slo converter slo 1 monitors: - type: error_budget window: 7_day alert: critical: - "@slack-temp-channel-1" - "@slack-eng-tech" warn: "@slack-eng-tech" threshold: critical: 100 warning: 75 slis: - short_name: test-slo-converter-sli-1 type: external service: service-name name_filter: test slo converter sli 1 - short_name: test-slo-converter-sli-1 type: latency metric: trace.http.request resources: - post_/api/v1/deployments - get_/api/v1/deployments - post_/api/v1/deployments/ threshold: critical: 1 # 1s - short_name: test-slo-converter-sli-2 service: devops-portal type: error-rate metric: numerator: trace.http.request.errors denominator: trace.http.request.hits resources: - post_/api/v1/deployments - get_/api/v1/deployments - post_/api/v1/deployments/ threshold: critical: 0.01 # 1% slis: - short_name: test-standalone-slo-converter-sli-1 type: latency metric: trace.http.request resources: - post_/api/v1/deployments - get_/api/v1/deployments threshold: critical: 1 # 1s