<?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: opentelemetry collector config using otlp exporter for traces in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204933#M30688</link>
    <description>&lt;P&gt;I was just informed that the backend would not support gRPC yet, so you'd need to use HTTP, in which case &lt;EM&gt;endpoint&lt;/EM&gt; takes a proper URL, which should be the base one. Have you tried this already?&lt;/P&gt;&lt;P&gt;endpoint: https://{environmentid}.live.dynatrace.com:443/api/v2/otlp&lt;/P&gt;</description>
    <pubDate>Thu, 16 Feb 2023 09:13:40 GMT</pubDate>
    <dc:creator>alexander_dt</dc:creator>
    <dc:date>2023-02-16T09:13:40Z</dc:date>
    <item>
      <title>opentelemetry collector config using otlp exporter for traces</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204853#M30683</link>
      <description>&lt;P&gt;I am trying to use&amp;nbsp; opentelemetry otlp exporter (using grpc) to export traces to Dynatrace and here is my config for the exporter&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;exporters:
  otlp/dynatrace:
    endpoint: https://{environmentid}.live.dynatrace.com:443
    headers:
      Authorization: Api-Token &amp;lt;api_token&amp;gt;
    wait_for_ready: false
    sending_queue:
      enabled: false
    tls:
      insecure: false
      insecure_skip_verify: true&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P data-unlink="true"&gt;However, i get timeout error. I tried using&amp;nbsp;https://{environmentid}.live.dynatrace.com/api/v2/otlp/v1/traces:443&amp;nbsp; endpoint and got host not found error.&lt;/P&gt;&lt;P data-unlink="true"&gt;Please note that otlp exporter expect a port at the end of the endpoint string (separated by column)&lt;/P&gt;&lt;P data-unlink="true"&gt;I appreciate if you could share an example config with otlp exporter (not otlphttp exporter) to be used to export traces to Dynatrace. Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2023 14:15:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204853#M30683</guid>
      <dc:creator>hamid</dc:creator>
      <dc:date>2023-02-15T14:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: opentelemetry collector config using otlp exporter for traces</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204921#M30684</link>
      <description>&lt;P&gt;The two error messages you posted would suggest a network issue. Did you verify if the network is working, in particular DNS?&lt;/P&gt;&lt;P&gt;Of course, it could also be a configuration issue, which breaks the hostname (and subsequently DNS resolution). I am not too familiar with the precise syntax of the configuration file and not entirely sure if &lt;EM&gt;endpoint&lt;/EM&gt; is supposed to point to a hostname or a URL.&lt;/P&gt;&lt;P&gt;If it is the latter, I'd assume your configuration is all right (though you said you want to use gRPC, right?). The second URL (with the path) should not be correct, however, as you need to specify the port after the hostname, not after path.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2023 07:24:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204921#M30684</guid>
      <dc:creator>alexander_dt</dc:creator>
      <dc:date>2023-02-16T07:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: opentelemetry collector config using otlp exporter for traces</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204933#M30688</link>
      <description>&lt;P&gt;I was just informed that the backend would not support gRPC yet, so you'd need to use HTTP, in which case &lt;EM&gt;endpoint&lt;/EM&gt; takes a proper URL, which should be the base one. Have you tried this already?&lt;/P&gt;&lt;P&gt;endpoint: https://{environmentid}.live.dynatrace.com:443/api/v2/otlp&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2023 09:13:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/204933#M30688</guid>
      <dc:creator>alexander_dt</dc:creator>
      <dc:date>2023-02-16T09:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: opentelemetry collector config using otlp exporter for traces</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/246628#M32493</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;I am setting up AWS Lambda monitoring using opentelemetry by following this doumentation:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/aws-lambda-otel-dotnet?_ga=2.54283752.1940541144.1716812393-1645813302.1716812393" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/aws-lambda-otel-dotnet?_ga=2.54283752.1940541144.1716812393-1645813302.1716812393&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;But this documentation does not cover how to send captured traces from AWS Lambda to Dynatrace endpoint.&lt;/P&gt;&lt;P&gt;Where I am supposed to add Dynatrace endpoint details?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 27 May 2024 12:24:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/opentelemetry-collector-config-using-otlp-exporter-for-traces/m-p/246628#M32493</guid>
      <dc:creator>AdilSaleem</dc:creator>
      <dc:date>2024-05-27T12:24:27Z</dc:date>
    </item>
  </channel>
</rss>

