<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Dynatrace otel collector is not able to connect to the containerized AG otlp endpoint : Bad Gatway in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/291597#M3408</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/96360"&gt;@vinsontan_anz&lt;/a&gt;!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Were you able to find a solution or workaround for this issue? Is it still affecting your environment?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for any feedback!&lt;/P&gt;</description>
    <pubDate>Tue, 16 Dec 2025 15:59:08 GMT</pubDate>
    <dc:creator>Michal_Gebacki</dc:creator>
    <dc:date>2025-12-16T15:59:08Z</dc:date>
    <item>
      <title>Dynatrace Otel collector not connecting to the containerized ActiveGate otlp endpoint</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/288145#M3310</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The following is the log from the dynatrace otel collector:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;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"}&lt;/LI-CODE&gt;
&lt;P&gt;In the otel collector otlp endpoint configmap:&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;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-679992f2de27&lt;/LI-CODE&gt;
&lt;P&gt;So what could be the reason for the bad gateway ?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Dec 2025 11:33:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/288145#M3310</guid>
      <dc:creator>vinsontan_anz</dc:creator>
      <dc:date>2025-12-17T11:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace otel collector is not able to connect to the containerized AG otlp endpoint : Bad Gatway</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/291597#M3408</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/96360"&gt;@vinsontan_anz&lt;/a&gt;!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Were you able to find a solution or workaround for this issue? Is it still affecting your environment?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for any feedback!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 15:59:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/291597#M3408</guid>
      <dc:creator>Michal_Gebacki</dc:creator>
      <dc:date>2025-12-16T15:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace otel collector is not able to connect to the containerized AG otlp endpoint : Bad Gatway</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/291628#M3416</link>
      <description>&lt;P&gt;Yes, it was a bug on the otel collector config when Proxy is used in dynakube. The fix was released in dynatrace operator 1.7.2. The issue was basically the NO_PROXY env variable defined in the Dynatrace otel collector was not defining the AG endpoint with .svc.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 23:02:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Dynatrace-Otel-collector-not-connecting-to-the-containerized/m-p/291628#M3416</guid>
      <dc:creator>vinsontan_anz</dc:creator>
      <dc:date>2025-12-16T23:02:02Z</dc:date>
    </item>
  </channel>
</rss>

