Difference between revisions of "Pandora: QuickGuides EN: Remote Monitoring"

From Pandora FMS Wiki
Jump to: navigation, search
(Introduction)
 
(18 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
[[Pandora:QuickGuides_EN|Go back to Quick Guides index]]
 
[[Pandora:QuickGuides_EN|Go back to Quick Guides index]]
 
==Introduction==
 
 
The purpose of this document is to make the reader aware of the possibilities regarding configuration and usability in Pandora FMS as a monitoring tool for all kind of systems and applications.
 
 
During this guide we'll have a set of specific instructions to build your network environment with Pandora FMS.
 
 
These instructions will include short steps covering the installation and the initial configuration, followed by practical examples regarding the real use of the program with corresponding screenshots.
 
  
 
==Situation==
 
==Situation==
  
Let's think we want to implement a solution which integers Pandora FMS as a monitoring tool in a network environment, mainly to make different remote checks against the critical elements of this network (Servers, routers...) and to have an alert firing and sending an email any time the status of any of these elements is considered critical.
+
We want to implement a solution which integrates Pandora FMS as a monitoring tool in a network environment, mainly to make different remote checks against the critical elements on this network (Servers, routers, etc.) and to have an alert that can be triggered and send an email any time the status of any of these elements is considered critical.
  
In the same way, we want to dispose of a historic of all these events presented in a list with graphs of a router's interface traffic data.
+
We also want a historical view of all these events presented as a list, with graphs of a router's interface traffic data.
  
 
==Requirements==
 
==Requirements==
  
The requirements to make this implementation work properly are the following:
 
  
 
+
* Full Pandora FMS installation (Pandora Server, Pandora Console and database) on a server with access to all the machines which need to be monitored.
* Install a Pandora Server and a Pandora Console in a server with access to all the machines pending to be monitored.
+
* All the ports used to carry out remote checks should be open and listening.
* Have opened and listening all those ports we need to make our remote checks.
 
 
 
==Installation==
 
 
 
In order to know how to install all the elements of Pandora FMS, check the [[Pandora:Documentation en:Installing|Pandora FMS installation manual.]] It is also possible to operate from a [[Pandora:Documentation en:Appliance Install|virtual image]] containing all the necessary elements installed and configured.
 
  
 
==Monitoring our network with Pandora FMS==
 
==Monitoring our network with Pandora FMS==
  
The software agents of Pandora FMS aren't going to be used in this guide, since we've only going to explain the data collection by using the Network Server, with remote agents, so we'll leave them for another guide.
+
This kind of monitoring is based exclusively on remote checks so software agents aren't necessary.
  
It is recommended to read the Pandora FMS operation manual in order to obtain more information and a better understanding of the following processes:
+
We strongly recommended reading the Pandora FMS operation manual to obtain more information and a better understanding of the following processes:
  
 
===ICMP checks===
 
===ICMP checks===
  
The first thing we're going to do is to define modules to check the availability and latency of a remote element from Pandora Console.
+
The first thing we're going to do is establish checks for latency and availability of a remote element from the Pandora Console.
  
In order to monitor a server or one of it's services (FTP, SSH, etc.) remotely, we'll first have to create the corresponding agent to monitor this service, so let's get started from here. This agent is going to represent our router, and to achieve that we'll need to introduce it's main IP during the agent creation. This way we'll be able to perform all the remote checks against this IP by default.
+
In order to remotely monitor a server or one of it's services (FTP, SSH, etc.), first create the corresponding agent. Use the agent's main IP to perform all the remote checks against this IP by default.
  
In the management section of the Pandora FMS console click over '''Manage agents:'''
+
In the management section of the Pandora FMS console click on '''Manage agents:'''
  
 
<center>
 
<center>
<br>
 
 
[[file:anvi.jpg]]
 
[[file:anvi.jpg]]
<br>
 
 
</center>
 
</center>
  
In the next screen, click on the button '''Create agent:'''
+
On the next screen, click on the button '''Create agent:'''
  
 
<center>
 
<center>
<br>
+
[[file:bibi.jpg|800px]]
[[file:bibi.jpg]]
 
<br>
 
 
</center>
 
</center>
  
Fulfill all the date for your new agent and click on the button '''Create agent:'''
+
Fill out all the data for your new agent and click '''Create agent:'''
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent.jpeg|800px]]
[[file:Pandora_agent.jpeg]]
 
 
<br>
 
<br>
 
''Agent creation in Pandora FMS Console''
 
''Agent creation in Pandora FMS Console''
 
</center>
 
</center>
 +
<br>
  
Once the agent has been created, click over the upper right flap representing the modules. In this section, select to create a new Network Server module and click on '''Create:'''
+
Once the agent has been created, click on the upper right tab representing the modules. In this section, select to create a new Network Server module and click on '''Create:'''
  
 
<center>
 
<center>
<br>
+
[[file:sasa.jpg|800px]]
[[file:sasa.jpg]]
 
<br>
 
 
</center>
 
</center>
  
In the next form, select a module network component, and when the right menu is displayed, select the check you want to perform. In this example we will select Host Alive, which represents a ping check against the maghine, a simple check to know whether the machine is connected or not to the network.
+
On the next form, select a module network component, and when the correct menu is displayed, select the check you want to perform. In this example, select Host Alive, which conducts a ping check against the target, a simple check to know whether the machine is connected to the network or not.
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent18.jpeg|800px]]
[[file:Pandora_agent18.jpeg]]
 
 
<br>
 
<br>
 
''Creation of a remote ICMP module using predefined components''
 
''Creation of a remote ICMP module using predefined components''
 
</center>
 
</center>
  
In the case of boolean modules (check a service's availability for example) or xxxx_proc type in Pandora, which return values 0, when the result isn't good and any other value over 0 when it is good, these are represented with red and green colours respectively, automatically, so it is not necessary to define any range to change its status.
+
In the case of boolean modules (to check a service's availability for example) or xxxx_proc type in Pandora, which returns a value of 0 when the result is bad and 1 when it's good. These values are displayed in red and green respectively, and automatically, so it's not necessary to define a range of status changes.
  
We'll leave the advanced options for another moment. Note that the module has obtained the IP address of the agent. If you wish, this field can have a different one. Once you're done with the module definition, click on the '''Create''' button.
+
Leave the advanced options for later. Note that the module has obtained the agent's IP address. If you wish, this field can have a different IP address. Once you're done with the module definition, click '''Create''' .
  
In the following screen, all the modules defined in the agent will be shown... in this case the Host Alive module we've just created:
+
In the following screen, all the modules defined in the agent are shown. In this case the Host Alive module we've just created:
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent3.jpeg|800px]]
[[file:Pandora_agent3.jpeg]]
 
 
<br>
 
<br>
 
''View of a recently created remote module (not initialized)''
 
''View of a recently created remote module (not initialized)''
 
</center>
 
</center>
  
As you can see, there's a warning icon over the modules. This warning only means that no data has been received in the module yet, since it's just been added. Once the data begins to be received, this warning will disappear.
+
As you can see, there's a warning icon over the modules. This warning only means that no data has been received by the module yet, since it's just been added. Once the data begins to be received, this warning will disappear.
  
However, in the case of the Host Latency module, which returns the time in milliseconds that takes the server to establish contact with the remote machine, we can define value ranges for warning and critical status of the module.  
+
However, in the case of the Host Latency module, which returns the time that it takes the server to establish contact with the remote machine in milliseconds, we can define the module's value ranges to go from normal to warning or critical.  
  
For example, let's configure the module to enter in a warning status from 50 to 100 ms and in a critical status for a value above 100 ms.
+
For example, let's configure the module to create a warning status from 50 to 100 ms and a critical status for a value above 100 ms.
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent16.jpeg|800px]]
[[file:Pandora_agent16.jpeg]]
 
 
<br>
 
<br>
 
''Creation of a remote ICMP module using predefined components''
 
''Creation of a remote ICMP module using predefined components''
 
</center>
 
</center>
  
Once we've finished adding modules, click on the upper right flap "View", and go to the bottom of the new section, where the data will be shown once it is received:
+
Once we've finished adding modules, click on the upper right tab named "View", and go to the bottom of the new section, where the data will be shown once it is received:
  
 
<center>
 
<center>
<br>
+
[[file:Docu123445.png|800px]]
[[file:Docu123445.png]]
 
 
<br>
 
<br>
 
''Remote ICMP modules once they've been defined in the agent''
 
''Remote ICMP modules once they've been defined in the agent''
 
</center>
 
</center>
  
This has been an example of ICMP monitoring, with the most basic and simple checks that allow us to have an important and precise information about the status of our monitored machines. There are two kinds of ICMP checks:
+
This has been an example of ICMP monitoring, with the most basic and simple checks that return important and precise information about the status of our monitored targets. There are two kinds of ICMP checks:
  
* '''icmp_proc''', or host check (ping), which allows us to know whether an IP address is available or not.
+
* '''icmp_proc''', or host check (ping), which allows us to know whether an IP address is responsive or not.
  
* '''icmp_data''', or latency check. Basically it tells us the time in milliseconds it takes the machine located in that IP address to respond to a basic ICMP query.
+
* '''icmp_data''', or latency check. Basically it tells us the time in milliseconds it takes the machine located on that IP address to respond to a basic ICMP query.
  
 
===SNMP checks===
 
===SNMP checks===
  
Now let's define two remote SNMP modules, following the same procedure, to measure the ingoing and outgoing traffic of the 11th interface of a router.
+
Now let's define two remote SNMP modules to measure the incoming and outgoing traffic from interface 11 of a router.
  
In order to achieve this, we first need to check the OIDs our router model has and check which one matches the data we want to obtain.
+
In order to accomplish this task, we first need to check the OIDs our router model has and check which one matches the data we want to obtain.
  
The easiest way is to use the SNMP Explorer tool, so we can do a SNMP Walk against the IP of the router we want to monitor.
+
The easiest way is to use the SNMP Explorer tool, so we can do an SNMP Walk against the IP of the router we want to monitor.
  
Let's go to the management view of the desired agent and click on the SNMP Explorer tab, on the upper right section of the screen:
+
Go to the management view of the desired agent and click on the SNMP Explorer tab, on the upper right hand section of the screen:
  
 
<center>
 
<center>
<br>
 
 
[[file:Pandora_agent19.jpeg]]
 
[[file:Pandora_agent19.jpeg]]
<br>
 
 
</center>
 
</center>
  
In order to make the SNMP exploration, we need the router IP as well as its port, if it's not the default one, with valid authentication data. In our case we're going to use SNMP v1 with a SNMP community with read privileges.
+
In order to initiate the SNMP exploration, we need the router's IP as well as its port, if it's not the default one, with valid authentication data. In our case we're going to use SNMP v1 along with an SNMP community that has read privileges.
 
 
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent22.jpeg|800px]]
[[file:Pandora_agent22.jpeg]]
 
 
<br>
 
<br>
 
''Pandora FMS SNMP Explorer''
 
''Pandora FMS SNMP Explorer''
 
</center>
 
</center>
  
Once we perform the SNMP Walk, we will be able to see a list with all the router interfaces. Select the desired one, and then select the modules we want to create as well. In our case:
+
Once you perform the SNMP Walk you will be able to see a list with all the router interfaces. Select the desired one, and then select the modules you want to create. In our case:
  
 
<center>
 
<center>
<br>
 
 
[[file:Pandora_agent23.jpeg]]
 
[[file:Pandora_agent23.jpeg]]
 
<br>
 
<br>
''Result of a SNMP Walk from the Pandora FMS SNMP Explorer''
+
''Result of an SNMP Walk from the Pandora FMS SNMP Explorer''
 
</center>
 
</center>
  
Another way to define SNMP modules is by knowing it's numeric OID, defining the module the same way we did with the ICMP ones.
+
Another way to define SNMP modules is by it's numeric OID, defining the module the same way we did with the ICMP ones.
  
 
For example:
 
For example:
Line 165: Line 136:
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent24.jpeg|800px]]
[[file:Pandora_agent24.jpeg]]
 
 
<br>
 
<br>
 
''Creation of a remote SNMP module to check the ingoing traffic of a router's interface''
 
''Creation of a remote SNMP module to check the ingoing traffic of a router's interface''
 
</center>
 
</center>
  
If we wanted to add all the modules found by the SNMP Explorer, we should see something like this:
+
If we added all the modules found by the SNMP Explorer, we would see something like this:
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent25.jpeg|800px]]
[[file:Pandora_agent25.jpeg]]
 
 
<br>
 
<br>
 
''List of remote SNMP modules defined in Pandora FMS''
 
''List of remote SNMP modules defined in Pandora FMS''
Line 182: Line 151:
 
===TCP checks===
 
===TCP checks===
  
The TCP checking allows to check the state of a port or a TCP service.
+
TCP checking allows us to confirm the status of a port or a TCP service.
  
 
There are two specific fields for TCP tests:
 
There are two specific fields for TCP tests:
  
 
<center>
 
<center>
<br>
+
[[file:Cap5_snmp_9.png|800px]]
[[file:Cap5_snmp_9.png]]
 
 
<br>
 
<br>
 
''Using the fields TCP send and receive in a module''
 
''Using the fields TCP send and receive in a module''
 
</center>
 
</center>
  
The TCP checking by default simply looks if the destination port is open or not. Optionally you could send a text string and wait to receive something that will be processed directly as a data.
+
TCP checking, by default, simply determines whether the destination port is open or not. Optionally you could send a text string and wait to receive something that will be processed directly as data.
  
It is possible to send a text string(using the «^M» string to replace the CR)and you can wait when receiving  an answer substring to check that the communication is right. This allows to implement simple protocol checking. For example, we could check if a server is alive sending the string:
+
It's also possible to send a text string (using the «^M» string to replace the CR) to receive an answer substring to check that communication is correct. This allows us to implement simple protocol checking. For example, we can check if a server is alive by sending the following string:
  
 
   GET / HTTP/1.0^M^M  
 
   GET / HTTP/1.0^M^M  
  
And waiting to receive the string
+
And getting this string in return:
  
 
  200 OK
 
  200 OK
  
This is codified in TCP Send and TCP receive fields.
+
This is coded in the TCP Send and TCP Receive fields.
  
Now we have a chance to use a couple of predefined module components for the Network Server, in order to create two modules to check the status of a web and SMTP servers, respectively.
+
Now we have a chance to use a couple of predefined module components for the Network Server, in order to create two modules to check the status of the web and SMTP servers, respectively.**
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent7.jpeg|800px]]
[[file:Pandora_agent7.jpeg]]
 
 
<br>
 
<br>
 
''Creation of a remote TCP module using predefined components''
 
''Creation of a remote TCP module using predefined components''
 
</center>
 
</center>
  
Note that while in the module we are defining to check the web server, we're doing a TCP send/receive query, in the case of the SNMP server we only want to check whether the corresponding port is open or not.
+
Note that, while a TCP send/receive query is performed on the module we are defining to check the web server, in the case of the SNMP server we only want to check whether the corresponding port is open or not.
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent17.jpeg|800px]]
[[file:Pandora_agent17.jpeg]]
 
 
<br>
 
<br>
 
''Creation of a remote TCP module using predefined components''
 
''Creation of a remote TCP module using predefined components''
 
</center>
 
</center>
  
Once we are done, we can check the status of these servers in the agent's monitor view.
+
Once done, we can check the status of these web servers and SMTP in the agent's monitoring view.
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent8.jpeg|800px]]
[[file:Pandora_agent8.jpeg]]
 
 
<br>
 
<br>
 
''Remote TCP modules once they've been defined in the agent''
 
''Remote TCP modules once they've been defined in the agent''
Line 234: Line 199:
 
===Module detail in graphs===
 
===Module detail in graphs===
  
If we want to check the data history of one of the SNMP modules we've defined previously, for example one indicating the ingoing traffic of one of the router's interface, we would only have to go to the agent's module view, and click on the graphs icon of the desired module
+
If we want to check the data history of one of the SNMP modules we've defined previously, for example one indicating the ingoing traffic of one of the router's interfaces, we would only have to go to the agent's modular view, and click on the graph icon of the desired module
  
 
<center>
 
<center>
<br>
 
 
[[file:Pandora_agent26.jpeg]]
 
[[file:Pandora_agent26.jpeg]]
<br>
 
 
</center>
 
</center>
  
This way we would display a graph with the module data of the last 24 hours by default. In our case we've chosen to display the data of the last 6 hours. In order to change the graph format, just click on the gray bar located to the left.
+
A graph is displayed with the module data collected over the last 24 hours by default. In our case we've chosen to display the data collected during the last 6 hours. In order to change the graph format, just click on the grey bar located to the left.
  
 
<center>
 
<center>
<br>
 
 
[[file:Pandora_agent27.jpeg]]
 
[[file:Pandora_agent27.jpeg]]
 
<br>
 
<br>
Line 253: Line 215:
 
===Event listing===
 
===Event listing===
  
Besides all the features commented previously, we also have the possibility to see all the events occurred in our system, since modules changing their status to alerts fired.
+
Aside from all the features commented previously, we also have the possibility to see all the events that have occurred in our system, from modules changing their status to alerts triggered.
  
 
In order to access the event list, simply enter the Event section in the operation menu:
 
In order to access the event list, simply enter the Event section in the operation menu:
  
 
<center>
 
<center>
<br>
 
 
[[file:Pandora_agent28.jpeg]]
 
[[file:Pandora_agent28.jpeg]]
<br>
 
 
</center>
 
</center>
  
 
Once inside, we can see the list of unvalidated events during the last 8 hours by default.
 
Once inside, we can see the list of unvalidated events during the last 8 hours by default.
  
If we want to choose the events we want to show, we have a filter to manage this in the upper section of the console:
+
If you want to choose the events you want shown, there is a filter to manage this in the upper section of the console:
  
 
<center>
 
<center>
<br>
+
[[file:Pandora_agent29.jpeg|800px]]
[[file:Pandora_agent29.jpeg]]
 
 
<br>
 
<br>
 
''Event list in Pandora FMS''
 
''Event list in Pandora FMS''

Latest revision as of 11:17, 14 July 2017

Go back to Quick Guides index

1 Situation

We want to implement a solution which integrates Pandora FMS as a monitoring tool in a network environment, mainly to make different remote checks against the critical elements on this network (Servers, routers, etc.) and to have an alert that can be triggered and send an email any time the status of any of these elements is considered critical.

We also want a historical view of all these events presented as a list, with graphs of a router's interface traffic data.

2 Requirements

  • Full Pandora FMS installation (Pandora Server, Pandora Console and database) on a server with access to all the machines which need to be monitored.
  • All the ports used to carry out remote checks should be open and listening.

3 Monitoring our network with Pandora FMS

This kind of monitoring is based exclusively on remote checks so software agents aren't necessary.

We strongly recommended reading the Pandora FMS operation manual to obtain more information and a better understanding of the following processes:

3.1 ICMP checks

The first thing we're going to do is establish checks for latency and availability of a remote element from the Pandora Console.

In order to remotely monitor a server or one of it's services (FTP, SSH, etc.), first create the corresponding agent. Use the agent's main IP to perform all the remote checks against this IP by default.

In the management section of the Pandora FMS console click on Manage agents:

Anvi.jpg

On the next screen, click on the button Create agent:

Bibi.jpg

Fill out all the data for your new agent and click Create agent:

Pandora agent.jpeg
Agent creation in Pandora FMS Console


Once the agent has been created, click on the upper right tab representing the modules. In this section, select to create a new Network Server module and click on Create:

Sasa.jpg

On the next form, select a module network component, and when the correct menu is displayed, select the check you want to perform. In this example, select Host Alive, which conducts a ping check against the target, a simple check to know whether the machine is connected to the network or not.

Pandora agent18.jpeg
Creation of a remote ICMP module using predefined components

In the case of boolean modules (to check a service's availability for example) or xxxx_proc type in Pandora, which returns a value of 0 when the result is bad and 1 when it's good. These values are displayed in red and green respectively, and automatically, so it's not necessary to define a range of status changes.

Leave the advanced options for later. Note that the module has obtained the agent's IP address. If you wish, this field can have a different IP address. Once you're done with the module definition, click Create .

In the following screen, all the modules defined in the agent are shown. In this case the Host Alive module we've just created:

Pandora agent3.jpeg
View of a recently created remote module (not initialized)

As you can see, there's a warning icon over the modules. This warning only means that no data has been received by the module yet, since it's just been added. Once the data begins to be received, this warning will disappear.

However, in the case of the Host Latency module, which returns the time that it takes the server to establish contact with the remote machine in milliseconds, we can define the module's value ranges to go from normal to warning or critical.

For example, let's configure the module to create a warning status from 50 to 100 ms and a critical status for a value above 100 ms.

Pandora agent16.jpeg
Creation of a remote ICMP module using predefined components

Once we've finished adding modules, click on the upper right tab named "View", and go to the bottom of the new section, where the data will be shown once it is received:

Docu123445.png
Remote ICMP modules once they've been defined in the agent

This has been an example of ICMP monitoring, with the most basic and simple checks that return important and precise information about the status of our monitored targets. There are two kinds of ICMP checks:

  • icmp_proc, or host check (ping), which allows us to know whether an IP address is responsive or not.
  • icmp_data, or latency check. Basically it tells us the time in milliseconds it takes the machine located on that IP address to respond to a basic ICMP query.

3.2 SNMP checks

Now let's define two remote SNMP modules to measure the incoming and outgoing traffic from interface 11 of a router.

In order to accomplish this task, we first need to check the OIDs our router model has and check which one matches the data we want to obtain.

The easiest way is to use the SNMP Explorer tool, so we can do an SNMP Walk against the IP of the router we want to monitor.

Go to the management view of the desired agent and click on the SNMP Explorer tab, on the upper right hand section of the screen:

Pandora agent19.jpeg

In order to initiate the SNMP exploration, we need the router's IP as well as its port, if it's not the default one, with valid authentication data. In our case we're going to use SNMP v1 along with an SNMP community that has read privileges.

Pandora agent22.jpeg
Pandora FMS SNMP Explorer

Once you perform the SNMP Walk you will be able to see a list with all the router interfaces. Select the desired one, and then select the modules you want to create. In our case:

Pandora agent23.jpeg
Result of an SNMP Walk from the Pandora FMS SNMP Explorer

Another way to define SNMP modules is by it's numeric OID, defining the module the same way we did with the ICMP ones.

For example:

  • Ingoing traffic (interface 11): .1.3.6.1.2.1.2.2.1.10.11
  • Outgoing traffic (interface 11): .1.3.6.1.2.1.2.2.1.16.11

Pandora agent24.jpeg
Creation of a remote SNMP module to check the ingoing traffic of a router's interface

If we added all the modules found by the SNMP Explorer, we would see something like this:

Pandora agent25.jpeg
List of remote SNMP modules defined in Pandora FMS

3.3 TCP checks

TCP checking allows us to confirm the status of a port or a TCP service.

There are two specific fields for TCP tests:

Cap5 snmp 9.png
Using the fields TCP send and receive in a module

TCP checking, by default, simply determines whether the destination port is open or not. Optionally you could send a text string and wait to receive something that will be processed directly as data.

It's also possible to send a text string (using the «^M» string to replace the CR) to receive an answer substring to check that communication is correct. This allows us to implement simple protocol checking. For example, we can check if a server is alive by sending the following string:

 GET / HTTP/1.0^M^M 

And getting this string in return:

200 OK

This is coded in the TCP Send and TCP Receive fields.

Now we have a chance to use a couple of predefined module components for the Network Server, in order to create two modules to check the status of the web and SMTP servers, respectively.**

Pandora agent7.jpeg
Creation of a remote TCP module using predefined components

Note that, while a TCP send/receive query is performed on the module we are defining to check the web server, in the case of the SNMP server we only want to check whether the corresponding port is open or not.

Pandora agent17.jpeg
Creation of a remote TCP module using predefined components

Once done, we can check the status of these web servers and SMTP in the agent's monitoring view.

Pandora agent8.jpeg
Remote TCP modules once they've been defined in the agent

3.4 Module detail in graphs

If we want to check the data history of one of the SNMP modules we've defined previously, for example one indicating the ingoing traffic of one of the router's interfaces, we would only have to go to the agent's modular view, and click on the graph icon of the desired module

Pandora agent26.jpeg

A graph is displayed with the module data collected over the last 24 hours by default. In our case we've chosen to display the data collected during the last 6 hours. In order to change the graph format, just click on the grey bar located to the left.

Pandora agent27.jpeg
Module data graph in Pandora FMS

3.5 Event listing

Aside from all the features commented previously, we also have the possibility to see all the events that have occurred in our system, from modules changing their status to alerts triggered.

In order to access the event list, simply enter the Event section in the operation menu:

Pandora agent28.jpeg

Once inside, we can see the list of unvalidated events during the last 8 hours by default.

If you want to choose the events you want shown, there is a filter to manage this in the upper section of the console:

Pandora agent29.jpeg
Event list in Pandora FMS

Go back to Pandora FMS Quick Guides Index