- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
The SLO widget supports advanced metric query filtering, including the use of template variables to dynamically scope results displayed.
First, create a metric-based SLO. This example uses APM trace metrics to measure the availability of an example service called web-store
.
sum:trace.rack.request.hits{service:web-store} by {resource_name}.as_count()
sum:trace.rack.request.errors{service:web-store} by {resource_name}.as_count()
sum:trace.rack.request.hits{service:web-store} by {resource_name}.as_count()
Select the SLO in the SLO widget editor. You can apply additional filters in the widget configuration to further scope the results displayed. This does not modify the original definition of the SLO. In the example, we add the $env
and $availability-zone
tags to the filter by field of the widget.
With this configuration, what happens when the Dashboard template variable is changed to env:prod
and availability-zone:northcentralus
?
The SLO widget filters the SLO metric queries by those additional tags for your visualization purposes:
sum:trace.rack.request.hits{service:web-store, env:prod, availability-zone:northcentralus} by {resource_name}.as_count()
sum:trace.rack.request.errors{service:web-store, env:prod, availability-zone:northcentralus} by {resource_name}.as_count()
sum:trace.rack.request.hits{service:web-store, env:prod, availability-zone:northcentralus} by {resource_name}.as_count()
Additional helpful documentation, links, and articles: