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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...