All Apps and Add-ons

How to debug Splunk DB Connect 2?

wegscd
Contributor

I am getting some inputs converted from Splunk DB Connect 1 to Splunk DB Connect 2.

I have a tail rising column query (using a timestamp field in the database) that I got into V2 and got it working. I did some refinements, but now no more data is showing up in the index.

I can see the query running in rpc.log, though I have no idea of how many rows are getting returned. The tail_rising_column_checkpoint_value is such that I would be expecting more data.

Is there some logging I can crank up on the Splunk end to determine if the data is getting returned from the query and lost on the way to the index, or if the query is not returning any rows???

0 Karma
1 Solution

woodcock
Esteemed Legend

There is a dbx2.log in the $SPLUNK_HOME/var/log*/ directory on the server where you are running the app. Tjis log is not forwarded so you have to go CLI.

0 Karma

wegscd
Contributor

dbx2.log has even less information in it than rpc.log. Just shows database errors and websocket timeouts.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...