All Apps and Add-ons

Splunk DB Connect 2: How to troubleshoot why Health Monitoring stopped generating results?

imanpoeiri
Communicator

Hi Experts,

I notice another problem on Splunk DB Connect 2 where the health monitoring stops generating results. Current recorded transactions count is 3084 hits.

This causes difficulties to monitor the performance of the SQL and the errors that may occur during the time queries are executed.

Any idea how do I enable this back or clear the past transactions if that would help to bring back the health monitoring?

Cheers!

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

There are too many potential problems to guess at.

0 Karma

bworrellZP
Communicator

Having the same issues. The older events show as connected to health.py, new ones do not. Any thought on where to change it?

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...