Merge branch 'main' into ale/eng-9201-router-router-should-work-if-controlplane-is-down

Author: alepane21

docs-website/docs.json

@@ -174,7 +174,8 @@
                   "router/open-telemetry",
                   "router/open-telemetry/custom-attributes",
                   "router/open-telemetry/prometheus-otlp-ingestion",
-                  "router/open-telemetry/setup-opentelemetry-collector"
+                  "router/open-telemetry/setup-opentelemetry-collector",
+                  "router/open-telemetry/dynatrace"
                 ]
               },
               {

docs-website/router/open-telemetry.mdx

@@ -120,6 +120,8 @@ High metric cardinality can lead to performance issues by consuming excessive re
 
 You can configure multiple exporters. A common case is to forward telemetry data to Cosmo Cloud and e.g. Datadog Agent which has native support to ingest [OpenTelemetry](https://docs.datadoghq.com/opentelemetry/) data.
 
+For a Dynatrace example that exports to Dynatrace and Cosmo Cloud at the same time, see [Dynatrace](/router/open-telemetry/dynatrace).
+
 <CodeGroup>
   ```bash config.yaml
   telemetry:

docs-website/router/open-telemetry/dynatrace.mdx

@@ -0,0 +1,56 @@
+---
+title: "Dynatrace"
+description: "Export OpenTelemetry traces and metrics to Dynatrace and Cosmo Cloud."
+icon: "server"
+---
+
+Use multiple OTLP exporters when you want to send telemetry data to Dynatrace and Cosmo Cloud at the same time.
+
+<Warning>
+  Do not commit Dynatrace API tokens to source control. Reference them through an environment variable such as `${DYNATRACE_API_TOKEN}`.
+</Warning>
+
+## Router configuration
+
+The following example exports traces and metrics to both Cosmo Cloud and Dynatrace:
+
+<CodeGroup>
+  ```yaml config.yaml
+  telemetry:
+    service_name: "cosmo-router"
+
+    tracing:
+      enabled: true
+      exporters:
+        # Cosmo Cloud
+        - endpoint: https://cosmo-otel.wundergraph.com
+          exporter: "http"
+          headers: {Authorization: Bearer ${ROUTER_TOKEN}}
+
+        # Dynatrace traces
+        - endpoint: https://${DYNATRACEHOST}.live.dynatrace.com
+          path: /api/v2/otlp/v1/traces
+          exporter: "http"
+          headers: {Authorization: "Api-Token ${DYNATRACE_API_TOKEN}"}
+
+    metrics:
+      otlp:
+        enabled: true
+        exporters:
+          # Cosmo Cloud
+          - endpoint: https://cosmo-otel.wundergraph.com
+            exporter: "http"
+            headers: {Authorization: Bearer ${ROUTER_TOKEN}}
+
+          # Dynatrace metrics
+          - endpoint: https://${DYNATRACEHOST}.live.dynatrace.com
+            path: /api/v2/otlp/v1/metrics
+            exporter: "http"
+            headers: {Authorization: "Api-Token ${DYNATRACE_API_TOKEN}"}
+  ```
+</CodeGroup>
+
+## Notes
+
+- Dynatrace uses different OTLP HTTP paths for traces and metrics.
+- If you do not want to export to Cosmo Cloud, remove the Cosmo Cloud exporters from the configuration.