====== Differences between Templates, Policies and Bulk Operations ======

{{indexmenu_n>34}}

<WRAP center round todo 60%>

We are working on the translation of the Pandora FMS documentation. Sorry for any inconvenience.

</WRAP>

===== Differences between Templates, Policies and Bulk Operations =====

The three concepts may seem similar, but in practice they work and have different objectives. This section will explain the differences and how to make correct use of each tool.

==== Templates ====
The **templates** allow the creation of a set of Remote Modules in a simple way. When applying the template to an Agent, all the Modules of the template will be created in it, in no case will they delete or modify the existing ones. If, after applying a template, changes are made to it, they will only become effective in the Agents when applying it again: if the Modules already exist in the Agent, they will be created again.

In addition to being useful for creating Modules on Agents that already exist on Pandora, templates can be used to automatically create Modules when running a Recon Task. The application of the templates is done through the Pandora console.

{{ wiki:Scheme-applying-templates.png?700 }}

=== When to use Templates? ===
   * When you want to apply a standard of Remote Modules to Agents quickly.
   * When you want to create new Remote Modules in Agents discovered by a Recon Task.

==== Policy ====

**Policies** are an easy way to manage **thousands of Agents**. They contain all the information to manage (create, delete and modify) any element related to the monitoring of Pandora Agents. Modules, alerts, file collections, inventory modules, plugins and the Agent filter on which the policy will be applied are defined in a policy.

   * The first difference with the templates is that the policies support all kinds of Modules, as well as alerts and file collections.
   * The second difference is that the policies support updating Agents, deleting and editing each of the components configured in the policy.

The policies are applied by the Pandora FMS server that creates, deletes or modifies the elements defined in the policy in each of the Agents defined in it simultaneously (in a single application).

{{ wiki:Scheme-applying-policies.png?700 }}

=== When to use the Policies? ===
   * When you need to monitor a large number of machines in a simple way.
   * When you want to parameterize the monitoring of a large number of machines.

==== Massive Operations ====
**Massive operations** allow you to manage Agents, Modules, users, alerts or policies on a large number of those objects. The main difference between [[en:documentation:pandorafms:complex_environments_and_optimization:01_massive_operations|Massive Operations]], [[en:documentation:pandorafms:management_and_operation:03_templates_and_components|Templates]] and [[en:documentation:pandorafms:complex_environments_and_optimization:02_policy|Policies]] is that Massive Operations are a tool to manage the different components of Pandora FMS instantly and on the spot, without having to build any type of template or default configurations and that do not need to be used again. They are very useful when you want to make the same change to a large number of Agents, alerts, Modules, etc.

Examples:

   * Move a group of Agents.
   * Change the action of all alerts so that they send an email to the same person.
   * Change the maximum and minimum values for the Module called ''CPU Usage'' in all Agents.

Massive operations are actions that are performed through the Pandora console on each of the monitoring components: agents, modules, alerts, policies, etc.

{{ wiki:Scheme-using-massive-operations.png?700 }}

=== When to use Bulk Operations? ===
   * When you want to make the same change to a large number of elements (Agents, alerts, policies, Modules, etc).

[[:en:documentation:start| Back to Pandora FMS documentation index]]