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.
