All Classes and Interfaces
Class
Description
The Datadog Agent's
GET /info document (fields this package reads).Missing or invalid credentials (HTTP 401).
The caller cancelled the operation (future cancelled, thread interrupted, client closed).
Invalid or missing configuration.
Conflicting write or check-and-set mismatch (HTTP 409, 412).
The operations of one scenario category (
core, secrets, logging,
tracing) for the ConformanceRunner.Results of a conformance run.
Result of one scenario.
Outcome of a scenario or step.
Result of one step.
Runs the shared conformance scenarios (
conformance/scenarios/*.json, SPEC section 6)
against targets supplied by a service's integration test.Builder for
ConformanceRunner.Conformance operations of the
core category: health, ping,
serverVersion, close.A target of the
core conformance category that is not the service client: a fake for unit
tests of the runner, or an adapter for a client whose core methods differ.The Datadog APM client (API.md section 1).
Builder that configures and creates a client in one chain.
Immutable configuration of a
DatadogApmClient, DatadogTracing.initTracing() and
DatadogSpansQuery (SPEC section 2.2, API.md section 0, DECISIONS.md #1).Builder of the configuration.
Base class of every error raised by the Datadog APM SDK (SPEC section 2.1).
Datadog <-> OpenTelemetry id conversion (API.md section 3, DECISIONS.md #3).
A trace id split the way Datadog stores it.
Datadog log correlation (DECISIONS.md #3).
Datadog span formats to the SPEC section 5 trace model (API.md sections 2.1 and 4).
Datadog header propagation (
x-datadog-*) with ddtrace's conflict rules (API.md section 3,
DECISIONS.md #5).A W3C context that lost against Datadog headers in
DatadogPropagator.extract(io.opentelemetry.context.Context, C, io.opentelemetry.context.propagation.TextMapGetter<C>).A warning attached to a partial or adjusted Datadog query result (
meta.warnings[]).Datadog sites and the query API base URL (API.md section 0).
One span returned by the spans search API.
Datadog error attributes (DECISIONS.md #2).
Span exporter wrapper installed by
DatadogTracing.initTracing().The Datadog spans query client: the SaaS API at
https://api.<site> with the headers
DD-API-KEY and DD-APPLICATION-KEY (the application key needs apm_read).A point in time for a Datadog query: an absolute instant (sent as ISO-8601 in UTC with
milliseconds) or a Datadog date expression (
now-15m, ISO-8601, epoch milliseconds) sent
as is.initTracing for Datadog: the OpenTelemetry SDK exporting OTLP to the Datadog Agent
(HTTP/protobuf on 4318 by default, or gRPC on 4317), unified service tagging, the Datadog + W3C
propagators, the Datadog error attributes and the terminated-context links (API.md section 2,
DECISIONS.md #2, #5).A running Datadog tracing setup returned by
DatadogTracing.initTracing().A service dependency edge.
Reads configuration from environment variables (SPEC section 2.2).
Canonical error codes shared by every Grow Codes SDK (SPEC section 2.1).
Service hook that replaces the error
HttpTransport derived from a failed response, for
vendor-specific mapping (for example a 403 that means bad credentials, or a 500 whose body says
the request will never succeed).Evaluates the
expect object of a scenario step (SPEC section 6).Implements the
health() contract (SPEC section 2.4): never throws for an unhealthy or
unreachable service, only for CancelledException and ConfigException.Result of
health() (SPEC section 2.4).Callbacks invoked for every HTTP attempt (SPEC section 2.5).
The HTTP engine shared by every client of the SDK (SPEC section 2.3), built on
HttpClient.SpanExporter that keeps finished spans in memory.TraceQueryClient over in-memory spans (usually InMemorySpanExporter.spans()),
including a dependency graph computed from parent/child spans of different services.Shared Jackson configuration of the SDK.
JUnit 5 adapter: one dynamic test per scenario.
Minimal logger used by the transport (SPEC section 2.5).
The record does not exist (HTTP 404).
Executes one scenario step and returns its result (or an
OpResult).A step result with optional extra views for the expectations
count and tree.Converts SDK attribute values (
AttrValue: String, numbers, Boolean, lists, maps) into
OpenTelemetry Attributes.OTLP span exporters (gRPC and HTTP/protobuf) configured from a
TracingConfig: endpoint,
headers, compression, export timeout and TLS.The credentials lack a permission (HTTP 403).
Generic polling helper (
pollUntil): used by waitForLog, waitForTrace and
service waiters.The service rate-limited the call (HTTP 429); see
DatadogApmException.retryAfter().Redaction helpers for headers, URLs, structured fields and free text (SPEC section 2.6).
Retry settings with full-jitter exponential backoff (SPEC section 2.3).
Builder for
RetryPolicy.A parsed conformance scenario (
conformance/scenarios/*.json).One step of a scenario.
Package identity used in the
User-Agent header.Builder of
SearchSpansOptions.A credential held in a
char[] that never prints itself.A span as returned by a
TraceQueryClient (normalized model; not the OpenTelemetry API
span).Span event.
Span kind (wire values are lower case).
Span link.
Span status.
Status code (wire values are lower case).
One bucket of an aggregation.
Converts OpenTelemetry SDK
SpanData into the normalized query Span.Creates the span exporter for a
TracingConfig (see OtlpExporters.factory()).Buckets of a numeric facet.
Order of the groups.
A span with its children (see
Traces.buildTree(java.util.List<codes.grow.packages.datadogapm.tracing.query.Span>)).Options of
Spans.withSpan(java.lang.String, codes.grow.packages.datadogapm.tracing.ThrowingSupplier<T, E>): attributes, kind, links, tracer, parent context.Builder for
SpanOptions.Span helpers on top of the OpenTelemetry API.
Everything an
OpHandler needs for one step.Creates the object a scenario runs against (client, provider, log client, tracing handle).
A runnable that may throw.
A supplier that may throw.
A connect, request or total deadline was exceeded (or HTTP 408, 504).
TLS settings: custom CA, client certificate (mutual TLS) and the test-only
insecureSkipVerify.Builder for
TlsOptions.A trace: its id and its spans sorted by start time, then span id.
Tracing of plain functions:
Traced.run(String, Callable) and the Traced.Method
annotation honoured by TracedProxy.Marks an interface method (or its implementation) to run in a span when called through a
TracedProxy.Wraps a
HttpClient: every request runs in a client span and carries the propagation
headers.Proxy-based interceptor that runs methods annotated with Traced.Method (on the
interface or on the implementation) in a span.Trace and span id normalisation (lower-case hex; 64-bit trace ids are left-padded to 32).
Reads traces back from the service.
Span ordering and tree helpers.
Filter of
TraceQueryClient.searchTraces(codes.grow.packages.datadogapm.tracing.query.TraceSearchQuery) (limit defaults to 20).Builder for
TraceSearchQuery.Search result entry.
Sets up the OpenTelemetry SDK from a
TracingConfig.Immutable tracing setup used by
Tracing.initWith(codes.grow.packages.datadogapm.tracing.TracingConfig, codes.grow.packages.datadogapm.tracing.SpanExporterFactory).Span batch processor settings.
Builder for
TracingConfig.Export body compression.
Export protocol.
Sampler (OpenTelemetry
OTEL_TRACES_SAMPLER names).Jakarta Servlet filter that continues the caller's trace (W3C/B3 headers per the configured
propagators) and records one server span per request (Servlet API is a
provided
dependency).Running tracing setup returned by
Tracing.initWith(codes.grow.packages.datadogapm.tracing.TracingConfig, codes.grow.packages.datadogapm.tracing.SpanExporterFactory).OkHttp interceptor (OkHttp is an optional dependency) that runs each call in a client span and
adds the propagation headers.
Conformance operations of the
tracing category: span, flush,
getTraceUntil, listServices.Target of the
tracing conformance scenarios.Settings of one
HttpTransport.Builder for
TransportConfig.One logical HTTP call executed by
HttpTransport (with retries).Builder for
TransportRequest.A response returned by
HttpTransport (2xx or an accepted status).Network error or HTTP 500, 502, 503.
The service or deployment does not offer this capability (HTTP 501).
The request or a value is invalid (HTTP 400, 413, 422, other 4xx).