Getting Data In

Splunk DB Connect: How do dbmon tail inputs work when configured on a search head cluster or pool?

Lucas_K
Motivator

How do dbmon tailing inputs work when they are configured on a search head cluster (or pool).

I thought as they are part of inputs.conf then each search head should be performing them. This is un-like a savedsearch in which the scheduler should allocate the job (shc) or the first in a pool to lock the job will be the one to run it.

I'm just looking at migrating some configuration to a search head cluster and this particular issue popped up and i'm not sure what would actually occur. My guess is that there would be duplicate data within the destination dbmon index.

jcoates_splunk
Splunk Employee
Splunk Employee

Hi, DB Connect 1.1.x is supported on Search Head Pool, but not on Search Head Cluster.
I think that you're correct, and in a pool only one member will run jobs... the docs only discuss installation though, not results.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...