Difference between revisions of "Pandora: Documentation en: Managing and Administration"

From Pandora FMS Wiki
Jump to: navigation, search
(Assignment of profiles and groups with user management permission (UM).)
 
(90 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
 +
 +
{{WIP}}
  
 
= Pandora FMS  Management=
 
= Pandora FMS  Management=
Line 5: Line 7:
 
== Introduction ==
 
== Introduction ==
  
This chapter deals with several aspects of the daily management of Pandora FMS such as: group administration, user creation, etc.
+
This chapter deals with several aspects of Pandora FMS daily management such as: group administration, user creation, backups, workspace, etc.
  
 
==  Profiles, users, groups and ACL ==
 
==  Profiles, users, groups and ACL ==
  
Pandora FMS is a Web management tool that allows multiple users to work with different permissions in multiple groups of agents that are defined. Before adding users, the groups and profiles must be well defined and have a clear understanding of what data visibility we want each user to have.
+
Pandora FMS is a Web management tool. Thanks to its 100% multitenant permission system, multiple users can work with different permissions accessing Pandora FMS setup without seeing each other's information.
  
Pandora's permissions system is 100% ''multitenant'', that is to say, that different clients or departments access the information of the same Pandora setup without some of them seeing the information of the others.
+
To add users, it is important to have groups and profiles properly defined, and know exactly which data you want each user to see and/or modify.
 +
 
 +
<center>
 +
[[image:Standard-user-profile.jpg]]
 +
</center><br>
  
 
=== Users in Pandora FMS ===
 
=== Users in Pandora FMS ===
  
Users are managed from ''Profiles > Users management'', where you can view the list of defined users.
+
Users are managed from ''Profiles > Users management'', where you may see the list of defined users.
  
 
<center><br><br>
 
<center><br><br>
Line 21: Line 27:
 
</center><br><br>
 
</center><br><br>
  
The user definition consists of the following fields:
+
User definition consists of the following fields:
  
 
<center><br><br>
 
<center><br><br>
Line 27: Line 33:
 
</center><br><br>
 
</center><br><br>
  
We detail the relevant user fields:
+
Here are the relevant user fields:
  
*'''User ID''': Identifier to be used by the user to authenticate in the application. This is a value that is used as an identifier, so it should not have rare characters or spaces.  
+
* '''User ID''': Identifier that the user will use to authenticate himself in the application. This identifier is a value that should not have rare characters or spaces.  
*'''Full Display Name''': field where the complete name is placed, this is a descriptive field and may contain spaces and non-standard characters.
+
* '''Full Display Name''': Field where you put the full name, this if it is a descriptive field and can contain spaces and non-standard characters.
* '''Timezone''': field where you put the time zone of the console for the visualization of different elements(Agent detail,Monitor detail, ...).
+
* '''Password''': Password that the user will have to access.
*''' Global Profile''': An Administrator user will not be governed by the internal ACL system and will have access to everything. The standard user will be governed by the permissions assigned to them according to the different Pandora ACL systems.
+
* '''Global Profile''': An Administrator user will not be governed by the internal ACL system and will have access to everything. The standard user will be ruled by the Pandora FMS ACL permissions assigned to him.
*'''Skin''': field where you can choose a custom skin.
+
* '''E-mail and phone''': Optional fields where we can add extra user information.
*'''Interactive charts''': field where you can choose whether the user sees dynamic or static graphs. This setting allows you to overwrite the one defined by the system.
+
* '''Login Error''': If this field is marked, the user will only be able to access to the API but not in an interactive way through the console.
*'''Block size for pagination''': Block size by default for that user.
+
* '''Session time''': Time in which the user can be connected without activity before the user considers his session expired and forces him to authenticate again.
*'''Not login'': if this field is checked, the user will only be able to access the API but not interactively through the console.
+
* '''Language''': By default is the system language. You can also assign a specific language in which the user will see the Pandora FMS console.
*'''Home screen''': change the default screen to which the user enters after logging into the console, for example, the event viewer, or a visual console defined by the administrator.
+
* '''Timezone''': Field to put the console time zone to visualize different elements (Agents General View, Modules View, ...).
*'''Default event filter''': to define the default filter that the user will have when entering the event view. Then you can change it, but this will be the one that applies "by default".
+
* '''Block size for pagination''': Default size of pagination for this user.
*'''Session time''':Time in which the user can be logged on without activity before the user considers his session expired and forces them to authenticate themselves again.
+
* '''Skin''': Field where you can choose a custom skin.
 +
* '''Home screen''': Change the default screen the user enters after logging in the console, for example, the event viewer, or a visual console defined by the administrator.
 +
* '''Default event filter''': Allows to define the default filter that the user will have when entering the event view. Later you can change it, but this will be the one applied "by default".
 +
* '''Disabled newsletter''': Activate or deactivate the Pandora FMS newsletters.
 +
* '''Comments''': Additional information to the fields defined above.
 +
* '''Profiles/Groups assigned to this user''': Selection of profiles and/or groups in which the user will be organized or have access to.  
  
==== User Edition by the own User ====
+
==== User Edition by the User itself ====
  
 
All users can modify certain parameters of their own settings in ''Workspace > Edit my User''.
 
All users can modify certain parameters of their own settings in ''Workspace > Edit my User''.
  
The user creation form appears where you can configure some sections, except of course, the permissions on groups.
+
The user creation form will appear, where you can configure some sections, except for group permissions.
  
 
<center><br><br>
 
<center><br><br>
 
[[image:gestusuario.png|800px]]
 
[[image:gestusuario.png|800px]]
 
</center><br><br>
 
</center><br><br>
 +
 +
===== Notification setup =====
 +
 +
To customize logged-in user’s notifications, the administrator must have previously granted him notification edition permissions. In case of having said permissions, as well as all options activated, notifications and their forwarding by email can be enabled/disabled.
 +
 +
<center>
 +
[[image:Notificaciones1.PNG]]
 +
</center><br>
 +
 +
Notifications allow to see warning messages related to the following sections on screen:
 +
 +
* <b>System status</b>. Where the following notifications are generated:
 +
** Expired or nearly expired license warning (~15 days or less).
 +
** Too many files attached warning.
 +
** Piled-up .data files in data_in warning (> 1000 files and increasing).
 +
** Piled-up BADXML files in data_in warning (> 150 files).
 +
** Overall module queuing (increasing) by server warning.
 +
** PHP setup warning.
 +
** Review whether pandora_db is running on the main database.
 +
** Review whether pandora_db is running on the history database.
 +
** History database update status (MR correct).
 +
** Status warnings, component down or uninitiated => Any of the Pandora FMS servers with status=1 and ''keepalive - now()'' may be higher than ''server_keepalive * 2''.
 +
** Tentacle service down.
 +
** No master-mode server warning.
 +
** In the case of activated logs, Elastic/Logstash connectivity status.
 +
** In case of using Pandora FMS HA, error in DB replication.
 +
** Connection error with GIS map servers GIS (WMS).
 +
** Log size.
 +
** Mounting point/disk/almost full volume warning (data_in/mysql/tmp...)(> 90%).
 +
** History database connection failure.
 +
** Metaconsole synchronization failure.
 +
** Next scheduled shutdowns (in less than 15 days).
 +
** Metaconsole: Synchronization status:
 +
*** Node synchronization failures.
 +
*** Event replication failures.
 +
*** Agent cache.
 +
 +
* <b>Message</b>:
 +
** Messages received by the user yet to be read.
 +
 +
* <b>Pending task</b>:
 +
** Policies yet to be applied.
 +
** Queued policies running/complete, and acknowledged once completed.
 +
** Pending re-creation policies.
 +
** Defined server plugins whose executable does not exist.
 +
** Metaconsole:
 +
*** Pending synchronization tasks.
 +
*** Completed synchronization tasks.
 +
*** Pending notifications by node.
 +
*** Policy queue status.
 +
 +
* <b>Advertisement</b>.
 +
** Enterprise version not installed reminder.
 +
** Do you know our Enterprise version?
 +
** Do you know the module library?
 +
** Discover eHorus.
 +
** Discover Integria IMS.
 +
 +
* <b>Official communication</b>:
 +
** Update notifications.
 +
** Messages generated from Ártica ST headquarters (update to PHP7, phantomjs, etc.)
 +
 +
* <b>Suggestion</b>:
 +
** Did you know Pandora FMS can be integrated with Telegram?
 +
** Did you know alerts can be scaled?
 +
** Monitor your complete applications using services.
 +
 +
The options found in notification setup are these:
 +
 +
* <b>Notified users</b>: Users that will receive the activated notifications.
 +
* <b>Notified groups</b>: Groups that will receive the activated notifications.
 +
* <b>Notify all users</b>: Option that will allow to notify all users.
 +
* <b>Also email users with notification content</b>: To enable sending emails for each notification.
 +
* <b>Users can modify notification preferences</b>: To allow users to modify notification preferences (the system administrator can restrict this option).
 +
* <b>Users can postpone notifications up to</b>: It allows to postpone notifications so that they are not received more than once in a certain interval (which can be chosen in the drop-down).
  
 
=== Groups in Pandora FMS ===
 
=== Groups in Pandora FMS ===
 +
====Introduction====
 +
The concept of group in Pandora FMS is fundamental. The groups are sets of elements with their own rules whose purpose is to help to control user access to certain elements inside Pandora FMS.
 +
 +
It is important to know that an agent can only belong to one group, but that a user can have access to one or several of these groups.
 +
 +
When configuring the groups, it will be necessary to take into account that the group All is a special group that cannot be eliminated, and all the groups are its subgroups. Any element that is associated to the All group can be seen/administered by a user that has permissions in any group.
  
The concept group in Pandora is fundamental. It serves to regulate the system of access to agents for a user. An agent can only belong to one group and a user can access one or more groups.
+
====Group all====
  
{{Warning|The group ''All'' is a especial group which can't be deleted. Every group is a subgroup of the ''All'' group. Any element (report, graph, event...) associated to the group ''All'' will be seen/managed by a user that has permissions in any group.}}
+
Pandora FMS has a group system, which are entities into which agents are classified and which are used to grant permissions. That way users are granted some permissions assigned to one or several groups, and thus they will be able to interact with agentes and other elements in their context.
 +
 
 +
To make group assigning and filtering easier, there is a tool called group "All". Group "All", depending on the context, means ALL groups or ANY of them. From version 3.1 is exclusive identifier is ID 0. But it is totally controlled by the code, ther is no group with that ID in the DB.
 +
 
 +
====Group creation====
  
 
Groups are defined in the section  ''Profiles > Manage agent groups''.
 
Groups are defined in the section  ''Profiles > Manage agent groups''.
Line 63: Line 159:
 
</center><br><br>
 
</center><br><br>
  
Inside a group's creation / modification, we have some fields that require an explanation:
+
Inside group creation / modification, there is the following form:
This form will appear:
 
  
 
<center><br><br>
 
<center><br><br>
Line 70: Line 165:
 
</center><br><br>
 
</center><br><br>
  
We detail the relevant user fields:
+
These are the relevant user fields:
 +
 
 +
* '''Name''': Group name. This group can be used in the automatic agent provisioning, so it is not recommended that it contains spaces or rare characters (although it is supported).
 +
* '''Icon''': Combo where the icon for the group can be chosen.
 +
* '''Parent''': Combo where another group can be defined as the parent of the group being created.
 +
* '''Password''': Optional. It allows restricting automatic agent creation (automatic software or satellite agent provision) so that only agents with the same password as the one defined in this field can be created.
 +
* '''Alerts''': If checked, the agents belonging to the group will be able to send alerts. If not checked, alerts will not be sent. You can use this property to quickly disable alert generation for a certain group of agents.
 +
* '''Propagate ACL''': If enabled, the child groups will have the same ACL permissions as the group.
 +
* '''Custom ID''': Groups have an ID in the database. In this field it is possible to set another custom ID that can be used from an external program to perform an integration (e.g. CMDBs).
 +
* '''Contact''': Contact information accessible through _groupcontact_ macro.
 +
* '''Skin''': A skin can be assigned to the group.
 +
 
 +
====Importing groups from CSV====
 +
<br>
 +
{{Metaconsole}}
 +
 
 +
This is an Enterprise feature. The extension allows to import a file separated by some separating character in Pandora FMS server.
 +
 
 +
Access the extension from ''Admin tools > Extensions manager > CSV import group''.
 +
 
 +
<center>
 +
[[image:ex17.png|800px]]
 +
</center><br>
 +
 
 +
The file to be imported is chosen by clicking on “Select file” and the combo is chosen from a combo. Once the previous fields are filled out, click “Go”.
  
* '''Name''':group name. This group can be used in the automatic provisioning of agents, so it is not recommended that it contains spaces or rare characters (although it is supported).
+
The CSV file must contain the following fields in the following order: Group name, icon, parent id and propagation (1 or 0).
* '''Icon''': combo where the icon for the group can be chosen.
 
* '''Parent''': combo where another group  can be defined as the parent of the group being created.
 
* '''Password''': optional. It allows restricting the automatic creation of agents (automatic provision of software or satellite agents) so that only agents with the same password as the one defined in this field can be created.
 
* '''Alerts''': if checked, the agents belonging to the group will be able to send alerts, if not checked they will not be able to send alerts. You can use this property to quickly disable the generation of alerts for a certain group of agents.
 
* '''Propagate ACL''': if enabled, the child groups will have the same ACL permissions as the group.
 
* '''Custom ID''':  groups have an ID in the database; in this field it is possible to put another custom ID that can be used from an external program to perform an integration (e. g. CMDB' s).
 
* '''Contact''': contact information accessible via the _groupcontact_ macro
 
* '''Skin''': a skin can be assigned to the group.
 
  
 
===  Profiles in Pandora FMS ===
 
===  Profiles in Pandora FMS ===
  
Pandora profiles allow you to define what permissions a user can have. The combination of profiles plus a group, associated with a user, allows you to define what permissions a user has over a group of agents, so that they can have different profiles in different groups. Profiles are managed from ''Profiles > profile management''.
+
Pandora FMS profiles allow to define which permissions a user is granted. The combination of profiles and a group associated to a user allows to define which permissions a user has on a group of agents, so that he can have different profiles in different groups. Profiles are managed from ''Profiles'' > ''Profile management''.  
  
 
<center><br><br>
 
<center><br><br>
 
[[image:gest1.png|800px]]
 
[[image:gest1.png|800px]]
 
</center><br><br>
 
</center><br><br>
 +
 +
==== List of profiles ====
  
 
This list defines what each profile enables:
 
This list defines what each profile enables:
  
 
<table cellpadding=1 cellspacing=1 style='background-color: #f0f0f0; border: 1px solid #acacac'>
 
<table cellpadding=1 cellspacing=1 style='background-color: #f0f0f0; border: 1px solid #acacac'>
<tr><th style='background-color: #cacaca'>Operation<Th style='background-color: #cacaca'>Access Bit
+
<tr><th style='background-color: #cacaca'>BIT ACCESS<th style='background-color: #cacaca'>OPERATION
<tr><td>See agent data (all views) <td>AR
+
<tr><td>IR<td>- See incidents
<tr><td>Tactical view <td>AR
+
<tr><td>IW<td>- Validate traps<br>- Messages
<tr><td>Group view <td>AR
+
<tr><td>IM<td>- Manage incidents<br>- View agent data (all views)<br>- Tactical view<br>- Group view<br>- See users<br>- See SNMP console<br>- Tree view<br>- Extension Module Group<br>- Search bar
<tr><td>Create a visual console <td>RW
+
<tr><td>AW<td>- Agent management view<br>- Edit agent and its .conf<br>- Massive operations<br>- Create agent<br>- Duplicate remote configuration<br>- Policy management
<tr><td>Create a report <td>RW
+
<tr><td>AD<td>- Management of service stops<br>- Deactivate agent/module/alert
<tr><td>Create a combined graph <td>RW
+
<tr><td>LW<td>- Alert assignment already created<br>- Alert management
<tr><td>See report, graph, etc. <td>RR
+
<tr><td>LM<td>- Define, modify templates, commands and actions
<tr><td>Apply report template<td>RR
+
<tr><td>UM<td>- User management
<tr><td>Create report template<td>RM
+
<tr><td>DM<td>- Database Maintenance
<tr><td>See event <td>ER
+
<tr><td>ER<td>- See event
<tr><td>Validate/Comment event <td>EW
+
<tr><td>EW<td>- Validate/Comment event<br>- Manage filters<br>- Execute responses
<tr><td>Delete event <td>EM
+
<tr><td>EM<td>- Delete event<br>- Change owner/Re-open event
<tr><td>Excecute responses<td>EW
+
<tr><td>RR<td>- View report, graph, etc<br>- Apply a report template
<tr><td>Create an incidence through the event (Response) <td>EW&IW
+
<tr><td>RW<td>- Create a visual console<br>- Create report<br>- Create combined Graph
<tr><td>Manage responses<td>PM
+
<tr><td>RM<td>- Create a report template
<tr><td>Manage filters<td>EW
+
<tr><td>MR<td>- Network map view
<tr><td>Personalize event columns<td>PM
+
<tr><td>MW<td>- Editing network maps<br>- Deleting own network maps
<tr><td>Change owner/Re-open event <td>EM
+
<tr><td>MM<td>- Deletion of any network map
<tr><td>See users <td>AR
+
<tr><td>VR<td>- Visual console view
<tr><td>See Console SNMP <td>AR
+
<tr><td>VW<td>- Visual console edition<br>- Deletion of own visual consoles<br>- Deletion of any visual console
<tr><td>Validate traps <td>IW
+
<tr><td>VM<td>- Visual console management
<tr><td>Menssages <td>IW
+
<tr><td>PM<td>- Manage responses<br>- Customize event columns<br>- Update manager (Operation and Administration)<br>- Manage groups<br>- Create inventory modules<br>- Manage modules (including all sub-options)<br>- Manage SNMP console<br>- Manage profiles<br>- Manage servers<br>- System audit (edit and view)<br>- Setup (all lower tabs incl)<br>- Administration extensions
<tr><td>Cron jobs <td>PM
+
<tr><th style='background-color: #cacaca'><th style='background-color: #cacaca'>PERMITS COMBINATION
<tr><td>Tree view <td>AR
+
<tr><td>EW & IW<td>- Create incidence through the event (Response)
<tr><td>Update manager (Operation and Management) <td>PM
+
<tr><td>LM & AR / AW & LW<td>- Validate alerts
<tr><td>Extension Module Group<td>AR
 
<tr><td>Agent management view <td>AW
 
<tr><td>Editing the agent and its .conf <td>AW
 
<tr><td>Assigning already created Alerts <td>LW
 
<tr><td>Define, modify templates, commando and actions <td>LM
 
<tr><td>Group management <td>PM
 
<tr><td>Create inventory modules <td>PM
 
<tr><td>Manage modules (Including all suboptions)<td>PM
 
<tr><td>Massive operations <td>AW
 
<tr><td>Create agent <td>AW
 
<tr><td>Duplicate remote configuration <td>AW
 
<tr><td>Management of downtimes<td>AD
 
<tr><td>Alert management <td>LW
 
<tr><td>User management <td>UM
 
<tr><td>SNMP Console management <td>PM
 
<tr><td>Profile management<td>PM
 
<tr><td>Server management<td>PM
 
<tr><td>System audit (editing and visualization)<td>PM
 
<tr><td>Setup (all lower flaps incl) <td>PM
 
<tr><td>DB maintenance <td>DM
 
<tr><td>Extension management <td>PM
 
<tr><td>Searcha bar <td>AR
 
<tr><td>Plicy management<td>AW
 
<tr><td>Deactivate agent/module/alert<td>AD
 
<tr><td>Validate alerts<td>LM&AR o AW&LW
 
<tr><td>Network maps view<td>MR
 
<tr><td>Network maps  editing<td>MW
 
<tr><td>Deleting own network maps<td>MW
 
<tr><td>Deleting any network map <td>MM
 
<tr><td>Visual console view<td>VR
 
<tr><td>Visual console editing<td>VW
 
<tr><td>Deleting own visual consoles<td>VW
 
<tr><td>Deleting any visual console<td>VM
 
  
 
</table>
 
</table>
  
=== Permission assignment===
+
=== Permission granting ===
 +
From user editing, you may grant a user access to a group with a certain profile:
  
From the user output, you can assign a user access to a group with a certain profile:
+
<center>
 +
[[Image:acl_groups.png|center]]
 +
</center>
 +
 
 +
If you do not assign any group or profile to the user, when the user tries to log in, there will be a login error like the one below:
  
 
<center>
 
<center>
[[Image:acl_groups.png|center]]
+
[[Image:Fallo_login.png|center]]
 
</center>
 
</center>
  
In this example, the user has access with the operator profile to the "ehorus" and "hosting" group.
+
==== Assignment of profiles and groups with user management permission (UM).====
 +
 
 +
From Pandora FMS version 748 on, an improvement in the management of users, permissions and groups is enabled.
 +
 
 +
Several possible scenarios have been taken into account, which we will now explain:
 +
 
 +
*A "manager" user with UM permissions that belongs to the group ALL will be able to manage any user regardless of the group he belongs to.
 +
*Accesses to groups can be added before creating a user as such.
 +
*A "manager" user can edit profiles and groups only on the users he can see because they belong to the groups he manages with UM permissions.
 +
*An administrator user can create other administrator users and can manage any other user, but in no case a "manager" user with UM permissions can remove UM permissions to another user who has the same permissions on the same group. This can only be modified by an administrator.
 +
*A "manager" user without UM permissions on a group, can not see which users belong to that group.
 +
*A "manager" user can eliminate the relation of users with the groups that it manages and even the complete user if only this one has relation with the groups that it manages.
 +
 
 +
{{warning|In case the last profile/group relationship of an user is going to be deleted and the user is going to be deleted Pandora shows a warning.}}
 +
 
 +
*A "manager" user that has UM permissions in a group and not in another one, can only see the profile/group information of the groups that he manages, even if the user he observes has more permissions of other groups. The rest of the user's information will be unrelated to the "manager" user. In this way the "manager" user will only be able to obtain information or modify the permissions on the groups that he manages, but at no time will he be able to remove more permissions or eliminate the user.
  
 
==== Permission system extended by tags ====  
 
==== Permission system extended by tags ====  
  
In the Enterprise version, individual access to an agent's modules can be configured with a Tag system. Tags are configured in the system, assigned to the modules you want and additionally, you can restrict access to a user only to modules that have those tags defined.
+
In the Enterprise version, individual access to the modules of an agent can be configured by a Tag system. Some tags are configured in the system, they are assigned to the modules you wish, and additionally, access may be restricted to a user only to the modules that have those tags defined.  
  
 
<br>
 
<br>
 
{{Tip|Access by Tags does not replace access by groups, it only complements it.}}
 
{{Tip|Access by Tags does not replace access by groups, it only complements it.}}
  
Tags are defined in ''Profiles > Module Tags''.
+
Tags are defined in ''Profiles'' > ''Module Tags''.
  
 
<center><br><br>
 
<center><br><br>
Line 178: Line 278:
 
</center><br><br>
 
</center><br><br>
  
In the configuration of a module, one or more tags can (optionally) be assigned to it:
+
In module configuration, one or more tags can (optionally) can assigned:
  
 
<center>
 
<center>
Line 184: Line 284:
 
</center>
 
</center>
  
To assign specific access to a tag, it is done through the user editor, in the profile and group assignment, adding a tag:
+
You may assign specific access to a tag through the user editor, in profile and group assigning, by adding a tag:
  
 
<center>
 
<center>
Line 190: Line 290:
 
</center>
 
</center>
  
In this example, the user has access with the operator profile to the "ehorus" and "hosting" group and also to the "Infrastructure" group, but only to the modules marked with the "Security" tag.
+
In this example, the user has access by means of the operator profile to the "eHorus" and "hosting" group and also to the "Infrastructure" group, but only to modules labeled with the "Security" tag.
  
{{Warning|This system, which we call Tag-based security mode allows restricting access to all agent content, but has performance impact, so it is designed exclusively to give access to small portions of information, that is, it should not be used with more than two or three tags per user/profile/group combination.}}
+
{{Warning|This system, which is called Tag-based security mode allows restricting access to all agent content, but it has performance impact, so it is designed exclusively to give access to small portions of information, that is, it should not be used with more than two or three tags per user/profile/group combination.}}
  
{{Tip|In some global views (tactical view, group view, general tree counts) the totals show all the modules, not just the "visible" for the tag. }}
+
{{Tip|In some global views (tactical view, group view, general tree counts) the totals show all the modules, not just the ones "visible" by the tag. }}
  
==== Jerarquía ====
+
==== Hierarchy ====
  
En apartados anteriores, se explicó que los permisos de un grupo se pueden extender a los hijos mediante la opción de configuración '''Propagate ACL'''. Sin embargo, desde la configuración de usuarios, se puede limitar esta funcionalidad y evitar que el ACL se propague marcando ''No hierarchy''.
+
In previous sections, we explained that the permissions of a group can be extended to the children by means of the configuration option ''Propagate ACL''. However, from user configuration, you may limit this feature and prevent the ACL from propagating by checking ''No hierarchy''.
  
Como referencia para los ejemplos, se plantea una configuración con dos grupos padre "Applications" y "Databases" con dos hijos cada uno, "Development_Apps" y "Management_Apps" para el primero y "Databases_America" y "Databases_Asia" para el segundo. Ambos grupos padre están marcados para que se propague el ACL.
+
As a reference for the examples, here we propose a configuration with the two parent groups "Applications" and "Databases" with two children each, "Development_Apps" and "Management_Apps" for the first one and "Databases_America" and "Databases_Asia" for the second one. Both parent groups are set for ACL to be spread.
  
 
<center>
 
<center>
Line 206: Line 306:
 
</center>
 
</center>
  
En la vista de edición de usuario, si se añaden los siguientes perfiles:
+
In the user edit view, the following profiles are added:
  
 
<center>
 
<center>
Line 212: Line 312:
 
</center>
 
</center>
  
El usuario tendrá acceso a los grupos "Applications", "Development_Apps", "Management_Apps" y "Databases".
+
The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps" and "Databases".
  
En cambio, si se añade un hijo de "Databases":
+
However, if a child of "Databases" is added:
  
 
<center>
 
<center>
Line 220: Line 320:
 
</center>
 
</center>
  
Ahora el usuario podrá acceder a los grupos "Applications", "Development_Apps", "Management_Apps", "Databases" y "Databases_Asia", pero no a "Databases_America".
+
The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps", "Databases" and "Databases_Asia", but not to "Databases_America".
  
==Group "All" ==
+
==== Secondary groups ====
  
Pandora has a system of groups, which are entities in which agents are classified and used to break down privileges. In this way, users are given certain permissions framed in one or more groups and thus have the ability to see and interact with agents and other objects in their context.
+
From update package 721 agents may have secondary groups. Unlike the primary group, these secondary groups are optional.
  
To make it easier to assign and filter groups, a tool called group "All" is available. The group All means, depending on the context, ALL groups or ANY of them.  From version 3.1 its reserved identifier is ID 0, with the difference that it is totally controlled by code, without there being a group with that ID in the database.
+
<center>
 +
[[File:Secondary agent.png|center]]
 +
</center>
  
== ACL Enterprise System==
+
An agent belonging to a secondary group means that it actually belongs to several groups at the same time. With this feature, two users with different permissions may have access to the same agent by just adding the appropriate secondary groups.
  
 +
For example, if an agent called "Portal" has "Infrastructures" as main group and "Hosting" as secondary group, any user that has access to "Infrastructures" and/or a "Hosting" may access it.
 +
 +
Some views, such as ''Tree View'', may show repeated agents. That is the usual performance when using secondary groups.
 +
 +
=== ACL Enterprise System ===
 +
====Introduction====
 
The ACL Open Source model is based on "unix style" role/action/group/user (4 items).  
 
The ACL Open Source model is based on "unix style" role/action/group/user (4 items).  
  
The ACL Enterprise system allows you to define -according to profile- which pages (defined one by one or by "groups") users have access to. This will allow you to redefine which sections of the interface a user can see. For example, to allow a user to visualize only the "Group" view and the "Detailed" agent view, skipping pages such as "Alert view" or "Monitor view", already grouped in the classic Pandora FMS ACL system as "AR" (Agent Read Privileges).
+
The ACL Enterprise system allows you to define -according to profile- which pages (defined one by one or by "groups") users have access to. This will allow you to redefine which sections of the interface a user can see. For example, to allow a user to see only the "Group" view and the "Detailed" agent view, skipping pages such as "Alert view" or "Monitor view", already grouped in the classic Pandora FMS ACL system as "AR" (Agent Read Privileges).
 +
 
 +
This feature allows you to restrict the administration per page. It is very useful to allow some specific low-level operations.
 +
 
 +
{{Tip|Both models are "parallel" and compatible. The classic ACL system is complementary and it is evaluated prior to the ACL Enterprise system.}}
  
This feature allows you to restrict the administration per page. It is very useful to allow some specific low-level operations. Both models are "parallel" and compatible, and this is only an Enterprise feature. The classic ACL system is complementary and is evaluated prior to the ACL Enterprise system.
+
====Configuration====
  
In order to be able to use the new ACL system, the first step is to activate it in the Enterprise configuration tab. This option is only visible if you are using the Enterprise version.  
+
In order to be able to use the new ACL system, the first step is to activate it in the configuration tab. This option is only visible if you use the Enterprise version.  
  
 
<br><br><center>
 
<br><br><center>
Line 242: Line 354:
 
</center><br><br>
 
</center><br><br>
  
To configure the Enterprise ACL system, go to the specific option for ACL Enterprise in Administration -> Setup. On this screen you can add new items in the new ACL System and view the items defined by profile. You can also delete items from the Enterprise ACL system.  
+
To configure the Enterprise ACL system, go to the specific option for ACL Enterprise in ''Administration'' > ''Setup''. On this screen you may add new items in the new ACL System and see the items defined by profile. You can also delete items from the Enterprise ACL system.  
  
 
<br>
 
<br>
Line 252: Line 364:
 
<br>
 
<br>
  
The Enterprise ACL system, if enabled, restricts ALL pages to ALL groups (including the Administrator!) to all defined (allowed) pages in the Enterprise ACL system. If a user with the "Administrator" profile does not have pages included in the Enterprise ACL system, they will not be able to see anything.  
+
{{warning|If the Enterprise ACL system is enabled, it restricts ALL pages to ALL groups (including the Administrator!) to all defined (allowed) pages in the Enterprise ACL system. If a user with the "Administrator" profile does not have pages included in the Enterprise ACL system, they will not be able to see anything.}}
  
 
{{warning|Please, be careful with this, because you may lose access to the console if you enable improper ACL Enterprise configuration for your user.}}
 
{{warning|Please, be careful with this, because you may lose access to the console if you enable improper ACL Enterprise configuration for your user.}}
  
If we have mistakenly lost access to the console, you can disable the Enterprise ACL system from the command line:
+
If you have mistakenly lost access to the console, you may disable the Enterprise ACL system from the command line:
  
 
  /usr/share/pandora_server/util/pandora_manage.pl /etc/pandora_server.conf --disable_eacl
 
  /usr/share/pandora_server/util/pandora_manage.pl /etc/pandora_server.conf --disable_eacl
  
You can define "page by page", "complete sections", set a rule "any" or add "custom pages" that are not accessible from the menu.
+
You can define "page by page", "complete sections", set "any" rule or add "custom pages" that are not accessible from the menu.
  
There are two ways to add pages to a profile: With the'' wizard'' (default) or with the ''custom edit''.  Above the button to add a rule, there is a button to change this mode.
+
There are two ways to add pages to a profile: with the'' wizard'' (default) or with ''custom edit''.  Above the button to add a rule, there is a button to change this mode.
  
===Wizard===
+
=====Wizard=====
  
 
In the wizard we will choose the sections and pages of some combo controls.
 
In the wizard we will choose the sections and pages of some combo controls.
  
{{warning|The pages that appear in these combos are only those accessible from the menu. To give access to pages that can be accessed in another way (e. g. the agent's main view) we must use the custom editor}}
+
{{warning|The pages that appear in these combos are only those accessible from the menu. To give access to pages that can be accessed in another way (e. g. the agent main view) use the custom editor.}}
  
 
To include a Pandora FMS page in the "allowed pages", you must select the profile to which the rule will be applied, then select in "Section" control the section that contains the desired page. You can then select any of your pages in the "Page" control.
 
To include a Pandora FMS page in the "allowed pages", you must select the profile to which the rule will be applied, then select in "Section" control the section that contains the desired page. You can then select any of your pages in the "Page" control.
Line 282: Line 394:
 
Another option is to select a section and the value "All" in the "Page" control. This will allow the chosen profile to see "all" of the selected section. Also by selecting "All" in both controls, users of that profile will be allowed to view "all" of "all" sections, just as it would be without the Enterprise ACL System for that profile.
 
Another option is to select a section and the value "All" in the "Page" control. This will allow the chosen profile to see "all" of the selected section. Also by selecting "All" in both controls, users of that profile will be allowed to view "all" of "all" sections, just as it would be without the Enterprise ACL System for that profile.
  
{{warning|To display a section in the menu, the user must have access to at least the first page of the section. For example, for the "Monitoring" section to be displayed they must have access to at least "Tactical View".}}
+
{{warning|For a section in the menu to be displayed, the user must have access to at least the first page of the section. For example, for the "Monitoring" section to be displayed they must have access to at least "Tactical View".}}
  
===Personalized Editing===
+
=====Custom editing=====
  
To add individual pages that are not accessible from the menu we can manually enter your sec2. To do this, access the page we want to add and copy the parameter sec2.  
+
To add individual pages that are not accessible from the menu, you may manually enter your sec2. To that end, access the page you wish to add and copy the parameter sec2.  
  
For example, if we want to add the main view of the agents, we will enter the view of any agent and find a URL similar to this one:
+
For example, if you wish to add the main view of the agents, enter the view of any agent and find a URL similar to this one:
  
 
  http://localhost/pandora/index.php?sec=estado&sec2=operation/agentes/ver_agente&id_agente=7702
 
  http://localhost/pandora/index.php?sec=estado&sec2=operation/agentes/ver_agente&id_agente=7702
Line 302: Line 414:
 
<br>
 
<br>
  
===Security===
+
====Security====
  
Any page that is not "allowed" will not be displayed in the menu, and its use will not be allowed, even when the user enters the URL in "manual" mode. Any page that isn't allowed by the "Classic" ACL system of Pandora FMS will not be allowed by the Enterprise ACL system (this is valid for the classic ACL system). This would be a concrete example of several filters:
+
Any page that is not "allowed" will not be displayed in the menu, and its use will not be allowed, even when the user enters the URL in "manual" mode. Any page that isn't allowed by the "Classic" Pandora FMS ACL system will not be allowed by the Enterprise ACL system (this is valid for the classic ACL system). This would be a specific example of several filters:
  
 
<br>
 
<br>
Line 314: Line 426:
 
<br>
 
<br>
  
In addition, there is a control that checks if a page belongs to a section, which reinforces the security against manual modifications of the URL. This check will be skipped for pages added with the custom editor as well as when you have access to all pages in a section, thus optimizing the load.
+
In addition, there is a control that checks whether a page belongs to a section, which reinforces security against manual URL modifications. This check will be skipped for pages added with the custom editor, as well as the access to each pages belonging to a full section whose access is granted, thus optimizing the load.
 
 
== Workspace ==
 
 
 
This section allows you to interact with Pandora users, or edit the user's details, as well as some diverse operations, such as access to the incidences system (to open tickets), chat with other users connected to Pandora, etc.
 
 
 
=== Chat ===
 
 
 
It allows to interact in a chat with other users connected to that Pandora console. Useful for example, if we want to comment something to another operator.
 
 
 
=== Connected users ===
 
 
 
This extension shows other users connected to the Pandora FMS Console other than their own. This functionality is important because the Pandora FMS console allows connections of multiple users.
 
 
 
The extension is accessed from ''Workspace > Connected users''.
 
 
 
<center><br><br>
 
[[image:ex4b.png|800px]]
 
</center><br><br>
 
 
 
=== Messages ===
 
 
 
Pandora FMS has a tool that allows different users to send messages among themselves.
 
 
 
==== See messages ====
 
 
 
When a user has a message, an envelope icon appears at the top right of the console.
 
 
 
<center><br><br>
 
[[image:gest20.png|600px]]
 
</center><br><br>
 
 
 
Messages that have a user can be viewed in ''Workspace > Messages > Messages list'', and from there you can read, delete or write a message for a specific group or user.
 
  
 
== Servers ==
 
== Servers ==
  
The detailed view of the servers is used to know, besides the general state of the Pandora FMS servers, its load level and delay. Let's see a screenshot of a server status screen, that we remember, is reached through the operation menu -> Pandora Servers.
+
The detailed view of the servers is used to know, besides the general state of the Pandora FMS servers, their load level and delay. Let us see a screenshot of a server status screen that is reached through the operation menu > Pandora Servers.
  
 
<center>
 
<center>
Line 358: Line 438:
 
Some icons have special relevance, as seen in the above caption:
 
Some icons have special relevance, as seen in the above caption:
  
* Poll request: It requests the remote test server to run all the checks it has, forcing it to run them again. Valid for all network servers, e. g. Network server, WMI server, Plugin server, WEB server, etc.
+
* Poll request: It asks the remote test server to run all the checks it has, forcing it to run them again. Valid for all network servers, e. g. Network server, WMI server, Plugin server, WEB server, etc.
* Editing recon server tasks.
+
* Editing Discovery server tasks.
* Edit remote server configuration. Valid for Pandora servers or satellite servers .
+
* Edit remote server configuration. Valid for Pandora FMS servers or satellite servers .
  
In addition, in this view we can see several important data, each column shows the following information:
+
In addition, in this view you may see several important data, each column shows the following information:
  
*Server name, usually uses the hostname of the machine.
+
*Server name, usually the hostname of the machine.
*Status (green = active, grey = stopped or dropped).
+
*Status (green = active, grey = stopped or down).
 
*Server type: data server, network server, etc.
 
*Server type: data server, network server, etc.
*Progress bar indicating the load percentage of total modules for that type of server. In this case all servers are at 100% except recon server, which has no associated tasks so it is at 0%.
+
*Progress bar indicating the total module load percentage for that type of server. In this case, all servers are at 100% except for recon server, which has no associated tasks so it is at 0%.
 
*Number of such modules executed by the server with respect to the total number of such modules.
 
*Number of such modules executed by the server with respect to the total number of such modules.
*Server Lag: Higher time spent by the oldest module waiting to receive data / Nº of modules that are out of their lifetime. In this example there are approx. 3000 modules out of their lifespan, with a lag time of 10 minutes 13 seconds. This indicator is useful to know if we have many modules and to know if the server is at the limit of its load capacity, as it is this case, that without being an excessive delay (10 minutes 13 sec, for modules that on average have a life time of 5 min), the number of modules that are out of time is considerable. In the case of the network server this figure is much lower, being only 19 modules with lag (10 minutes) of a total of almost 1500 modules.
+
*Server Lag: Highest amount of time spent by the oldest module waiting to receive data / Nº of modules out of their lifetime. In this example, there are approx. 3000 modules out of their lifespan, with a lag time of 10 minutes 13 seconds. This indicator is useful to know if you have many modules and to know if the server is at load capacity limit, as it is this case. Although it does not have an excessive delay (10 minutes 13 sec, for modules that have a lifespan average of 5 min), the number of modules out of time is considerable. In the case of the network server, this figure is much lower, being only 19 modules with a lag (10 minutes) of a total of almost 1500 modules.
*Total number of threads configured on the server: Total number of modules in queue waiting to be attended. These parameters reflect excessive load status. There should almost never be queued modules; this reflects the server's inability to process the data.
+
*Total number of threads configured on the server: Total number of modules in queue waiting to be attended. These parameters reflect excessive load status. There should almost never be queued modules. This reflects the server's inability to process the data.
 
*Number of seconds since the server updated its data. Each server has a "Keepalive" that updates its status, to make sure it is active and updating its statistics.
 
*Number of seconds since the server updated its data. Each server has a "Keepalive" that updates its status, to make sure it is active and updating its statistics.
  
== Backup ==
+
==Credential store==
  
Extension that allows backing up the DB and restore it.
 
  
The extension is accessed from ''Admin tools > Extension manager > Backup''.
+
Pandora FMS features a credential store. This repository manages the IDs used in sections such as Discovery Cloud or agent automatic deployment.
  
To back up, type the Backup description and click on "Create".
+
<center>
 +
[[File:Cred_store.png]]
 +
</center>
  
<center><br><br>
+
Next, the "Credential store" tab is displayed.
[[image:ex12.png|800px]]
 
</center><br><br>
 
 
 
When the backup is done, it appears in the Backup list with the running icon.
 
  
 
<center>
 
<center>
[[image:ex13.png|800px]]
+
[[File:Cred_store1.png]]
 
</center>
 
</center>
  
Once the Backup has been created, it is possible to:
 
* Download it by clicking on this icon:
 
  
<center>
+
There are three different login information types to register:
[[image:ex14.png]]
+
 
</center>
+
# Amazon Web Services (AWS) login information
 +
# Microsoft Azure login information
 +
# Custom login information
 +
 
 +
 
 +
[[File:Cred_store2.png]]
 +
 
  
*Do a rollback by clicking on this icon:.
+
To add a new entry, press the "add" button and fill out the pop-up form.  
  
<center>
 
[[image:ex15.png]]
 
</center>
 
  
The rollback applies a previously created backup and restores it. This will destroy all existing data in the console and apply the data that exists in the backup on which the rollback is made.
+
The group assigned to the password controls its '''visibility'''. That means that if the password 'test' is assigned to the group named 'All', '''all''' Pandora FMS console users will be able to see said password.
  
* Delete it by clicking on this icon:
+
In a similar way, if 'test' is allocated to the group named 'Applications', only users with permissions on 'Applications' will have access to the password.
  
<center>
 
[[image:ex16.png]]
 
</center>
 
  
== Cron Job ==
+
[[File:Cred_store3.png]]
  
''(Only Enterprise version)''
 
  
This extension allows you to schedule the execution of tasks from Pandora's server.
 
  
The extension can be accessed from ''Servers > Cron jobs''.
+
Once added, it can be checked, filtered etc.
  
<center><br><br>
+
[[File:Cred_store5.png]]
[[File:Cron_jobs.jpg|800px]]
 
</center><br><br>
 
  
To add a task, the following fields must be filled in:
 
* '''Task''': combo where the task to perform can be chosen.
 
**Send personalized report via e-mail
 
** Run custom script
 
** Pandora FMS BD Backup Copy
 
** Save custom report to disk
 
* '''Schedule''':  Field where the frecuency of the task performance can be chosen.
 
** Without schedule: These tasks will be executed only once and at the specified time..
 
** Hourly
 
** Daily
 
** Weekly
 
** Monthly
 
** Yearly
 
* '''First run''': Field where the date and time of the first execution of the task is chosen; it will be executed periodically, taking this date and time as a reference.
 
* '''Parameters''': Field that allows entering parameters in the task to be performed.  It varies by task.
 
** ''Pandora FMS BD Backup Copy'': Description and path where the backup will be stored.
 
** ''Send report via e-mail'': report to be sent and recipient's e-mail address.
 
** ''Run script'': script command to run.
 
** ''Save report to disk'': report to be saved and its path to be stored.
 
  
Once the data has been filled in, click on create and the task appears in the list of scheduled tasks.
+
Within password customization, the only thing that cannot be modified is the type of login information:
  
<center><br><br>
 
[[File:Cron_jobs_list.jpg|800px]]
 
</center><br><br>
 
  
Once the scheduled task has been created, it is possible to force its execution by clicking on the green circle to the right of the task or delete it by clicking on the red cross on the left.
+
[[File:Cred_store6.png]]
  
 
== Scheduled downtimes ==
 
== Scheduled downtimes ==
 +
===Introduction===
 +
Pandora FMS has a small scheduled downtime management system. This system allows you to disable alerts at intervals when there is a downtime, disabling the agent. When an agent is disabled it does not collect information either, so that in a downtime, for most metrics or report types, the intervals where there is a downtime are not taken into account in the reports because there is no data in the agents during those intervals.
 +
 +
<center>
 +
<br><br>
 +
[[Image:Downtimegeneral.png|800px]]
 +
<br><br>
 +
</center>
  
Pandora FMS has a small management system of planned downtimes. This system allows you to deactivate the alerts at intervals when there is a downtime, deactivating the agent. When an agent is deactivated it doesn't collect information either, so that in a downtime, for most metrics or report types, the intervals where there is a downtime are not taken into account in the reports because there is no data in the agents during those intervals.
+
=== Create a scheduled downtime ===
  
 
To create a downtime, go to the ''Tools > Scheduled downtime'' menu and press the button to create one:
 
To create a downtime, go to the ''Tools > Scheduled downtime'' menu and press the button to create one:
Line 464: Line 521:
 
</center>
 
</center>
  
We find the following configurable parameters:
+
You will find the following configurable parameters:
  
 
* '''Name:''' Name of the scheduled downtime.
 
* '''Name:''' Name of the scheduled downtime.
* '''Group:''' The group to which we want it to belong to.
+
* '''Group:''' The group you want it to belong to.
 
* '''Description'''.
 
* '''Description'''.
* '''Type:''' we can set the following types of downtimes:
+
* '''Type:''' You may set the following types of downtimes:
** ''Quiet:'' Marks as "quiet" the modules we indicate, so they will not generate alerts, events, and will not store historical data.
+
** ''Quiet:'' Check as "quiet" the indicated modules, so they will not generate alerts nor events.
** ''Disable Agents:'' Disables the selected agents. It is important to know that if an agent is manually disabled before the task is triggered, it will become enabled once this task is completed.
+
** ''Disable Agents:'' It disables the selected agents. It is important to know that if an agent is manually disabled before the task is launched, it will become enabled once this task is completed.
** ''Disable Alerts:'' Disables alerts of selected agents.
+
** ''Disable Alerts:'' It disables alerts of selected agents.
* '''Execution:''' Allows us to configure whether we want it to run once or periodically.
+
* '''Execution:''' It allows to configure whether you want it to run once or periodically.
* '''Set time:''' Setting the day and time at which the planned stop will start and end either once or periodically, depending on what has been previously configured in "Execution".
+
* '''Set time:''' Setting the day and time at which the scheduled downtime will start and end either once or periodically, depending on what has been previously configured in "Execution".
  
  
{{tip|If the administrator of Pandora FMS enables it in the visual configuration section, it is possible to create planned stops in a last date. They will not be executed, but their existence will be reflected in different reports. This is particularly relevant since it affects, among others, availability reports and SLAs.}}
+
{{tip|If the Pandora FMS administrator enables it in the visual configuration section, it is possible to create scheduled downtimes in a past date. They will not be executed, but their existence will be reflected in different reports. This is particularly relevant since it affects, among others, availability reports and SLAs.}}
  
 
<center>
 
<center>
Line 484: Line 541:
 
</center>
 
</center>
  
Finally we specify which specific agents we want to include in that downtime.
+
Finally, specify which specific agents you want to include in that downtime.
  
 
<center>
 
<center>
Line 492: Line 549:
 
</center>
 
</center>
  
When a programmed downtime is "active" it cannot be modified or deleted, but from version 5.0 onwards there is an option where we can stop the execution in "Stop downtime", so that all the agents/modules/alarms that the scheduled downtime is temporarily disabling can be re-enabled. This option does not support periodic planned downtimes. From version 6.0 onwards, you can postpone planned non-periodic downtimes even if they are 'active'.
+
When a scheduled downtime is "active", it cannot be modified or deleted, but from version 5.0 onwards there is an option where you may stop the execution in "Stop downtime", so that all agents/modules/alarms that the scheduled downtime disabled temporarily may be re-enabled. This option does not support periodic scheduled downtimes. From version 6.0 onwards, non-periodic scheduled downtimes can be delayed even if they are 'active'. When this downtime is over, you may modify or delete it.
 
 
<center>
 
<br><br>
 
[[Image:Downtime10.png|800px]]
 
<br><br>
 
</center>
 
 
 
When this downtime is over, we can modify or delete it.
 
  
=== Alternatives to downtime management on the console ===
+
=== Alternatives to console downtime management ===
  
There are often certain "cyclical" situations that we have to take into account and the method of managing downtimes is too specific: for example, we want to be able to deactivate all agents quickly and on time or to plan a general downtime every week from a certain time to another. For this type of operations, there are ways to do it from the command line.
+
There are often certain "cyclical" situations to be taken into account and the method of downtime management is too specific: for example, you may want to be able to deactivate all agents quickly and on time or to plan a general downtime every week from time to time. For this type of operations, there are ways to do it from the command line.
  
There is a faster way to put all agents in service mode, through the use of the CLI,'' pandora_manage. pl'' of Pandora management through the command line:
+
There is a faster way to set all agents in service mode, through the use of Pandora FMS management CLI, ''pandora_manage. pl'' through the command line:
  
 
  ./pandora_manage.pl /etc/pandora/pandora_server.conf --enable_group 1
 
  ./pandora_manage.pl /etc/pandora/pandora_server.conf --enable_group 1
Line 518: Line 567:
 
  [INFO] Enabling group 1
 
  [INFO] Enabling group 1
  
This activates all agents; to disable them, it would be the same but slightly different:
+
Disabling them would be the following way:
  
 
  ./pandora_manage.pl /etc/pandora/pandora_server.conf --disable_group 1
 
  ./pandora_manage.pl /etc/pandora/pandora_server.conf --disable_group 1
Line 524: Line 573:
 
== Audit Log ==
 
== Audit Log ==
  
Pandora FMS keeps a log of all the changes and important actions that occur in the Pandora FMS console. This log can be viewed in the ''Admin tools > System Audit Log''.
+
Pandora FMS keeps a log of all changes and important actions taken in Pandora FMS console. This log can be seen in ''Admin tools'' > ''System Audit Log''.
  
 
<center><br><br>
 
<center><br><br>
Line 530: Line 579:
 
</center><br><br>
 
</center><br><br>
  
On this screen, you can see a series of entries related to console activity, user information, action type, date and a brief description of the recorded events.
+
On this screen, you may see a series of entries related to console activity, user information, action type, date and a brief description of the events recorded.
  
 
<center>
 
<center>
Line 536: Line 585:
 
</center>
 
</center>
  
In the upper left corner, you can filter which entry is going to be displayed by different criteria including: actions, user and IP, you can even perform a text search and determine the maximum hours.
+
In the upper left corner, you may filter which entry will be displayed by different criteria including: actions, user and IP, you may even perform a text search and determine the maximum amount of hours.
  
 
The available filtering fields:
 
The available filtering fields:
  
* '''Action''': las diferentes acciones posibles entre las que filtrar -> ACL Violation, Agent management, Agent remote configuration, Alert management, Command management, Dashboard management, Event alert management, Event deleted, Extension DB inface, File collection, Logoff, Logon, Logon Failed, Massive management, Module management, No session, Policy management, Report management, Setup, System, Template alert management, User management, Visual console builder.
+
* '''Action''': The different possible filtering actions > ACL Violation, Agent management, Agent remote configuration, Alert management, Command management, Dashboard management, Event alert management, Event deleted, Extension DB inface, File collection, Logoff, Logon, Logon Failed, Massive management, Module management, No session, Policy management, Report management, Setup, System, Template alert management, User management, Visual console builder.
 
* '''User'''.
 
* '''User'''.
* '''Free text for search''': it will search in the fields ''User'', ''Action'' and ''Comments''.
+
* '''Free text for search''': It will search in the fields ''User'', ''Action'' and ''Comments''.
* '''Max. Hours old''': number of backward hours in which to display events.
+
* '''Max. Hours old''': Number of backward hours where to display events.
* '''IP''':  IP address of origin.
+
* '''IP''':  Source IP address.
  
 
It is also possible to export the information displayed on the screen to a CSV file by clicking on the button at the top right of the screen.
 
It is also possible to export the information displayed on the screen to a CSV file by clicking on the button at the top right of the screen.
Line 551: Line 600:
 
[[image:audit_02.png]]
 
[[image:audit_02.png]]
 
<br>
 
<br>
Available actions to filter
+
Available filtering actions
 
<br>
 
<br>
 
</center>
 
</center>
 
<br>
 
<br>
  
With this tool, you can search, for example, for the task that a user performs on managing agents in the last hour.
+
With this tool, you may search, for example, for the task that a user performs on agent management in the last hour.
  
 
<center>
 
<center>
Line 562: Line 611:
 
</center>
 
</center>
  
Or the moment when a given user has logged on to the console. You can retrieve all information about actions performed by the entire user.
+
Or the moment when a given user has logged in the console. You may retrieve all information about the actions performed by the entire user.
In addition, you can see the Pandora server service start date or when the console configuration was changed.
+
In addition, you may see the Pandora FMS server service start date or when the console configuration was changed.
  
 
<center>
 
<center>
Line 571: Line 620:
 
== Local server logs ==
 
== Local server logs ==
  
In the latest versions of the Pandora FMS console, you can check the status of the logs through the menu <i>Extensions > Extension management > System logs</i>.
+
In latest Pandora FMS console versions, log status can be checked through the menu <i>Extensions > Extension management > System logs</i>.
  
  
Line 578: Line 627:
 
</center>
 
</center>
  
From this extension you can view the logs of both the console and the local server:
+
From this extension you may see the logs of both the console and the local server:
  
 
<center>
 
<center>
Line 585: Line 634:
  
  
If you are unable to view the content, please check the permissions of your log files:
+
If you cannot see the content, check your log file permissions:
  
 
  chown -R pandora:apache /var/log/pandora/
 
  chown -R pandora:apache /var/log/pandora/
  
  
You can adjust the logrotate options to maintain this setting by modifying the file /etc/logrotate.d/pandora_server
+
You may change the rotator options to keep these settings by modifying the /etc/logrotate.d/pandora_server file.
  
 
<pre>
 
<pre>
/var/log/pandora/pandora_server.log  
+
/var/log/pandora/pandora_server.log
 +
/var/log/pandora/websocket.log  
 
/var/log/pandora/pandora_server.error {
 
/var/log/pandora/pandora_server.error {
 
weekly
 
weekly
Line 617: Line 667:
 
</pre>
 
</pre>
  
 +
On the other hand, there is also a specific configuration for the console log rotation in <b>/etc/logrotate.d/pandora_console</b>:
  
Note: If your system is SuSE, replace apache with www-data; in case of using a different system, check the users corresponding to the Apache service.  
+
<pre>
 +
/var/www/html/pandora_console/log/audit.log
 +
/var/www/html/pandora_console/log/console.log {
 +
        weekly
 +
        missingok
 +
        size 100000
 +
        rotate 3
 +
        maxage 15
 +
        compress
 +
        notifempty
 +
        create 644 apache root
 +
}
 +
</pre>
 +
 
 +
 
 +
<b>Note</b>: If your system is SuSE, replace apache with www-data. In case of using a different system, check the users corresponding to the Apache service.  
 
(httpd)
 
(httpd)
 
<br>
 
<br>
 +
 +
{{Warning|If updating from <b>OUM</b> a version prior to <b>747</b> you will need to manually modify the <b>logrotate</b> file.}}
 +
 +
== Cron Job ==
 +
 +
This Pandora FMS Enterprise extension allows to schedule task execution from Pandora FMS server.
 +
 +
The extension can be accessed from ''Servers'' > ''Cron jobs''.
 +
 +
<center><br><br>
 +
[[File:Cron_jobs.jpg|800px]]
 +
</center><br><br>
 +
 +
To add a task, the following fields must be filled in:
 +
* '''Task''': Combo where the task to perform can be chosen.
 +
**Send custom report via e-mail
 +
** Run custom script
 +
** Pandora FMS BD Backup
 +
** Save custom report in disk
 +
* '''Schedule''':  Field where task frequency can be chosen.
 +
** Without schedule: These tasks will be executed only once and at the specified time..
 +
** Hourly
 +
** Daily
 +
** Weekly
 +
** Monthly
 +
** Yearly
 +
* '''First run''': Field where the date and time of the first task execution is chosen. It will be executed periodically, taking this date and time as a reference.
 +
* '''Parameters''': Field that allows entering parameters in the task to be performed. It varies by task.
 +
** ''Pandora FMS BD Backup'': Description and path where the backup will be stored.
 +
** ''Send report via e-mail'': Report to be sent and recipient's e-mail address.
 +
** ''Run script'': Script command to run.
 +
** ''Save report to disk'': Report to be saved and the path to store it.
 +
 +
Once the data has been filled in, click on create and the task will appear in the scheduled tasks list.
 +
 +
<center><br><br>
 +
[[File:Cron_jobs_list.jpg|800px]]
 +
</center><br><br>
 +
 +
Once the scheduled task has been created, it is possible to force its execution by clicking on the green circle to the right of the task or delete it by clicking on the red cross on the left.
 +
 +
 +
{{tip|If the cron job is "non scheduled", it will be deleted automatically when executed.}}
 +
  
 
== DB management from the console ==
 
== DB management from the console ==
  
the core of Pandora FMS system is its database. It stores all data collected by monitored systems, agent configuration, alarms, events, audit data, different users and their data. That is, all system data.
+
The core of Pandora FMS system is its database. It stores all data collected by monitored systems, agent configuration, alerts, events, audit data, different users and their data. That is, all system data.
  
The efficiency and reliability of this module is vital for the correct functioning of Pandora FMS, the maintenance of Pandora FMS database in good condition is critical for Pandora FMS to work correctly.  
+
Efficiency and reliability are vital for Pandora FMS to work properly, so database maintenance is essential.  
  
To perform regular database maintenance, administrators can use standard MySQL commands from the command line or manage the database from the console without extensive knowledge of Mysql.
+
To perform regular database maintenance, administrators can use standard MySQL commands from the command line or manage the database from the console although they may not have extensive Mysql knowledge.
  
The database diagnostic report is obtained from "Admin tools -> Diagnostic info"
+
Pandora FMS has multiple extensions that can be used from the console to see information from the database.
  
The management of the Database by means of sql statements is carried out from "Admin tools -> Admin Tools -> DB Interface"
+
=== Diagnostic tool ===
  
The database schema check management is performed from "Admin tools -> Admin Tools -> DB Schema Check"
+
This section shows general information about Pandora FMS installation. It is necessary to emphasize the high amount of information that is obtained from the database, where the recommended parameters can be seen, as well as warnings about existing values that need to be changed.
  
 
<center><br><br>
 
<center><br><br>
 
[[File:Captura de pantalla de 2017-10-09 13-37-10.png]]
 
[[File:Captura de pantalla de 2017-10-09 13-37-10.png]]
 
</center><br><br>
 
</center><br><br>
 +
 +
<center>
 +
[[File:Diagnostic_info1.png]]
 +
</center>
 +
<center>
 +
[[File:Diagnostic_info2.png]]
 +
</center>
 +
<center>
 +
[[File:Diagnostic_info3_new.png]]
 +
</center>
 +
<center>
 +
[[File:Diagnostic_info4.png]]
 +
</center>
  
 
=== DB Interface ===
 
=== DB Interface ===
  
This is an extension that allows you to execute commands in the database and see the result. It is an advanced tool that should only be used by people who know SQL and the Pandora FMS database schema in enough detail.  
+
This is an extension that allows you to execute commands in the database and see the result. It is an advanced tool that should only be used by people who have a certain amount of knowledge about SQL and the Pandora FMS database schema.  
  
 
{{warning|If misused, this  tool may "destroy" data or permanently render the application inoperative.}}
 
{{warning|If misused, this  tool may "destroy" data or permanently render the application inoperative.}}
Line 656: Line 779:
 
=== DB Schema Check ===
 
=== DB Schema Check ===
  
This is an extension that allows you to check the structural differences between the database established in your Pandora FMS and a pattern scheme to compare possible errors.  
+
This is an extension that allows to check the structural differences between the database set in your Pandora FMS and a pattern scheme to compare possible errors.
 +
 
 +
It works like this:
 +
* A temporary database is created with the structure that the installation database should have (different depending on the installed version).
 +
* The database created is compared with the database referenced in the installation.
 +
* The temporary database is deleted.
  
You access the extension from'' Admin tools > Admin Tools -> DB Schema Check''.
 
  
 
<center><br><br>
 
<center><br><br>
Line 665: Line 792:
  
 
Enter the data to access your database and click on "Run test".
 
Enter the data to access your database and click on "Run test".
 +
 +
{{Tip|It is recommended to use this extension to check whether a database migration has been correctly performed.}}
 +
 +
{{Warning|This check can only be done in MySQL Databases.}}
 +
 +
== Network Tools ==
 +
 +
*<b>Traceroute path</b>: If empty, Pandora FMS will search the traceroute system.
 +
*<b>Ping path</b>: If empty, Pandora FMS will search the ping system.
 +
*<b>Nmap path</b>: If empty, Pandora FMS will search the nmap system. 
 +
*<b>Dig path</b>: If empty, Pandora FMS will search the dig system. 
 +
*<b>Snmpget path</b>: If empty, Pandora FMS will search the snmpget system.
 +
 +
== Backup ==
 +
 +
Extension that allows backing up the DB and restoring it.
 +
 +
To make a backup, first select the destination folder where the data will be stored. Once chosen, write a backup description.
 +
 +
<center><br><br>
 +
[[image:ex12.png|800px]]
 +
</center><br><br>
 +
 +
When the backup is done, it will appear in the Backup list with the running icon.
 +
 +
<center>
 +
[[image:ex13.png|800px]]
 +
</center>
 +
 +
Once the Backup has been created, it is possible to:
 +
* Download it by clicking on this icon:
 +
 +
<center>
 +
[[image:ex14.png]]
 +
</center>
 +
 +
*Do a rollback by clicking on this icon:.
 +
 +
<center>
 +
[[image:ex15.png]]
 +
</center>
 +
 +
The rollback applies a previously created backup and restores it. This will destroy all existing data in the console and apply the data that exists in the backup on which the rollback is made.
 +
 +
{{Warning|By means of this tool it is possible to recover the database backup made through this feature. It is not possible to load a manual backup.}}
 +
 +
* Delete it by clicking on this icon:
 +
 +
<center>
 +
[[image:ex16.png]]
 +
</center>
 +
 +
 +
 +
 +
  
 
== Plugin log ==
 
== Plugin log ==
Line 670: Line 853:
 
Extension that allows you to easily register server plugins.
 
Extension that allows you to easily register server plugins.
  
The extension can be accessed through ''Servers > Register plug-in''.
+
The extension can be accessed through ''Servers'' > ''Register plug-in''.
  
 
<center><br><br>
 
<center><br><br>
Line 676: Line 859:
 
</center><br><br>
 
</center><br><br>
  
To register a plugin choose the file by clicking on Browse and click on "Upload".
+
To register a plugin choose the file by clicking on "Browse" and "Upload".
  
 
More information about server plugins can be found in the development and extension chapter.
 
More information about server plugins can be found in the development and extension chapter.
  
You can see it in the section [[https://wiki.pandorafms.com/index.php?title=Pandora:Documentation_en:Anexo_Agent_Plugins|Server Plugin Development]] the format of the .pspz files.
+
You may see in section [[https://wiki.pandorafms.com/index.php?title=Pandora:Documentation_en:Anexo_Agent_Plugins|Server Plugin Development]] the format of the .pspz files.
  
 
== Insert data ==
 
== Insert data ==
Line 690: Line 873:
 
</center><br><br>
 
</center><br><br>
  
The format of the CSV file must be date; value per line. The date must be given in Y/m/d H: i: s format:
+
The format of the CSV file must be date;value per line. The date must be given in Y/m/d H:i:s format:
  
 
  2011/08/06 12:20:00;77.0
 
  2011/08/06 12:20:00;77.0
 
  2011/08/06 12:20:50;68.8
 
  2011/08/06 12:20:50;68.8
  
== Importing agents from CSV ==
 
 
''(Enteprise feature)''
 
 
Extension that allows to import a file separated by some separator in the Pandora server.
 
 
It's accessible from ''Admin tools > Extensions manager > CSV import''.
 
 
<center><br><br>
 
[[image:ex17.png|800px]]
 
</center><br><br>
 
 
Choose the file to import by clicking on "Select file". Choose the server where the export will take place and from a combo you choose the separator. Once you have completed the above fields, click on "Go".
 
 
The CSV file must contain the following fields in the following order: Agent Name, IP Address, Operating System ID, Interval and Group ID to which the agent must belong.
 
  
 
== Resource registration ==
 
== Resource registration ==
This extension allows you to import .prt files containing the definition of network component, smnp component, local component or wmi component. You can also add all of them (except the local component) to a template.
+
This extension allows you to import .prt files containing the definition of network component, smnp component, local component or wmi component. You may also add all of them (except for the local component) to a template.
  
 
<center><br><br>
 
<center><br><br>
Line 777: Line 945:
 
==Text string translator==
 
==Text string translator==
  
This extension belongs to the section ''Setup > Translate string'' and allows translating text strings of the Pandora FMS interface to customize it.
+
This extension belongs to the menu ''Setup > Translate string'' and allows translating Pandora FMS interface text strings to customize it.
  
 
<center><br><br>
 
<center><br><br>
Line 785: Line 953:
 
The fields to be filled in are detailed below:
 
The fields to be filled in are detailed below:
  
* '''Language''': allows to filter the strings by language.
+
* '''Language''': It allows to filter strings by language.
* '''Free text for search (*)''': Content of the string you want to customize.
+
* '''Free text for search (*)''': Content of the string you wish to customize.
 +
 
 +
Three columns will appear: the first one will show the original string, the second one the current translation and in the third one the custom translation you wish to add.
 +
 
 +
== Workspace ==
 +
 
 +
This section allows interacting with Pandora FMS users, or edit the user's details, as well as several actions, such as access to the issue system (to open tickets), chatting with other users connected to Pandora FMS, etc.
 +
 
 +
=== Chat ===
 +
 
 +
It allows to interact with other users connected to that Pandora FMS console through a chat. It is useful in case you want to say something to another operator for example.
 +
 
 +
===Issues===
 +
 
 +
Pandora FMS allows managing issues from the console thanks to its integration with Integria IMS.
 +
 
 +
For more information about this tool, check issue management with Integria IMS.
 +
 
 +
=== Messages ===
 +
 
 +
Pandora FMS has a tool that allows different users to send messages among themselves.
 +
 
 +
==== See messages ====
 +
 
 +
When a user has a message, an envelope icon appears at the top right of the console.
 +
 
 +
<center><br><br>
 +
[[image:gest20.png|600px]]
 +
</center><br><br>
 +
 
 +
User messages can be seen in ''Workspace > Messages > Messages list'', and from there you may read, delete or write a message to a specific group or user.
 +
 
 +
=== Connected users ===
 +
 
 +
This extension shows other users connected to the Pandora FMS Console other than their own. This feature is important because Pandora FMS console allows multiple user connections.
 +
 
 +
The extension is accessed from ''Workspace > Connected users''.
 +
 
 +
<center><br><br>
 +
[[image:ex4b.png|800px]]
 +
</center><br><br>
 +
 
 +
==Software agent repository==
 +
 
 +
Software agent repository is part of the deployment center, which controls agent installer available versions (programs) to be deployed.
 +
 
 +
You may access it through this menu:
 +
 
 +
<center>
 +
[[File:Agent_repo1.png]]
 +
</center>
 +
 
 +
 
 +
To add a new installer to the repository, click "Add agent".
 +
 
 +
[[File:Agent_repo2.png]]
 +
 
 +
 
 +
Fill out the information related to the target OS type, the architecture, the installing file, etc.
 +
 
 +
<center>
 +
[[File:Agent_repo3.png]]
 +
</center>
 +
 
 +
 
 +
'''Note:''' Installers for Linux (and all Unix and BSD range) are shared by all architectures. Both x64, x86, ARM, etc share the same installer.
 +
 
 +
 
 +
 
 +
Make sure the upload was successful:
 +
 
 +
<center>
 +
[[File:Agent_repo4.png]]
 +
</center>
 +
 
 +
 
 +
The uploaded agent installer will appear on the list together with the information about its version, by whom and when it was uploaded etc.:
 +
 
 +
<center>
 +
[[File:Agent_repo5.png]]
 +
</center>
 +
 
 +
== Custom themes ==
  
Three columns will appear: in the first one it will show the original string, in the second, one the current translation and in the third one the custom translation that you want to add.
+
Pandora FMS offers the possibility of uploading CSS files, in order to set custom themes in the visual console.
 +
 
 +
To that end, include the following comment in the CSS file:
 +
 
 +
/*
 +
Name: My custom Theme
 +
*/
 +
 
 +
Then, import the CSS file to the following path:
 +
 
 +
pandorafms/pandora_console/include/styles/CustomTheme.css
 +
 
 +
Once the desired themes are uploaded, go to ''Setup > Setup > Visual styles'' and select the appropriate theme from the ''Style template'' drop-down.
 +
 
 +
<center>
 +
[[File:CustomTheme1.png]]
 +
</center><br>
  
  

Latest revision as of 14:38, 4 September 2020

Go back to Pandora FMS documentation index

Template wip.png

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

 


1 Pandora FMS Management

1.1 Introduction

This chapter deals with several aspects of Pandora FMS daily management such as: group administration, user creation, backups, workspace, etc.

1.2 Profiles, users, groups and ACL

Pandora FMS is a Web management tool. Thanks to its 100% multitenant permission system, multiple users can work with different permissions accessing Pandora FMS setup without seeing each other's information.

To add users, it is important to have groups and profiles properly defined, and know exactly which data you want each user to see and/or modify.

Standard-user-profile.jpg


1.2.1 Users in Pandora FMS

Users are managed from Profiles > Users management, where you may see the list of defined users.



User list new.png



User definition consists of the following fields:



Detalle usuario 2018.png



Here are the relevant user fields:

  • User ID: Identifier that the user will use to authenticate himself in the application. This identifier is a value that should not have rare characters or spaces.
  • Full Display Name: Field where you put the full name, this if it is a descriptive field and can contain spaces and non-standard characters.
  • Password: Password that the user will have to access.
  • Global Profile: An Administrator user will not be governed by the internal ACL system and will have access to everything. The standard user will be ruled by the Pandora FMS ACL permissions assigned to him.
  • E-mail and phone: Optional fields where we can add extra user information.
  • Login Error: If this field is marked, the user will only be able to access to the API but not in an interactive way through the console.
  • Session time: Time in which the user can be connected without activity before the user considers his session expired and forces him to authenticate again.
  • Language: By default is the system language. You can also assign a specific language in which the user will see the Pandora FMS console.
  • Timezone: Field to put the console time zone to visualize different elements (Agents General View, Modules View, ...).
  • Block size for pagination: Default size of pagination for this user.
  • Skin: Field where you can choose a custom skin.
  • Home screen: Change the default screen the user enters after logging in the console, for example, the event viewer, or a visual console defined by the administrator.
  • Default event filter: Allows to define the default filter that the user will have when entering the event view. Later you can change it, but this will be the one applied "by default".
  • Disabled newsletter: Activate or deactivate the Pandora FMS newsletters.
  • Comments: Additional information to the fields defined above.
  • Profiles/Groups assigned to this user: Selection of profiles and/or groups in which the user will be organized or have access to.

1.2.1.1 User Edition by the User itself

All users can modify certain parameters of their own settings in Workspace > Edit my User.

The user creation form will appear, where you can configure some sections, except for group permissions.



Gestusuario.png



1.2.1.1.1 Notification setup

To customize logged-in user’s notifications, the administrator must have previously granted him notification edition permissions. In case of having said permissions, as well as all options activated, notifications and their forwarding by email can be enabled/disabled.

Notificaciones1.PNG


Notifications allow to see warning messages related to the following sections on screen:

  • System status. Where the following notifications are generated:
    • Expired or nearly expired license warning (~15 days or less).
    • Too many files attached warning.
    • Piled-up .data files in data_in warning (> 1000 files and increasing).
    • Piled-up BADXML files in data_in warning (> 150 files).
    • Overall module queuing (increasing) by server warning.
    • PHP setup warning.
    • Review whether pandora_db is running on the main database.
    • Review whether pandora_db is running on the history database.
    • History database update status (MR correct).
    • Status warnings, component down or uninitiated => Any of the Pandora FMS servers with status=1 and keepalive - now() may be higher than server_keepalive * 2.
    • Tentacle service down.
    • No master-mode server warning.
    • In the case of activated logs, Elastic/Logstash connectivity status.
    • In case of using Pandora FMS HA, error in DB replication.
    • Connection error with GIS map servers GIS (WMS).
    • Log size.
    • Mounting point/disk/almost full volume warning (data_in/mysql/tmp...)(> 90%).
    • History database connection failure.
    • Metaconsole synchronization failure.
    • Next scheduled shutdowns (in less than 15 days).
    • Metaconsole: Synchronization status:
      • Node synchronization failures.
      • Event replication failures.
      • Agent cache.
  • Message:
    • Messages received by the user yet to be read.
  • Pending task:
    • Policies yet to be applied.
    • Queued policies running/complete, and acknowledged once completed.
    • Pending re-creation policies.
    • Defined server plugins whose executable does not exist.
    • Metaconsole:
      • Pending synchronization tasks.
      • Completed synchronization tasks.
      • Pending notifications by node.
      • Policy queue status.
  • Advertisement.
    • Enterprise version not installed reminder.
    • Do you know our Enterprise version?
    • Do you know the module library?
    • Discover eHorus.
    • Discover Integria IMS.
  • Official communication:
    • Update notifications.
    • Messages generated from Ártica ST headquarters (update to PHP7, phantomjs, etc.)
  • Suggestion:
    • Did you know Pandora FMS can be integrated with Telegram?
    • Did you know alerts can be scaled?
    • Monitor your complete applications using services.

The options found in notification setup are these:

  • Notified users: Users that will receive the activated notifications.
  • Notified groups: Groups that will receive the activated notifications.
  • Notify all users: Option that will allow to notify all users.
  • Also email users with notification content: To enable sending emails for each notification.
  • Users can modify notification preferences: To allow users to modify notification preferences (the system administrator can restrict this option).
  • Users can postpone notifications up to: It allows to postpone notifications so that they are not received more than once in a certain interval (which can be chosen in the drop-down).

1.2.2 Groups in Pandora FMS

1.2.2.1 Introduction

The concept of group in Pandora FMS is fundamental. The groups are sets of elements with their own rules whose purpose is to help to control user access to certain elements inside Pandora FMS.

It is important to know that an agent can only belong to one group, but that a user can have access to one or several of these groups.

When configuring the groups, it will be necessary to take into account that the group All is a special group that cannot be eliminated, and all the groups are its subgroups. Any element that is associated to the All group can be seen/administered by a user that has permissions in any group.

1.2.2.2 Group all

Pandora FMS has a group system, which are entities into which agents are classified and which are used to grant permissions. That way users are granted some permissions assigned to one or several groups, and thus they will be able to interact with agentes and other elements in their context.

To make group assigning and filtering easier, there is a tool called group "All". Group "All", depending on the context, means ALL groups or ANY of them. From version 3.1 is exclusive identifier is ID 0. But it is totally controlled by the code, ther is no group with that ID in the DB.

1.2.2.3 Group creation

Groups are defined in the section Profiles > Manage agent groups.



Gest5.png



Inside group creation / modification, there is the following form:



Gestion grupo.png



These are the relevant user fields:

  • Name: Group name. This group can be used in the automatic agent provisioning, so it is not recommended that it contains spaces or rare characters (although it is supported).
  • Icon: Combo where the icon for the group can be chosen.
  • Parent: Combo where another group can be defined as the parent of the group being created.
  • Password: Optional. It allows restricting automatic agent creation (automatic software or satellite agent provision) so that only agents with the same password as the one defined in this field can be created.
  • Alerts: If checked, the agents belonging to the group will be able to send alerts. If not checked, alerts will not be sent. You can use this property to quickly disable alert generation for a certain group of agents.
  • Propagate ACL: If enabled, the child groups will have the same ACL permissions as the group.
  • Custom ID: Groups have an ID in the database. In this field it is possible to set another custom ID that can be used from an external program to perform an integration (e.g. CMDBs).
  • Contact: Contact information accessible through _groupcontact_ macro.
  • Skin: A skin can be assigned to the group.

1.2.2.4 Importing groups from CSV


This feature is in Metaconsole.


This is an Enterprise feature. The extension allows to import a file separated by some separating character in Pandora FMS server.

Access the extension from Admin tools > Extensions manager > CSV import group.

Ex17.png


The file to be imported is chosen by clicking on “Select file” and the combo is chosen from a combo. Once the previous fields are filled out, click “Go”.

The CSV file must contain the following fields in the following order: Group name, icon, parent id and propagation (1 or 0).

1.2.3 Profiles in Pandora FMS

Pandora FMS profiles allow to define which permissions a user is granted. The combination of profiles and a group associated to a user allows to define which permissions a user has on a group of agents, so that he can have different profiles in different groups. Profiles are managed from Profiles > Profile management.



Gest1.png



1.2.3.1 List of profiles

This list defines what each profile enables:

BIT ACCESSOPERATION
IR- See incidents
IW- Validate traps
- Messages
IM- Manage incidents
- View agent data (all views)
- Tactical view
- Group view
- See users
- See SNMP console
- Tree view
- Extension Module Group
- Search bar
AW- Agent management view
- Edit agent and its .conf
- Massive operations
- Create agent
- Duplicate remote configuration
- Policy management
AD- Management of service stops
- Deactivate agent/module/alert
LW- Alert assignment already created
- Alert management
LM- Define, modify templates, commands and actions
UM- User management
DM- Database Maintenance
ER- See event
EW- Validate/Comment event
- Manage filters
- Execute responses
EM- Delete event
- Change owner/Re-open event
RR- View report, graph, etc
- Apply a report template
RW- Create a visual console
- Create report
- Create combined Graph
RM- Create a report template
MR- Network map view
MW- Editing network maps
- Deleting own network maps
MM- Deletion of any network map
VR- Visual console view
VW- Visual console edition
- Deletion of own visual consoles
- Deletion of any visual console
VM- Visual console management
PM- Manage responses
- Customize event columns
- Update manager (Operation and Administration)
- Manage groups
- Create inventory modules
- Manage modules (including all sub-options)
- Manage SNMP console
- Manage profiles
- Manage servers
- System audit (edit and view)
- Setup (all lower tabs incl)
- Administration extensions
PERMITS COMBINATION
EW & IW- Create incidence through the event (Response)
LM & AR / AW & LW- Validate alerts

1.2.4 Permission granting

From user editing, you may grant a user access to a group with a certain profile:

Acl groups.png

If you do not assign any group or profile to the user, when the user tries to log in, there will be a login error like the one below:

Fallo login.png

1.2.4.1 Assignment of profiles and groups with user management permission (UM).

From Pandora FMS version 748 on, an improvement in the management of users, permissions and groups is enabled.

Several possible scenarios have been taken into account, which we will now explain:

  • A "manager" user with UM permissions that belongs to the group ALL will be able to manage any user regardless of the group he belongs to.
  • Accesses to groups can be added before creating a user as such.
  • A "manager" user can edit profiles and groups only on the users he can see because they belong to the groups he manages with UM permissions.
  • An administrator user can create other administrator users and can manage any other user, but in no case a "manager" user with UM permissions can remove UM permissions to another user who has the same permissions on the same group. This can only be modified by an administrator.
  • A "manager" user without UM permissions on a group, can not see which users belong to that group.
  • A "manager" user can eliminate the relation of users with the groups that it manages and even the complete user if only this one has relation with the groups that it manages.

Template warning.png

In case the last profile/group relationship of an user is going to be deleted and the user is going to be deleted Pandora shows a warning.

 


  • A "manager" user that has UM permissions in a group and not in another one, can only see the profile/group information of the groups that he manages, even if the user he observes has more permissions of other groups. The rest of the user's information will be unrelated to the "manager" user. In this way the "manager" user will only be able to obtain information or modify the permissions on the groups that he manages, but at no time will he be able to remove more permissions or eliminate the user.

1.2.4.2 Permission system extended by tags

In the Enterprise version, individual access to the modules of an agent can be configured by a Tag system. Some tags are configured in the system, they are assigned to the modules you wish, and additionally, access may be restricted to a user only to the modules that have those tags defined.


Info.png

Access by Tags does not replace access by groups, it only complements it.

 


Tags are defined in Profiles > Module Tags.



Gesttags5.png



In module configuration, one or more tags can (optionally) can assigned:

Tags 1.png

You may assign specific access to a tag through the user editor, in profile and group assigning, by adding a tag:

Acl tags.png

In this example, the user has access by means of the operator profile to the "eHorus" and "hosting" group and also to the "Infrastructure" group, but only to modules labeled with the "Security" tag.

Template warning.png

This system, which is called Tag-based security mode allows restricting access to all agent content, but it has performance impact, so it is designed exclusively to give access to small portions of information, that is, it should not be used with more than two or three tags per user/profile/group combination.

 


Info.png

In some global views (tactical view, group view, general tree counts) the totals show all the modules, not just the ones "visible" by the tag.

 


1.2.4.3 Hierarchy

In previous sections, we explained that the permissions of a group can be extended to the children by means of the configuration option Propagate ACL. However, from user configuration, you may limit this feature and prevent the ACL from propagating by checking No hierarchy.

As a reference for the examples, here we propose a configuration with the two parent groups "Applications" and "Databases" with two children each, "Development_Apps" and "Management_Apps" for the first one and "Databases_America" and "Databases_Asia" for the second one. Both parent groups are set for ACL to be spread.

Acl hierarchy groups.png

In the user edit view, the following profiles are added:

Acl hierarchy 1.png

The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps" and "Databases".

However, if a child of "Databases" is added:

Acl hierarchy 2.png

The user will have access to the groups named "Applications", "Development_Apps", "Management_Apps", "Databases" and "Databases_Asia", but not to "Databases_America".

1.2.4.4 Secondary groups

From update package 721 agents may have secondary groups. Unlike the primary group, these secondary groups are optional.

Secondary agent.png

An agent belonging to a secondary group means that it actually belongs to several groups at the same time. With this feature, two users with different permissions may have access to the same agent by just adding the appropriate secondary groups.

For example, if an agent called "Portal" has "Infrastructures" as main group and "Hosting" as secondary group, any user that has access to "Infrastructures" and/or a "Hosting" may access it.

Some views, such as Tree View, may show repeated agents. That is the usual performance when using secondary groups.

1.2.5 ACL Enterprise System

1.2.5.1 Introduction

The ACL Open Source model is based on "unix style" role/action/group/user (4 items).

The ACL Enterprise system allows you to define -according to profile- which pages (defined one by one or by "groups") users have access to. This will allow you to redefine which sections of the interface a user can see. For example, to allow a user to see only the "Group" view and the "Detailed" agent view, skipping pages such as "Alert view" or "Monitor view", already grouped in the classic Pandora FMS ACL system as "AR" (Agent Read Privileges).

This feature allows you to restrict the administration per page. It is very useful to allow some specific low-level operations.

Info.png

Both models are "parallel" and compatible. The classic ACL system is complementary and it is evaluated prior to the ACL Enterprise system.

 


1.2.5.2 Configuration

In order to be able to use the new ACL system, the first step is to activate it in the configuration tab. This option is only visible if you use the Enterprise version.



Enterprise acl setup.png



To configure the Enterprise ACL system, go to the specific option for ACL Enterprise in Administration > Setup. On this screen you may add new items in the new ACL System and see the items defined by profile. You can also delete items from the Enterprise ACL system.



Acl setup1.png



Template warning.png

If the Enterprise ACL system is enabled, it restricts ALL pages to ALL groups (including the Administrator!) to all defined (allowed) pages in the Enterprise ACL system. If a user with the "Administrator" profile does not have pages included in the Enterprise ACL system, they will not be able to see anything.

 


Template warning.png

Please, be careful with this, because you may lose access to the console if you enable improper ACL Enterprise configuration for your user.

 


If you have mistakenly lost access to the console, you may disable the Enterprise ACL system from the command line:

/usr/share/pandora_server/util/pandora_manage.pl /etc/pandora_server.conf --disable_eacl

You can define "page by page", "complete sections", set "any" rule or add "custom pages" that are not accessible from the menu.

There are two ways to add pages to a profile: with the wizard (default) or with custom edit. Above the button to add a rule, there is a button to change this mode.

1.2.5.2.1 Wizard

In the wizard we will choose the sections and pages of some combo controls.

Template warning.png

The pages that appear in these combos are only those accessible from the menu. To give access to pages that can be accessed in another way (e. g. the agent main view) use the custom editor.

 


To include a Pandora FMS page in the "allowed pages", you must select the profile to which the rule will be applied, then select in "Section" control the section that contains the desired page. You can then select any of your pages in the "Page" control.



Acl setup4.png



Another option is to select a section and the value "All" in the "Page" control. This will allow the chosen profile to see "all" of the selected section. Also by selecting "All" in both controls, users of that profile will be allowed to view "all" of "all" sections, just as it would be without the Enterprise ACL System for that profile.

Template warning.png

For a section in the menu to be displayed, the user must have access to at least the first page of the section. For example, for the "Monitoring" section to be displayed they must have access to at least "Tactical View".

 


1.2.5.2.2 Custom editing

To add individual pages that are not accessible from the menu, you may manually enter your sec2. To that end, access the page you wish to add and copy the parameter sec2.

For example, if you wish to add the main view of the agents, enter the view of any agent and find a URL similar to this one:

http://localhost/pandora/index.php?sec=estado&sec2=operation/agentes/ver_agente&id_agente=7702

Enter the contents of parameter sec2 (operation/agents/see_agent) in the text box.



Acl setup5.png



1.2.5.3 Security

Any page that is not "allowed" will not be displayed in the menu, and its use will not be allowed, even when the user enters the URL in "manual" mode. Any page that isn't allowed by the "Classic" Pandora FMS ACL system will not be allowed by the Enterprise ACL system (this is valid for the classic ACL system). This would be a specific example of several filters:



Acl example.png



In addition, there is a control that checks whether a page belongs to a section, which reinforces security against manual URL modifications. This check will be skipped for pages added with the custom editor, as well as the access to each pages belonging to a full section whose access is granted, thus optimizing the load.

1.3 Servers

The detailed view of the servers is used to know, besides the general state of the Pandora FMS servers, their load level and delay. Let us see a screenshot of a server status screen that is reached through the operation menu > Pandora Servers.

Server explained 2017.png

Some icons have special relevance, as seen in the above caption:

  • Poll request: It asks the remote test server to run all the checks it has, forcing it to run them again. Valid for all network servers, e. g. Network server, WMI server, Plugin server, WEB server, etc.
  • Editing Discovery server tasks.
  • Edit remote server configuration. Valid for Pandora FMS servers or satellite servers .

In addition, in this view you may see several important data, each column shows the following information:

  • Server name, usually the hostname of the machine.
  • Status (green = active, grey = stopped or down).
  • Server type: data server, network server, etc.
  • Progress bar indicating the total module load percentage for that type of server. In this case, all servers are at 100% except for recon server, which has no associated tasks so it is at 0%.
  • Number of such modules executed by the server with respect to the total number of such modules.
  • Server Lag: Highest amount of time spent by the oldest module waiting to receive data / Nº of modules out of their lifetime. In this example, there are approx. 3000 modules out of their lifespan, with a lag time of 10 minutes 13 seconds. This indicator is useful to know if you have many modules and to know if the server is at load capacity limit, as it is this case. Although it does not have an excessive delay (10 minutes 13 sec, for modules that have a lifespan average of 5 min), the number of modules out of time is considerable. In the case of the network server, this figure is much lower, being only 19 modules with a lag (10 minutes) of a total of almost 1500 modules.
  • Total number of threads configured on the server: Total number of modules in queue waiting to be attended. These parameters reflect excessive load status. There should almost never be queued modules. This reflects the server's inability to process the data.
  • Number of seconds since the server updated its data. Each server has a "Keepalive" that updates its status, to make sure it is active and updating its statistics.

1.4 Credential store

Pandora FMS features a credential store. This repository manages the IDs used in sections such as Discovery Cloud or agent automatic deployment.

Cred store.png

Next, the "Credential store" tab is displayed.

Cred store1.png


There are three different login information types to register:

  1. Amazon Web Services (AWS) login information
  2. Microsoft Azure login information
  3. Custom login information


Cred store2.png


To add a new entry, press the "add" button and fill out the pop-up form.


The group assigned to the password controls its visibility. That means that if the password 'test' is assigned to the group named 'All', all Pandora FMS console users will be able to see said password.

In a similar way, if 'test' is allocated to the group named 'Applications', only users with permissions on 'Applications' will have access to the password.


Cred store3.png


Once added, it can be checked, filtered etc.

Cred store5.png


Within password customization, the only thing that cannot be modified is the type of login information:


Cred store6.png

1.5 Scheduled downtimes

1.5.1 Introduction

Pandora FMS has a small scheduled downtime management system. This system allows you to disable alerts at intervals when there is a downtime, disabling the agent. When an agent is disabled it does not collect information either, so that in a downtime, for most metrics or report types, the intervals where there is a downtime are not taken into account in the reports because there is no data in the agents during those intervals.



Downtimegeneral.png

1.5.2 Create a scheduled downtime

To create a downtime, go to the Tools > Scheduled downtime menu and press the button to create one:



Downtime1.png

You will find the following configurable parameters:

  • Name: Name of the scheduled downtime.
  • Group: The group you want it to belong to.
  • Description.
  • Type: You may set the following types of downtimes:
    • Quiet: Check as "quiet" the indicated modules, so they will not generate alerts nor events.
    • Disable Agents: It disables the selected agents. It is important to know that if an agent is manually disabled before the task is launched, it will become enabled once this task is completed.
    • Disable Alerts: It disables alerts of selected agents.
  • Execution: It allows to configure whether you want it to run once or periodically.
  • Set time: Setting the day and time at which the scheduled downtime will start and end either once or periodically, depending on what has been previously configured in "Execution".


Info.png

If the Pandora FMS administrator enables it in the visual configuration section, it is possible to create scheduled downtimes in a past date. They will not be executed, but their existence will be reflected in different reports. This is particularly relevant since it affects, among others, availability reports and SLAs.

 


Downtime2.png

Finally, specify which specific agents you want to include in that downtime.



Downtime5.png

When a scheduled downtime is "active", it cannot be modified or deleted, but from version 5.0 onwards there is an option where you may stop the execution in "Stop downtime", so that all agents/modules/alarms that the scheduled downtime disabled temporarily may be re-enabled. This option does not support periodic scheduled downtimes. From version 6.0 onwards, non-periodic scheduled downtimes can be delayed even if they are 'active'. When this downtime is over, you may modify or delete it.

1.5.3 Alternatives to console downtime management

There are often certain "cyclical" situations to be taken into account and the method of downtime management is too specific: for example, you may want to be able to deactivate all agents quickly and on time or to plan a general downtime every week from time to time. For this type of operations, there are ways to do it from the command line.

There is a faster way to set all agents in service mode, through the use of Pandora FMS management CLI, pandora_manage. pl through the command line:

./pandora_manage.pl /etc/pandora/pandora_server.conf --enable_group 1

Pandora FMS Manage tool 3.1 PS100519 Copyright (c) 2010 Artica ST
This program is Free Software, licensed under the terms of GPL License v2
You can download latest versions and documentation at http://www.pandorafms.org

[*] Pandora FMS Enterprise module loaded.

[INFO] Enabling group 1

Disabling them would be the following way:

./pandora_manage.pl /etc/pandora/pandora_server.conf --disable_group 1

1.6 Audit Log

Pandora FMS keeps a log of all changes and important actions taken in Pandora FMS console. This log can be seen in Admin tools > System Audit Log.



Gest67.png



On this screen, you may see a series of entries related to console activity, user information, action type, date and a brief description of the events recorded.

Audit 1.png

In the upper left corner, you may filter which entry will be displayed by different criteria including: actions, user and IP, you may even perform a text search and determine the maximum amount of hours.

The available filtering fields:

  • Action: The different possible filtering actions > ACL Violation, Agent management, Agent remote configuration, Alert management, Command management, Dashboard management, Event alert management, Event deleted, Extension DB inface, File collection, Logoff, Logon, Logon Failed, Massive management, Module management, No session, Policy management, Report management, Setup, System, Template alert management, User management, Visual console builder.
  • User.
  • Free text for search: It will search in the fields User, Action and Comments.
  • Max. Hours old: Number of backward hours where to display events.
  • IP: Source IP address.

It is also possible to export the information displayed on the screen to a CSV file by clicking on the button at the top right of the screen.

Audit 02.png
Available filtering actions


With this tool, you may search, for example, for the task that a user performs on agent management in the last hour.

Audit 03.png

Or the moment when a given user has logged in the console. You may retrieve all information about the actions performed by the entire user. In addition, you may see the Pandora FMS server service start date or when the console configuration was changed.

Audit 04.png

1.7 Local server logs

In latest Pandora FMS console versions, log status can be checked through the menu Extensions > Extension management > System logs.


System logs menu.png

From this extension you may see the logs of both the console and the local server:

System logs main.png


If you cannot see the content, check your log file permissions:

chown -R pandora:apache /var/log/pandora/


You may change the rotator options to keep these settings by modifying the /etc/logrotate.d/pandora_server file.

/var/log/pandora/pandora_server.log
/var/log/pandora/websocket.log 
/var/log/pandora/pandora_server.error {
	weekly
	missingok
	size 300000
	rotate 3
	maxage 90
	compress
	notifempty
        copytruncate
	create 660 pandora apache
}
/var/log/pandora/pandora_snmptrap.log {
	weekly
	missingok
	size 500000
	rotate 1
	maxage 30
	notifempty
	copytruncate
	create 660 pandora apache
}

On the other hand, there is also a specific configuration for the console log rotation in /etc/logrotate.d/pandora_console:

/var/www/html/pandora_console/log/audit.log
/var/www/html/pandora_console/log/console.log {
        weekly
        missingok
        size 100000
        rotate 3
        maxage 15
        compress
        notifempty
        create 644 apache root
}


Note: If your system is SuSE, replace apache with www-data. In case of using a different system, check the users corresponding to the Apache service. (httpd)

Template warning.png

If updating from OUM a version prior to 747 you will need to manually modify the logrotate file.

 


1.8 Cron Job

This Pandora FMS Enterprise extension allows to schedule task execution from Pandora FMS server.

The extension can be accessed from Servers > Cron jobs.



Cron jobs.jpg



To add a task, the following fields must be filled in:

  • Task: Combo where the task to perform can be chosen.
    • Send custom report via e-mail
    • Run custom script
    • Pandora FMS BD Backup
    • Save custom report in disk
  • Schedule: Field where task frequency can be chosen.
    • Without schedule: These tasks will be executed only once and at the specified time..
    • Hourly
    • Daily
    • Weekly
    • Monthly
    • Yearly
  • First run: Field where the date and time of the first task execution is chosen. It will be executed periodically, taking this date and time as a reference.
  • Parameters: Field that allows entering parameters in the task to be performed. It varies by task.
    • Pandora FMS BD Backup: Description and path where the backup will be stored.
    • Send report via e-mail: Report to be sent and recipient's e-mail address.
    • Run script: Script command to run.
    • Save report to disk: Report to be saved and the path to store it.

Once the data has been filled in, click on create and the task will appear in the scheduled tasks list.



Cron jobs list.jpg



Once the scheduled task has been created, it is possible to force its execution by clicking on the green circle to the right of the task or delete it by clicking on the red cross on the left.


Info.png

If the cron job is "non scheduled", it will be deleted automatically when executed.

 



1.9 DB management from the console

The core of Pandora FMS system is its database. It stores all data collected by monitored systems, agent configuration, alerts, events, audit data, different users and their data. That is, all system data.

Efficiency and reliability are vital for Pandora FMS to work properly, so database maintenance is essential.

To perform regular database maintenance, administrators can use standard MySQL commands from the command line or manage the database from the console although they may not have extensive Mysql knowledge.

Pandora FMS has multiple extensions that can be used from the console to see information from the database.

1.9.1 Diagnostic tool

This section shows general information about Pandora FMS installation. It is necessary to emphasize the high amount of information that is obtained from the database, where the recommended parameters can be seen, as well as warnings about existing values that need to be changed.



Captura de pantalla de 2017-10-09 13-37-10.png



Diagnostic info1.png

Diagnostic info2.png

Diagnostic info3 new.png

Diagnostic info4.png

1.9.2 DB Interface

This is an extension that allows you to execute commands in the database and see the result. It is an advanced tool that should only be used by people who have a certain amount of knowledge about SQL and the Pandora FMS database schema.

Template warning.png

If misused, this tool may "destroy" data or permanently render the application inoperative.

 


It is accessed from Admin tools > DB interface.



Ex10.png



Write the command in the blank field and click on "Execute SQL".

1.9.3 DB Schema Check

This is an extension that allows to check the structural differences between the database set in your Pandora FMS and a pattern scheme to compare possible errors.

It works like this:

  • A temporary database is created with the structure that the installation database should have (different depending on the installed version).
  • The database created is compared with the database referenced in the installation.
  • The temporary database is deleted.




Captura de pantalla de 2017-10-09 13-47-04.png



Enter the data to access your database and click on "Run test".

Info.png

It is recommended to use this extension to check whether a database migration has been correctly performed.

 


Template warning.png

This check can only be done in MySQL Databases.

 


1.10 Network Tools

  • Traceroute path: If empty, Pandora FMS will search the traceroute system.
  • Ping path: If empty, Pandora FMS will search the ping system.
  • Nmap path: If empty, Pandora FMS will search the nmap system.
  • Dig path: If empty, Pandora FMS will search the dig system.
  • Snmpget path: If empty, Pandora FMS will search the snmpget system.

1.11 Backup

Extension that allows backing up the DB and restoring it.

To make a backup, first select the destination folder where the data will be stored. Once chosen, write a backup description.



Ex12.png



When the backup is done, it will appear in the Backup list with the running icon.

Ex13.png

Once the Backup has been created, it is possible to:

  • Download it by clicking on this icon:

Ex14.png

  • Do a rollback by clicking on this icon:.

Ex15.png

The rollback applies a previously created backup and restores it. This will destroy all existing data in the console and apply the data that exists in the backup on which the rollback is made.

Template warning.png

By means of this tool it is possible to recover the database backup made through this feature. It is not possible to load a manual backup.

 


  • Delete it by clicking on this icon:

Ex16.png




1.12 Plugin log

Extension that allows you to easily register server plugins.

The extension can be accessed through Servers > Register plug-in.



Ex9.png



To register a plugin choose the file by clicking on "Browse" and "Upload".

More information about server plugins can be found in the development and extension chapter.

You may see in section [Plugin Development] the format of the .pspz files.

1.13 Insert data

Extension that allows to import data in a comma separated file (CSV) to an agent module. This extension is accessed from Resources > Insert Data.



Insert data1.png



The format of the CSV file must be date;value per line. The date must be given in Y/m/d H:i:s format:

2011/08/06 12:20:00;77.0
2011/08/06 12:20:50;68.8


1.14 Resource registration

This extension allows you to import .prt files containing the definition of network component, smnp component, local component or wmi component. You may also add all of them (except for the local component) to a template.



Resource registration screenshot.png



1.14.1 .prt file format

<?xml version="1.0"?>
<pandora_export version="1.0" date="yyyy-mm-dd" time="hh:mm">
	<component>
		<name></name>
		<description></description>
		<module_source></module_source>
		<id_os></id_os>
		<os_version></os_version>
		<data></data>
		<type></type>
		<max></max>
		<min></min>
		<max_cri></max_cri>
		<min_cri></min_cri>
		<max_war></max_war>
		<min_war></min_war>
		<historical_data></historical_data>
		<ff_treshold></ff_treshold>
		<module_interval></module_interval>
		<id_module_group></id_module_group>
		<group></group>
		<tcp_port></tcp_port>
		<tcp_send></tcp_send>
		<tcp_rcv_text></tcp_rcv_text>
		<snmp_community></snmp_community>
		<snmp_oid></snmp_oid>
		<snmp_version></snmp_version>
		<auth_user></auth_user>
		<auth_password></auth_password>
		<privacy_method></privacy_method>
		<privacy_pass></privacy_pass>
		<auth_method></auth_method>
		<security_level></security_level>
		<plugin></plugin>
		<plugin_username></plugin_username>
		<plugin_password></plugin_password>
		<plugin_parameters></plugin_parameters>
		<wmi_query></wmi_query>
		<key_string></key_string>
		<field_number></field_number>
		<namespace></namespace>
		<wmi_user></wmi_user>
		<wmi_password></wmi_password>
		<max_timeout></max_timeout>
		<post_process></post_process>
	</component>
	<component>...</component>
	<component>...</component>
	<template>
		<name></name>
		<description></description>
	</template>
</pandora_export>

1.15 Text string translator

This extension belongs to the menu Setup > Translate string and allows translating Pandora FMS interface text strings to customize it.



Translate string.png



The fields to be filled in are detailed below:

  • Language: It allows to filter strings by language.
  • Free text for search (*): Content of the string you wish to customize.

Three columns will appear: the first one will show the original string, the second one the current translation and in the third one the custom translation you wish to add.

1.16 Workspace

This section allows interacting with Pandora FMS users, or edit the user's details, as well as several actions, such as access to the issue system (to open tickets), chatting with other users connected to Pandora FMS, etc.

1.16.1 Chat

It allows to interact with other users connected to that Pandora FMS console through a chat. It is useful in case you want to say something to another operator for example.

1.16.2 Issues

Pandora FMS allows managing issues from the console thanks to its integration with Integria IMS.

For more information about this tool, check issue management with Integria IMS.

1.16.3 Messages

Pandora FMS has a tool that allows different users to send messages among themselves.

1.16.3.1 See messages

When a user has a message, an envelope icon appears at the top right of the console.



Gest20.png



User messages can be seen in Workspace > Messages > Messages list, and from there you may read, delete or write a message to a specific group or user.

1.16.4 Connected users

This extension shows other users connected to the Pandora FMS Console other than their own. This feature is important because Pandora FMS console allows multiple user connections.

The extension is accessed from Workspace > Connected users.



Ex4b.png



1.17 Software agent repository

Software agent repository is part of the deployment center, which controls agent installer available versions (programs) to be deployed.

You may access it through this menu:

Agent repo1.png


To add a new installer to the repository, click "Add agent".

Agent repo2.png


Fill out the information related to the target OS type, the architecture, the installing file, etc.

Agent repo3.png


Note: Installers for Linux (and all Unix and BSD range) are shared by all architectures. Both x64, x86, ARM, etc share the same installer.


Make sure the upload was successful:

Agent repo4.png


The uploaded agent installer will appear on the list together with the information about its version, by whom and when it was uploaded etc.:

Agent repo5.png

1.18 Custom themes

Pandora FMS offers the possibility of uploading CSS files, in order to set custom themes in the visual console.

To that end, include the following comment in the CSS file:

/*
Name: My custom Theme
*/

Then, import the CSS file to the following path:

pandorafms/pandora_console/include/styles/CustomTheme.css

Once the desired themes are uploaded, go to Setup > Setup > Visual styles and select the appropriate theme from the Style template drop-down.

CustomTheme1.png



Go back to Pandora FMS Documentation Index