This repository was archived by the owner on Sep 4, 2025. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +14
-1
lines changed
website/docs/cloud-docs/agents Expand file tree Collapse file tree 1 file changed +14
-1
lines changed Original file line number Diff line number Diff line change @@ -58,7 +58,8 @@ version constraints become known.
5858
5959| Terraform Cloud Agent version | Compatible OpenTelemetry Collector version |
6060| ----------------------------- | ------------------------------------------ |
61- | All versions | <= 0.42.0 |
61+ | >= 0.1.12, <= 1.7.0 | <= 0.42.0 |
62+ | >= 1.7.1 | Tested up to 0.73.0 |
6263
6364### Running the collector
6465
@@ -93,6 +94,18 @@ docker run \
9394
9495The collector should start with your modified configuration.
9596
97+ ## DataDog Agent
98+
99+ The Terraform Cloud Agent may target a DataDog agent directly instead of an
100+ OpenTelemetry collector. To configure the DataDog agent to accept OTLP
101+ connections, refer to the [ DataDog OpenTelemetry
102+ documentation] ( https://docs.datadoghq.com/opentelemetry/otlp_ingest_in_the_agent ) .
103+ Note that the tfc-agent talks to a gRPC OTLP receiver only. Be sure to
104+ configure the DataDog agent to accept a gRPC OTLP connection. Once the
105+ DataDog agent is listening for gRPC connections, [ configure the tfc-agent] using
106+ the address of the DataDog agent's gRPC listener in place of the OpenTelemetry
107+ collector address.
108+
96109## Tracing
97110
98111The agent emits tracing spans which are useful in understanding and debugging
You can’t perform that action at this time.
0 commit comments