<?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: DQL query for RPC ServiceEndpoint and ChannelEndPoint in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/275002#M1933</link>
    <description>&lt;P&gt;It should be due data protection reason. In this way you can mark the request attribute as sensitive data and only allowed users can view the value. Another example is if you don’t want to store the data in Dynatrace anymore, you don’t need to change the code and restart the application, with all complication.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Apr 2025 21:28:25 GMT</pubDate>
    <dc:creator>yanezza</dc:creator>
    <dc:date>2025-04-11T21:28:25Z</dc:date>
    <item>
      <title>DQL query for RPC ServiceEndpoint and ChannelEndPoint</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274623#M1922</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;
&lt;P&gt;I am using OneAgent SDK in Java to trace some RPC-like spans, and I want to find them later with DQL using a "fetch".&lt;BR /&gt;&lt;BR /&gt;My snippet with the OneAgent SDK is this:&lt;/P&gt;
&lt;LI-CODE lang="java"&gt;        OutgoingRemoteCallTracer tracer = OneAgentSdkSingleton.getInstance().traceOutgoingRemoteCall(
                method,
                "Foo",
                bar.getBar1(),
                ChannelType.OTHER,
                bar.getBar2());&lt;/LI-CODE&gt;
&lt;P&gt;and with a simple "fetch spans" I can find the spans just right, but I absolutely cannot find the value of getBar1() (ServiceEndpoint) and getBar2() (ChannelEndPoint) for the RPC call span.&lt;BR /&gt;&lt;BR /&gt;Any idea on where can I find those values?&lt;BR /&gt;&lt;BR /&gt;thanks&lt;/P&gt;</description>
      <pubDate>Wed, 09 Apr 2025 11:56:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274623#M1922</guid>
      <dc:creator>bonelli</dc:creator>
      <dc:date>2025-04-09T11:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: DQL query for RPC ServiceEndpoint and ChannelEndPoint</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274830#M1925</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;Have you tried to report and capture request attributes?&lt;BR /&gt;&lt;A href="https://www.dynatrace.com/news/blog/capture-any-request-attributes-using-oneagent-sdk/" target="_blank"&gt;https://www.dynatrace.com/news/blog/capture-any-request-attributes-using-oneagent-sdk/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Apr 2025 07:47:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274830#M1925</guid>
      <dc:creator>yanezza</dc:creator>
      <dc:date>2025-04-10T07:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: DQL query for RPC ServiceEndpoint and ChannelEndPoint</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274967#M1929</link>
      <description>&lt;P&gt;thank you&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/47327"&gt;@yanezza&lt;/a&gt;&amp;nbsp;, yes we did work around it with a request attribute inside the scope of the tracer, and it works.&lt;BR /&gt;But it feels like a workaround, even if it is a nice one: why can't I get those precise fields out with DQL, since I can get everything else just fine?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 12:34:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/274967#M1929</guid>
      <dc:creator>bonelli</dc:creator>
      <dc:date>2025-04-11T12:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: DQL query for RPC ServiceEndpoint and ChannelEndPoint</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/275002#M1933</link>
      <description>&lt;P&gt;It should be due data protection reason. In this way you can mark the request attribute as sensitive data and only allowed users can view the value. Another example is if you don’t want to store the data in Dynatrace anymore, you don’t need to change the code and restart the application, with all complication.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 21:28:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-query-for-RPC-ServiceEndpoint-and-ChannelEndPoint/m-p/275002#M1933</guid>
      <dc:creator>yanezza</dc:creator>
      <dc:date>2025-04-11T21:28:25Z</dc:date>
    </item>
  </channel>
</rss>

