Let's get started.īefore you can monitor a service, you first need to define a host that is associated with the service. Each of these services can be monitored using one of the plugins that gets installed as part of the Nagios plugins distribution. I'll walk you through monitoring some basic services that you'll probably use sooner or later. Read the documentation on developing plugins for more information. Plugins are easy to write, so don't let this thought scare you off. If you don't happen to find an appropriate plugin for monitoring what you need, you can always write your own. The Nagios Exchange website hosts a number of additional plugins that have been written by users, so check it out when you have a chance. There are also a large number of contributed plugins that can be found in the contrib/ subdirectory of the plugin distribution. The official Nagios plugins distribution comes with plugins that can be used to monitor a variety of services and protocols. When you find yourself needing to monitor a particular application, service, or protocol, chances are good that a plugin exists to monitor it. The sample configuration entries below reference objects that are defined in the sample commands.cfg and localhost.cfg config files. Note: These instructions assume that you've installed Nagios according to the quickstart guide. For more information about monitoring services using SNMP, check out the documentation on monitoring switches and routers. The SNMP agent allows you to remotely monitor otherwise private (and inaccessible) information about the host. Tip: Occassionally you will find that information on private services and applications can be monitored with SNMP. More information on monitoring private services on different types of hosts can be found in the documentation on: This situation requires that an intermediary monitoring agent be installed on any host that you need to monitor such information on. These private services or attributes of hosts are not usually exposed to external clients. Examples of private services associated with hosts are things like CPU load, memory usage, disk usage, current user count, process information, etc. Private services, in contrast, cannot be monitored with Nagios without an intermediary agent of some kind. These services and applications, as well as their underlying protocols, can usually be monitored by Nagios without any special access requirements. There are many more public services that you probably use on a daily basis. Examples of public services include HTTP, POP3, IMAP, FTP, and SSH. By "public" I mean services that are accessible across the network - either the local network or the greater Internet. ![]() This document describes how you can monitor publicly available services, applications and protocols.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |