Reporting

Splunk DB Connect 1: Can I run dbquery with a variable?

stepheneardley
Path Finder

I need to schedule a report which runs dbquery, but I need that report to run with a variable in the query e.g.

| eval myVar=stuff
| dbquery source "select * from table where timestamp >= '".myVar."'"

Or something like that, but of course this doesn't work since dbquery must be the first command of a search.

Has anyone come across this before or found a way around it?

0 Karma
1 Solution

somesoni2
Revered Legend

You can try like this (using map command)

| gentimes start=-1 | eval myVar=stuff | map search="| dbquery source \"select * from tble where timestamp >= $myVar$ \" "

View solution in original post

0 Karma

somesoni2
Revered Legend

You can try like this (using map command)

| gentimes start=-1 | eval myVar=stuff | map search="| dbquery source \"select * from tble where timestamp >= $myVar$ \" "
0 Karma

stepheneardley
Path Finder

Worked a treat. Thanks. I can't figure out what gentimes is used for though.

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!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...