Re: [Nagios-devel] Hosts and Services
Posted: Fri Jun 17, 2005 1:37 pm
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
---1463810816-993735849-1119044212=:30092
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
The model for hosts and services exist separately such that if one of a=20
number of services fails on a host, the host check command is used to=20
verify if the host is up/down before checking all the other services.
Similarly if a host is down, parent hosts are checked to see if the path=20
to host is down or just the target host. This is also done using the host=
=20
check_command.
So while it might look redundant from a data model perespective - it=20
actually is quite useful.
-sg
On Fri, 17 Jun 2005, craig cook wrote:
> I've been poking around the data model for nagios 2.x recently and from
> what I can see the =E2=80=9Ccheck_command=E2=80=9D and related variables =
in the =E2=80=9Cdefine
> host{=E2=80=9C section are actually redundant...
>
>
> Should those variables be removed and let the =E2=80=9Cdefine service{=E2=
=80=9D section
> handle =E2=80=9Ccheck_commands=E2=80=9D?
>
>
> e.g.
>
> define host {
>
> host_name linux-server
> address 10.0.0.1
> parents linux-server2
> hostgroups web-servers
> check_command ping-linux-servers
> contact_group linux-admins
> [snip]
> }
>
>
> should actually become something like
>
>
> define host {
> host_name linux-server
> address 10.0.0.1
> parents linux-server2
> hostgroups web-servers
> }
>
>
> define service {
> service ping-linux-servers
> check_command_line ping ...
> }
>
>
> define host_service {
> host_name linux-server
> service ping-linux-servers
> contact_group linux-admins
> }
>
>
> (more of a relational way of thinking)
>
>
> For host =E2=80=9Ccontact_groups=E2=80=9D you do not actually get contact=
ed when a host
> fails, it is actually a =E2=80=9Cservice=E2=80=9D that has executed and f=
ailed on that
> host. If the =E2=80=9Chost check_command=E2=80=9D was removed, this would=
be a little
> clearer.
>
>
> Comments?
>
>
> (If this is as clear a mud I'll try and explain it a different way)
>
>
> Craig Cook
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=CCk
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
--=20
---1463810816-993735849-1119044212=:30092--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
while the remaining parts are likely unreadable without MIME-aware tools.
---1463810816-993735849-1119044212=:30092
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
The model for hosts and services exist separately such that if one of a=20
number of services fails on a host, the host check command is used to=20
verify if the host is up/down before checking all the other services.
Similarly if a host is down, parent hosts are checked to see if the path=20
to host is down or just the target host. This is also done using the host=
=20
check_command.
So while it might look redundant from a data model perespective - it=20
actually is quite useful.
-sg
On Fri, 17 Jun 2005, craig cook wrote:
> I've been poking around the data model for nagios 2.x recently and from
> what I can see the =E2=80=9Ccheck_command=E2=80=9D and related variables =
in the =E2=80=9Cdefine
> host{=E2=80=9C section are actually redundant...
>
>
> Should those variables be removed and let the =E2=80=9Cdefine service{=E2=
=80=9D section
> handle =E2=80=9Ccheck_commands=E2=80=9D?
>
>
> e.g.
>
> define host {
>
> host_name linux-server
> address 10.0.0.1
> parents linux-server2
> hostgroups web-servers
> check_command ping-linux-servers
> contact_group linux-admins
> [snip]
> }
>
>
> should actually become something like
>
>
> define host {
> host_name linux-server
> address 10.0.0.1
> parents linux-server2
> hostgroups web-servers
> }
>
>
> define service {
> service ping-linux-servers
> check_command_line ping ...
> }
>
>
> define host_service {
> host_name linux-server
> service ping-linux-servers
> contact_group linux-admins
> }
>
>
> (more of a relational way of thinking)
>
>
> For host =E2=80=9Ccontact_groups=E2=80=9D you do not actually get contact=
ed when a host
> fails, it is actually a =E2=80=9Cservice=E2=80=9D that has executed and f=
ailed on that
> host. If the =E2=80=9Chost check_command=E2=80=9D was removed, this would=
be a little
> clearer.
>
>
> Comments?
>
>
> (If this is as clear a mud I'll try and explain it a different way)
>
>
> Craig Cook
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=CCk
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
--=20
---1463810816-993735849-1119044212=:30092--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]