Nagios configuration management

Agreed that its pretty hard to do without scripting.

For every service check command, I have defined (in a db table) what it typically depends on, which saves me from having to manually configure every service dependency. Host dependencies I do by hand, but doing mac address discovery on switches via a script is something that would help automate that.

examples:

"check_http_content" would depend on a "check_http" which would depend on a "check_ping".
"check_cisco_ifstate" would depend on a "check_snmp_ok" which would depend on a "check_ping"

If you build your config from a database using a script, this isn't too hard to implement. Otherwise, you would want to write a parser to go through your config file, and insert the dependencies based on the rules.

I can't imagine having any sizable nagios implementation without having a configuration database that you build your configs from, it allows you to add your own abstractions when nagios lacks them, and makes life simpler in many other ways.

I think the answer to your question is not definitive, but will reveal itself over time as you develop a deeper understanding of how Nagios works. Services are generally tied directly to the host they run on, but as you are discovering, that is just a convention. A convention that works and provides some shortcuts, mind you, but a convention, nonetheless.

Also know that that you can define any check as the host check. It does not need to be ping. Perhaps check_http is better for your use.

define host{
use         generic-host,host-pnp       ; Name of host template to use
host_name       www.microsoft.com
alias           www.microsoft.com
address         www.microsoft.com
check_command       check_http
.
.
.
}

Given what you've said, I would create a dummy service with a bunch of you third party services tied to it for now and adjust it as you see fit.

To address your 3rd question, if you go the route of a host per service, you could use a host or service group to group them for display.