[ClusterLabs] VirtualDomain & "deeper" monitors - what/how?
kgaillot at redhat.com
Fri Apr 30 14:48:54 EDT 2021
On Fri, 2021-04-30 at 19:24 +0300, Andrei Borzenkov wrote:
> On 30.04.2021 17:57, Ken Gaillot wrote:
> > On Fri, 2021-04-30 at 11:00 +0100, lejeczek wrote:
> > > Hi guys
> > >
> > > I'd like to ask around for thoughts & suggestions on any
> > > semi/official ways to monitor VirtualDomain.
> > > Something beyond what included RA does - such as actual
> > > health testing of and communication with VM's OS.
> > >
> > > many thanks, L.
> > This use case led to a Pacemaker feature many moons ago ...
> > Pacemaker supports nagios plug-ins as a resource type (e.g.
> > nagios:check_apache_status). These are service checks usually used
> > with
> > monitoring software such as nagios, icinga, etc.
> The documentation for it is rather short. In particular ...
> > If the service being monitored is inside a VirtualDomain, named vm1
> > for
> > example, you can configure the nagios resource with the resource
> > meta-
> > attribute container="vm1". If the nagios check fails, Pacemaker
> > will
> > restart vm1.
> ... this is not documented anywhere.
> Is there any howto, blog or whatever with example usage and
Yep that little snippet is the only documentation. Documenting it
better has been on the to-do list forever but since I've never used the
feature, it would take up a lot of time experimenting before I felt
Pull requests welcome if anyone wants to dive in :)
> > (This feature was added before OS containers became popular, so the
> > naming is a bit unfortunate.)
> Manage your subscription:
> ClusterLabs home: https://www.clusterlabs.org/
Ken Gaillot <kgaillot at redhat.com>
More information about the Users