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
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

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

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...