Hello, thanks for this.
I think that we could probably make that work for us in lieu of DB registered pollers.
Two questions: will the patch work for the current poller-wrapper? And how far along are registered pollers in the database? i.e. is
this something that’s likely to come along shortly? If not I think we will try a deployment with the patch.
Regards
|
|
Richard Wigzell 13 Banbury Road, Oxford OX2 6NN
|
From: observium [mailto:observium-bounces@observium.org]
On Behalf Of Markus Klock
Sent: 09 January 2018 13:53
To: Observium <observium@observium.org>
Subject: Re: [Observium] exclude or skip wildcard match for poller and discovery
I was aware of this use case when I wrote the guide and made a patch that solves this case.
Basically I modified the poller-wrapper.py to accept group-ids and poll a specific group only.
You can then create a host-group in observium for the remote poller to poll and create another group with "all other hosts" and have poller 1 and poller 2 poll that group instead. Just make sure that all your hosts are in some of these
two groups to have them all polled.
The patch was not accepted however as the main plan is to register pollers in the database and be able to control this via Observium in a more controlled manner.
If you want to try it either way you can find the patch here: http://jira.observium.org/browse/OBS-2245
/Markus