Monitoring Splunk

Is there a known bug in DB Connect causing scheduled jobs to run twice?

rajinovat
New Member

Is there known bug in DB Connect causing scheduled jobs to run twice.. We had an incident over the weekend and messed up the report showing doubled events

0 Karma

musskopf
Builder

Not that I know... but are you using DB Dump or DB Tail?

If you're using DB Tail, it stores the last value at $SPLUNK_HOME/var/lib/splunk/persistentstorage/dbx, where each DB Tail configuration has its own directory and it saves the value for the "tailing" process insice state.xml.

If the process failed in the middle or something happen where this file wasn't updated, the next run will insert duplicated entries.

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!