Splunk Search

Continue on dbxquery Failure

ohbuckeyeio
Communicator

I have a search that performs a basic dbxquery connection and SQL search.  If the database table were to be dropped or there were any other errors encountered during the search, I would like the rest of the SPL to keep chugging along.

Is there a creative way to continue past the dbxquery error?

This is a simple example looking up an Oracle DB name:

 

| makeresults
| eval connection_name="<my db connection>"
| map search="| dbxquery connection=$connection_name$ query=\"select * from global_nameWRONG;\""
| eval test="didn't get here"
| table GLOBAL_NAME,test

 

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!

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

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 ...