topic Re: Difference between OPEN and ACTIVE statuses in Alerting

Difference between OPEN and ACTIVE statuses

wmisenhe — Wed, 25 Sep 2024 07:34:09 GMT

On the problem page in DT, we see the OPEN problems highlighted in red, and the greyed-out problems, implying they are closed. However, in dql queries, some of these grey problems' event.status is ACTIVE, even though they are not OPEN. I am trying to build a dashboard for problems, similar to the problems page, but with information we want beside the current, OPEN, red highlighted problems in DT.

Or is there a parameter that DT uses to differentiate between OPEN and ACTIVE

This is an example. It is greyed-out on the Problems page, however it is still technically ACTIVE.

On this example, the event.status_transition is UPDATED

Thank you in advance

Re: Difference between OPEN and ACTIVE status' in Dt

p_devulapalli — Thu, 05 Sep 2024 08:04:17 GMT

May be it could be that the problem is closed (manually or auto resolution based on some conditions etc.,) but the related event is still active in dynatrace? Can you please check if that is the case with this problem?

Re: Difference between OPEN and ACTIVE statuses

GosiaMurawska — Tue, 17 Dec 2024 10:21:07 GMT

Hi @wmisenhe, did you solve this problem? it would be great if you share it with the Community 🙂

Re: Difference between OPEN and ACTIVE statuses

wmisenhe — Thu, 19 Dec 2024 15:17:23 GMT

so we got around this by querying the dt.davis.problems and looking for "ACTIVE"
fetch dt.davis.problems
| filter event.status == "ACTIVE"
we were looking for Pcards that were currently active (red highlighted) and what they were to express them in a table for a dashboard. We had to do a lot more to show WHAT is was affecting, name, and time. Specifically expanding the array, joining, fetching, and appending the information we were looking for. But it looks nice and worked out