<?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: Fetch enhanced endpoints in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301493#M3412</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;That usually means those requests are not promoted/classified as individual key requests/endpoints in the metric dimension, so Dynatrace groups them under NON_KEY_REQUESTS.&lt;/P&gt;&lt;P&gt;You can try filtering them out:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;timeseries requests = sum(dt.service.request.count),
by: { dt.entity.service, endpoint.name }
| filter dt.entity.service == "SERVICE-9C186B48B0905E85"
| filter endpoint.name != "NON_KEY_REQUESTS"
| sort arraySum(requests) desc&lt;/LI-CODE&gt;&lt;P&gt;But this will only show endpoints that Dynatrace exposes individually in endpoint.name.&lt;/P&gt;&lt;P&gt;If you need all raw request names/paths, you may need to query spans instead, because service request metrics can aggregate non-key requests into NON_KEY_REQUESTS.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jul 2026 10:12:54 GMT</pubDate>
    <dc:creator>t_pawlak</dc:creator>
    <dc:date>2026-07-02T10:12:54Z</dc:date>
    <item>
      <title>Fetch enhanced endpoints</title>
      <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301488#M3408</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;how can I fetch with a DQL query the endpoint of a service after enhancing the new feature of Enhanced Endpoints ?&lt;/P&gt;&lt;P&gt;Trying with&amp;nbsp;&lt;/P&gt;&lt;P&gt;fetch dt.entity.service_method&lt;/P&gt;&lt;P&gt;I get only the old key request, how can I query all the endpoint discovered on a service ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pasquale&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 09:22:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301488#M3408</guid>
      <dc:creator>tesp11331</dc:creator>
      <dc:date>2026-07-02T09:22:57Z</dc:date>
    </item>
    <item>
      <title>Re: Fetch enhanced endpoints</title>
      <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301490#M3410</link>
      <description>&lt;P&gt;hi,&lt;BR /&gt;try this:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;timeseries requests = sum(dt.service.request.count),
by: { dt.entity.service, endpoint.name }
| filter dt.entity.service == "SERVICE-9C186B48B0905E85"
| sort arraySum(requests) desc&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 10:03:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301490#M3410</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-07-02T10:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Fetch enhanced endpoints</title>
      <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301492#M3411</link>
      <description>&lt;P&gt;Hi, it works but I get many endpoint names as&amp;nbsp;NON_KEY_REQUESTS&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 10:09:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301492#M3411</guid>
      <dc:creator>tesp11331</dc:creator>
      <dc:date>2026-07-02T10:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: Fetch enhanced endpoints</title>
      <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301493#M3412</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;That usually means those requests are not promoted/classified as individual key requests/endpoints in the metric dimension, so Dynatrace groups them under NON_KEY_REQUESTS.&lt;/P&gt;&lt;P&gt;You can try filtering them out:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;timeseries requests = sum(dt.service.request.count),
by: { dt.entity.service, endpoint.name }
| filter dt.entity.service == "SERVICE-9C186B48B0905E85"
| filter endpoint.name != "NON_KEY_REQUESTS"
| sort arraySum(requests) desc&lt;/LI-CODE&gt;&lt;P&gt;But this will only show endpoints that Dynatrace exposes individually in endpoint.name.&lt;/P&gt;&lt;P&gt;If you need all raw request names/paths, you may need to query spans instead, because service request metrics can aggregate non-key requests into NON_KEY_REQUESTS.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 10:12:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301493#M3412</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-07-02T10:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: Fetch enhanced endpoints</title>
      <link>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301500#M3413</link>
      <description>&lt;P&gt;thank you, it is fine like that&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 10:45:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Fetch-enhanced-endpoints/m-p/301500#M3413</guid>
      <dc:creator>tesp11331</dc:creator>
      <dc:date>2026-07-02T10:45:35Z</dc:date>
    </item>
  </channel>
</rss>

