topic Re: Problems Application Summary in DQL

Generate Application Summary for Problems Using DQL

MarwanC — Wed, 17 Dec 2025 13:18:05 GMT

I am trying to extract valuable metrics that are a similar view in the application problem summary but I do not know where to extract these info from (see the screen shot)

Any DQL (or typescript) or any hint how extract this is much appreciated.

Marwan...

Re: Problems Application Summary

deni — Mon, 25 Aug 2025 22:16:23 GMT

Hi @MarwanC ,

I would suggest to start from here:

fetch dt.davis.problems | join [ fetch events ], on: { left[event.id] == right[event.id]}

If you give some more concrete example on what final table you expect to see I can try to help more.

Regards, Deni

Re: Problems Application Summary

MarwanC — Wed, 27 Aug 2025 10:01:03 GMT

Thank you Deni, I meant the name of the column for the exact metrics shown in the problems application

Re: Problems Application Summary

MarwanC — Fri, 29 Aug 2025 06:55:12 GMT

Thanks Deni, thanks for filling in the blanks, this is indeed what I was looking for for linking problems with number of events, and this DQL does the job now (I added the latest obe below) Hoever, I need all other data, affect infra, affected, services , SLO (see screen shot I provided above) per problem and I must have all the data in order to build the relevance model to a particular problem. I will share my finding for other to benefit, but for now here the problem vs events relevance metric, fetch dt.davis.problems
| join [
fetch events
], on: { left[event.id] == right[event.id]}
| fields event.kind, right.affected_entity_types, display_id
| summarize count(), by: display_id

Re: Problems Application Summary

MarwanC — Mon, 29 Sep 2025 10:01:30 GMT

Hi Deni, Any further thoughts on how to extract the table similar to the table in the problem application (see attached screenshot). Thanks for your support. The join is the key to resolve this puzzle 🙂