Monitoring policy system in Pandora FMS. What they are like, what they are and where to find them
This post is also available in : Spanish
“Monitoring policy system”, “monitoring policy system”, “monitoring policy system”… As much as you repeat it, it still sounds boring, unappetizing and expensive. But you have to admit that an in-depth contact with the monitoring policy system, especially the system that concerns you, is also useful, convenient and practical after all. Therefore, to benefit you, we will start today with the policies in Pandora FMS. So take courage, concentrate and let’s go read!
Policies in Pandora FMS. What they are like, what they are and where to find them
Pandora FMS policies are designed for those customers who own large monitoring environments. At the beginning of Pandora FMS, each monitoring element had to be managed individually, which entailed investing a lot of time particularly in large environments. Due to this fact, we came up with the possibility of managing the monitoring of a company in an homogeneous and centralized way, and that is the purpose of policies.
What is a policy and where can I find it?
A policy is no more than a Pandora FMS functionality focused on large work environments, with which you can manage monitoring swiftly and effectively. This feature is exclusively reserved for the Enterprise version of Pandora FMS. Once you open the Pandora FMS console, go to the Configuration -> Policies menu where the policies created by Pandora FMS by default are shown, together with the customized ones and you can manage all of them or create new ones there.
What can I do with policies?
The only requirement necessary before starting a policy is that you must have previously created all the agents that are going to be used in the policy, since there is no option to create agents within a policy.
Once you have carried out this first step, you can start managing Pandora FMS policies. Within policy operations you can create a new policy and modify/duplicate/delete an existing policy, as well as import new policies. It should be highlighted that, in order to delete an existing policy, no agent of Pandora FMS must belong to this policy, otherwise it will be necessary to delete all the agents belonging to the policy to be eliminated.
Let’s show the example of creating a new policy. Firstly, give it a symbolic name and a small description. Once created, add the monitoring you want, so you can:
- Add or delete agents or groups to which apply the desired monitoring.
- Add, delete or modify modules.
- Add, delete or modify an agent plugin.
- Add, delete or modify an alert on a policy module.
- Add, delete or modify an alert of a module not created by a policy.
- Add or delete an inventory module.
All the changes that are made in the policy (add, delete or modify any parameter) are added to a “queue” of actions to be carried out in the policy. Once you finish configuring everything you want to add in the created policy, go to the “queue” view of policies and apply all pending changes. It is important to keep in mind that any change made in the policy will not be effective until the policy in the “queue” is applied.
Once the policy is applied, everything that has been configured in it will be created. It should be noted that at the time of creating the modules through the policy you can see three different types of modules.
Firstly, the linked modules. They are just modules created by the policy, which can only be managed from the policy that has been created. In case the policy is deleted, the module will also be deleted.
Secondly, the adopted modules. These are modules that have been applied by the policy, but which already existed with the same name before creating the policy. In this case, the modules will begin to use the data added by the policy and they will be managed from said policy. Unlike the previous modules, if the policy is deleted, the modules will continue to exist, but they will use the data with which they were locally generated.
Finally, the non-linked modules. These are modules that have been created within the policy, but that will no longer be managed by this one. It is a special case used to create “individual exceptions” to policy modules. As in the previous case, when the policy is deleted, the module will not be deleted.
This monitoring policy system is not clear enough yet, any real example?
Let’s take the example of a company that wants to monitor different elements in the following way: it wants to perform a specific type of monitoring for each type of element (switch, router, server …) and a specific global monitoring for all of them. To be able to carry out this monitoring, without having to individually create each module/alert… in each agent to be monitored, the following policies would be created:
A “global” policy would be created, in which to add all the created agents regardless of the type of element they point to, where you would configure the common elements that you want to monitor in all of them.
Then a “specific” policy would be created for each one of the different elements that make up the environment to be monitored, where only the agents of each type would be added in their corresponding policy with the specific elements to be monitored in each one of them.
If you have gotten to this point and read about our monitoring policy system, you already know what Pandora FMS is like: “That flexible monitoring system which is capable of monitoring devices, infrastructures, applications, services and business processes…” But if you still want to know more about system monitoring this is the right place to learn more. Lucky you! In this blog there are dozens of articles that can get you in this exciting world. Here is a link to our home page: https://blog.pandorafms.org/
Or you can also get to know Pandora FMS directly. Click here: https://pandorafms.com/
You can even send us any questions you may have about Pandora FMS. Do it in a very simple way, thanks to the contact form which is located at the following address:https://pandorafms.com/contact/