- Evaluate ClickStack alongside Datadog without touching application code, using your existing agents to send the same telemetry to both platforms.
- Ease a migration, moving to ClickStack while keeping your current collection layer in place and adopting OpenTelemetry instrumentation gradually.
- Run both stacks in parallel over the long term, using each platform for what it does best.

Why run ClickStack alongside Datadog
For most teams, the reason to move observability data out of Datadog is cost. Log and trace volumes grow as applications scale and more services are instrumented, leaving a choice between higher spend and keeping less of the telemetry you produce. Those cost controls then limit what you can see during an investigation: sampled traces, unindexed logs, rolled-up metrics, and short retention windows all reduce the context available when you need it most. ClickStack is built on ClickHouse, which for large log and tracing workloads can be over 100x more cost-efficient than Datadog. That difference in storage economics is what makes running ClickStack alongside Datadog worthwhile:- Longer retention. Set retention to match your operational needs rather than your budget, and keep the events you may need weeks or months later.
- Full-fidelity data. Store every log and trace without sampling, so investigations run against complete data rather than a subset.
- No API rate limits. Query your telemetry as a database rather than through a metered API, with no per-query or per-endpoint throttling.
- Full SQL access. Analyze logs, metrics, and traces with SQL, and join them with business or infrastructure data already in ClickHouse.
- Agentic workloads. Expose your telemetry to AI agents through the ClickStack MCP server and run unlimited analytical queries directly against ClickHouse.
How the Datadog receiver works
In a typical OpenTelemetry deployment, telemetry is sent to an OpenTelemetry collector before it reaches a backend. The collector receives data from agent-mode collectors and from OpenTelemetry SDKs instrumenting applications, applies any filtering or transformations, batches events, and exports them to the target destination.


What the receiver handles
The receiver translates Datadog payloads into their correct OpenTelemetry representation so that ClickStack can interpret, correlate, and query the data without any Datadog-specific logic:- Log records. Datadog millisecond timestamps are converted to nanoseconds and used to populate the OpenTelemetry timestamp, observed timestamp, body, and severity fields, so records no longer appear at the Unix epoch.
- Resource attributes and severity. Datadog statuses such as
info,warn, anderrormap to the corresponding OpenTelemetrySeverityNumberandSeverityText. Hostnames, service names, environments, and known container, cloud, and Kubernetes tags are promoted to standard resource attributes. - Trace and log correlation. The
dd.trace_idanddd.span_idfields populate the OpenTelemetry trace and span identifiers, and the receiver reconstructs full 128-bit trace IDs from Datadog’s split representation. Enabled by default, this lets Datadog-sourced logs and spans correlate with services instrumented using OpenTelemetry. - Structured JSON logs. A
decode_json_messageoption, enabled by default, performs the JSON processing that normally happens in the Datadog backend, extracting the body, timestamp, severity, trace identifiers, resource fields, and remaining attributes. - Compatibility with current agents. Datadog Agent 7.59 and later compresses HTTP payloads with Zstandard by default. The receiver supports Zstandard alongside gzip, so current agents connect without their payloads being rejected.
Enabling the Datadog receiver
The Datadog receiver is included in the ClickStack distribution of the OpenTelemetry collector, listening on port8126. It is disabled by default and enabled with the ENABLE_DATADOG_RECEIVER environment variable.
Once enabled, point your Datadog agent at the receiver and authenticate it with the ingestion key generated by the ClickStack interface (ClickStack UI).
With Open Source ClickStack the collector secures its endpoints using an ingestion key generated when the stack is deployed. You enable the receiver, copy that key from the ClickStack interface (ClickStack UI), and use it as the Datadog agent’s API key.
1
Start a collector with the receiver enabled
The example below will use the all-in-one image. If you’re using a different distribution model, ensure the same flag is applied to the container running the collector.Set The receiver is now available at Complete the remaining setup process as described in the open source getting started guide.
ENABLE_DATADOG_RECEIVER=true and expose port 8126:http://localhost:8126.Running a local Datadog agentThe Datadog agent also listens on port
8126. If the agent runs on the same host as the collector, map the collector to a different host port to avoid a conflict, for example -p 18126:8126, and point the agent at that port instead.2
Copy your ingestion API key
In the ClickStack interface (ClickStack UI), select your user in the bottom-left corner, go to Team Settings > API Keys, and copy the Ingestion API Key.

3
Configure the Datadog agent
Update the agent configuration file at This configuration:
/opt/datadog-agent/etc/datadog.yaml to send logs, traces, and metrics to the receiver. Use your ClickStack ingestion key as the API key, and point each destination at the receiver endpoint:- Sends metrics, traces, and logs to the receiver rather than to Datadog.
- Disables the v3 metrics intake, since the receiver supports the Datadog v2 metrics endpoint.
- Turns off remote updates and remote configuration, which depend on the Datadog backend.
4
Restart the agent
Restart the Datadog agent so it picks up the new configuration. On macOS:Telemetry from the agent now flows into ClickStack, where you can explore it in ClickStack UI.
Worked example
The following example uses a sample application to show the full path from an instrumented app through the Datadog agent into ClickStack.1
Clone and run the sample app
The example uses the Hacker News demo app, instrumented with Datadog on the Follow the instructions in the README to run the app.
datadog-instrumentation branch. Clone that branch:
2
Launch ClickStack with the receiver enabled
Start the all-in-one image with the Datadog receiver enabled. Here we map the receiver to host port The receiver is available at
18126 so it doesn’t clash with the local Datadog agent, which also uses 8126:http://127.0.0.1:18126.3
Install and configure the Datadog agent
Install the Datadog agent. On macOS:Update See Enabling the Datadog receiver for the full agent configuration and for where to find your ingestion key.
/opt/datadog-agent/etc/datadog.yaml to point at the receiver on port 18126, using your ClickStack ingestion key as the API key, then restart the agent:4
Explore your telemetry in ClickStack
Open the ClickStack UI interface at http://localhost:8080 and explore the traces, logs, and metrics captured from the Datadog agent.




