More and more, we're seeing a couple opportunities in Davis for root cause analysis as well as within the Problem page to better display impacted services. In the attached example I'm showing a slowdown for a specific application SQL query for a specific database and the AI fails to highlight the specific service (backtrace) as a root cause or in the affected service.
We're trying to put some logic in the alerting as a work around to this, but in an environment with hundreds of databases and thousands of services querying these databases, we are looking for Davis/AI to simplify the step and remove the need to dive into the problem to find the impacted/root cause service.
This would save us continual workflow issues and remove a user error prone manual step.
Featured Posts
