<?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 Use OTel Attributes as request names in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Use-OTel-Attributes-as-request-names/m-p/270817#M35797</link>
    <description>&lt;P&gt;I have a service that uses that same URL for every request, even though every request is not doing the same thing.&amp;nbsp; The good news is that we have been able to apply Otel instrumentation to the service and can see a span in our traces that tells us more specifically what the request is.&amp;nbsp; The bad news is that you can only really see this data within a single trace.&amp;nbsp; I would like to use the Otel attribute value as the service request name, can this be done?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Mar 2025 07:41:48 GMT</pubDate>
    <dc:creator>gdalessandro</dc:creator>
    <dc:date>2025-03-10T07:41:48Z</dc:date>
    <item>
      <title>Use OTel Attributes as request names</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Use-OTel-Attributes-as-request-names/m-p/270817#M35797</link>
      <description>&lt;P&gt;I have a service that uses that same URL for every request, even though every request is not doing the same thing.&amp;nbsp; The good news is that we have been able to apply Otel instrumentation to the service and can see a span in our traces that tells us more specifically what the request is.&amp;nbsp; The bad news is that you can only really see this data within a single trace.&amp;nbsp; I would like to use the Otel attribute value as the service request name, can this be done?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 07:41:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Use-OTel-Attributes-as-request-names/m-p/270817#M35797</guid>
      <dc:creator>gdalessandro</dc:creator>
      <dc:date>2025-03-10T07:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: Use OTel Attributes as request names</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Use-OTel-Attributes-as-request-names/m-p/271916#M35933</link>
      <description>&lt;P&gt;&amp;nbsp;It looks like there are some hard limits currently around &lt;A href="https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-detection-and-naming/service-types/unified-service#endpoint-detection" target="_self"&gt;endpoint naming&lt;/A&gt; for unified services. Fingers crossed that OpenPipeline will soon gain the ability to modify span data on arrival. Perhaps post this type of functionality as a product idea..&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 21:18:45 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Use-OTel-Attributes-as-request-names/m-p/271916#M35933</guid>
      <dc:creator>marco_irmer</dc:creator>
      <dc:date>2025-03-07T21:18:45Z</dc:date>
    </item>
  </channel>
</rss>

