Pandora: Documentation en: Massive Operations

From Pandora FMS Wiki
Jump to: navigation, search

Go back to Pandora FMS documentation index

1 Massive Operations

1.1 Introduction

The Massive Operations feature allows you to conduct actions related to agents, modules, users, alerts, policies, SNMP, satellite or plugins in a massive way. In recent years, the importance of massive operations have grown in large-volume environments. This functionality has been designed to facilitate the administrators work in situations in which they have to deal with systems which contain a very large amount of components.

You're able to access the massive operations features by clicking on 'Administration' and 'Massive Operations' as shown below.

Massive operations1.png


A piece of advice:
The PHP language requires an appropriate configuration of the timeout parameters. In order to do this, please open the configuration file called 'php.ini' by entering the following command:

sudo vi /etc/php5/apache2/php.ini;

Please modify the timeout parameters as shown below.

max_execution_time = 0 
max_input_time = -1

1.2 Massive Operations - Agents

1.2.1 Agent massive edition

Within the 'massive agents edition' subsection, it's possible to filter by 'destination', 'agents' and 'group' and to change general parameters like 'parent agent', 'group', 'execution interval' or 'operating system'.

Agentes 1.PNG

When you choose some, you could modify some parameters:

Agentes 2.PNG


  • Cascade protection: Parameter with which an avalanche of alerts can be avoided. It is possible to choose an agent or a module of an agent. In the first case, when the chosen agent is in critical, the agent will not generate alerts. In the second case, only when the specified module is critical, the agent will not generate alerts.
  • Module definition: Three work modes can be selected
    • Learning mode: If an XML arrives with new modules, they will be created automatically (by default).
    • Normal mode: If an XML arrives with new modules, will not be created unless they are already declared in the console previously.
    • Auto-disable mode: Same as learning mode, but if all modules go to unknown, the agent will be disabled until information arrives again.

1.2.2 Agent massive delete

Within the 'massive agents deletion' subsection, it's possible to filter by group.

Agentes 3 eliminar.PNG



1.3 Massive Operations - Modules

1.3.1 Modules massive delete

When deleting modules, it is possible to select the modules to be edited in two ways:


  • Module selection: If you choose search by module you can filter by module type, tags, module status and, in the last section, we will select the agents to which we want to eliminate the filtered modules.


Masivas, eliminar módulos.PNG



  • Agent selection: If you choose search by agent you can filter by agent group, agent status, module status, and tag. Once filtered, we will select the agents that contain modules that we want to eliminate.


Masivas, eliminar módulos SelecAgente.PNG



1.3.2 Modules massive edition

When editing modules, it is possible to select the modules to be edited in two ways:

  • Agent selection: If you choose search by agent you will be able to filter by group, module state, agent state, using tags and the agent or agents that contain modules that you want to modify. Finally, we will select the module or modules.



Operaciones masivas, editar modulos por age.PNG



  • Module selection: If you choose search by module you can filter by module type, status, tag and the module or modules you want to modify. Finally, we will select which agent or agents to make this modification for their modules.



Operaciones masivas, editar modulos por mod.PNG



Once this is done, a menu will be displayed in which we can adjust parameters for these modules. For example to change the contact interval, values for critical state, to modify the group to the selected module...



Operaciones masivas, editar modulos parametros.PNG





Operaciones masivas, editar modulos parametros2.PNG





Operaciones masivas, editar modulos parametros3.PNG



  • FF threshold: FlipFlop (FF) is known as a common phenomenon in monitoring: when a value fluctuates frequently between alternative values (RIGHT/WRONG), which makes it difficult to interpret. When this occurs, a "threshold" is usually used so that in order to consider something as having changed status, it has to "stay" more than X intervals in a state without being altered. We call this in Pandora FMS terminology: "FF Threshold".
  • Post process: Parameter by which the data received by the module can be converted. By default it is disabled with the value 0.
  • FF interval: If the flip-flop threshold is activated and there is a state change, the module interval will be changed for the next execution.
  • 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 sending of a CR. To send several strings in a row in a send/response manner, you're 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 send/receive in several steps, each step should be separated by the '|' (pipe) character.
  • WMI Query: WMI query. It's very similar to a sentence in SQL.
  • Plugin: Once choosed the plugin, you can use the following macros:
    • _agent_: Complete agent's name which fired the alert.
    • _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's 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.
  • Web Checks: This essential field defines the WEB check to be performed. This is defined in one or more steps, or simple requests. These simple requests must be written in a special format in the Web checks field. Checks start with the tab page task_begin and end with the tab page task_end.

1.3.3 Modules massive copy

Module copying allows you to select one or more modules and copy them to the agent of your choosing. Start by filtering them by group, status and agent, which will deploy a tag filter through which the module or modules contained within can be selected, having the possibility to copy their alerts too.


Masivas cop mod.PNG



In the lower zone we select the destination agent or agents for which to copy the modules and alerts. We will be able to filter by group and status.


Masivas cop mod destino.PNG



1.4 Massive Operations - Plugins

Plugins will be able to be edited in a massive way. So, a plugin, the agents which contain it and the data that you want to modify must be chosen.


Masivas, editar plugins.PNG




1.5 Massive Operations - Users

1.5.1 Add profiles massively

In order to add new profiles, you're able to pick profiles, groups and users.


Masivas, añadir usuarios.PNG



1.5.2 Delete profiles massively

In order to delete profiles, you're required to fill out the profile, group and user information.


Masivas, eliminar usuarios.PNG



1.6 Massive Operations - Alerts

1.6.1 Add alerts massively

In order to add new alerts, it's possible to filter by group. To do so, it's required to select an agent, module and the template to add.


Masivas, añadir alertas.PNG



1.6.2 Delete alerts massively

In order to delete alerts, it's possible to filter by group. To do so, it's also required to select a template, group, agent and modules.

Masivas, remover alertas.PNG

1.6.3 Add alert actions massively

In order to add actions to alerts, it's possible to filter by group and to select agents, templates and to select the action you intend to add.


Masivas, añadir acciones.PNG



1.6.4 Delete alert actions massively

In order to delete alert actions, it's possible to filter by group and to select agents, templates and the actions you intend to delete.


Masivas, remover acciones.PNG



1.6.5 Enable/Disable alerts massively

In order to enable or disable alerts, it's possible to filter by group. To do so, it's required to fill out the information about agents, templates and two columns about enabling and disabling the alert options.


Masivas, activar desactivar alertas.PNG



1.6.6 Change standby alerts massively

In order to assign a stand-by state to an alert, it's possible to filter by group. In order to do so, you're required to fill out the information about the agents, templates and the alerts you're intending to put into a stand-by state.


Masivas, alertas standby.PNG



1.7 Massive Operations - Policies

1.7.1 Add policy alerts massively

In order to add alerts, you're required to fill out the destination policy, the template to add, to provide a regular expression to match the agents and modules of the policy.


Politicas, add alerts.PNG




1.7.2 Delete policy alerts massively

In order to delete policy alerts, it's required to fill out the destiny policy, the template to delete, to provide a regular expression to match the policy agents and its corresponding modules.


Politicas, delete alerts.PNG



1.7.3 Add tags to policy modules massively

To add tags to the policy modules you must fill in the target policy and that said module , then select from the list of tags those that you want to add.



Politicas, tags selectmodulos.PNG



1.7.4 Add policy modules to tags massively

To add modules to the tags you must fill in the target policy and that said tag , then select from the list of modules those that you want to add.



Politicas, tags modulos.PNG



1.7.5 Add modules to policies from existing agents massively

To add modules of a certain agent to the policy or policies we want, we must first select the source agent, using filters to make the search more direct. Then you must choose from your list of modules those you want to backup and then from the list of policies those ones to be the backup destination.


Politicas, añadirmodulos.PNG



1.7.6 Edit policy modules massively

To edit modules of a certain policy, first we must select the policy we want. After we must choose from the list of modules the one we want to edit and then fill in the features we want to change.


Politicas, editarmodulos1.PNG



Politicas, editarmodulos2.PNG



Politicas, editarmodulos3.PNG



  • FF threshold: FlipFlop (FF) is known as a common phenomenon in monitoring: when a value fluctuates frequently between alternative values (RIGHT/WRONG), which makes it difficult to interpret. When this occurs, a "threshold" is usually used so that in order to consider something as having changed status, it has to "stay" more than X intervals in a state without being altered. We call this in Pandora FMS terminology: "FF Threshold".
  • Post process: Parameter by which the data received by the module can be converted. By default it is disabled with the value 0.
  • FF interval: If the flip-flop threshold is activated and there is a state change, the module interval will be changed for the next execution.
  • 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 sending of a CR. To send several strings in a row in a send/response manner, you're 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 send/receive in several steps, each step should be separated by the '|' (pipe) character.
  • WMI Query: WMI query. It's very similar to a sentence in SQL.
  • Plugin: Once choosed the plugin, you can use the following macros:
    • _agent_: Complete agent's name which fired the alert.
    • _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's 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.
  • Web Checks: This essential field defines the WEB check to be performed. This is defined in one or more steps, or simple requests. These simple requests must be written in a special format in the Web checks field. Checks start with the tab page task_begin and end with the tab page task_end.

1.8 Massive Operations - SNMP alerts

1.8.1 Edit SNMP alerts massively

Firstly, alerts must be filtered by text, type and priority


SNMP, editaralertasSNMP1.PNG


Once the alerts have been selected, certain parameters may be changed.



SNMP, editaralertasSNMP2.PNG


1.8.2 Delete SNMP alerts massively

First, alerts must be filtered according to text, type and priority, and then selected the alerts to be deleted.


SNMP, borraralertasSNMP1.PNG


1.9 Massive Operations - Satellite

1.9.1 Edit modules massively

Critical and warning fields of modules generated in agents that have been created through satellite can be edited.


Salite, edicionmodulos.PNG


Go back to Pandora FMS Documentation Index