- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
It’s possible to get percentiles in Datadog by submitting data as a histogram metric through DogStatsD. The Agent embeds a DogStatsD server that receives DogStatsD packets, perform data aggregation, and send final percentile metrics to Datadog.
Since this aggregation is taken care of on the collection side, this isn’t available as a graphing function in the GUI.
Out of the histogram data, you get: 95th percentile, 50th percentile, avg, max, count.
Through the “histogram_percentiles” line of the configuration file of the Agent, get extra percentiles, such as:
Histograms are computed every 10 seconds on a host per host basis by the Datadog Agent. This collection model comes with its advantages and its limitations.
If you have two reporting streams of aggregated data, it is not possible today to aggregate across the raw datapoints from both streams, only aggregate across the aggregates.
<METRIC_NAME>.avg
for all regions, takes the average stream values for each region and produces an average of averages.Making a change to increase tag complexity (adding additional tags to be more specific) leads to changes in the behavior of a rolled up metric visualization
<METRIC_NAME>.avg
(without any tags) would be aggregating across all raw points (StatsD takes all the raw datapoints, aggregates it and then ships over a single metric stream), adding a tag like region (US, EU) tag causes StatsD to bin raw datapoints into two region bins, aggregate them, and ship over two streams. This means when graphing <METRIC_NAME>.avg
AVG by * means an aggregate across the two streams rather than a single one.