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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...