DEV.co
Open-Source Observability · DataDog

dd-trace-java

dd-trace-java is Datadog's official APM client for Java applications, providing automatic instrumentation for distributed tracing, continuous profiling, and error tracking. It uses bytecode injection via ByteBuddy to capture traces from Java applications with minimal configuration.

Source: GitHub — github.com/DataDog/dd-trace-java
725
GitHub stars
344
Forks
Java
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
RepositoryDataDog/dd-trace-java
OwnerDataDog
Primary languageJava
LicenseApache-2.0 — OSI-approved
Stars725
Forks344
Open issues399
Latest releasev1.63.2 (2026-06-26)
Last updated2026-07-08
Sourcehttps://github.com/DataDog/dd-trace-java

What dd-trace-java is

A Java agent library that instruments bytecode at runtime using ByteBuddy to collect distributed traces, profiles, and performance metrics. Supports automatic instrumentation across 100+ Java libraries and frameworks, with manual instrumentation APIs for custom code paths.

Quickstart

Get the dd-trace-java source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/DataDog/dd-trace-java.gitcd dd-trace-java# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Datadog-native APM deployment

Organizations already using Datadog monitoring who need seamless Java tracing integration with native dashboard, alerting, and correlation features.

Distributed systems observability

Microservices architectures requiring end-to-end request tracing, service dependency mapping, and latency analysis across Java services.

Continuous profiling and performance optimization

Teams needing production-grade CPU, memory, and wall-clock profiling linked to trace data for identifying code hotspots and bottlenecks.

Implementation considerations

  • Requires running as a Java agent with `-javaagent` flag; integration at application startup, not runtime attachment.
  • ByteBuddy instrumentation incurs CPU and memory cost; baseline impact should be tested in staging before production deployment.
  • Datadog backend connectivity is required; ensure network egress rules and API key provisioning are in place before rollout.
  • 399 open issues suggest active development and potential minor breaking changes; test minor version upgrades in CI/CD before broad rollout.
  • Automatic instrumentation covers 100+ frameworks; custom or proprietary code may require manual span/trace API usage.

When to avoid it — and what to weigh

  • Non-Datadog observability stack — If you use Prometheus, Jaeger, Honeycomb, or other non-Datadog APM backends, this client is Datadog-specific and will require separate integration work or vendor lock-in.
  • Strict JVM startup overhead constraints — Bytecode instrumentation adds startup time and memory overhead; latency-critical applications with sub-second startup requirements should evaluate impact.
  • Legacy Java versions (pre-8) — Unknown if older Java versions are supported; compatibility matrix not provided in available data.
  • Minimal external dependencies — Integration requires Datadog agent or collector backend; no offline-only or fully self-contained tracing mode mentioned.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), an OSI-approved permissive license allowing commercial use, modification, and distribution with attribution.

Apache-2.0 permits commercial use, internal deployment, and modification without royalty. However, Datadog backend consumption is a separate commercial contract; verify Datadog SaaS pricing aligns with expected trace volume and retention policies.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityModerate
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

As a bytecode instrumentation agent, dd-trace-java has elevated JVM privileges; review source code or Datadog security reports for bytecode transformation safety. Ensure API keys are stored securely (secrets management, not in code). Trace data may contain sensitive payloads; configure sampling and redaction policies appropriately. Verify Datadog backend TLS and authentication posture separately.

Alternatives to consider

OpenTelemetry Java SDK + OTLP exporter

Vendor-neutral, multi-backend support (Jaeger, Tempo, Honeycomb, Datadog via OTLP bridge). Lower lock-in risk, broader ecosystem support, but requires more configuration.

Jaeger Java client

Open-source, cloud-native tracing. Lightweight but less automatic instrumentation; better for organizations running Kubernetes and seeking vendor independence.

Competitor APM platform with similar automatic instrumentation; choose if already standardized on New Relic infrastructure and dashboards.

Software development agency

Build on dd-trace-java with DEV.co software developers

Evaluate dd-trace-java in a staging environment with your Datadog account. Test startup overhead, verify automatic instrumentation coverage, and confirm trace quality before production rollout.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

dd-trace-java FAQ

Does dd-trace-java require a Datadog subscription?
Yes, the library sends traces to Datadog infrastructure. A Datadog agent or SaaS account with API credentials is required for operational use.
Will instrumentation work with third-party frameworks?
Automatic instrumentation covers 100+ popular Java libraries (Spring, Hibernate, databases, queues). Custom code or proprietary frameworks require manual span API usage.
What is the startup time and memory overhead?
Unknown from available data; baseline depends on number of libraries loaded and sampling rate. Datadog recommends profiling in staging to quantify impact for your application.
Can I use dd-trace-java with OpenTelemetry?
Unknown from available data; interoperability between Datadog instrumentation and OpenTelemetry SDKs requires review of compatibility matrix or Datadog documentation.

Custom software development services

DEV.co helps companies turn open-source tools like dd-trace-java into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source observability stack.

Ready to instrument your Java services?

Evaluate dd-trace-java in a staging environment with your Datadog account. Test startup overhead, verify automatic instrumentation coverage, and confirm trace quality before production rollout.