Pandora: Documentation en: Remote Monitoring

From Pandora FMS Wiki
Revision as of 10:24, 2 July 2020 by Sergio.gomez (talk | contribs) (SNMP Wizard)
Jump to: navigation, search

Go back to Pandora FMS documentation index

1 Remote Monitoring

1.1 Introduction

Pandora FMS Network Server is an essential piece of Pandora FMS, because it allows remote checks to be conducted from a central point. The Data Server and the Network Server are carrying out the tasks they have been assigned through a multiprocess queue system. A network server can also work with other network servers, balance the load and act as a support device in case another network server fails, carrying out the work the failing server was supposed to do. If you would like to know more about High Availability (HA) under Pandora FMS, please take a look at the corresponding chapter.

Network Servers only work with assigned network modules. Because there are network tests to perform, the Network Server should of course have complete visibility (IP addresses and ports) over the devices you are going to perform the tests on. It is completely futile to perform tests against a system with ports which cannot be seen or for which you do not have the proper paths. The existence of firewalls (or the problems generated though the existence of these kinds of devices) or pre-existing paths in the network have nothing to do with Pandora FMS nor with one of its specific configurations.

Besides the network server, there are many more additional Pandora FMS server subtypes that execute remote tests. This chapter will discuss network servers, remote plugin servers and server that launch remote tests against Windows machines (WMI Server). Other servers that also process remote tests, as WEB test server (WEB Server or Goliat server), have specific documentation chapters.


1.2 Basic network monitoring

Pandora FMS Network Modules carry out remote monitoring tasks. The remote execution of tasks can be summarized in three blocks:

ICMP Tests

Those are basic network tests that allow to find out whether a host is accessible and alive and the time it takes to get to that device through the network.

TCP Tests

This test checks if a system has the TCP port open which was specified in the module definition. Additionally, a text string can be sent and it can wait to receive a specific response to check whether the communication is correct. This method allows simple protocol checks to be implemented and verification of whether the other end responds or not.

For example, the "GET/HTTP/1.0^M^M" string could be sent to check whether an HTTP server is alive, waiting to receive the "200 OK" string.

SNMP Tests

It is possible to launch SNMP petitions remotely (called 'SNMP Polling') to systems that have their SNMP service activated to obtain data like: 'interface status' and 'consumed network bandwidth by interface', etc. There is a specific section devoted to SNMP with Pandora FMS (later on).


In conclusion it is quite obvious that the network server is the one which carries out the different network tests assigned to each agent. Each agent is assigned to a Network Server - and it is this Network Server the one that executes the task and transfers the results to the DB of Pandora FMS.

1.2.1 General Configuration of a Module for Network Monitoring

To remotely monitor any kind of equipment or an equipment service (FTP, SSH, etc.), create the corresponding agent to monitor the service first.


When talking about creating an agent, it does not mean installing a software agent in the target machine, but creating an agent in the Pandora FMS interface.


Go to the Pandora FMS section for console administration and click on Resources > Manage agents:


In the following screen, please click on Create agent:


Enter the proper data to define your new agent and click on Create:


Once you have created the agent, please click on the drop down menu of the modules. Select 'Create a new network module' in it and click on the Create button:


Select a network component module in the following form: Look for the check you need in the drop-down menu on the right. In this example, 'Host Alive' is selected which represents a ping for the machine. It is a simple check to find out if the machine is connected to the internet or not.


The advanced options are left for later. Make sure the modules have obtained the agent's IP address. You may enter a different IP address here. Once you have finished defining the module, press the Create button.

In the following screen, all modules for the agent are shown. On the picture below, you can see the preset Keepalive (which was created along with the agent) and the added 'Host Alive' module:


As seen, there is a warning attached to the modules. The warning only means that no data has been received by the module yet, because it has been just added. Once data starts to be received, the warning disappears.

To see the data from the newly created module, click on the 'view' button on the top right and look at the bottom where the data will appear once it starts receiving data:


To add another kind of network check, proceed exactly as described above, but with a different kind of module.

1.2.2 ICMP Monitoring

The previous example was the one of ICMP monitoring. These are the more basic and simple checks which give us important and precise information. There are two kinds of ICMP checks:

  • icmp_proc, host (ping) check which allows to come to know if an IP address responds or not.
  • icmp_data or latency check. It basically tells us the time in milliseconds it takes to respond to an ICMP basic query.

1.2.3 TCP Monitoring

TCP check allows to check the state of a port or a TCP service.

The main parameters of these type of modules are target port, target IP, and the TCP send and receive data.

By default, TCP check is simply a test for whether the destination port is open or not. You are also able to send a text string and wait to receive something which will be processed directly as data by Pandora FMS, through TCP Send and TCP Receive fields.

It is possible to send a text string (using the «^M» string to replace the CR) and to wait to receive an answer substring to check whether the communication is working properly or not. This allows simple protocol checks to be implemented. If you want to check whether a server is alive or not, you may send the following string:

 GET / HTTP/1.0^M^M 

Wait to receive the string:

200 OK

This string is coded in 'TCP send' and 'TCP receive' fields.

TCP send

The field to configure the parameters intended to be sent to the TCP port. It accepts the '^M' string as a replacement for the CR sending. To send several strings in a row in a send/response manner, you are required to separate them by the character:

TCP receive

The field to configure the text strings which we expect to receive on the TCP connection. If they are sent/received in several steps, each step should be separated by the '|' (pipe) character.

By means of the Pandora FMS TCP check, you are able to do more than just inspecting whether a port is open or waiting for an answer from a simple request. It is possible to send data, wait to receive something, send something afterwards, wait to receive something and so on. Only if all the processes are carried out in the right way, the results can be validated.

To use the Pandora FMS Dialog and Response Checking System, you may separate the different petitions by the | ('pipe') character.

This is an example of an SMTP conversation:

R: 220 Blah blah blah
R: 250
R: 250 OK
R: 250 OK
R: 354 Start mail input; end with .
S: .......your mail here........
S: .
R: 250 OK
R: 221 Service closing blah blah blah

If you want to check the first protocol points, the necessary fields to emulate this conversation would be:

TCP Send


TCP Receive


If the three first steps are OK (code 250), then the SMTP is working properly. It does not need to send a complete mail here (but it could, in any case). This enables protocol-based TCP checks which could be used for any protocol that uses plain text conversations.

1.2.4 Remote execution modules

From version 741 onwards, the following network server Enterprise modules are available:

  • Remote execution data
  • Remote execution data proc
  • Remote execution data string
  • Remote execution data inc

To be able to use those modules successfully, connection data of the agent intended to monitor is necessary. Therefore, register the connection data against the target in the safe credential storage:


Once the credentials are registered, use them when defining the module.

Create a new network server module.

Choose one of the menu options in module type.


For remote executions, the following types of data are valid:

  • remote_execution_data: numeric.
  • remote_execution proc: boolean (0 FALSE, different from 0 TRUE).
  • remote_execution_data_string: alphanumeric (string).
  • remote_execution_data_inc: incremental (ratio).

Define these:

  1. The credential set to be used for the connection.
  2. Optionally the target IP (otherwise that of the agent will be used).
  3. Optionally the target OS (otherwise that of the agent will be used).
  4. Optionally the port to connect to (22 in Linux, whatever in Windows).
  5. The command to forward to carry out the monitoring process.




The system will execute the command against the remote machine, receiving the number of files in the temporary work directory.


You may also choose a type of alphanumeric data to see the command’s literal output:

Module setup:


Target OS parameter can be configured to inherit the operative system of the agent that is beign targeted.




Template warning.png

The module’s performance is the same when allocating alerts, generating events or viewing reports.


Template warning.png

From Pandora FMS version 743 onwards, the following tokens related to remote execution modules parameters will be available in pandora_server.conf: ssh_launcher, rcmd_timeout and rcmd_timeout_bin.


1.2.5 SNMP Monitoring Introduction to SNMP Monitoring

When we talk about SNMP monitoring, the most important thing is to separate the testing concepts (polling) and traps. SNMP testing means ordering Pandora FMS to execute a "get" command against an SNMP device such as a router or a switch. This is a synchronous operation (which takes place from time to tima actively).

Receiving an SNMP trap, on the other hand, is an asynchronous operation (based on changes or events that may take place or not). It is commonly used to receive 'alerts' coming from a device, e.g. if a switch knocks down a port or its fan is too hot.

SNMP checks of the polling type are carried out creatinf network modules in Pandora FMS as it is usually done.

Using SNMP Traps is something completely different. It is possible to receive traps from any device without the need of configuring anything except the SNMP console in Pandora FMS, where all traps received will appear on the SNMP console. Alerts can be defined through filtering rules by enay of its fields.

Pandora FMS works with SNMP using individual OIDs, where each OID is a network module. If you want to monitor a 24-port 'Cisco Catalyst' switch and find out the operating system and the entry and exit port, you have to define a total of 72 modules (24 x 3).

To work with SNMP devices, you are required to know the following:

  • What the SNMP Protocol is and how it works. The published RFC3411 from the IETF describes it in detail.
  • The IP and the SNMP community of the remote device.
  • How to activate the device's SNMP management so that you are able to perform SNMP queries from the network server. This network server must be allocated by the agent where network modules are to be defined. Bear in mind that if you wish for other network servers to make queries in case the assigned server fails, these will make those queries with another IP address.
  • The specific OID of the remote device which you want to check (or use one of the multiple Pandora FMS wizards or its SNMP OID browser).
  • How to manage the data returned by the device. SNMP devices usually return data in different formats. Pandora FMS can manage almost all of them. Pandora FMS manages data of the 'counter' kind as 'remote_snmp_inc'. They are of special importance, since they are counters, they cannot be considered numeric data but element rate per second. The majority of SNMP statistical data are of the counter kind and it is necessary to set them as 'remote_snmp_inc' if you want to monitor them properly. Monitoring through Network Modules with SNMP

To monitor any element through SNMP, you should at least know its IP and its SNMP community. It would also be quite important to know the OID that you want to monitor, although you could obtain it by means of an SNMP Walk as long as you know where each OID comes from. However, this is not always an easy task.

To monitor an element through SNMP, create an agent for it. If you already have one, simply add a new network module and follow the previous instructions.

Once the module has been created, select an SNMP data type in the configuration module form just like the ones shown on the image:

Cap5 snmp 1.png

Any of the three SNMP data types are valid. Simply select the one which matches the type of data that you want to monitor.

Once you have selected an SNMP data type, the form will expand, showing additional fields for SNMP like the following:

Cap5 snmp 2.png

Next, define the fields:

SNMP community

The SNMP community is necessary to monitor the element. It acts as a password.

SNMP version

The SNMP protocol version of the device. It could be 1, 2, 2c or 3. Version 3 includes encryption and safe authentication when communicating, which makes configuration more burdensome and makes Pandora FMS network server polling performance worse.


The OID identifier to monitor. They can consist of numeric values and dots. These strings are translated automatically to more descriptive alphanumeric strings if the corresponding MIBs are installed within the system. MIBs are manufacturer libraries that help translate OIDs into more descriptive strings.

An alphanumeric OID can be similar to this one:

The numeric equivalent would be something like this:

Pandora FMS includes some OIDs in its database which could be used directly. When creating the module, select the 'Cisco MIBs' component to show a list of the available MIBs for Cisco devices:

Cap5 snmp 4.png

Once you have selected the proper component, you will be able to pick the available MIB for it:

Cap5 snmp 5.png

By doing this, the fields will be filled out with the necessary information.

There are more MIBs included in Pandora FMS. With Enterprise Version, there are several MIB packages for different devices included. Once you have entered the data, please click on the Create button.

To see the data of the created module, click on the upper flap named View and take a look at the bottom of the page, where the data will be displayed once it starts to receive any. With these data you could see a realtime SNMP graph.

SNMP nueva.png SNMP Monitoring from Agents

Windows software agents have a feature for obtaining SNMP information. In Unix/Linux snmpget agents it is usually available, so it can be called from the module_exec line.

The 'snmpget.exe' feature has been added to the Windows default agent (which is part of the 'net-snmp' project and comes with a BSD license). The basic 'MIBs' and a wrapper / script to wrap the call into the 'snmpget.exe' feature have also been added.

Using this call, SNMP can be monitored from an agent, obtaining information from any remote system to which the agent has access to, so you can work as a 'satellite agent' or 'proxy agent' (according to the documentation).

In Windows, the syntax for this execution is:

module_exec getsnmp.bat <comunidad_SNMP> <ip de destino> <OID>

Some examples of SNMP modules executed by Windows agents are:

module_name SNMP_if3_in
module_type generic_data_inc
module_exec getsnmp.bat public .
module_name SNMP_if3_desc
module_type generic_data_string
module_exec getsnmp.bat public IF-MIB::ifDescr.3
module_name SNMP_Sysup
module_type generic_data
module_exec getsnmp.bat public DISMAN-EVENT-MIB::sysUpTimeInstance

The same examples, executed under UNIX agents:

module_name SNMP_if3_in
module_type generic_data_inc
module_exec snmpget -v 1 -c public .
module_name SNMP_Sysup
module_type generic_data
module_exec snmpget -v 1 -c public DISMAN-EVENT-MIB::sysUpTimeInstance

It is important to highlight that only the 'basic' OIDs are translatable into their numerical equivalent. It is advisable to always use numerical OIDs, because the tool might be able to translate it or not. In any case, the MIBs can always be obtained from the '/util/mibs' directory in Windows or in '/usr/share/snmp/mibs' in Linux.

1.2.6 Pandora FMS SNMP MIB Browser

The SNMP explorer can be accessed through the Monitoring > SNMP > SNMP Browser menu.

From Pandora FMS version 744 new operations can be added to policies and agents. This development is only available for Pandora FMS Enterprise versions.

The first thing to understand is that Pandora FMS makes a complete path of the device tree, so if it is big (like a switch) this may take several minutes. You may also choose to explore only one sub-system, which will save you a lot of time.

For example, to get Cisco information only, you may explore your Cisco enterprise sub-mib starting with:


The browser is used to navigate, which means clicking on each branch and obtain values. The system will ask for that information and will show the requested OID information (if available). If there is no information about the device OID, this is only displayed in numeric format. The OID descriptive information is stored through MIBs [1]. If there is no MIB for the device you wish to explore, you may have to look for "pieces of information" throughout the information displayed by Pandora FMS, which is complex and takes time.

Pandora FMS SNMP browser allows to search for a text string both throughout the obtained OID values and the translated OID values (if available). It could be particularly helpful to look for known and specific strings and locate their OID. If it finds several entries, it will allow you to go from one occurrence to another and it will highlight them in yellow.

Snmp browser module creator.png

From version Enterprise 744 you may select several OIDs and add them to an agent by clicking on “Create agent modules”.

Select the agents where you wish to monitor said OIDs and add them to the bot on the right. These modules are created once you click on “Add modules”.



You may also select several OIDs to add them to a policy using the “Create policy modules” button.


Select all policies where you wish to add module configuration of those OIDs. If you want to generate a new policy for those OIDs click on “Create new policy”.


Fill out the fields assigning a name, a group, a policy description and click on “Create policy”.

Then it will be available in the policy board.

Add them to the box on the right and click on “Add modules” to apply this configuration on policies.



If what you want is to select a specific OID from Pandora FMS version 744 Enterprise the “Create agent module” button is available from the OID detail. This button will allow to select a specific agent and will redirect to module creation within said agent will all the selected SNMP data.


From the SNMP module editor, when you create or edit a network module, you may launch the SNMP browser by clicking on "SNMP Browser", which will open it on a floating window.

Once you choose the OID you were looking for, by clicking on the filter icon, choose that OID and it will appear automatically on the corresponding field of module definition to be used in your agent.

Snmp browser from module creation.jpg

1.2.7 MIB Management

Through Pandora FMS you can upload and manage the MIBS to be able to add new mibs or delete the ones that are not revelant. These MIBs will be only used by Pandora FMS, which will also use the operating system (in /usr/share/snmp/mibs). Pandora FMS will use the {PANDORA_CONSOLE}/attachment/mibs path to store the mibs.

New snmp browser mibmanager.png

It is important to point out that Pandora FMS MIB manager only manages the "polling" MIBs that have nothing to do with SNMP traps MIBs. For this feature, there is another manager, exclusive to the Enterprise version of Pandora FMS.

1.2.8 Pandora FMS SNMP Wizard

In the agent management view, there is a set of tools specifically created to create modules remotely: The Agent Wizard.

Agent wizard.png SNMP Wizard

Agent wizard snmp wizard.png

Set the IP target, the community and other desired parameters (SNMP v3 is supported) to make an SNMP-Walk to the host.

Snmp wizard form.png

Once the data is correctly retrieved, a form for module creation will appear:

Snmp wizard module creator.png

It is possible to create modules from the following kinds of SNMP data through the SNMP Wizard:

  • Devices
  • Processes
  • Free Space on Harddrives
  • Temperature Sensors
  • Other SNMP Data

You may select the kind of module and add the desired elements from the left combo to the right one. Once you have completed this process, click on the 'Create modules' button.

This wizard will create two kinds of modules:

  • SNMP Modules for data with a static OID (sensors, memory data, CPU data, etc.).
  • Plugin Modules for data with dynamic OID or calculated data (processes, disk space, used memory in percentage, etc).

Template warning.png

For plugin modules the remote SNMP plugin will be used. So if the plugin is not installed in the system, these features will remain disabled. The plugin must be named "snmp_remote. pl". The location where it is hosted is not relevant.


For the SNMP wizard to be able to obtain data from an SNMP device thanks to the remote components, it is necessary to fulfill 2 requirements:

  - To have registered in Pandora the Private Enterprise Number (PEN) of the device manufacturer.
  - To have registered and enabled in Pandora components of the SNMP wizard for the device manufacturer.

If the scanned device fulfills these requirements, all the modules from which data could have been obtained will be shown to give us the opportunity to select which we want to create and which not.

These modules will be shown organized in blocks based on the group the wizard component that has generated them belongs to.

All the blocks will be shown compressed in the first moment to facilitate the visualization. In this way, they can be expanded to modify the selections or the data. In addition, in each block where modules have been marked for creation, an informative icon will be displayed to indicate this.

IMG8 wizard components.png

If we deploy a block, we can choose which modules will be added and which will not, as well as the option of modifying the name, description or thresholds of each module individually.

IMG9 wizard components.png

Once the Create modules button is pressed, a summary list of the chosen modules with their configuration will be displayed. In this list you will see the modules that could not be created, either because they already exist in the agent or because 2 or more modules with the same name have been configured in the wizard itself.

In spite of all the modifications that we do, before they are added to the agent, there will be a last chance to confirm the creation of these modules or to cancel it and keep on modifying the wizard result.

IMG10 wizard components.png

Once the creation of the modules has been confirmed, it will be re-evaluated one by one whether they can be created or not, to avoid duplicate modules in case the same modules have been created by another means in the time frame of the confirmation.

We will be notified if the process could be completed successfully or if there were any modules that could not be created. SNMP Interface Wizard

Agent wizard snmp interfaces wizard.png

In the Agent Wizard, there is an SNMP wizard specifically created for browsing interfaces.

This Wizard browses the SNMP branch IF-MIB::interfaces, offering the possibility of creating multiple modules of different interfaces with multiple selections.

Like the SNMP Wizard (after selecting the IP target, community, etc.), the system directs an SNMP query on the host and fills out the module creation form.

Select one or more interfaces from the left combo. After that, the common elements available to them (e.g. description, speed, inbound / outbound traffic, etc.) will appear on the right. You can select one or more elements of this combo and click on 'Create modules' to create these modules for each selected interface in the combo on the left.

Agent wizard snmp interfaces creation.png

1.2.9 Common Advanced Features of Network Modules

The following screen shows the advanced features for network module configuration:

Cap5 snmp 8.png


Module description. There is already a default description which can be changed.

Custom ID

Custom identifier which is necessary if you wish for the server to send multicast messages with information about agents. You can also use this field to integrate Pandora FMS data into an external information system like a CMDB.


The module's execution interval. As shown in the example, it could be different from the agent's interval.

The values shown depend on those configured in the "Settings > Visual Styles" section in the "Interval Values" section.

An administrator user will be given the possibility to define a custom interval at the time of creating or editing a module. Standard users will only be able to define previously configured intervals, displaying the default ones when not being defined in "Visual Styles".

Post Process

The module's post processing. It is useful to multiply or divide the returned value, e.g. when you obtain bytes and you want to show the value in Megabytes.

Min. Value

The module's minimum value. Any value lower than the one defined here will be considered 'invalid' and ruled out.

Max. Value

The module's maximum value. Any value higher than the one defined here will be considered 'invalid' and ruled out.

Export Target

It is useful to export the values returned by the module to an Export Server. It is only available in the Pandora FMS Enterprise Version, and could come in pretty handy if you have configured an export server previously. Check the section on the export server for more details.


If Cron from is set, the module will be run once the current date and time match the date and time configured in Cron from, ignoring the module's own interval. For example, the following configuration would cause the module to be run every Monday at 6:30:

Cron from ex1.png

If both Cron from and Cron to are set, the module will be run once when the current date and time fall between the date and time configured in Cron from and the date and time configured in Cron to, ignoring the module's own interval. For example, the following configuration would cause the module to be run everyday between 6 and 7:

Cron from ex2.png

For local modules, the corresponding module_crontab line is added to the agent's configuration file. See Programmed Monitoring for more information.


Time the agent will wait for the execution of the module in seconds.


This categorization has no effect on the normal user interface, it is intended to be used together with the Metaconsole.

1.3 Windows Remote Monitoring with WMI

WMI is a Microsoft system for obtaining remote information from computers running Windows OS. It is available from Windows XP version to the most current versions. WMI allows you to get all kinds of information from the OS, applications and even hardware. WMI queries can be made locally (in fact, Pandora FMS agent does it internally, calling the API of the operating system and asking the WMI subsystem) or remotely. In some systems, remote access to WMI is not enabled and must be enabled in order to be consulted from the outside.

Pandora FMS allows remote monitoring of Windows equipment through WMI queries. To do this, it is be necessary to enable the wmiserver component in the Pandora FMS server configuration file.

# wmiserver : '1' or '0'. Set to '1' to activate the WMI server in this setup.
  wmiserver 1

Queries are made in WQL, a kind of Microsoft-specific SQL language for internal queries to the operating system, and any query that appears in the WMI system database can be made.

To start monitoring through WMI, first create the corresponding agent, and once ready, click on the top flap of the modules (Modules). Then, select the option to create a new WMI module and press the Create button.:


Some fields are WMI specific and require a short explanation:


Space for WMI names. This field is different from 'empty string' by default and depends on the information source of the application intended to monitor.


Name of the Administrator or any other user which has been granted the privileges to remotely execute WMI queries.


Password for the Administrator or any other user.

WMI Query

WMI query. It is very similar to a sentence in SQL, e.g.:

SELECT LoadPercentage from Win32_Processor WHERE DeviceID = "CPU0"
SELECT SerialNumber FROM Win32_OperatingSystem
SELECT AvailableBytes from Win32_PerfRawData_PerfOS_Memory
SELECT DiskWriteBytesPersec from Win32_PerfRawData_PerfDisk_PhysicalDisk WHERE name = "_Total"

Key String

Optional field to compare the returned query with a string. In case it exists, the module will return either '1' or '0' instead of the string itself.

Field Number

The number of the returned field, starting from 0 (WMI queries are able to return more than one field). Most of the time, the value is 0 or 1.


If you do not know the exact parameters, you may also select one of the preinstalled ones included in the Pandora FMS Database. Therefore, select the WMI module component:


Once you have done that, select a WMI check from one of the available ones:


The required information is filled out automatically, except for the user and its password. Please remember that only users with administration permissions and their passwords are valid here. Otherwise, the module cannot return any value:


The Pandora FMS Enterprise version owns more than 400 WMI Remote Monitoring Modules for Windows. They are available for the following devices and components:

  • Active Directory
  • BIOS
  • System Information
  • Windows Information
  • Printers
  • IIS
  • LDAP
  • Microsoft Exchange

1.4 WMI Wizard

Under the Agent Wizard feature shown on the picture below, there is a WMI wizard which is intended to browse in and create modules with WMI queries on a specified agent:

Agent wizard wmi wizard.png

You will need to specify the Administrator (or a user with WMI query permissions) user and password on the target server to make the first WMI queries. This information will be used to create modules.

Wmi wizard module creator.png

It is possible to create modules from different kinds of WMI data through the WMI Wizard:

  • Services: Creates boolean monitors in 'normal' status if the service is running and in 'critical' when it is shut down.
  • Processes: The process monitor will only receive any data if the process is active, otherwise it will be on 'unknown' status.
  • Free space on disk The available space on the hard drive.
  • WMI components: It will choose from the WMI components registered on the system (they are found under 'Administration' -> 'Manage modules' -> 'Network components').

1.5 Monitoring with server remote plugins

This type of monitoring consists on executing plugins remotely from Pandora FMS server against other systems. Installations come with several server plugins by default ready to use, and the user can always add as many as needed.

A remote plugin is a script or executable that supports parameters and returns a value. Through a plugin you can implement any type of operation by yourself, and through a few input parameters, customize as you may want that application you have developed to work. This would allow you, for example, to pass the target IP of the test as a parameter. The result could be a number, a boolean value (0 error, > 0 OK), or a text string. The only limitation of remote plugins is that they can only return a single value.

To register a plugin in Pandora FMS, go to the management section of the console, and once there, click on Manage servers, then click on "Manage plugins":



From this screen you can see that you already have a few plugins registered. Here you may also register your plugin manually. To explain how it works, see an already registered plugin, click on the one called "UDP Plugin" that allows you to perform a UDP connectivity test to a remote machine.

Plugin create 1.jpg

Plugin Type

There are two types of plugins: standard (standard) and Nagios plugins. Standard plug-ins are scripts that execute actions and support parameters. Nagios add-ons are, as its name indicates, Nagios add-ons that can be used in Pandora FMS. The difference is mainly that nagios plugins return an error level to indicate whether the test was successful or not and an additional descriptive string. This description is not a numerical value that can be used as a module value, so in this case it will be used to update the module description.

In this case (for the example plugin, UDP port check), Standard will be selected since it is not a Nagios plugin.

Max. Timeout

The expiration time of the plugin. If you do not receive a response within the specified time, it is not run anymore. It is a very important factor when implementing monitoring with plugins. If the plugin execution time is longer than the specified value, you would never obtain data with it (it will not even be initiated). This value is recommended to always be higher than the time it usually takes to return a value of the script or executable which is used as a plug in. If there is no preconfigured value, it is recommended to use the same value which can be found under plugin_timeout in the configuration.


In the execution of a plugin, there are three timeouts: server, plugin and module. Please note that the server prevails over the others, and secondly, the plugin. That is, if you have a server with a 10-second timeout and a plugin with a 20-second timeout and a module that uses that plugin with a 30-second timeout, the maximum time to wait for the execution of that module will be 10 seconds.


For this example, the value selected is '15'.


Description of the add-on. Write a brief description, such as: Check a remote UDP port (by using NMAP). Use IP address and Port options. The description is not trivial, since it will be shown in the user interface of the plugin. Make sure it explains what the plugin is for.

Plugin create 2.jpg

Plug-in Command

Path to the plugin executable. By default, if the installation has been standard, they will be in the /usr/share/pandora_server/util/plugin/ directory. Although it could be any path in the system. In this case, type /usr/share/pandora_server/util/plugin/udp_nmap_plugin. sh in the field. If you use your own plugin, make sure that you know the path where you left the plugin and that you have run permissions (chmod 755).

Plug-in parameters

A string with the plugin parameters, which will go after the command and a blank space. This field accepts macros such as _field1_ _field2_... _fieldN_. This is where the most complex part of a plugin's operation is, we will see it with an example.

Parameter Macros

Unlimited macros can be added for use in the plugin parameter field. These macros will appear as text fields in the module configuration so that the user abstracts the complexity of using a plugin module. It is about the user using a plugin as if it were a "library" module in which he fills in fields, without having to know the process behind it. Macros definition allows the user to fill in the script call parameters without knowing how it works, neither the script nor the way to call it.

Each macro has 3 fields:

  • Description: A short string describing the macro. It is the label next to the field.
  • Default value: The default value assigned to the field.
  • Help: A text with an explanation of the macro, to show some examples of use or better explain what that field is for.

An example of a macro configuration:

Macro configuration.png

An example of this macro in the module editor:

Macro editor2.jpg

1.5.1 Internal Macros

Like the alerts, it is possible to use internal macros in the plugin configuration, too.

The supported macros are:

  • _agent_ o _agentalias_: Alias of the agent to which the module belongs.
  • _agentname_: Name of the agent to which the module belongs.
  • _agentdescription_: Description of the agent to which the module belongs.
  • _agentstatus_: Current status of the agent to which the module belongs.
  • _address_: Address of the agent to which the module belongs.
  • _module_: The module's name.
  • _modulegroup_: The module's group name.
  • _moduledescription_: A description of the module.
  • _modulestatus_: The status of the module.
  • _moduletags_: The module's associated tags.
  • _id_agent_: The ID of the agent. It is quite useful to generate a direct URL to redirect to a Pandora FMS console webpage.
  • _id_module_: The module's ID.
  • _policy_: The name of the policy the module belongs to (if that applies).
  • _interval_: The execution interval of the module.
  • _target_ip_: The target IP address of the module.
  • _target_port_: The target port number of the module.
  • _plugin_parameters_: The plug-in parameters of the module.
  • _email_tag_: The emails associated to module tags.

1.5.2 A remote plugin from the inside

The UP plugin code is extremely simple and helps to explain how the whole process works:

# This is called like -p xxx -t xxxx
nmap -T5 -p $PORT -sU $HOST | grep open | wc -l

This Linux plugin takes two parameters, the UDP port to test and the destination address, with the -p and -sU parameters respectively. When registering the plugin you have defined two macros, one for the port and another for the IP so that when the user is going to create a plugin module it only sees that, nothing else.

Once the plugin has been registered, in order to use it in an agent, you must create a plugin server module, click on the top tab of the modules ("Modules"). There, select create a new network module and click on the Create button:


In the following form, fill in the empty fields, select the module type Generic module to acquire numeric data, specify the IP address to which the analysis must be performed, and also the port on which to do it:

Example1 edition module.png

Once you have finished, press the Create button.

The following screen will show the modules for the agent, the "UDP Port check" module that you have just created:

Udp port check demo.jpg

1.5.3 Example #1 : Plugin Module for MySQL

This is another more complex example on how to implement a plugin. It is another plugin included by default in Pandora FMS. In this case, it is the MySQL check plugin.

First, create a plugin module ('Administration' -> 'Manage Servers' -> 'Manage plug ins') for MySQL using the following data:

  • Name: MySQL
  • Plugin type: Standard
  • Max. timeout: 10 seconds
  • Description: MySQL check plugin
  • Plugin command: /usr/share/pandora_server/util/plugin/
  • Plugin parameters: -s _field1_ -u _field2_ -p _field3_ -q _field4_
  • Macro _field1_:
    • Description: IP Address
    • Default value: X.X.X.X
  • Macro _field1_:
    • Description: User
    • Default value: User
  • Macro _field1_:
    • Description: Password
    • Default value: Password
  • Macro _field1_:
    • Description: Check
    • Default value: Connections
    • Help: Possible values: Connections/Com_select/Com_update/Innodb_rows_read

When it is ready, the plugin should look like this:

Plugin mysql1.png
Plugin mysql2.png
Plugin mysql3.png
Plugin mysql4.png

This plug in provides four checks:

  • -q Connections: Connections
  • -q Com_select: Number of select queries from start
  • -q Com_update: Number of update queries from start
  • -q Innodb_rows_read: Innodb file readings

Create a module in the agent of the computer where Pandora FMS is installed and assign it; its name will be Mysql Connections, using as plugin "MySQL", as IP localhost, as user pandora, as password the password of Pandora FMS database, and as check the word Connections.

After its creation, it should look like this:

Plugin mysql module.png
Mysql module2.png

Once created, it will appear in the list of modules, as a plugin type module (in this case, yet to be initialized)


1.5.4 Example 2 SMTP Server Remote Plugin Module

This plugin sends an email using a remote server, you can specify server IP, port, user and password and authentication scheme, as well as destination email. It returns 1 if it works and 0 if it fails, that is, it should be used using generic_proc type.

This is a screenshot of the module definition using this plug in:

Pandora plugin SMTP5.png
Smtp module2.png

1.5.5 Example 3 - DNS Server Remote Plug In

This plug in checks the IP address of a specified domain (e.g., This is a fixed IP, using an external DNS as reference. That way it is possible to validate whether the domain is returning the correct IP address to avoid unnecessary balancing, DNS attacks, etc. It returns value '1' if it works properly and '0' if not. The plugin is required to be of the 'generic_proc' type.

This is a screen shot of the module definition using this plugin:

Pandora plugin DNS5.png
Dns module2.png

1.6 Custom field macros for remote monitoring

When configuring remote modules, having to enter agent-specific configuration options multiple times can quickly become tedious (e.g., an SNMP community string). Custom field macros allow you to use agent custom fields as macros for certain module configuration options.

In the following example, an SNMP network component that can be reused across SNMP agents with different community strings will be created:

  • First, go to Resources/Custom fields in your Pandora FMS Console and define a new custom field that will be used to store the SNMP community string. Write down its ID, since it will be part of the macro later, and fill in the appropriate community string in your SNMP agents.
Snmp custom field.png
  • Then create a new SNMP network component and enter _agentcustomfield_n_ as the SNMP community string, where n is the ID of the custom field (in our example, _agentcustomfield_11_).
Custom field network component.png
  • Finally, configure a module using the newly created network component. The module will start working automatically.

Custom field macros work with SNMP, WMI, plug-in and inventory modules. They can be used in standalone modules, network components and policy modules.

For a WMI module, you could analogously define two new custom fields to store the username and the password, and use the corresponding custom field macros in the module definition.

Wmi custom field.png

1.7 Remote wizard and network test execution (Exec Server)

This feature allows some actions to be run on Pandora FMS remote servers from the Pandora FMS Console. Thus, allowing the use of the agent SNMP Wizards, MIBs' browser and 'event responses' from a remote server, as well as accessing it from the server where the console is.

Internally, it works through SSH remote command execution from the Pandora FMS console to the enabled servers, which will be called “Exec Server”. These servers can be Pandora FMS or Satellite Servers, but always in Linux.

1.7.1 Configuration

It is important to keep in mind that, in order to use this feature correctly, it will be necessary for the agent which is being worked on to have been previously created by the server that is going to be employed, and for said server to have the remote configuration enabled in case it is a satellite server.

Template warning.png

If remote cofiguration is not enabled, satellite modules will not be created through wizard.


To configure Exec Server correctly, the systems must be configured following a series of steps:

1. In the Pandora FMS server list, access the server edition you want to use as exec server:


2. Edit the IP of the server where you will launch the desired commands and activate “Exec Server” check. Using the option "Port" you can specify the port used to connect via SSH to this server. This option can be configured on the Network Server and / or Satellite Server.

3. The configuration test is not performed yet because the system is not completely configured at this point and it would generate an error message.

Server 222 2.png

4. Enable the server where the Pandora FMS console runs so that the “apache” or equivalent user has a shell execution. Modify the following line in the /etc/passwd file so that the user has a valid shell, for example:


5. Create the “.ssh” directory in the “/var/www/” route and give permissions for the “apache” user:

mkdir /var/www/.ssh
chown apache /var/www/.ssh

6. Execute as root:

su apache

7. Generate the SSH key for the connection to the remote machine executing the following command:


Accept any questions that it might ask you by clicking “enter”:


8. Before accessing "Exec server” by SSH (which will be a Pandora FMS server or a Linux server satellite), create on that machine a specific user, called “pandora_exec_proxy” and also create the “/home/pandora_exec_proxy/.ssh/” folder:

sudo useradd pandora_exec_proxy -m
mkdir /home/pandora_exec_proxy/.ssh/

NOTE: The user does not have a password, so it cannot be used for remote connection.

9. Copy the contents of the public key, generated in the previous step, from the Pandora FMS console to the “exec server” server. In order to do this, copy the contents of the /var/www/.ssh/ file (by copying and pasting that content) to the /home/pandora_exec_proxy/.ssh/authorized_keys'' file and change that file's permissions:

chown -R pandora_exec_proxy /home/pandora_exec/.ssh/

10. Once the user is created, from the machine where the console is running, and through the “apache” user, execute the following command manually to verify that you can log in without entering a password (replacing the IP by the hostname/IP from the Exec server which has been configured in previous steps):

 ssh [email protected]_address

11. When all these steps are correct, edit (in the console) the /etc/pass file in order to leave the apache user as it was originally (without local shell):


12. Finally, test the configuration in the editing section of your proxy server, within Pandora FMS console, and if the test indicator turns green, it will be fully operational and functional.


1.7.2 Using the exec servers feature

From now on, in the MIB browser, in agent SNMP wizard and event responses, you can choose from where you will launch the request, whether from the local console or from the configured Exec server:


And the same goes for the WMI Wizard, the SNMP interfaces one and SNMP agent wizard (not available for satellite servers)


Depending on the selected server, when launching the Wizard, adapted modules for satellite server or server will be created. In the satellite server case, write the modules in the remote configuration file so that they can be executed by the server.

For executing “event response”, firstly configure a new event response that uses the new exec server:


And then, launch it from an event:


1.8 Path monitoring

Pandora FMS offers by default complete route monitoring between two network points, visually indicating the path that is being followed at all times to communicate between these two points.

To use this system you need:

  • A software agent at the point of origin of the route you want to analyze
  • Being able to reach the destination point via ICMP from the point of origin.

The Pandora FMS path analyzer uses an agent plugin to map the route. This agent plugin uses several methods to collect information, reporting structured information to Pandora FMS server.

Note: Optionally, if you want to scan routes over the Internet, it is recommended that you deploy the mtr application on your route source computer. More information at:

1.8.1 Configuration

From version 7.0 OUM715 onwards, the plugin is included in the agent. To configure it, activate the execution of the plugin from the Pandora FMS console, once the agent's remote configuration is enabled.

Access the plugin configuration tab in your agent and add the following line (if the agent version is earlier than 7.0 715, or if you have not deployed the plugin in the utility folder, specify the full path to the plugin to run it)

route_parser -t target_address

Where target address can be a v4 IP address or an FQDN domain name.

Route conf2.png

1.8.2 Visualization

Once the system is configured and reporting, a new tab will appear in the agent view with the path communications have followed to reach the target:

Sample route view to a machine on a network other than the source network (LAN connections)

Route view1.png

Sample route to example view (Google's DNS) (WAN connections)

Route view2.png

Go back to Pandora FMS documentation index