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!

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Get the T-shirt to Prove You Survived Splunk University Bootcamp

As if Splunk University, in Las Vegas, in-person, with three days of bootcamps and labs weren’t enough, now ...

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...