When you set up monitoring, you define the environment required for ensuring that the Boxes deployed on the EV Observe platform works correctly and as such, that the platform is running smoothly.

• You do this using dedicated host templates that check the most important Box resources.  See the description

• This implemented in two steps:
  • Check if the Box system works correctly. Self-monitoring of a Box is performed using the dedicated host template called EVObserve Box-Self monitoring.
  • Check if the Box can be reached from the EV Observe platform and if it is able to report data. EVObserve Box-Monitoring by other Box is performed using the dedicated host template called EVObserve Box-Self monitoring.

Operating principle

Display	Steps
	(1) A monitoring agent known as the supervisor is used to monitor all other components on the EV Observe platform. (2) To ensure that the supervisor remains operational, it must be cross-monitored by another monitoring agent known as the sentinel.

Caution

• Each customer is in charge of the monitoring and maintenance of the Boxex.
• One Box must never monitor another Box because in the event of an incident, you would not receive a warning.

What are the resources to be monitored?

Resources to be monitored when self-monitoring of a Box

You must monitor the following usage using the EVObserve Box-Self monitoring template:

• CPU load
  • Insufficient CPU will cause instability in the Box and slow down the running of services.
  • There should be approximately 1 vCPU for 1,000 services. You must adapt this based on the number of services used.

• RAM
  • Insufficient RAM can prevent the running of services, cause disruption to the nagios and openvpn services and interrupt monitoring.

• Disk space
  • When there is insufficient disk space, the system file is accessible only in read mode. This causes instability and interrupts monitoring.
     

Resources to be monitored when cross-monitoring of a Box

You must ensure that the monitored Box collects and sends monitored data at regular intervals, every X minutes. This is the role of the Box-Live-Status service in the EVObserve Box-Monitoring by other Box host template.

• If the status changes to Critical, this means that the monitored Box is no longer sending data to the central platform.
• In this case, Web app statuses will no longer be up-to-date and you must act quickly to reestablish communication.

Procedures

How to set up monitoring for a Box

Step 1: Set up self-monitoring for the Box

1. Go to the Web app.

2. Run a discovery.

• Select Configure > Hosts > Discovery in the menu.

• Specify the discovery information as shown below.
  • IP address: 127.0.0.1
  • SNMP community: coservit

• Click Discover.

If a host is detected, the discovery will be completed successfully.

3. Add the Box as a new host.

• Click + Add to monitoring.

• Use the dedicated host template to set up self-monitoring for the Box.
  • Host category: Select the Monitoring Box category.
  • Template: Select the EVObserve Box-Self monitoring template.

• Click Validate.

4. Reload the configuration of the new Box.

5. Check that data is correctly sent by the Web app.
 

Step 2: Cross-monitor the Box

1. Add a host that will be specifically dedicated to cross-monitoring the new Box.

• Select Configure > Hosts > List in the menu.

• Click + Add.

• Specify the information below.
  • Host name: Enter the following name, {Box_Name} monitoring.
    Replace {Box_Name} with the name of the Box you want to monitor as specified in step 1.
     
  • IP/DNS address: Enter the IP address of the VPN.
  • Monitored by: Select the shared monitoring server hosted at your site.

• Use the dedicated host template to set up cross-monitoring for the Box.
  • Host category: Select the Monitoring Box category.
  • Template: Select the EVObserve Box-Monitoring by other Box template.

• Click Validate.