Splunk Search

Is it possible to time out a dbquery operation?

VMDX
Engager

We want to protect our underlying database against dangerous operations, but also want to retain the flexibility of allowing the use of dbquery.

We've implemented a query killer on the database side, but it looks like the java bridge swallows up that error and doesn't expose it except in logs, which means a select * from table shows up as completed, with no errors, but only containing some of the rows in the table... seems like a dangerous non-error.

Is there any way we can time out a dbquery operation from the Splunk side?

Tags (1)
1 Solution

araitz
Splunk Employee
Splunk Employee

Not today, but we'll work on something for a future release.

View solution in original post

0 Karma

araitz
Splunk Employee
Splunk Employee

Not today, but we'll work on something for a future release.

0 Karma
Get Updates on the Splunk Community!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...