I had a poke around in Splunk Answers, but I couldn't find anything on this specifically.
I have a dashboard that has 8+ panels, with maybe more required. Each panel does something slightly different, but each uses the same search string (at least before the first pipe sign). For performance reasons, I'd like to be able to run the search only once for the dashboard (eg. as a base search), and then let the search in the other panels refer back to the initial search. However, I don't want to show the full (or any) results of the initial/base search in the first panel at the top of my dashboard. That is, I want the results of the base search to be "hidden", but accessible by the other searches lower down in the dashboard. I don't want to run the initial search as a saved search, I'd like it be available in (as close as possible to) real time.
Is this possible with Splunk?
... View more
We have some old DB Connect 1.2.2 inputs defined that need to migrated to DB Connect 3.1.4. In order to debug some weird issues between the two versions, I need to be able to see the exact SQL query that the DB Connect 1.2.2 is running.
I can see SQL queries running in DB Connect 3 in the log file $SPLUNK_HOME/var/log/splunk/splunk_app_db_connect_audit_server.log. I'm looking for similar logs in DB Connect 1.
I've read through the troubleshooting documentation for DB Connect 1.2.2.
I've increased the verbosity of the logging for SPLUNK_HOME/var/log/splunk/dbx.log in $SPLUNK_HOME/etc/apps/dbx/local/java.conf as follows:
level = DEBUG
file = dbx.log
console = false
logger.com.splunk.dbx = DEBUG
I can see where the input is getting kicked off periodically, but I can't see the actual SQL queries being run. Does anyone know how to configure this logging for DB Connect 1.2.2? I'd do a packet dump on the database session, but I don't have root access on this server to run tcpdump.
... View more