14 Dec 2023 09:00 PM
Problem are essentially what Dynatrace is designed to find and inform clients about. It's essentially the most basic and critical reason to own Dynatrace. The existing Problems page does not provide us what we need to research and analyze problems. Barely gives us what we need to organize and present live problems.
For the reason there is a history of such requests to expose Problem data more as metrics. And the reason myself and many clients export Problems into other tools so we can actually work with the data. DT Blog Post, "Using the consolidated API, I started to pull events and problems from all environments and store them in a time series database (influxDB)."
So, it's a little over the 1 year anniversary of this request. Any updates from DT (other than TypeScript in a Gen3 Workflow).
Asked 1 year ago
https://community.dynatrace.com/t5/Open-Q-A/Does-a-metric-exist-for-Problem-count/m-p/197976#M23183
Asked 2 years ago
Solved! Go to Solution.
12 Feb 2024 08:53 PM
@ct_27 yeah that would be a great enhancement. It would be nice to really pull out some of this Problem data to help formulate yearly or even quarterly reviews pertaining to Problems and the associated statistics.
13 Feb 2024 01:05 PM
No TypeScript but dql you can use in a Dashboard
fetch events, from:$dt_timeframe_from, to:$dt_timeframe_to
| filter event.kind == "DAVIS_PROBLEM"
| summarize {activeEvents = countDistinct(event.id), by: {`10m interval` = bin(timestamp, 10m)}}