This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Abstract
Even though Dynatrace platform tries to identify the most relevant monitored entity to report log based event sometimes its behavior does not match your expectations and problems raised b...
Hi All, I've seen that in latest SaaS release, it was mentioned that problem comments can now be queried via DQL, I've been trying to find the field name through which comments can be accessed but f...
Self Service Summary A Kubernetes cluster has remained inactive for an extended period, leading to a problem card. The problem was manually closed, but after some time, another problem was created f...
Hello, As long as you can only use higher or lower in Davis anomaly detection, this could be a workaround. testing on status 4: timeseries myseries = avg(xxx.device.status),by: {`d...
Good morning.
I have an use case where I want to alert on custom topology (one-to-many relationships) while making use of Davis to "smartly" merge my alerts and somewhat understand root cause.
Co...
...herefore the detection condition is met.
The problem is that I can’t find this alert either in the Problems section or as a dt.davis.event / dt.davis.problem.
Our goal is to notify users whenever this c...
Good morning, So you have a title where you can not use {} A description you can not use {} And a event description where you can use {} I assume the the first two are just for documentation purp...
How do you get the Comments back in a DQL query when querying dt.davis.problems? I can see the comments in the UI for a given Problem but cannot see a column name that displays this data in DQL...
Hello,
Trying to create a anomaly detection, to keep it simple, cpu above 80% and dims:hosts.
So what is the elegant way to filter our a host. (or is that not possible without using segment...
our production application has issues with some functionalities.
after investigation, figured out it was related to oneagent.
relevant logs: [29.04.2025 08:06.59.288] [ERROR] /opt/dynatrace/onea...
