20 Oct 2025 06:32 AM
I have setup dynatrace components in a GKe cluster with telemetryingest capability which deployed dynatrace otel collector as part of the dynakube deployment. I have setup app pod to export otel traces to dynatrace otel collector but from the otel collector log, it shows bad gateway on connecting to dynatrace activegate otlp endpoint. I have setup custom properties on the spec.activegate to enable otlp.
The following is the log from the dynatrace otel collector:
2025-10-20T04:37:56.170Z info internal/retry_sender.go:133 Exporting failed. Will retry the request after interval. {"resource": {"service.instance.id": "e0b013ae-1f92-4803-bd84-6d08e2b2a5e6", "service.name": "dynatrace-otel-collector", "service.version": "0.38.0"}, "otelcol.component.id": "otlphttp", "otelcol.component.kind": "exporter", "otelcol.signal": "traces", "error": "failed to make an HTTP request: Post \"https://dynakube-activegate.dynatrace.svc/e/pyx45104/api/v2/otlp/v1/traces\": Bad Gateway", "interval": "13.351872759s"}In the otel collector otlp endpoint configmap:
apiVersion: v1
data:
DT_ENDPOINT: https://dynakube-activegate.dynatrace.svc/e/pyx45104/api/v2/otlp
kind: ConfigMap
metadata:
annotations:
internal.operator.dynatrace.com/template-hash: "3896151151"
creationTimestamp: "2025-10-17T07:45:16Z"
labels:
app.kubernetes.io/component: dynatrace-opentelemetry-collector
app.kubernetes.io/created-by: dynakube
app.kubernetes.io/name: dynatrace-operator
app.kubernetes.io/version: v1.7.1
name: dynatrace-otlp-api-endpoint
namespace: dynatrace
ownerReferences:
- apiVersion: dynatrace.com/v1beta5
blockOwnerDeletion: true
controller: true
kind: DynaKube
name: dynakube
uid: a219c91a-cd92-42f7-bbf5-a99e1dab9abe
resourceVersion: "1760687116331343019"
uid: 785693bf-0499-4ed7-aad3-679992f2de27So what could be the reason for the bad gateway ?