- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
Navigate to the SLO Manage page.
Start thinking from the perspective of your user:
Type of SLI | Description |
---|---|
Availability | Could the server respond to the request successfully? |
Latency | How long did it take for the server to respond to the request? |
Throughput | How many requests can be handled? |
Type of SLI | Description |
---|---|
Availability | Can the data be accessed on demand? |
Latency | How long does it take to read or write data? |
Durability | Is the data still there when it is needed? |
Type of SLI | Description |
---|---|
Correctness | Was the right data returned? |
Freshness | How long does it take for new data or processed results to appear? |
Do you require an SLI calculation that is time-based or count-based?
The following SLO types are available in Datadog:
Metric-based SLOs
Example: 99% of requests should complete in less than 250 ms over a 30-day window.
Monitor-based SLOs
Example: the latency of all user requests should be less than 250 ms 99% of the time in any 30-day window.
If you need to create a new monitor go to the Monitor create page.
Time Slice SLOs
Example: the latency of all user requests should be less than 250 ms 99% of the time in any 30-day window.
99%
, 99.5%
, 99.9%
, 99.95%
, or any other target value that makes sense for your requirements.7
, 30
, or 90 days
team
and service
is a common practice.Use tags to search for your SLOs from the SLO list view.
Additional helpful documentation, links, and articles: