diff --git a/docs/source/configuration/telemetry/exporters/metrics/dynatrace.mdx b/docs/source/configuration/telemetry/exporters/metrics/dynatrace.mdx index 82ae53780a..41942dbb38 100644 --- a/docs/source/configuration/telemetry/exporters/metrics/dynatrace.mdx +++ b/docs/source/configuration/telemetry/exporters/metrics/dynatrace.mdx @@ -33,7 +33,7 @@ telemetry: -You must specify `protocol: http` or the exporter will fail to connect to Dynatrace. +You must specify `protocol: http` or the exporter will fail to connect to Dynatrace. Additionally, if your Dynatrace endpoint does not contain a port, you must append `:443` to the endpoint. For example: `https://subdomain.live.dynatrace.com:443/api/v2/otlp/v1/traces`. diff --git a/docs/source/configuration/telemetry/exporters/tracing/dynatrace.mdx b/docs/source/configuration/telemetry/exporters/tracing/dynatrace.mdx index 36fd263a9a..2ba82a6358 100644 --- a/docs/source/configuration/telemetry/exporters/tracing/dynatrace.mdx +++ b/docs/source/configuration/telemetry/exporters/tracing/dynatrace.mdx @@ -33,7 +33,7 @@ telemetry: -You must specify `protocol: http` or the exporter will fail to connect to Dynatrace. +You must specify `protocol: http` or the exporter will fail to connect to Dynatrace. Additionally, if your Dynatrace endpoint does not contain a port, you must append `:443` to the endpoint. For example: `https://subdomain.live.dynatrace.com:443/api/v2/otlp/v1/traces`.