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!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...