<?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 Give a service, find if calling service having problem in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/Give-a-service-find-if-calling-service-having-problem/m-p/292948#M3034</link>
    <description>&lt;DIV&gt;
&lt;P&gt;I’m looking for guidance on creating a DQL query for as dashboard that can:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Take a given list of services.&lt;/LI&gt;
&lt;LI&gt;Identify their associated upstream and downstream dependencies.&lt;/LI&gt;
&lt;LI&gt;Display any alerts (active, or closed) that are impacting or affecting these services.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;The goal is to have a clear view of service relationships and understand how alerts propagate across dependencies. If anyone has an example query or best practices for achieving this in Dynatrace, I’d greatly appreciate your input.&lt;BR /&gt;Here my attempt look for at problem in upstream services.&lt;/P&gt;
&lt;/DIV&gt;
&lt;LI-CODE lang="javascript"&gt;fetch dt.entity.service 
//|filter in(id, "SERVICE-24844D84E75DDE51", "SERVICE-96A302DC14A0CCE9") // dashboard varaible
|fieldsAdd upstream_ids = called_by[dt.entity.service]
|expand upstream_id = upstream_ids // upstream_id = Caller_id
// Get associated upstream service
| lookup [fetch dt.entity.service | fieldsAdd managementZones ], sourceField:upstream_id, lookupField:id, executionOrder:leftFirst, prefix: "Caller_"

// Get problem assoicated(impacting or affecting) these upstream services
// this is where I need help, I'm getting null 
| lookup [fetch dt.davis.problems ], //| filter affected_entity_types == array(called_by[dt.entity.service]) | expand affected_entity_ids ]
         sourceField:Caller_id, lookupField:id, executionOrder:leftFirst, prefix: "Alert_"
          
| fields managementZones, entity.name, id, Caller_id,
Caller_entity.name,
Caller_managementZones, Alert_name, Alert_display_id

|sort entity.name&lt;/LI-CODE&gt;</description>
    <pubDate>Wed, 14 Jan 2026 07:53:13 GMT</pubDate>
    <dc:creator>PVThach</dc:creator>
    <dc:date>2026-01-14T07:53:13Z</dc:date>
    <item>
      <title>Give a service, find if calling service having problem</title>
      <link>https://community.dynatrace.com/t5/DQL/Give-a-service-find-if-calling-service-having-problem/m-p/292948#M3034</link>
      <description>&lt;DIV&gt;
&lt;P&gt;I’m looking for guidance on creating a DQL query for as dashboard that can:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Take a given list of services.&lt;/LI&gt;
&lt;LI&gt;Identify their associated upstream and downstream dependencies.&lt;/LI&gt;
&lt;LI&gt;Display any alerts (active, or closed) that are impacting or affecting these services.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;The goal is to have a clear view of service relationships and understand how alerts propagate across dependencies. If anyone has an example query or best practices for achieving this in Dynatrace, I’d greatly appreciate your input.&lt;BR /&gt;Here my attempt look for at problem in upstream services.&lt;/P&gt;
&lt;/DIV&gt;
&lt;LI-CODE lang="javascript"&gt;fetch dt.entity.service 
//|filter in(id, "SERVICE-24844D84E75DDE51", "SERVICE-96A302DC14A0CCE9") // dashboard varaible
|fieldsAdd upstream_ids = called_by[dt.entity.service]
|expand upstream_id = upstream_ids // upstream_id = Caller_id
// Get associated upstream service
| lookup [fetch dt.entity.service | fieldsAdd managementZones ], sourceField:upstream_id, lookupField:id, executionOrder:leftFirst, prefix: "Caller_"

// Get problem assoicated(impacting or affecting) these upstream services
// this is where I need help, I'm getting null 
| lookup [fetch dt.davis.problems ], //| filter affected_entity_types == array(called_by[dt.entity.service]) | expand affected_entity_ids ]
         sourceField:Caller_id, lookupField:id, executionOrder:leftFirst, prefix: "Alert_"
          
| fields managementZones, entity.name, id, Caller_id,
Caller_entity.name,
Caller_managementZones, Alert_name, Alert_display_id

|sort entity.name&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 14 Jan 2026 07:53:13 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Give-a-service-find-if-calling-service-having-problem/m-p/292948#M3034</guid>
      <dc:creator>PVThach</dc:creator>
      <dc:date>2026-01-14T07:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: Give a service, find if calling service having problem</title>
      <link>https://community.dynatrace.com/t5/DQL/Give-a-service-find-if-calling-service-having-problem/m-p/293761#M3088</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/94299"&gt;@PVThach&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;fetch dt.entity.service&lt;BR /&gt;| expand downstream_service = calls[dt.entity.service]&lt;BR /&gt;| fieldsAdd downstream_service_name = entityName(downstream_service, type:"dt.entity.service")&lt;BR /&gt;| expand upstream_service = called_by[dt.entity.service]&lt;BR /&gt;| fieldsAdd upstream_service_name = entityName(upstream_service, type:"dt.entity.service")&lt;BR /&gt;| lookup&amp;nbsp;&lt;BR /&gt;[&lt;BR /&gt;fetch dt.davis.problems&lt;BR /&gt;| expand affected_entity_ids&lt;BR /&gt;], sourceField:id, lookupField:affected_entity_ids, prefix:"problem."&lt;BR /&gt;| fieldsAdd problem_id = problem.display_id&lt;BR /&gt;| fields entity.name, upstream_service_name, downstream_service_name, problem_id, managementZones&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Feel free to modify it further based on your requirements.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 12:20:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Give-a-service-find-if-calling-service-having-problem/m-p/293761#M3088</guid>
      <dc:creator>raksh_hitha</dc:creator>
      <dc:date>2026-01-28T12:20:08Z</dc:date>
    </item>
  </channel>
</rss>

