If you're interested in a monitoring solution for your organization, you might find
Nagios XI to be a bit more accessible than Nagios Core. You can also get a free 1-hour consultation with a support technician by signing up for a Quickstart:
https://www.nagios.com/services/quickstart/
As a note, they do not offer quickstarts for Nagios Core; Just Nagios XI. It might also be worthwhile to spend some time understanding the different Nagios configuration objects:
https://assets.nagios.com/downloads/nag ... tions.html
Nagios configuration objects are the "building blocks" of how Nagios understands the infrastructure you want to monitor. Understanding them is critical in getting the most out of the software.
Here's the default Nagios Core contacts sample:
Code: Select all
###############################################################################
# CONTACTS.CFG - SAMPLE CONTACT/CONTACTGROUP DEFINITIONS
#
#
# NOTES: This config file provides you with some example contact and contact
# group definitions that you can reference in host and service
# definitions.
#
# You don't need to keep these definitions in a separate file from your
# other object definitions. This has been done just to make things
# easier to understand.
#
###############################################################################
###############################################################################
###############################################################################
#
# CONTACTS
#
###############################################################################
###############################################################################
# Just one contact defined by default - the Nagios admin (that's you)
# This contact definition inherits a lot of default values from the 'generic-contact'
# template which is defined elsewhere.
define contact{
contact_name nagiosadmin ; Short name of user
use generic-contact ; Inherit default values from generic-contact template (defined above)
alias Nagios Admin ; Full name of user
email nagios@localhost ; <<***** CHANGE THIS TO YOUR EMAIL ADDRESS ******
}
###############################################################################
###############################################################################
#
# CONTACT GROUPS
#
###############################################################################
###############################################################################
# We only have one contact in this simple configuration file, so there is
# no need to create more than one contact group.
define contactgroup{
contactgroup_name admins
alias Nagios Administrators
members nagiosadmin
}
Though, the above contact object references the "generic-contact" template, so you will need to make sure that template exists somewhere. Here's the one I currently have:
Code: Select all
define contact{
name generic-contact ; The name of this contact template
service_notification_period 24x7 ; service notifications can be sent anytime
host_notification_period 24x7 ; host notifications can be sent anytime
service_notification_options w,u,c,r,f,s ; send notifications for all service states, flapping events, and scheduled downtime events
host_notification_options d,u,r,f,s ; send notifications for all host states, flapping events, and scheduled downtime events
service_notification_commands notify-service-by-email ; send service notifications via email
host_notification_commands notify-host-by-email ; send host notifications via email
register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL CONTACT, JUST A TEMPLATE!
}
So you might want to add the admins
contactgroup to your environment, if you intend to use it.