- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`Technology | Library | Minimal tracer version | Recommended tracer version |
---|---|---|---|
Kafka | kafka-clients (v3.7 is not fully supported) | 1.9.0 | 1.43.0 or later |
RabbitMQ | amqp-client | 1.9.0 | 1.42.2 or later |
Amazon SQS | aws-java-sdk-sqs (v1) | 1.27.0 | 1.42.2 or later |
Amazon SQS | sqs (v2) | 1.27.0 | 1.42.2 or later |
Amazon Kinesis | Kinesis (v1) | 1.22.0 | 1.42.2 or later |
Amazon Kinesis | Kinesis (v2) | 1.22.0 | 1.42.2 or later |
Amazon SNS | SNS (v1) | 1.31.0 | 1.42.2 or later |
Amazon SNS | SNS (v2) | 1.31.0 | 1.42.2 or later |
Google PubSub | Google Cloud Pub/Sub | 1.25.0 | 1.42.2 or later |
To enable Data Streams Monitoring, set the following environment variables to true
on services that are sending or consuming messages:
DD_DATA_STREAMS_ENABLED
DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED
environment:
- DD_DATA_STREAMS_ENABLED: "true"
- DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED: "true"
Run the following when you start your Java application:
java -javaagent:/path/to/dd-java-agent.jar -Ddd.data.streams.enabled=true -Ddd.trace.remove.integration-service-names.enabled=true -jar path/to/your/app.jar
To set up Data Streams Monitoring from the Datadog UI without needing to restart your service, use Configuration at Runtime. Navigate to the APM Service Page and Enable DSM
.
Use Datadog’s Java tracer, dd-trace-java
, to collect information from your Kafka Connect workers.
dd-java-agent.jar
file to your Kafka Connect workers. Ensure that you are using dd-trace-java
v1.44+.STRIMZI_JAVA_OPTS
to add -javaagent:/path/to/dd-java-agent.jar
.Data Streams Monitoring uses one message attribute to track a message’s path through an SQS queue. As Amazon SQS has a maximum limit of 10 message attributes allowed per message, all messages streamed through the data pipelines must have 9 or fewer message attributes set, allowing the remaining attribute for Data Streams Monitoring.
The RabbitMQ integration can provide detailed monitoring and metrics of your RabbitMQ deployments. For full compatibility with Data Streams Monitoring, Datadog recommends configuring the integration as follows:
instances:
- prometheus_plugin:
url: http://<HOST>:15692
unaggregated_endpoint: detailed?family=queue_coarse_metrics&family=queue_consumer_count&family=channel_exchange_metrics&family=channel_queue_exchange_metrics&family=node_coarse_metrics
This ensures that all RabbitMQ graphs populate, and that you see detailed metrics for individual exchanges as well as queues.
To monitor a data pipeline where Amazon SNS talks directly to Amazon SQS, you must perform the following additional configuration steps:
Set the environment variable DD_TRACE_SQS_BODY_PROPAGATION_ENABLED
to true
.
For example:
environment:
- DD_DATA_STREAMS_ENABLED: "true"
- DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED: "true"
- DD_TRACE_SQS_BODY_PROPAGATION_ENABLED: "true"
Ensure that you are using Java tracer v1.44.0+.
Enable Amazon SNS raw message delivery.
There are no message attributes in Kinesis to propagate context and track a message’s full path through a Kinesis stream. As a result, Data Streams Monitoring’s end-to-end latency metrics are approximated based on summing latency on segments of a message’s path, from the producing service through a Kinesis Stream, to a consumer service. Throughput metrics are based on segments from the producing service through a Kinesis Stream, to the consumer service. The full topology of data streams can still be visualized through instrumenting services.
Data Streams Monitoring propagates context through message headers. If you are using a message queue technology that is not supported by DSM, a technology without headers (such as Kinesis), or Lambdas, use manual instrumentation to set up DSM.
Data Streams Monitoring can automatically discover your Confluent Cloud connectors and visualize them within the context of your end-to-end streaming data pipeline.
Install and configure the Datadog-Confluent Cloud integration.
In Datadog, open the Confluent Cloud integration tile.
Under Actions, a list of resources populates with detected clusters and connectors. Datadog attempts to discover new connectors every time you view this integration tile.
Select the resources you want to add.
Click Add Resources.
Navigate to Data Streams Monitoring to visualize the connectors and track connector status and throughput.
Data Streams Monitoring can collect information from your self-hosted Kafka connectors. In Datadog, these connectors are shown as services connected to Kafka topics. Datadog collects throughput to and from all Kafka topics. Datadog does not collect connector status or sinks and sources from self-hosted Kafka connectors.