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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...