Weblog entry #3 for Wayne
What are you guys using and why?
Comments on this Entry
Otherwise, I am very happy with OpenNMS and am looking forward for 1.6.
[ Parent | Reply to this comment ]
How did you install, did you add the repositories and then install via apt?
I get the below dependency error when using apt-get install opennms*
The following packages have unmet dependencies.
opennms-webapp: Depends: libopennms-java (= 1.5.90-1) but 1.5.93-1 is to be installed
Depends: opennms-common (= 1.5.90-1) but 1.5.93-1 is to be installed
opennms-webapp-jetty: Conflicts: opennms-webapp but 1.5.90-1 is to be installed
opennms-webapp-standalone: Conflicts: opennms-webapp but 1.5.90-1 is to be insta
[ Parent | Reply to this comment ]
But I haven't tried installing the testing branch. I'm still on the stable branch, 1.2.9:
ii libopennms-java 1.2.9-1sarge open network monitoring and management appli
ii opennms 1.2.9-1sarge open network monitoring and management appli
ii opennms-common 1.2.9-1sarge open network monitoring and management appli
ii opennms-contrib 1.2.9-1sarge open network monitoring and management appli
ii opennms-db 1.2.9-1sarge open network monitoring and management appli
ii opennms-doc 1.2.9-1sarge open network monitoring and management appli
ii opennms-server 1.2.9-1sarge open network monitoring and management appli
ii opennms-webapp 1.2.9-1sarge open network monitoring and management appli
I know the packages say "sarge" on them but they work fine for Etch. (The 1.2 branch is pretty old.)
[ Parent | Reply to this comment ]
Nagios for me (and a coworker). Monitoring around 200 Linux, Windows, Solaris, and OS X hosts. As far as the pain of configuring it, that's somewhat reduced with use of object templates. Example (from host-types.cfg):
define host{
use generic-host
name router-switch
check_command check-host-alive
max_check_attempts 20
notification_interval 240
notification_period 24x7
notification_options d,u,r
register 0
}
define host{
use generic-host
name dummy
max_check_attempts 20
notification_interval 240
notifications_enabled 0
register 0
address 127.0.0.1
notification_period none
}
These are two templates for switches and routers (router-switch for layer 3 items, dummy for cheap dumb switches that don't have an actual IP address, but we include to divide up the status map a bit more). The generic-host template comes from the Debian generic-host_nagios2.cfg by default.We generally make one configuration file per room we have systems in. Example (from ch314.cfg):
define host{
use generic-host
name ch314-host
parents ch314-switch
contact_groups admins
register 0
}
# Individual host definitions
define host{
use dummy
host_name ch314-switch
alias CH314 Switch
parents ch302-switch
}
define host{
use ch314-host
host_name ch314a
address A.B.C.1
}
define host{
use ch314-host
host_name ch314b
address A.B.C.2
}
define host{
use ch314-host
host_name ch314c
address A.B.C.3
}
# Service definitions
define service{
use ping
hostgroup_name ch314
contact_groups admins
}
define service {
host_name ch314b, ch314c
service_description SSH
check_command check_ssh
use generic-service
notification_interval 0 ; set > 0 if you want to be renotified
contact_groups admins
}
# Dependencies
define servicedependency {
host_name ch314b
service_description PING
dependent_host_name ch314b
dependent_service_description SSH
execution_failure_criteria c
}
# Hostgroup definitions
define hostgroup {
hostgroup_name ch314
alias Clement Hall 314
members ch314a, ch314b, ch314c, ch314-switch
}
Granted, we could combine all the SSH-able servers everywhere into one central service definition, but for the number of systems we have and the rate of change required, this works for us. Generally we can just copy one room's config file to another name, edit accordingly, and continue.
[ Parent | Reply to this comment ]
Regards,
Adamantios
[ Parent | Reply to this comment ]