Join the Conversation
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- All Apps and Add-ons
- :
- Re: DB Connect V2 Execution Frequency
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk DB Connect V2 Execution frequency
In the splunk DB connect V2, there is an option during DB Input called Execution
Frequency. I always had 120 seconds as the Execution frequency. I didnt have
any issues with it. recently it has been ingesting the same data over and over
again every 2 minutes. I had to change it to a very large number (i.e. 31104000).
Now it stopped ingesting the same data again and again.
As far as I can remember, this was working fine with 120 seconds before, has
anyone had the same issue with the Splunk DB Connect V2 ? I am using it to connect to postgresql.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you only need to do it once, then set it up, let it run, and then disable it. Otherwise, it will run every time execution frequency time passes.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you only need to do it once, then set it up, let it run, and then disable it. Otherwise, it will run every time execution frequency time passes.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I disabled the index, now I cannot search the data in query
How can I disable the index and still search the data.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Don't disable the index, disable the input.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks I did just that, disabled DB Input in Splunk DB Connect V2. So far I do not see anymore new data ingestions, I will wait a bit hope this fixes it. Thanks!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK seems this also doesnt work, currently its re-indexing the same data, in my search query I see duplicate events, the longer I wait the more duplicate data is ingested
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
How to find the worst searches in your Splunk environment and how to fix them
Share Your Feedback: On Admin Config Service (ACS)!
Build the Future of Agentic AI: Join the Splunk Agentic Ops Hackathon
