Massive Operations

Massive Operations

Massive operations allow you to carry out actions on agents, modules, users, alerts, policies, SNMP, satellite or plugins in a massive way. The importance of massive operations have grown in large-volume environments. This feature has been designed to make administrators' work easier in situations in which they have to deal with systems that contain a large amount of components.

You may access massive operations by clicking on Configuration > Bulk Operations:

Note: To carry out bulk operations, PHP language requires for the timeout parameters to be properly configured. In order to do it, open the PHP configuration file (php.ini).

To configure the timeout, open the php.ini file and fix its timeout parameters to a correct value:

sudo vi /etc/php5/apache2/php.ini;
 max_execution_time = 0
 max_input_time = -1


You may find more information regarding PHP 7 for Pandora FMS in this link.

Massive Operations: Agents

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Massive agent edition

Within agent edition, you may check those where you may want make changes. You may filter by Group (and check if you wish to include subgrous with Group recursion), Status and even by disabled agents (Show agents).

Once you have checked some, you could modify some parameters massively:

  • Cascade protection: Parameter with which alert overload can be avoided. It is possible to choose an agent or an agent module. In the first case, when the chosen agent is in critical state, the agent will not generate alerts. In the second case, only when the specified module is critical state, 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, they will not be created unless they are already declared in the console.
    • Auto-disable mode: Same as learning mode, but if all modules go into unknown, the agent will be disabled until new information arrives again.

Agent massive delete

Within the mass agent deletion subsection, it is possible to filter by group and state and even by disabled ones.

Massive operations: modules

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Mass module deletion

For module deletion, it is possible to select the modules to be edited in two ways:

  • Module selection: If you choose search by module, first filter by module type and once the screen is updated, choose the tags, module status, etc. and in the last section, select the agents the filtered modules will be deleted from.

  • Agent selection: If you choose search by agent, you may filter by agent group, agent status, module status and tags. Once filtered, select the agents that contain modules to delete and finally delete with the button Delete.

Module 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, select the module or modules.

  • Module selection: If you choose search by module, you may filter by module type, status, tag and the module or modules you wish to modify. Finally, select the agent or agents whose modules you wish to modify.

Once done, a menu will be displayed where you may adjust some parameters for these modules.

Post process: Parameter by which the data received by the module can be converted. It is disabled with the value 0 by default.

  • 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 happens, 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 changing. In Pandora FMS terminology this is called: “FF Threshold”.
  • FF interval: If the flip-flop threshold is enabled 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 sending a CR. To send several strings in a row in a send/response manner, separate them by the character“:”
  • TCP receive: The field to configure the text strings expected to be received 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 is very similar to a sentence in SQL.
  • Plugin: Once selected the plugin, you may use the following macros:
    • _agent_: Name of the agent the module belongs to.
    • _agentdescription_: Description of the agent the module belongs to.
    • _agentstatus_: Current agent status.
    • _address_: Address of the agent the module belongs to.
    • _module_: Module name.
    • _modulegroup_: Module group name.
    • _moduledescription_: Module description.
    • _modulestatus_: Module status.
    • _moduletags_: Tags associated to the module.
    • _id_agent_: Agent ID. It is quite useful to generate a direct URL or to redirect to a Pandora FMS console webpage.
    • _id_module_: Module ID.
    • _policy_: The name of the policy the module belongs to (if that applies).
    • _interval_: Module execution interval.
    • _target_ip_: Module target IP address.
    • _target_port_: Module target port.
    • _plugin_parameters_: Module plugin parameters.
    • _email_tag_: 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 tag task_begin and end with the tag task_end.

Mass module copying

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.

In the lower sections, select the destination agent or agents for which to copy the modules and alerts. Filter by group and status.

Finally click Copy.

Massive Operations: Plugins

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Choose a plugin, the agents that have it and the data you wish to change. Given the case that no module is used uding the selected plugin, a dialogue box will appear informing about that; the module list and the Update button will be disabled.

Massive Operations: Users

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Mass add profiles

To add new profiles, choose the profile from the Profile name list, the group on which to apply permissions and finally the user or users these permissions will be assigned to.

Delete profiles massively

In order to delete profiles, filter them by profile and group and you will be shown the users that meet those criteria. You may delete them by checking the ones you wish and then clicking on Delete.

Massive Operations: Alerts

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Add alerts massively

select the agent or agents, either by filtering by group. If you select several agents, you have the option of showing all agent modules or only those that match. Once the modules have been selected, in the list Alert template, select an alert template and finally click Add to apply it.

Delete alerts massively

To delete alerts, select the template in Alert template and the group. You may show alerts in modules disabled with Show alerts on disable modules, you may select the soubgroups with Group recursion. Select and finally click Delete.

Add alert actions massively

To add actions to the alerts, select one or more Agents with templates then select the desired Alert template and next the action to add (Action). The modules will be shown in the list to the right of When selecting agents.

  • You may filter agents through a group from the Group drop-down list and also include its subgroups by means of the option Group recursion.
  • You may filter modules throught the list When selecting agents:
    • All modules from selected agents (Show all modules).
    • Show only matching modules among selected agents.
    • Show only non-initialized modules or unknown modules (in any of those two statuses).

Finally add the desired action to the modules you have checked and click Create to finish.

Delete alert actions massively

In order to delete alert actions, filter by group in Group. Select agents in Agents with templates, the alert templates that will filter the modules and the actions you intend to delete. Click Delete to finish.

Enable/Disable alerts massively

In order to enable or disable alerts, filter by group, select agents, alert template and you will be shown the alerts within the enabled or disabled alert board. You may move those alerts to the desired board.

Change standby alerts massively

In order to assign a stand-by state to an alert, filter by group, select the agents, alert templates and you will be shown the existing alerts. Move them from the board Stand-by alerts to those active in Alerts without stand-by and the other way around.

Massive operations: Policies

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Add policy alerts massively

In order to add alerts to modules of a certain policy, indicate on which policy you wish to make changes, the alert template you wish to add and the modules on which alerts must be applied.

Delete policy alerts massively

In order to delete policy alerts set the policy whose alert you wish to delete, the alert template you want to delete from the policy and the modules whose alerts you wish to delete.

Add tags to policy modules massively

To add tags to the policy modules, indicate the target policy, the module itself and eventually select from the tag list those you wish to add.

Add policy modules to tags massively

To add modules to the tags set the target policy, the tag itself, and then select from the list of modules those that you want to add.

Add modules to policies from existing agents massively

To add modules from a certain agent to the desired policy or policies, first select the source agent, using filters based on the group and/or module status. Then choose from your module list those you want to copy and then select the policy you wish as backup destination. Click Copy to finish.

Mass operations: Policies

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Mass add policy alerts

To mass add alerts to modules from a certain policy, indicate the police those changes will be applied to. Select the alert template to add, and finally the module/s on which to apply the alerts:

Mass delete policy alerts

To delete alerts from the policies, indicate the policy on which to delet the alert, the alert template to be deleted from the policy and the modules from which to delete those alerts.

Mass add tags to policy modules

To add tags to policy modules, indicate the policy destination, the module itself and finally, select from the tag list, those you need to add.

Mass add policy modules to tags

To add modules to tags, indicate the target policy and the tag itself and then select from the module list those that you need to add for that tag.

Mass add modules to policies from existing agents

To add modules from a certain policy o policies, first you need to select the source agent, being able to use filters based on group and/or module status. Then you must choose from your module list those that will be copied and then select a policy or policies as copy targets. Click Copy to finish.

Edit policy modules massively

To edit modules from a certain policy, first select the source policy. then choose from your module list those to be edited and then fill out the fields to be changed. Once done, click Update to save changes. Describe briefly the module fields right after the images.

  • Flip-Flop Threshold: We know as FlipFlop (FF) a common phenomenon in monitoring: when a value frequently changes among alternative values (RIGHT/WRONG) which makes interpreting it more difficult. When that happens, a “threshold” is usually used so that to consider that something changed status, it must “stay” more than X back-to-back intervals in the same status without changing. We call this in PAndora FMS: FF Threshold
  • Posprocessing: Parameter by which the conversion of the data received by the module can be carried out. By default it is disabled, with value 0.
  • FF interval: In case of having the FF threshold activated and there is a status change, the module interval will change for the following execution.
  • TCP send: Field for configuring parameters to send to port TCP. It admits the ^M string to replace it by sending a carriage return. To send several strings in sending/response sequence, they must be separated by character
  • TCP receive: Field to configure the text strings that are expected to be received in the TCP connection. If they are sent/received in several steps, each steps it is separated by character
  • WMI Query: WMI query, similar to an SQL sequence.
  • Plugin: Once the plugin is selected, the following macros can be used:
    • _agent_: Agent name.
    • _agentdescription_: Agent description.
    • _agentstatus_ : Current agent status.
    • _address_: Agent adress.
    • _module_: Module name.
    • _modulegroup_: Module group name.
    • _moduledescription_: Module description.
    • _modulestatus_: Module status.
    • _moduletags_: Module-associated tags.
    • _id_agent_: Agent ID, useful for building the URL directly or redirecting to Pandora FMS console.
    • _id_module_: Module ID.
    • _policy_: Policy name (if appropriate).
    • _interval_: Module execution interval.
    • _target_ip_: Module target IP adress.
    • _target_port_: Module target port.
    • _plugin_parameters_: Module Plug-in parameters.
    • _email_tag_: Emails associated to module tags.
  • Web checks: This field is essential, it defines WEB checks to be carried out. This is define in one or several steps or simple requests. These simple requests must be written in a special format in the Web checks field. Checks are initiated with the tag task_begin and are finished with the tag task_end.

Massive operations: SNMP alerts

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Edit SNMP alerts massively

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

Once the alerts have been selected, you may change certain parameters. Then click Update to save the changes.

Delete SNMP alerts massively

First, alerts must be filtered according to text, type and priority, and then the selected SNMP alerts will be shown in SNMP alerts to be deleted. Select one or more and then click Delete to complete the process.

Mass operations: Satellite

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Edit modules massively

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

Massive operations: Services

This section is available from Pandora FMS version 748

Remember that to operate correctly with services, it is necessary to have the Prediction server enabled

Esta captura de pantalla ha sido simplificada con propósitos didácticos. Además puede diferir de la versión actual.

Mass service creation

Mass service creation allows to create new services by adding several elements at the same time. It is a very useful tool for creating new services made up of many elements with the same priority level.

  • Service(s) definition: It contains the same fields as the manual service creation: service name, agent where the modules created by the service will be stored, mode, thresholds for going into Critical and Warning, SLA calculation, alert assignment…

The only field that is different from manual service creation is:

  • Create a service per item: When enabled, a service will be created for each element selected in the bottom lists. This is very useful for keeping a constant SLA calculation on critical elements (e.g. link availability SLA). If enabled, a new field called Services Header will appear, where you may configure a common header text for all services that will be created for each element.

  • Item(s) definition: Here select the items (agents, modules or other services) that you will add to the service that will be created. To add them, once you have selected the items that you wish to add, click Add selected.

  • Service items summary: Select the weights that will have ALL the elements to add. If some specific weights must be modified for a particular element, once added it must be configured later within the service. These weights will be saved regardless of whether they are to be used (Manual mode) or not (Smart mode).

To finish, click on Create services.

Mass add elements to services

Versior 756 or superior.


This option allows adding several elements at once to the selected service. If it is a service in Manual mode, all elements with the same weight will be added.

  • Select service to be modified: List where the service to add the elements to must be selected.
  • Item type to be added: Type of element to be added to the service. It is possible to select among Agents, Modules and Services. It is possible to select more than one type of element in the same operation.

All selected elements will appear as a summary in the corresponding lists at the end of the page ( “Selected services”, “Selected agents”, “Selected modules” ). After selecting all the necessary items to add to the selected service, click Add elements and they will be added with the weights configured in section Service items summary.

Mass edit service elements

Version 756 or superior.


This option allows editing weights from several elements at once to the selected service.

After selecting the service that contains the elements to be edited by means of the list Select service to be modified, all the elements that service contains will be loaded in the selection lists at the end of the page. Only elements whose weights are to be edited must be selected and the new values must be edited and configured in the weight fields from section Service items summary. After clicking Update selected service elements, selected element weights will be updated to those configured.

This only applies to manual services, weights of services in Smart mode are always calculated automatically.

Mass delete elements from services

Version 756 or superior.


This option allows to delete several elements at once from the selected service.

After selecting the service that contains the elements you wish to delete from the list Select service to be modified, all elements that service contains will be loaded in the selection lists at the end of the page. Once selected, click Remove selected.

Mass service deletion

It will show you the list of all the services that have been created in our Pandora FMS system, on which we can select several and click on 'Delete' to delete them. This will also delete the modules created by the services we will delete.

Go back to Pandora FMS documentation index