Then, which tables should be exposed to make OMD not to show the site dead?

Best regards

De: Andreas Döhler <andreas.doeh...@gmail.com>
Enviado: lunes, 12 de marzo de 2018 20:04
Para: José Damián
Cc: checkmk-en@lists.mathias-kettner.de
Asunto: Re: [Check_mk (english)] added a new LiveStatus site to the same nagios 

Hi José,

this will not work as you only expose the services and there only three columns.
Why you don't use the existing filters for views on the target OMD site? There 
are many options to filter the shown data.
Some examples
- create a clone of an existing view with a new id and hardcode your host prefix
- create a search with the host prefix and save the result as bookmark for all 
and so on


José Damián <jdbenav...@hotmail.com<mailto:jdbenav...@hotmail.com>> schrieb am 
Mo., 12. März 2018 um 16:20 Uhr:


My OMD/CheckMK has a site configured as a LiveStatus connection to the port 
6557 of a Nagios server. It works and shows all hosts and services from several 
months ago.

I want to create a new site to hold only the preproduction servers services of 
that same Nagios server. In order to get that:

1. In the Nagios server, I cloned the running   livestatus   xinetd service in 
order to use a filter and to provide the new output through another TCP port 
(6558). The filter is:

GET services

Columns: host_name description state

Filter: host_name ~~ pre

2. In the OMD server, I checked the new Livestatus xinetd service by creating a 
TCP connection using netcat -- It works:

nc x.x.x.x:6558

3. In the OMD server, I clonned the LiveStatus Site using the "Distributed 
Monitoring" WATO and set up the new TCP port, but it appears "dead", which I 
cannot understand.

Why? What am I doing wrong?

Thanks in advance

checkmk-en mailing list
checkmk-en Info Page - Mathias 
This list is intended for discussion between users check_mk. To see the 
collection of prior postings to the list, visit the checkmk-en Archives.

checkmk-en mailing list

Reply via email to