Modules in Monitoring

Tornado

Analyze data received from your devices, process and generate actions to be executed

Director

A single place to configure your monitoring environment

Monitoring

Keep under control your company’s infrastructure on multiple levels.

Active Monitoring

With the Active Monitoring you can check the availability of your network resources, notify users of outages, and generate performance data for reporting.

Due to scalability and extensibility, Active Monitoring can be performed on large and complex environments across multiple locations.

With the help of NetEye’s Active Monitoring you can check availability of hosts and services, e.g. network services (HTTP, SMTP, SNMP, SSH, etc.), printers, switches or routers, temperature sensors, and other local or network-accessible services.

NetEye builds around Icinga and Icinga Web 2. You can learn more about this in a dedicated Monitoring Environment section.

With the help of NetEye’s Icinga Director you can define the resources you want to be monitored, set alerts for when something goes wrong, or even schedule downtime. Check out all options in the Director and enjoy your monitoring experience.

Passive Monitoring

NetEye’s monitoring strategy incorporates both Active and Passive Monitoring approaches. While Active Monitoring allows you to proactively monitor your infrastructure, a solution that performs Passive Monitoring creates a complete view of your infrastructure state, performance, and behavior, without actively interacting with it.

In the process of Passive Monitoring, NetEye will analyze the data received from your devices, process it and then, if required, generate and execute actions based on your needs and preferences.

Passive Monitoring proves to be useful when monitored devices and infrastructure do not support an agent for Active Monitoring, and it is possible to tune them to send particular events to NetEye for subsequent processing.

Passive Monitoring is more resource-efficient compared to Active Monitoring. It consumes minimal resources as it works with existing data flows. Additionally, it doesn’t introduce additional traffic or load. This makes it perfectly suitable for critical production environments where minimizing disruption is crucial.

To assist in running Passive Monitoring processes, i.e. receiving data from various sources without implementing custom processors, Tornado software was integrated into NetEye.

Tornado, a Complex Event Processor, receives reports of events from data sources such as monitoring, email, and telegram, matches them against pre-configured rules, and executes the actions associated with those rules. These may include sending notifications, logging to files, and annotating events in a time series graphing system.

Self Monitoring

In order to provide a high-quality monitoring experience, it is important to always ensure that NetEye is functioning the way it should. Thus, just as NetEye monitors the state of hosts and services, it is important to also monitor the health of NetEye itself.

For this purpose NetEye provides several options to perform Self Monitoring. Here, NetEye relies on two mechanisms:

1. a special neteye-local host to be monitored

2. a number of health checks that are carried out on that host

There are multiple reasons for monitoring NetEye’s health so that, depending on the scenario, you may run light or deep checks.

While a light check is a quick way to learn whether important parts of NetEye are up and running, deep checks are intended for tasks like verifying the integrity and consistency of resources.

Check out the dedicated NetEye Self Monitoring section to learn more about how to create a default host/service check or run health checks.