- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Ingestion controls affect what traces are sent by your applications to Datadog. APM Metrics are always calculated based on all traces, and are not impacted by ingestion controls.
The Ingestion Control page provides visibility at the Agent and tracing libraries level into the ingestion configuration of your applications and services. From the ingestion control configuration page, you can:
All metrics used in the page are based on live traffic data of the past 1 hour. Any Agent or library configuration change is reflected in the page.
Get an overview of the total ingested data over the past hour, and an estimation of your monthly usage against your monthly allocation, calculated with the active APM infrastructure (hosts, Fargate tasks, and serverless functions).
If the monthly usage is under 100%
, the projected ingested data fits within your monthly allotment. A monthly usage value over 100%
means that the monthly ingested data is projected to be over your monthly allotment.
Click Remotely Configure Agent Ingestion to manage ingestion sampling for your services globally. You can remotely configure Agent sampling parameters if you are using Agent version 7.42.0 or higher. Read How Remote Configuration Works for information about enabling remote configuration in your Agents.
Three ingestion sampling mechanisms are controllable from the Datadog Agent:
DD_APM_MAX_TPS
locally at the Agent level.DD_APM_ERROR_TPS
locally at the Agent level.DD_APM_ENABLE_RARE_SAMPLER
locally at the Agent level.With remote configuration, you don’t have to restart the Agent to update these parameters. Click Apply
to save the configuration changes, and the new configuration takes effect immediately.
Note: The Other Ingestion Reasons
(gray) section of the pie chart represents other ingestion reasons which are not configurable at the Datadog Agent level.
Note: Remotely configured parameters take precedence over local configurations such as environment variables and datadog.yaml
configuration.
The service table contains information about the ingested volumes and ingestion configuration, broken down by service:
sampling_service
dimension, set on the datadog.estimated_usage.apm.ingested_bytes
metrics. For more information, read APM usage metrics.Automatic
if the default head-based sampling mechanism from the Agent applies. If the ingestion was configured in the tracing libraries with trace sampling rules, the service is marked as Configured
. For more information about configuring ingestion for a service, read about changing the default ingestion rate.Limited Resource
when some spans are dropped due to the Datadog Agent reaching CPU or RAM limits set in its configuration, Legacy Setup
when some spans are ingested through the legacy App Analytics mechanism, or OK
otherwise.Filter the page by environment, configuration, and status to view services for which you need to take an action. To reduce the global ingestion volume, sort the table by the Downstream Bytes/s
column to view services responsible for the largest share of your ingestion.
Note: The table is powered by the usage metrics datadog.estimated_usage.apm.ingested_spans
and datadog.estimated_usage.apm.ingested_bytes
. These metrics are tagged by service
, env
and ingestion_reason
.
The Traffic Breakdown column breaks down the destination of all traces originating from the service. It gives you an estimate of the share of traffic that is ingested and dropped, and for which reasons.
The breakdown is composed of the following parts:
Complete traces ingested (blue): The percentage of traces that have been ingested by Datadog.
Complete traces not retained (gray): The percentage of traces that have intentionally not been forwarded to Datadog by the Agent or the tracing library. This can happen for one of two reasons depending on your configuration:
Complete traces dropped by the tracer rate limiter (orange): When you choose to manually set the service ingestion rate as a percentage with trace sampling rules, a rate limiter is automatically enabled, set to 100 traces per second by default. See the rate limiter documentation to manually configure this rate.
Traces dropped due to the Agent CPU or RAM limit (red): This mechanism may drop spans and create incomplete traces. To fix this, increase the CPU and memory allocation for the infrastructure that the Agent runs on.
Click on any service row to view the Service Ingestion Summary, a detailed view providing actionable insights on the ingestion configuration of the service.
Explore the Ingestion reasons breakdown to see which mechanisms are responsible for your service ingestion. Each ingestion reason relates to one specific ingestion mechanism. After changing your service ingestion configuration, you can observe the increase or decrease of ingested bytes and spans in this timeseries graph based on the past hour of ingested data.
If most of your service ingestion volume is due to decisions taken by upstream services, investigate the detail of the Sampling decision makers top list. For example, if your service is non-root, (meaning that it never decides to sample traces), observe all upstream services responsible for your non-root service ingestion. Configure upstream root services to reduce your overall ingestion volume.
For further investigations, use the APM Trace - Estimated Usage Dashboard, which provides global ingestion information as well as breakdown graphs by service
, env
and ingestion reason
.
See the Datadog Agent and tracing library versions your service is using. Compare the versions in use to the latest released versions to make sure you are running recent and up-to-date Agents and libraries.
Note: You need to upgrade the Agent to v6.34 or v7.34 for the version information to be reported.
Remote sampling rules let you dynamically configure sampling rules from the Datadog UI, without redeploying your service. Follow the instructions in the resource-based sampling guide to get started. Adaptive sampling rates let Datadog control sampling rates on your behalf to match a configured monthly ingested volume budget. Follow the instructions in the Adaptive sampling guide to get started. To request access to both features, complete the following form.
Request AccessClick Manage Ingestion Rate to get instructions on how to configure your service ingestion rate.
To specify a specific percentage of a service’s traffic to be sent, add an environment variable or a generated code snippet to your tracing library configuration for that service.
ingestion_reason:rule
.If sampling rules are set in multiple locations, the following precedence rules apply in order, where rules that appear first on the list can override lower precedence rules:
DD_TRACE_SAMPLING_RULES
)DD_TRACE_SAMPLE_RATE
)DD_APM_TARGET_TPS
and DD_APM_MAX_TPS
To phrase it another way, Datadog uses the following precedence rules:
추가 유용한 문서, 링크 및 기사: