Splunk Search

dbConnect sinkhole not working for dbmon directory

shou
Explorer

I'm using dbConnect, and my $SPLUNK_HOME/var/spool/dbmon directory is filling up with old data. I've checked dbx/local/inputs.conf and the move policy value is set to sinkhole. We have another Splunk environment with the same config parameters that seems to be maintaining the dbmon directory correctly. What else can I look at?

Here's the stanza from inputs.conf:

[batch://$SPLUNK_HOME/var/spool/dbmon/*.dbmonevt]
crcSalt =
disabled = 0
move_policy = sinkhole
sourcetype = dbmon:spool

Tags (1)

shou
Explorer

The "Answer Your Own Question" button isn't working for me for some reason, so posting this here:

Turns out this is a result of slower indexer performance in the environment exhibiting this behavior combined with a large amount of data generated by this query. Waiting long enough caused the data to be indexed and deleted as expected.

0 Karma

splunkIT
Splunk Employee
Splunk Employee

Generally splunk would delete the file one they have been indexed. Can you confirm whether the files have already been indexed? Also check the splunkd.log for relevant errors.

0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...