Difference between revisions of "Pandora: Metaconsole: Documentation en: Synchronization and propagation"

From Pandora FMS Wiki
Jump to: navigation, search
(Created page with "=Herramientas de sincronización= '''La metaconsola''' tiene '''herramientas de sincronización de elementos''', las cuales son fundamentales para la correcta gestión de las...")
 
 
(31 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=Herramientas de sincronización=
+
{{WIP}}
'''La metaconsola''' tiene '''herramientas de sincronización de elementos''', las cuales son fundamentales para la correcta gestión de las Instancias. La sincronización se basa en pasar toda la información creada en la metaconsola a las distintas Instancias para gestionar desde la metaconsola toda la información posible de cada una de ellas.
 
  
Por ejemplo, si tenemos 20 instancias(nodos) distintos en nuestra empresa, y queremos que un mismo usuario tenga los mismos permisos de acceso en dichos 20, podremos crear un usuario con los perfiles deseados y sincronizaremos dicho usuario para tenerlo en las 20 instancias(nodos) y así no tener que crearlo de manera individual en cada instancia.
+
=Synchronization tools=
 +
The '''Metaconsole''' has '''tools for the synchronization of elements''', which are fundamental for the correct management of the Instances. The synchronization is based on passing all the information created in the metaconsole to the different Instances to manage all possible information of each of them from the Metaconsole.  
  
Otro ejemplo, tenemos que monitorizar distintos clientes que están repartidos por nuestras instancias, de manera que algunos clientes además se encuentran repetidos en distintas instancias. Podremos crear los distintos grupos a los que van a pertenecer los agentes de las distintas instancias, y posteriormente sincronizar cada grupo correspondiente con su instancia.
+
For example, if we have 20 different instances(nodes) in our company, and we want the same user to have the same access permissions in those 20, we can create a user with the desired profiles and synchronize that user to have it in the 20 instances(nodes) and thus not have to create it individually in each instance.
  
A continuación, vamos a ver en detalle las distintas sincronizaciones que nos permite realizar la metaconsola.
+
Another example, we have to monitor different clients that are distributed throughout our instances, so that some clients are also repeated in different instances. We will be able to create the different groups to which the agents of the different instances will belong, and then synchronize each corresponding group with its instance.
  
==Sincronización de usuarios==
+
Next, we are going to see in detail the different synchronizations that the Metaconsole allows us to make.
  
Esta opción permite al usuario sincronizar los usuarios de la Metaconsola y sus perfiles en las instancias.
+
==User Synchronization==
  
Dentro de esta sincronización podemos encontrar dos distintas opciones:  
+
This option allows the user to synchronize the users of the Metaconsole and their profiles in the instances.
* Copiar los perfiles configurados al usuario
+
 
 +
Within this synchronization we can find two different options:  
 +
* Copy the configured profiles to the user
 
<center>
 
<center>
 
[[File:sync_usuarioscopia.png]]  
 
[[File:sync_usuarioscopia.png]]  
 
</center>
 
</center>
* Dar nuevos perfiles al usuario creado.
+
* Give new profiles to the created user
 
<center>
 
<center>
 
[[File:sync_usuariosnuevos.png]]  
 
[[File:sync_usuariosnuevos.png]]  
 
</center>
 
</center>
  
En ambos casos tenemos la opción de crear los grupos asociados a los perfiles en caso de que no existan en la instancia(nodo).
+
In both cases we have the option to create the groups associated to the profiles in case they do not exist in the instance(node).
  
Se recomienda antes de usar esta sincronización, tener en cuenta los usuarios que se van a crear nuevos en las instancias, debidos a posibles conflictos en el ID de usuario. Es recomendable no tener usuarios creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos usuarios tanto en está como en las instancias.
+
Before using this synchronization, it is recommended to take into account the users that are going to create new ones in the instances, due to possible conflicts with the user ID. It is recommended not to have users created in the instances and to create them all from the meta console in order to have the same users both in there as in the instances.
  
{{Tip|En ambos casos, los perfiles que no existan en la instancia se crearán.}}
+
{{Tip|In both cases, profiles that do not exist in the instance will be created.}}
  
{{Warning|'''Ante la duda''' de cuál de estas dos opciones utilizar se deberán '''Copiar los perfiles del usuario'''.}}
+
{{Warning|'''When in doubt''' about which option is best to use, '''user profiles must be copied'''.}}
  
==Sincronización de grupos==
+
==Group Synchronization==
  
Esta opción permite al usuario sincronizar los grupos de la Metaconsola con las instancias.
+
This option allows the user to synchronize the Metaconsole groups with the instances.
 
<center>
 
<center>
 
[[File:sync_grupos.png]]  
 
[[File:sync_grupos.png]]  
 
</center>
 
</center>
  
Es recomendable no tener grupos creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos grupos tanto en está como en las instancias.
+
It is recommended not to have groups created in the instances and to create them all from the meta console in order to have the same groups both in there and in the instances.
  
{{Warning|Una vez sincronizados los grupos, no se deben modificar los nombres de los mismos ni en la metaconsola, ni en el nodo. Si se hace, habrá que modificarlos en ambos sitios para que no dé problemas ya que la sincronizacion se basa en el ID, pero algunas operaciones utilizan en el nombre. La sincronización en la version actual sincroniza el nombre la primera vez, pero si hay cambios posteriores de nombres en los grupos no se sincronizan}}
+
{{Warning|Once the groups have been synchronized, their names should not be modified either in the meta console or in the node. If it is done, it will be necessary to modify them in both places so that it does not give problems since the synchronization is based on the ID, but some operations use the name. The synchronization in the current version synchronizes the name the first time, but if there are later changes of names in the groups they will not be synchronized.}}
  
==Sincronización de Alertas==
+
==Alert Synchronization==
 +
 
 +
This option allows the user to synchronize the Metaconsole alerts with the instances.
  
Esta opción permite al usuario sincronizar las aletas de la Metaconsola con las instancias.
 
 
<center>
 
<center>
 
[[File:sync_alertas.png]]  
 
[[File:sync_alertas.png]]  
 
</center>
 
</center>
  
Es recomendable no tener alertas creados en las instancias y crearlas todas desde la metanconsola para así tener las mismas alertas tanto en está como en las instancias.
+
It is recommended not to have alerts created in the instances and to create them all from the console in order to have the same alerts both in there and in the instances.
  
==Sincronización de Componentes==
+
==Component Synchronization==
  
Esta opción permite al usuario sincronizar los componentes de la Metaconsola con las instancias.
+
This option allows the user to synchronize the components of the Metaconsole with the instances.
 
<center>
 
<center>
 
[[File:sync_componentes.png]]  
 
[[File:sync_componentes.png]]  
 
</center>
 
</center>
  
Es recomendable no tener componentes creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos componentes tanto en está como en las instancias.
+
It is recommended not to have components created in the instances and to create them all from the Metaconsole in order to have the same components both in there and in the instances.
  
==Sincronización de Tags==
+
==Tag Synchronization==
  
Esta opción permite al usuario sincronizar los tags de la Metaconsola con las instancias.
+
This option allows the user to synchronize the tags of the Metaconsole with the instances.
 
<center>
 
<center>
 
[[File:sync_tagsnew.png]]  
 
[[File:sync_tagsnew.png]]  
 
</center>
 
</center>
  
Es recomendable no tener tags creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos tags tanto en está como en las instancias.
+
It is recommended not to have tags created in the instances and to create them all from the Metaconsole in order to have the same tags both in there and in the instances.
  
==Sincronización de OS==
+
==OS Synchronization===
  
Esta opción permite al usuario sincronizar los sistemas operativos de la Metaconsola con las instancias.
+
This option allows the user to synchronize the OS of the Metaconsole with the instances.
 
<center>
 
<center>
 
[[File:sync_OS.png]]  
 
[[File:sync_OS.png]]  
 
</center>
 
</center>
  
Es recomendable no tener sistemas operativos creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos sistemas operativos tanto en está como en las instancias.
+
It is recommended not to have OS created in the instances and to create them all from the Metaconsole in order to have the same OS both in there and in the instances.
 +
 
 +
==Module Groups Synchronization==
  
==Sincronización de Module Groups==
+
This option allows the user to synchronize the module groups operating in the Metaconsole with the instances.
  
Esta opción permite al usuario sincronizar los grupos de módulos operativos de la Metaconsola con las instancias.
 
 
<center>
 
<center>
 
[[File:sync_modulegroups.png]]  
 
[[File:sync_modulegroups.png]]  
 
</center>
 
</center>
  
Es recomendable no tener los grupos de módulos creados en las instancias y crearlos todos desde la metanconsola para así tener los mismos sistemas operativos tanto en está como en las instancias.
+
It is recommended not to have the groups of modules created in the instances and to create them all from the Metaconsole in order to have the same groups of modules both in there and in the instances.
  
=Herramientas de Propagación=
+
=Propagation tools=
  
La metaconsola tiene herramientas de propagación de elementos. A diferencia de la sincronización, no se trata de una herramienta fundamental para el funcionamiento óptimo de la Metaconsola, solo facilita la disponibilidad de los datos en las Instancias, algo que es necesario si, por ejemplo, utilizamos políticas que se aplican en diferentes instancias (o nodos).
+
The MetaConsole has tools for the propagation of elements. Unlike synchronization, it is not a fundamental tool for the optimal functioning of the Metaconsole, it only facilitates the availability of data in the Instances, something that is necessary if, for example, we use policies that are applied in different instances (or nodes).
  
{{Tip|Se recomienda sincronizar las instancias con la metaconsola después de la creación de los distintos elementos en la herramienta de propagación.}}
+
{{Tip|It is recommended to synchronize the instances with the meta console after the creation of the different elements in the propagation tool.}}
  
A continuación, vamos a ver en detalle las distintas propagaciones o gestión de datos que nos permite realizar la metaconsola.
+
Next, we are going to see in detail the different propagations or data management that allows us to make the meta console.
  
==Gestión de usuario==
+
==User Management==
  
En esta sección se pueden realizar las siguientes acciones:
+
The following actions can be performed in this section:
* Gestión de usuarios
+
*User management
* Gestión de perfiles
+
*Profile management
* Editar mi usuario
+
*Edit my user
  
Por ejemplo, tenemos 10 instancias dentro de nuestra metaconsola, donde queremos que un usuario con permisos especiales opere dentro de 3 de ellas. En primer lugar, nos iríamos a gestión de perfiles donde crearíamos un perfil especial con los permisos que queramos. Posteriormente creamos al usuario que vamos a querer que gestione las tres instancias, asignándole el permiso que hemos creado. Por último, sincronizaremos dicho usuario y perfiles con las instancias para tenerlo ya en las tres. Después de un tiempo el usuario se nos ha quedado obsoleto, pero en vez de borrar el usuario lo inactivamos por si en un futuro lo queremos volver a usar, nos vamos a la gestión de usuarios y utilizamos el símbolo de la bombilla para desactivarlo hasta nuevo aviso.
+
For example, we have 10 instances inside our meta console, where we want a user with special permissions to operate inside 3 of them. First, we would go to profile management where we would create a special profile with the permissions we want. Then we create the user we want to manage the three instances, assigning the permission we have created to it. Finally, we will synchronize this user and profiles with the instances to have it in all three. After a while the user has become obsolete, but instead of deleting the user we deactivate it in case we want to use it again in the future, we go to user management and use the bulb icon to deactivate it until further notice.
  
===Gestión de usuarios===
+
===User Management===
  
En este apartado podemos ver la lista de usuarios ya creados, modificar la configuración de los mismos, borrarlos, desactivarlos o crear usuarios nuevos.
+
In this section we can see the list of users already created, modify their configuration, delete them, deactivate them or create new users.
 
<center>
 
<center>
 
[[File:gestion_usuarios.png]]  
 
[[File:gestion_usuarios.png]]  
 
</center>
 
</center>
  
====Crear un nuevo usuario====
+
====Create a new user====
  
Para añadir un usuario hagamos click en el botón de “Create User”, donde nos aparecerá el siguiente formulario el cual deberemos rellenar:
+
To add a user click on the "Create User" button, where we will see the following form which must be filled:
 
<center>
 
<center>
 
[[File:gestion_creacionusuarios.png]]  
 
[[File:gestion_creacionusuarios.png]]  
 
</center>
 
</center>
 
<center>
 
<center>
[[File:gestion_creacionusuarios2.png]]  
+
[[File:gestion_creacionusuarios2.2.png]]  
 
</center>
 
</center>
  
Los parámetros que requieren explicación son:
+
The parameters that require explanation are:
 
 
* '''Interactive charts''': Permite que el usuario pueda o no ver las gráficas interactivas y como última opción basarse en la opción configurada en la configuración global.
 
  
* '''Metaconsole access''': Fija los permisos de acceso del usuario a la metaconsola siendo estos.
+
* '''Interactive charts''': It allows the user to choose if they prefer to see the interactive graphics, or on the contrary, to use the general configuration of the Metaconsole.
  
** '''Básico''': Con este acceso el usuario podrá utilizar en el Wizard solamente a los componentes cuyo nivel de Wizard sea ''Básico''. Siempre que tenga permisos ACLs sobre el grupo al que pertenezcan.
+
* '''Metaconsole access''': It sets the user permissions to access the console. These permissions can be:
 +
**'''Basic''': With this access the user will be able to use in the Wizard only the components whose Wizard level is ''Basic'', as long as the user has ACL permissions on the group they belong to.
 +
**'''Advanced''': With this access the user will be able to use any of the components in the Wizard regardless of their Wizard level, as long as the user has ACL permissions on the group they belong to.
  
** '''Avanzado''': Con este acceso el usuario podrá utilizar en el Wizard cualquiera de los componentes independientemente de su nivel de Wizard. Siempre que tenga permisos ACLs sobre el grupo al que pertenezcan.
+
* '''Search custom field view''': Seleccionamos el filtro por defecto para la vista de "Campos personalizados"
  
* '''Not Login''': Si se selecciona esta opción el usuario podrá acceder a la API
+
* '''Not Login''': If this option os selected, the user will be able to access the API.
  
* '''Enable agents management''': Esta opción sirve para habilitar la administración de agentes en el Wizard. Si está desactivada solamente estarán disponibles los Wizard de módulos y alertas.
+
* '''Enable agents management''': This option is used to enable the agent management in the Wizard. If it is deactivated, only the Wizards of modules and alerts will be available.
  
* '''Enable node access''': Esta opción sirve para habilitar el acceso a las instancias. Si está activada, se podrá acceder a través del nombre de agentes y módulos en muchos sitios a las consolas de las instancias. Por ejemplo, desde el mapa de red o la vista de eventos.
+
* '''Enable node access''': This option is used to enable access to the instances. If it is activated, it will be possible to access the consoles of the instances through the name of agents and modules in many places; for example, from the network map or the events view.
  
====Modificar/Desactivar/Borrar un usuario====
+
====Modify/Deactivate/Delete a user====
  
En la lista de usuarios se disponen de opciones para:
+
In the user list the following options are available:  
* Activar/Desactivar el usuario
+
* Activate/Deactivate the user
* Editar el usuario
+
* Edit the user
* Borrar el usuario de la Metaconsola
+
* Delete the user form the Metaconsole
* Borrar el usuario de la Metaconsola y de todas las Instancias
+
* Delete the user form the Metaconsole and all Instances
  
 
<center>
 
<center>
Line 148: Line 152:
 
</center>
 
</center>
  
El formulario de edición de un usuario es igual al de creación, pero incluyendo el editor de perfiles.
+
A user's editing form is the same as the creation form, but including the profile editor.
 +
 
 
<center>
 
<center>
 
[[File:gestion_modificacionusuarios2.png]]  
 
[[File:gestion_modificacionusuarios2.png]]  
 
</center>
 
</center>
  
En el editor de perfiles se le puede asignar al usuario perfiles en grupos determinados y además limitar esos privilegios a los Tags seleccionados. Si no se seleccionan Tags, el usuario tendrá acceso a todos los módulos, tengan asociados Tags o no.
+
In the profile editor the user can be assigned profiles in certain groups besides limiting those privileges to the selected Tags. If Tags are not selected, the user will have access to all modules, whether they have associated Tags or not.
  
===Gestión de perfiles===
+
===Profile Management===
  
En este apartado podemos ver la lista de perfiles ya creados, modificar la configuración de los mismos, borrarlos o crear perfiles nuevos.  
+
In this section we can see the list of profiles already created, modify their configuration, delete them or create new profiles.  
  
 
<center>
 
<center>
Line 163: Line 168:
 
</center>
 
</center>
  
Hay una serie de flags de ACLs que darán acceso a las diferentes funcionalidades de Pandora FMS. Para saber qué función habilita cada flag de ACLs de los perfiles, visite la sección [[Pandora:Documentation_es:Gestion_y_Administracion#Perfiles_en_Pandora_FMS|Perfiles en Pandora FMS]] en el manual de usuario.
+
There are a series of ACL flags that will give access to the different Pandora FMS functionalities. To know which function enables each ACL flag of the profiles, visit section [[Pandora:Documentation_es:Gestion_y_Administracion#Perfiles_en_Pandora_FMS|Perfiles en Pandora FMS]] in the user manual.
  
====Crear un nuevo perfil====
+
====Create a new profile====
  
Para añadir un perfil hagamos click en el botón de “Create”, donde nos aparecerá el siguiente formulario donde deberemos rellenar aquellos permisos que queremos dar con el perfil:
+
To add a profile click on the "Create" button to see the following form, where we must fill in those permissions that we want to give with the new profile:
  
 
<center>
 
<center>
Line 176: Line 181:
 
</center>
 
</center>
  
{{Tip|Algunos de estos bits no tienen sentido en la Metaconsola. Sin embargo puede que queramos utilizar la Metaconsola para sincronizar perfiles a las Instancias, donde sí que podrían ser útiles.}}
+
{{Tip|Some of these bits don't make sense in the Metaconsole. However, we may want to use the Metaconsole to synchronize profiles to Instances, where they could be useful.}}
  
====Modificar/ Borrar un perfil====
+
====Modify/Delete a profile====
  
En la lista de perfiles se disponen de opciones para:
+
In the list of profiles you have options to:
* Editar el perfil
+
* Edit the profile
* Borrar el perfil de la Metaconsola
+
* Delete a profile from Metaconsole
 
<center>
 
<center>
 
[[File:Dac2.1.png]]
 
[[File:Dac2.1.png]]
 
</center>
 
</center>
  
===Editar mi usuario===
+
===Edit my user===
  
En este apartado podemos configurar el usuario que está autenticado en la metaconsola. Los perfiles asignados al usuario serán meramente informativos. En caso de que el usuario autenticado no sea administrador, este será el único apartado que podrá ver.
+
In this section we can configure the user who is authenticated in the Metaconsole. The profiles assigned to the user will be merely informative. If the authenticated user is not an administrator, this will be the only section you can see.
  
 
<center>
 
<center>
Line 195: Line 200:
 
</center>
 
</center>
  
==Gestión de agentes==
+
{{WIP}}
  
En esta sección se pueden realizar las siguientes acciones:
+
==Agent management==
  
* Migración de agentes entre instancias
+
The following actions can be performed in this section:
* Autoprovisionamiento de agentes
 
* Gestión de grupos
 
  
Por ejemplo, tenemos pensado crear una gestión de 15 instancias en la metaconsola, y queremos que la distribución de los agentes sea por carga de cada instancia, creándose los agentes de manera que siempre se generen en la instancia con menor carga. Para ellos nos iremos al autoprovisionamiento y activaremos la opción indicada para ello. Una vez realizado, nos hemos dado cuenta que ciertos agentes deberían ir juntos en la misma instancia, entonces nos iremos a la migración de agentes entre instancias, donde escogeremos que agentes se mueven en que otras instancias de manera que no tengamos que borrar y crear los agentes manualmente.
+
*Migration of agents between instances
 +
*Self-provisioning of agents
 +
*Group management
  
===Migración de agentes===
+
For example, we are planning to manage 15 instances in the metaconsole, and we want the distribution of the agents to be organized according to the load of each instance, creating the agents so that they are always generated in the instance with the lowest load. To do this, we will go to auto-provisioning and activate the option indicated for it. Once done, if for example, we realize that certain agents should go together in the same instance, we will go to the migration of agents between instances, where we will choose which agents move to which other instances so that we don't have to delete and create the agents manually.
  
{{Warning|Esta funcionalidad requiere un servidor Metaconsola iniciado para funcionar.}}
+
===Agent Migration===
  
En esta sección podemos migrar agentes entre nuestras las instancias conectadas a nuestra metaconsola.
+
{{Warning|This feature requires a running Metaconsole server to work.}}
 +
 
 +
In this section we can migrate agents between the instances connected to our Metaconsole.
 
<center>
 
<center>
 
[[File:gestion_migagentes.png]]  
 
[[File:gestion_migagentes.png]]  
 
</center>
 
</center>
  
Para que no se transfieran los datos históricos de los agentes a transferir deberemos tener activada la casilla de “Discard history data”. Una vez que tengamos todo seleccionado y le demos al botón “move”, empezará a realizar las siguientes comprobaciones para poder realizar la migración.
+
In order for the historical data of the agents to be transferred, the "Discard history data" checkbox must be activated. Once we have everything selected and we press the "move" button, it will start to perform the following checks to be able to perform the migration.
  
;Los agentes no existen en el servidor destino: No debe existir ningún agente a migrar con el mismo nombre de agente en el servidor objetivo.
+
;The agents do not exist in the destination server: There must not exist any agent to migrate with the same agent name in the target server.
  
;Las colecciones necesarias están sincronizadas con el servidor destino: Para evitar que el agente intente descargar colecciones inexistentes una vez migrado, verifique que las colecciones existen en ambos servidores (origen y destino).
 
  
;Las definiciones de alertas necesarias están sincronizadas con el servidor objetivo: Verifique que las plantillas, acciones y comandos definidas en el servidor origen están definidas también en el servidor destino. Las relaciones se realizan a través de ID, por lo que estos valores también deberán ser idénticos.
+
;The necessary collections are synchronized with the destination server: To prevent the agent from attempting to download non-existent collections once migrated, verify that the collections exist on both servers (source and destination).
  
;Los ficheros de configuración de los agentes software asociados a los agentes no existen en el servidor objetivo: No deben existir ficheros de configuración con el mismo nombre que los asociados a los agentes que vamos a migrar en el servidor objetivo. De ser así deberemos eliminarlos del servidor destino.
+
;The necessary alert definitions are synchronized with the target server: Verify that the templates, actions and commands defined on the source server are also defined on the target server. The relations are made through ID, so these values must also be identical.
  
;Ambos servidores tienen la misma versión: Verifique que las versiones de Pandora FMS son idénticas en ambos servidores.
+
;The configuration files of the software agents associated to the agents do not exist in the target server: There must not be configuration files with the same name as those associated to the agents that we are going to migrate in the target server. If so, we must remove them from the destination server.
  
;La dirección del servidor destino está configurada: Verifique que la dirección IP de su servidor destino (Dataserver) está configurada, puede acceder a la siguiente pantalla a través de <i>Servidores > Administrar servidores</i> de la instancia a la que queremos trasladar los agentes:
+
;Both servers have the same version: Verify that Pandora FMS versions are identical in both servers.
 +
 
 +
;The address of the destination server is configured: Verify that the IP address of your destination server (Dataserver) is configured, you can access the following screen through <i>Servers > Manage servers</i> of the instance to which we want to move the agents:
  
 
<center>
 
<center>
Line 235: Line 243:
 
</center>
 
</center>
  
;Las políticas necesarias están sincronizadas con el servidor destino: Verifique que las políticas del servidor origen están disponibles en el servidor destino. Las relaciones se realizan a través de ID, por lo que estos valores también deberán ser idénticos.
+
;The necessary policies are synchronized with the target server: Verify that the source server policies are available on the target server. All relations are made through ID, so these values must also be identical.
  
;Los grupos están sincronizados con el servidor destino: Verifique que los grupos del servidor origen están definidos en el servidor destino. Las relaciones se realizan a través de ID, por lo que estos valores también deberán ser idénticos.
+
;The groups are synchronized with the destination server: Verify that the groups of the source server are defined in the destination server. All relations are made through ID, so these values must also be identical.
  
;Los plugins remotos están sincronizados con el servidor destino: Verifique que los plugins de servidor están definidos en el servidor destino. Las relaciones se realizan a través de ID, por lo que estos valores también deberán ser idénticos.
+
;The remote plugins are synchronized with the destination server: Verify that the server plugins are defined in the destination server. All relations are made through ID, so these values must also be identical.
  
;Los plugins de inventario están sincronizados con el servidor destino: Verifique que los plugins de inventario están definidos en el servidor destino. Las relaciones se realizan a través de ID, por lo que estos valores también deberán ser idénticos.
+
;Inventory plugins are synchronized with the target server: Verify that the inventory plugins are defined on the target server. All relations are made through ID, so these values must also be identical.
  
Una vez realizadas todas las comprobaciones daremos al botón “Next” para continuar con la migración, donde nos aparecerá una tabla con el status de la migración.
+
Once all the checks are done, click on the "Next" button to continue with the migration, where a table with the status of the migration will appear.
  
{{Tip|Para evitar bloquear la cola de trabajo, siempre se procesará el agente a transferir con menor prioridad, esto evita que el sistema quede bloqueado transfiriendo un agente con muchos datos, dando prioridad a la migración del agente sobre la migración de los datos.}}
+
{{Tip|In order to avoid blocking the work queue, the agent to be transferred will always be processed with lower priority, this avoids the system being blocked by transferring an agent with a lot of data, giving priority to the migration of the agent over the migration of the data.}}
  
{{Tip|Para optimizar el proceso el agente original se desactivará y se establecerá el modo de deshabilitado automático. Por defecto, esta configuración <b>eliminará</b> el agente original en 30 días.}}
+
{{Tip|In order to optimize the process the original agent will be deactivated and the automatic disable mode will be established. By default, this configuration will <b>eliminate </b> the original agent in 30 days.}}
  
{{Warning|Es posible que los módulos de predicción definidos pierdan funcionalidad una vez migrado el agente. Revise las definiciones tras la migración.}}
+
{{Warning|Defined prediction modules may lose functionality once the agent is migrated. Review definitions after migration.}}
  
===Autoprovisionamiento de agentes===
+
===Agent Autoprovisioning===
  
Cuando desplegamos Pandora en entornos grandes y complejos con muchos nodos de Pandora y entorno de metaconsola, encontramos la problemática de decidir cómo desplegar los agentes: ¿a qué servidor se les asigna? ¿cómo equilibrar la carga de trabajo?
+
When we deploy Pandora in big and complex environments with many Pandora nodes and Metaconsole environment, we find the problem of deciding how to deploy the agents: which server is assigned to them? how to balance the workload?
  
Para esto aparece el concepto de auto-aprovisionamiento de agentes, que permite asignar un agente a uno de los múltiples servidores de Pandora que tengamos en nuestra infraestructura.
+
For this, the concept of agents auto-provisioning appears, which allows assigning an agent to one of the multiple Pandora servers that we have in our infrastructure.
  
{{Warning|Esta funcionalidad requiere un servidor Metaconsola con ProvisioningServer iniciado para funcionar.}}
+
{{Warning|This feature requires a Metaconsole server with a Provisioning Server running in order to work.}}
{{Warning|Esta funcionalidad se utiliza para la gestionar la asignación <b>inicial</b> de los agentes a un servidor determinado. Cuando instale sus agentes por primera vez, seleccione como <i>server_ip</i> la dirección IP de la Metaconsola.}}
+
{{Warning|This functionality is used to manage the assignment <b>initial</b> of the agents to a given server. When you install your agents for the first time, select the IP address of the Metaconsole as <i>server_ip</i>.}}
  
Para poder utilizar esta funcionalidad deberemos configurar el servidor y la metaconsola.
+
To be able to use this feature we will have to configure the server and the Metaconsole.
  
====Configuración Servidor====
+
====Server Configuration====
  
Para que el sistema de auto aprovisionamiento funcione deberemos habilitar el ProvisioningServer en /etc/pandora/pandora_server.conf:
+
For the autoprovisioning system to work we must enable the ProvisioningServer at /etc/pandora/pandora_server.conf:
  
 
  # Enables auto provisioning service
 
  # Enables auto provisioning service
 
  provisioningserver 1
 
  provisioningserver 1
  
{{Tip|Verifique que la dirección IP de sus servidores destino (Dataserver) está configurada en cada nodo, puede acceder a la siguiente pantalla a través de <i>Servidores > Administrar servidores</i>}}
+
{{Tip|Verify that the IP address of your destination servers (Dataserver) is configured in each node. You can access the following screen through <i>Servers > Manage servers </i>}}
  
 
<center>
 
<center>
Line 278: Line 286:
 
</center>
 
</center>
  
====Configuración Consola====
+
====Console Configuration====
  
En este apartado podremos escoger entre los tres tipos distintos de autoprovisionamiento, activando el que queremos mediante un interruptor:
+
In this section we can choose between three different types of autoprovisioning, activating the one we want by means of a switch:
  
 
<center>
 
<center>
Line 286: Line 294:
 
</center>
 
</center>
  
;Round Robin: Utiliza el método de planificación Round-robin para distribuir, de manera equitativa y en un orden racional, todos los nuevos agentes software de Pandora que lleguen a la Metaconsola. La distribución de los agentes se hará de forma circular, asignando el servidor correspondiente a cada nuevo agente.
+
;Round Robin: It uses the Round-robin planning method to distribute, in an equitable way and in a rational order, all the new Pandora software agents that reach the Metaconsole. The distribution of the agents will be done in a circular way, assigning the corresponding server to each new agent.
  
;Less Loaded: Se asignarán los nuevos agentes a aquellos servidores con menos carga dinámicamente.
+
;Less Loaded: The new agents will be dynamically assigned to those servers with less load.
  
;Custom: En la clasificación personalizada, podremos definir nuestras propias reglas de clasificación, en base a ciertos parámetros recuperados de la información reportada por el agente (nombre del agente y su dirección IP.).
+
;Custom: In the customized classification, we will be able to define our own classification rules, based on certain parameters retrieved from the information reported by the agent (name of the agent and its IP address).
  
Si escogemos el caso de “Custom” hagamos click en el botón de “Create a custom entry” donde nos aparecerá el siguiente formulario:
+
If we choose the Custom option, we will click on the "Create a custom entry" button where the following form will appear:
  
 
<center>
 
<center>
Line 298: Line 306:
 
</center>
 
</center>
  
Donde en configuration tendremos que poner el contenido que se agregará al archivo de configuración, es la personalización que utilizaremos para la clasificación del agente, por ejemplo:
+
In the configuration section we will have to put the content that will be added to the configuration file. It is a way of customization that will be used to classify the agents; an example would be:
  
 
  # Text contained here will be validated and inserted in the agent configuration
 
  # Text contained here will be validated and inserted in the agent configuration
 
  server_ip 192.168.80.164
 
  server_ip 192.168.80.164
  
Una vez creado deberemos introducir las reglas que queramos que los agentes cumplan dándole al botón “add”.
+
Once created we will have to introduce the rules that we want the agents to comply with by hitting the "add" button.
  
 
<center>
 
<center>
Line 309: Line 317:
 
</center>
 
</center>
  
Podremos especificar las condiciones de coincidencia en forma de reglas usando los siguientes campos:
+
We will be able to specify the matching conditions in the form of rules using the following fields:
* alias del agente
+
* agent alias  
* dirección del agente
+
* agent address
  
Podremos especificar las operaciones usando los siguientes campos:
+
We will be able to specify the operations using the following fields:
 
* OR
 
* OR
 
* AND
 
* AND
  
===Gestión de Grupos===
+
===Autoconfiguration===
 +
In this section you can edit the autoconfigurations of the agents in a centralized way from the Metaconsole. In order to make this edition, we must have activated the "Centralized management".
 +
 
 +
For more information, visit this [[Pandora:Documentation_en:Configuration_Agents#Automatic_agent_configuration|link]].
 +
 
 +
 
 +
 
 +
===Group Management===
  
En esta sección podemos gestionar, borrar y crear nuevos grupos en la metaconsola.
+
In this section we can manage, delete and create new groups in the Metaconsole.
  
 
<center>
 
<center>
Line 325: Line 340:
 
</center>
 
</center>
  
====Creación de un grupo====
+
====Create a Group====
  
Para crear un nuevo grupo hagamos click en el botón “créate group” y nos aparecerá el siguiente formulario:
+
To create a new group, click on the "create group" button and the following form will appear:
  
 
<center>
 
<center>
Line 333: Line 348:
 
</center>
 
</center>
  
Los parámetros que requieren explicación son:
+
The parameters that require explanation are:
  
* '''Parent''': combo donde se puede definir otro grupo como padre del grupo que se está creando.
+
* '''Parent''': combo where another group can be defined as the parent of the group being created.
* '''Propagate ACL''': Permite propagar las ACL a los subgrupos hijos.
+
* '''Propagate ACL''': allows ACLs to be propagated to child subgroups..
* '''Custom ID''':los grupos tienen un ID en la Base de Datos, en este campo es posible poner otro ID personalizado que pueda ser usado desde un programa externo para realizar una integración.
+
* '''Custom ID''':the 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.
  
====Modifcar/Borrar un grupo====
+
====Modify/Delete a group====
  
En la lista de grupos se disponen de opciones para:
+
In the list of groups there are options for:
  
* Editar el grupo
+
*Editing the group
* Borrar el grupo de la Metaconsola
+
*Deleting the Metaconsole group
  
 
<center>
 
<center>
Line 350: Line 365:
 
</center>
 
</center>
  
==Gestión de módulos==
+
===Tree group===
 +
In this section we can perform exactly the same actions as in the previous section, changing the display mode:
 +
 
 +
<center>
 +
[[File:tree_group_meta.png]]
 +
</center>
 +
 
 +
===Collections===
 +
 
 +
From Pandora FMS OUM729 you can centralize the management of collections from the Metaconsole.
 +
 
 +
<center>
 +
[[File:mc_col_menu.png]]
 +
</center>
 +
 
 +
The first time you access collection management, with <b> centralized management enabled </b>, an internal process of synchronization of the collections from the nodes to the Metaconsole will be performed:
 +
 
 +
<center>
 +
[[File:mc_col_message.png]]
 +
</center>
 +
 
 +
 
 +
From this moment on, you will have the collections in the Metaconsole. To avoid conflicts, you must manually copy the collection directories from the nodes to the Metaconsole:
 +
 
 +
Source location (node):
 +
 
 +
 
 +
/var/www/html/pandora_console/attachment/collection/
 +
 
 +
 
 +
Destination location (Metaconsole):
 +
 
 +
/var/www/html/pandora_console/attachment/collection/
 +
 
 +
 
 +
<b>Note:</b> Remember to assign the correct permissions to the transferred files:
 +
 
 +
chmod apache. -R  /var/www/html/pandora_console/attachment/collection/*
 +
 
 +
 
 +
Once the files are transferred, you can recreate the collection to force synchronization to nodes.
 +
 
 +
For more information about the collections, please visit this [[Pandora:Documentation_en:Policy#File_Collections|link]].
  
En esta sección se pueden realizar las siguientes acciones:
+
==Module Management==
* Gestión de grupos de componentes
 
* Gestión de componentes locales
 
* Gestión de componentes de red
 
* Gestión de plugins
 
  
Antes de empezar vamos a explicar que es un componente: es un “modulo genérico” que se puede aplicar repetidamente sobre un agente, siendo una especia de “copia maestra” de un módulo. Esto es muy útil para poder monitorizar nuevos agentes con los componentes guardados en la base de datos.
+
The following actions can be performed in this section:
 +
* Component Group Management
 +
* Local component management
 +
* Network Component Management
 +
* Plugin management
  
Por ejemplo, tenemos 12 instancias donde queremos crear el mismo tipo de módulos en cada una: queremos crear 10 módulos locales, 5 módulos de red y 3 plugins personalizados. Pues gracias a la gestión en la metaconsola podremos crear dichos componentes, cada uno en su sección, y posteriormente sincronizarlos para tenerlos en las diferentes instancias sin tener que crear manualmente uno a uno los distintos módulos y plugins a utilizar.
+
Before we start, let's explain what a component is: it is a "generic module" that can be applied repeatedly on an agent, being a kind of "master copy" of a module. This is very useful to monitor new agents with the components stored in the database.
  
===Gestión de grupos de componentes===
+
For example, we have 12 instances where we want to create the same type of modules in each: we want to create 10 local modules, 5 network modules and 3 custom plugins. Thanks to the management in the Metaconsole we will be able to create these components, each one in its section, and then synchronize them to have them in the different instances without having to manually create them.
  
En esta sección podremos borrar y crear nuevos grupos de componentes.
+
===Component Group Management===
 +
 
 +
In this section we can delete and create new groups of components.
 
<center>
 
<center>
 
[[File:gestionar_grupocompo.png]]
 
[[File:gestionar_grupocompo.png]]
Line 375: Line 434:
 
</center>
 
</center>
  
====Creación de grupo====
+
====Group creation====
  
Para poder crear un nuevo grupo hagamos click en el botón “Create”
+
To create a new group click on the "Create" button.
 
<center>
 
<center>
 
[[File:gestionar_crearcompogrupo.png]]
 
[[File:gestionar_crearcompogrupo.png]]
 
</center>
 
</center>
  
====Borrar grupo====
+
====Group deletion====
  
 
<center>
 
<center>
Line 388: Line 447:
 
</center>
 
</center>
  
===Gestión de componentes locales===
+
===Local component management===
  
En esta sección podremos borrar, duplicar y crear nuevos componentes locales. Un componente local es la definición de un módulo definido en la configuración de los agentes software, definido como "trozos" de texto que se pueden cortar y pegar en la configuración de los agentes.
+
In this section we can delete, duplicate and create new local components. A local component is the elaboration of a module defined in the configuration of software agents, structured as "pieces" of text that can be cut and pasted in the configuration of agents.
  
 
<center>
 
<center>
Line 396: Line 455:
 
</center>
 
</center>
  
====Creación componente local====
+
====Local component creation====
  
Para poder crear un componente local hagamos click en el botón “Create” done nos aparecerá el siguiente formulario:
+
In order to create a local component click on the "Create" button where the following form will appear:
  
 
<center>
 
<center>
Line 410: Line 469:
 
</center>
 
</center>
  
Para ver en detalle más información sobre los parámetros de creación de un nuevo componente local podéis visitar el siguiente [[Pandora:Documentation_es:Plantillas_y_Componentes#Crear_componentes_de_red_nuevos | Crear usuario]]) podrán utilizar esta plantilla
+
In order to see in detail more information about the parameters for the creation of a new local component you can visit  [[Pandora:Documentation_en:Templates_and_components#Creating_new_Network_Components| Create user]].
  
====Duplicar/Borrar un componente local====
+
====Duplicate/Delete a local component====
  
En la lista de componentes locales se disponen de opciones para:
+
In the list of local components you have options for:
* Duplicar un componente local
+
* Duplicating a local component
* Borrar un componente local de la Metaconsola
+
* Deleting a local component of the Meta Console
 
<center>
 
<center>
 
[[File:meta_net_component_op_col.png]]
 
[[File:meta_net_component_op_col.png]]
 
</center>
 
</center>
  
===Gestión de componentes de red===
+
===Network Component Management===
  
En esta sección podremos borrar, duplicar y crear nuevos componentes de red. Un componente de red agrupa a todos los módulos de tipo remoto (wmi, tcp, snmp, icmp, plugin, web, etc).
+
In this section we can delete, duplicate and create new network components. A network component groups all remote modules (wmi, tcp, snmp, icmp, plugin, web, etc).
  
 
<center>
 
<center>
Line 429: Line 488:
 
</center>
 
</center>
  
====Creación componente de red====
+
====Creating Network Component====
  
Puede crear tres tipos de componentes de red:
+
There are three types of network components that can be created:
  
* Network (de red).
+
* Network
* Plugin (de complemento del servidor).
+
* Plugin  
* WMI.
+
* WMI
 +
 
 +
To create a new network component in the drop-down menu select a network component from the three possible (WMI, Network or Plugin): and click on the button ''Create''. Next, we will see a screen to create a network component.
  
Para crear un nuevo componente de red en el menú desplegable seleccione un componente de red de los tres posibles (WMI, Red o Plugin): y hagamos click en el botón ''Create''. A continuación vemos el caso de una pantalla de creación de componente de red.
 
  
 
<center>
 
<center>
Line 449: Line 509:
 
</center>
 
</center>
  
Para ver en detalle más información sobre los parámetros de creación de un nuevo componente de red podéis visitar pincha en el enlace para consultarlo.
+
To see in detail more information about the parameters of creation of a new network component you can visit the section [[Pandora:Documentation_en:Templates_and_components#Creating_new_Network_Components | Network component]].
[[Pandora:Documentation_es:Plantillas_y_Componentes#Crear_componentes_de_red_nuevos | Componente de red]]
 
  
====Duplicar/Borrar un componente de red====
 
  
En la lista de componentes de red se disponen de opciones para:
+
====Duplicating/Deleting a Network Component====
* Duplicar un componente de red
+
 
* Borrar un componente de red de la Metaconsola
+
In the list of network components you have options for:
 +
* Duplicating a network component
 +
* Deleting a network component from the Metaconsole
 +
 
  
 
<center>
 
<center>
Line 462: Line 523:
 
</center>
 
</center>
  
===Gestión de plugins===
+
===Plugin Management===
  
En esta sección podremos borrar, modificar y crear nuevos plugins que usarán los componentes de red de tipo plugin.
+
In this section we will be able to delete, modify and create new plugins that will use plugin type network components.
  
 
<center>
 
<center>
Line 470: Line 531:
 
</center>
 
</center>
  
====Creación de plugin====
+
====Creating a Plugin====
 +
 
 +
To create a plugin click on the "Add" button and the following form will appear:
  
Para crear un plugin hagamos click en el botón “Add” y aparecerá el siguiente formulario:
 
 
<center>
 
<center>
 
[[File:gestionar_compoplugincrear.png]]
 
[[File:gestionar_compoplugincrear.png]]
Line 480: Line 542:
 
</center>
 
</center>
  
Los parámetros que requieren explicación son:
+
The parameters that require explanation are:
  
* '''Plug-in command''': Donde pondremos la PATH donde se encuentra el plugin
+
* '''Plug-in command''': Where we will put the PATH to where the plugin is located
* '''Plug-in parameters''': Donde pondremos los parámetros que debemos escribir para que el plugin funcione correctamente.
+
* '''Plug-in parameters''': Where we will put the parameters that we must write so that the plugin works correctly.
  
 
<center>
 
<center>
Line 489: Line 551:
 
</center>
 
</center>
  
====Modificar/Borrar un plugin====
+
====Modifying/Deleting a Plugin====
  
En la lista de plugin se disponen de opciones para:
+
In the plugin list there are options for:
* Modificar un plugin
+
* Modifying a plugin
* Borrar un plugin de la Metaconsola
+
* Deleting a plugin from the Metaconsole
  
Ciertos plugins tienen un candado delante de la opción de modificar, porque estos plugins no pueden ser modificados ni borrados.
+
Certain plugins have a padlock in front of the Modify option, because these plugins cannot be modified or deleted.
  
 
<center>
 
<center>
Line 501: Line 563:
 
</center>
 
</center>
  
==Gestión de Alertas==
+
==Alert Management==
 +
 
 +
The following actions can be performed in this section:
 +
* Management of commands
 +
* Management of shares
 +
* Management of templates
  
En esta sección se pueden realizar las siguientes acciones:
 
* Gestión de comandos
 
* Gestión de acciones
 
* Gestión de templates
 
 
<center>
 
<center>
 
[[File:gestionar_alertasgeneral.png]]
 
[[File:gestionar_alertasgeneral.png]]
 
</center>
 
</center>
  
Por ejemplo, en nuestra metaconsola tenemos 5 instancias con distintos clientes en el cual en todas ellas necesitamos medir en cada agente la temperatura de su CPU. Con esta información, necesitamos que una alerta salte cuando la CPU supere cierta temperatura, y lo que queremos es realizar un comando que haga que la CPU elimine ciertos servicios para no ser utilizada de una manera excesiva provocándole la subida de temperatura. Crearíamos una alerta que realice dicho comando y luego la sincronizaríamos con todas nuestras instancias para no tener que realizarla manualmente una a una.
+
For example, in our meta console we have 5 instances with different clients and in all of them we need to measure in each agent the temperature of its CPU. With this information, we need an alert to be triggered when the CPU exceeds a certain temperature, and what we want is to create a command that will make the CPU eliminate certain services so as not to be used in an excessive way, causing it to rise in temperature. We would generate an alert that carries out this command and then synchronize it with all our instances so that we don't have to do it manually one by one.
  
En esta sección solo se hablará de la gestión de templates, en particular las diferencias con la gestión de alertas de las instancias. Para conocer más sobre su funcionamiento y configuración se puede consultar el apartado del manual de Pandora FMS [[Pandora:Documentation_es:Alertas | Sistema de alertas]].
+
In this section we will only talk about the management of templates, in particular, the differences with the management of alerts of the instances. To know more about its operation and configuration you can consult the [[Pandora:Documentation_en:Alerts | Alert System]] section inside the Pandora FMS manual.
  
===Gestión de templates===
+
===Template Management===
  
La única diferencia con la gestión de alertas de las instancias, está en la creación de una nueva template. A la hora de crear una template nos aparece una opción llamada “Wizard level”
+
The only difference with regard to the management of alerts of the instances, is in the creation of a new template. When creating a template we have an option called "Wizard level".
  
 
<center>
 
<center>
Line 523: Line 586:
 
</center>
 
</center>
  
Este campo definirá qué usuarios podrán utilizar esta plantilla para crear alertas desde el Wizard.
+
This field will define which users will be able to use this template to create alerts from the Wizard.
 +
 
 +
* '''No Wizard''': This template will not be available in the Wizard.
 +
* '''Basic''': Any user with access to the Wizard will be able to use this template to create alerts.
 +
* '''Advanced''': Only users with advanced level of access to Metaconsole will be bale to use this template (see section [[Pandora:Metaconsole:Documentation_en:Synchronization_and_propagation#Create_a_new_user| Create user]]).
  
* '''No Wizard''': Esta plantilla no estará disponible en el Wizard
+
==Event Alert Management==
* '''Básico''': Cualquier usuario con acceso al Wizard podrá utilizar esta plantilla para crear alertas
 
* '''Avanzado''': Solamente los usuarios con nivel avanzado de acceso a metaconsola (Ver [[Pandora:Metaconsole:Documentation_es:Administration#Crear_un_usuario | Crear usuario]]) podrán utilizar esta plantilla
 
  
==Gestión de Alerta de Eventos==
+
The following actions can be performed in this section:
 +
* Create event alert
 +
* Modify/Delete/Disable/Silence event alerts
  
En esta sección se pueden realizar las siguientes acciones:
 
* Crear alerta de evento
 
* Modificar/Borrar/Deshabilitar/Silenciar alertas de eventos
 
 
<center>
 
<center>
 
[[File:gestionar_alertaseventos.png]]
 
[[File:gestionar_alertaseventos.png]]
 
</center>
 
</center>
  
Por ejemplo, tenemos 4 instancias donde tenemos en un agente la monitorización del servidor apache de cada una de las páginas web situadas en las distintas instancias. Crearemos una alerta de evento que nos avise cuando dicha monitorización se caiga para avisar al administrador que se debe de levantar el servicio Apache de inmediato, y así no habría que crearla manualmente una a una en los agentes de las instancias.
+
For example, we have 4 instances where we have in one of the agents the monitoring of the apache server of each of the web pages located in the different instances. We will create an event alert that will warn us when this monitoring goes down to warn the administrator that the Apache service should be immediately fixed, so that it wouldn't be necessary to create one by one manually in the instances agents.
  
Para conocer más sobre su funcionamiento y configuración se puede consultar el apartado [[Pandora:Documentation_es:Eventos#Alertas_de_eventos._Correlaci.C3.B3n_de_eventos | Sistema de Alertas]] del manual de Pandora FMS.
+
To find out more about its operation and configuration, please consult the section [[Pandora:Documentation_es:Eventos#Alertas_de_eventos._Correlaci.C3.B3n_de_eventos | Alert System]] of the Pandora FMS manual.
  
==Gestión de componentes==
+
==Component Management ==
  
En esta sección se pueden realizar las siguientes acciones:
+
The following actions can be performed in this section:
* Gestión de tags
+
* Tag Management
* Gestión de grupo de módulos
+
* Module group management
* Gestión de OS
+
* OS Management
 
<center>
 
<center>
 
[[File:gestionar_componentes.png]]
 
[[File:gestionar_componentes.png]]
 
</center>
 
</center>
  
===Gestión de tags===
+
===Manage tags===
  
En esta sección podremos borrar, modificar y crear nuevos tags.
+
In this section we will be able to delete, modify, and create new tags.
  
====Creación de tags====
+
====Creating Tags====
  
Para crear un nuevo tag hagamos click en el botón “créate tag” y a continuación nos saldrá el siguiente formulario que tendremos que rellenar:
+
To create a new tag we click on the button “create tag” and then we will get the following form to fill in:
 
<center>
 
<center>
 
[[File:gestionar_tagscrear.png]]
 
[[File:gestionar_tagscrear.png]]
 
</center>
 
</center>
  
====Modificar/Borrar tags====
+
====Modify/Delete tags====
  
En la lista de tags se disponen de opciones para:
+
In the list of tags we have options to:
* Editar el tag
+
* Edit the tag
* Borrar el tag de la Metaconsola
+
* Delete the tag from the Metaconsole
 
<center>
 
<center>
 
[[File:Dac2.1.png]]
 
[[File:Dac2.1.png]]
 
</center>
 
</center>
  
===Gestión de grupos de módulo===
+
===Module Groups Management===
  
En esta sección podemos borrar y crear nuevos grupos de módulos.
+
In this section we can delete and create new groups of modules.
 
<center>
 
<center>
 
[[File:gestionar_gruposmodulos.png]]
 
[[File:gestionar_gruposmodulos.png]]
 
</center>
 
</center>
  
====Creación de un grupo====
+
====Group Creation====
  
Para poder crear un nuevo grupo de módulo hagamos click en el botón “Create module group”:
+
To be able to create a new module group we will click on the button “Create module group”:
 
<center>
 
<center>
 
[[File:gestionar_gruposmoduloscrear.png]]
 
[[File:gestionar_gruposmoduloscrear.png]]
 
</center>
 
</center>
  
====Borrar grupo módulo====
+
====Deletin a Module Group====
 
<center>
 
<center>
 
[[File:gestionar_borrarcompogrupo.png]]
 
[[File:gestionar_borrarcompogrupo.png]]
 
</center>
 
</center>
  
===Gestión OS===
+
===OS Management===
  
En esta sección podemos borrar y crear nuevos OS del sistema.
+
In this section we can delete and create new OS.
  
 
<center>
 
<center>
Line 602: Line 666:
 
</center>
 
</center>
  
====Creación OS====
+
====OS Creation====
Para crear un nuevo OS hagamos click en el botón “créate OS” y nos aparecerá un formulario que deberemos rellenar:
+
To create a new OS we click on the button “create OS” and a form will appear for us to fill in:
  
 
<center>
 
<center>
Line 609: Line 673:
 
</center>
 
</center>
  
====Borrar OS====
+
====OS Deletion====
 
<center>
 
<center>
 
[[File:gestionar_borrarcompogrupo.png]]
 
[[File:gestionar_borrarcompogrupo.png]]
 
</center>
 
</center>
  
==Gestión de políticas==
+
==Policy Management==
  
Desde esta sección se pueden crear, modificar y borrar políticas.
+
From this section we can create, modify, and delete policies.
 
<center>
 
<center>
 
[[File:Meta_menu.png|800px]]
 
[[File:Meta_menu.png|800px]]
 
</center>
 
</center>
  
Por ejemplo, tenemos 7 instancias en la cuales 2 de ellas se van a monitorizar de la misma manera, con el mismo nombre de agentes y módulos. Crearíamos una política que nos realice la creación de módulo en los agentes de manera automática, la cual posteriormente sincronizaremos con las distintas instancias sin tener que crearla de una en una.
+
For example, we have 7 instances in which 2 of them are going to be monitored in the same way, with the same name of agents and modules. We would create a policy that creates the modules in the agents automatically, which we will later synchronize with the different instances without having to create it one by one.
  
===Creación políticas===
+
===Policy Creation===
  
Se pueden crear nuevas políticas hagamos click en el botón "Create" donde se muestra el siguiente formulario:
+
New policies can be created by clicking on the "Create" button, where the following form is displayed:
 
<center>
 
<center>
 
[[File:Meta_crear.png|800px]]
 
[[File:Meta_crear.png|800px]]
 
</center>
 
</center>
  
Para una mejor comprensión de como configurar las políticas, dirigase a la [[Pandora:Documentation_es:Politicas | gestión de políticas.]]
+
For a better understanding of how to configure policies, please refer to the section [[Pandora:Documentation_en:Policy | Policy Management.]]
  
===Modificar/Borrar políticas===
+
===Modify/Delete policies===
  
En la lista de políticas se disponen de opciones para modificar una política y eliminarla.
+
In the list of policies we have options to modify a policy and delete it.
Si una política tiene agentes, el botón de eliminar estará deshabilitado y aparecerá junto a él un botón para eliminar todos sus agentes. Este botón introducirá en la cola el eliminado de los agentes, y en cuanto se procese, volverá a estar activo el botón de eliminado de la política.  
+
If a policy has agents, the "Delete" button will be disabled and a button to delete all its agents will appear next to it. This button will introduce the agent deletion into the queue, and as soon as it is processed, the policy deletion button will be active again.  
 
<center>
 
<center>
 
[[File:Meta_borrar.png]]
 
[[File:Meta_borrar.png]]
 
</center>
 
</center>
  
==Gestión de catergorías==
+
==Category Management ==
En esta sección podemos modificar, borrar y crear nuevas categorías.
+
In this section we can modify, delete and create new categories.
  
 
<center>
 
<center>
Line 647: Line 711:
 
</center>
 
</center>
  
===Creación catergorías===
+
===Creating Categories===
  
Para crear una nueva categoría hagamos click en el botón “créate category”:
+
To create a new category click on the button “create category”:
 
<center>
 
<center>
 
[[File:gestionar categoriascrear.png]]
 
[[File:gestionar categoriascrear.png]]
 
</center>
 
</center>
  
===Modificar/Borrar categorías===
+
===Modify/Delete policies===
  
En la lista de categorías se disponen de opciones para:
+
In the list of categories we have options to:
* Editar la categoría
+
* Edit the category
* Borrar la categoría de la Metaconsola
+
* Delete the category from the Metaconsole
 
<center>
 
<center>
 
[[File:Dac2.1.png]]
 
[[File:Dac2.1.png]]
 
</center>
 
</center>
  
==Gestión de servidores==
+
==Server Management==
En esta sección podremos borrar los servidores que tengamos instalados en la metaconsola. Para poder realizar todas las funcionalidades deberían estar los servidores de Autoprovisionamiento y de Migración activados.  
+
In this section we will be able to delete the servers installed in the Metaconsole. In order to be able to use all the features, the Auto-provisioning and Migration servers should be activated.  
 
<center>
 
<center>
 
[[File:gestionar_server.png]]
 
[[File:gestionar_server.png]]
 
</center>
 
</center>
  
[[Pandora:Documentation|Volver a Índice de Documentación Pandora FMS]]
+
[[Pandora:Documentation|Back to Index of Documentation of Pandora FMS]]
  
 
[[Category: Pandora FMS]]
 
[[Category: Pandora FMS]]

Latest revision as of 09:40, 27 September 2019

Template wip.png

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

 


Contents

1 Synchronization tools

The Metaconsole has tools for the synchronization of elements, which are fundamental for the correct management of the Instances. The synchronization is based on passing all the information created in the metaconsole to the different Instances to manage all possible information of each of them from the Metaconsole.

For example, if we have 20 different instances(nodes) in our company, and we want the same user to have the same access permissions in those 20, we can create a user with the desired profiles and synchronize that user to have it in the 20 instances(nodes) and thus not have to create it individually in each instance.

Another example, we have to monitor different clients that are distributed throughout our instances, so that some clients are also repeated in different instances. We will be able to create the different groups to which the agents of the different instances will belong, and then synchronize each corresponding group with its instance.

Next, we are going to see in detail the different synchronizations that the Metaconsole allows us to make.

1.1 User Synchronization

This option allows the user to synchronize the users of the Metaconsole and their profiles in the instances.

Within this synchronization we can find two different options:

  • Copy the configured profiles to the user

Sync usuarioscopia.png

  • Give new profiles to the created user

Sync usuariosnuevos.png

In both cases we have the option to create the groups associated to the profiles in case they do not exist in the instance(node).

Before using this synchronization, it is recommended to take into account the users that are going to create new ones in the instances, due to possible conflicts with the user ID. It is recommended not to have users created in the instances and to create them all from the meta console in order to have the same users both in there as in the instances.

Info.png

In both cases, profiles that do not exist in the instance will be created.

 


Template warning.png

When in doubt about which option is best to use, user profiles must be copied.

 


1.2 Group Synchronization

This option allows the user to synchronize the Metaconsole groups with the instances.

Sync grupos.png

It is recommended not to have groups created in the instances and to create them all from the meta console in order to have the same groups both in there and in the instances.

Template warning.png

Once the groups have been synchronized, their names should not be modified either in the meta console or in the node. If it is done, it will be necessary to modify them in both places so that it does not give problems since the synchronization is based on the ID, but some operations use the name. The synchronization in the current version synchronizes the name the first time, but if there are later changes of names in the groups they will not be synchronized.

 


1.3 Alert Synchronization

This option allows the user to synchronize the Metaconsole alerts with the instances.

Sync alertas.png

It is recommended not to have alerts created in the instances and to create them all from the console in order to have the same alerts both in there and in the instances.

1.4 Component Synchronization

This option allows the user to synchronize the components of the Metaconsole with the instances.

Sync componentes.png

It is recommended not to have components created in the instances and to create them all from the Metaconsole in order to have the same components both in there and in the instances.

1.5 Tag Synchronization

This option allows the user to synchronize the tags of the Metaconsole with the instances.

Sync tagsnew.png

It is recommended not to have tags created in the instances and to create them all from the Metaconsole in order to have the same tags both in there and in the instances.

1.6 OS Synchronization=

This option allows the user to synchronize the OS of the Metaconsole with the instances.

Sync OS.png

It is recommended not to have OS created in the instances and to create them all from the Metaconsole in order to have the same OS both in there and in the instances.

1.7 Module Groups Synchronization

This option allows the user to synchronize the module groups operating in the Metaconsole with the instances.

Sync modulegroups.png

It is recommended not to have the groups of modules created in the instances and to create them all from the Metaconsole in order to have the same groups of modules both in there and in the instances.

2 Propagation tools

The MetaConsole has tools for the propagation of elements. Unlike synchronization, it is not a fundamental tool for the optimal functioning of the Metaconsole, it only facilitates the availability of data in the Instances, something that is necessary if, for example, we use policies that are applied in different instances (or nodes).

Info.png

It is recommended to synchronize the instances with the meta console after the creation of the different elements in the propagation tool.

 


Next, we are going to see in detail the different propagations or data management that allows us to make the meta console.

2.1 User Management

The following actions can be performed in this section:

  • User management
  • Profile management
  • Edit my user

For example, we have 10 instances inside our meta console, where we want a user with special permissions to operate inside 3 of them. First, we would go to profile management where we would create a special profile with the permissions we want. Then we create the user we want to manage the three instances, assigning the permission we have created to it. Finally, we will synchronize this user and profiles with the instances to have it in all three. After a while the user has become obsolete, but instead of deleting the user we deactivate it in case we want to use it again in the future, we go to user management and use the bulb icon to deactivate it until further notice.

2.1.1 User Management

In this section we can see the list of users already created, modify their configuration, delete them, deactivate them or create new users.

Gestion usuarios.png

2.1.1.1 Create a new user

To add a user click on the "Create User" button, where we will see the following form which must be filled:

Gestion creacionusuarios.png

Gestion creacionusuarios2.2.png

The parameters that require explanation are:

  • Interactive charts: It allows the user to choose if they prefer to see the interactive graphics, or on the contrary, to use the general configuration of the Metaconsole.
  • Metaconsole access: It sets the user permissions to access the console. These permissions can be:
    • Basic: With this access the user will be able to use in the Wizard only the components whose Wizard level is Basic, as long as the user has ACL permissions on the group they belong to.
    • Advanced: With this access the user will be able to use any of the components in the Wizard regardless of their Wizard level, as long as the user has ACL permissions on the group they belong to.
  • Search custom field view: Seleccionamos el filtro por defecto para la vista de "Campos personalizados"
  • Not Login: If this option os selected, the user will be able to access the API.
  • Enable agents management: This option is used to enable the agent management in the Wizard. If it is deactivated, only the Wizards of modules and alerts will be available.
  • Enable node access: This option is used to enable access to the instances. If it is activated, it will be possible to access the consoles of the instances through the name of agents and modules in many places; for example, from the network map or the events view.

2.1.1.2 Modify/Deactivate/Delete a user

In the user list the following options are available:

  • Activate/Deactivate the user
  • Edit the user
  • Delete the user form the Metaconsole
  • Delete the user form the Metaconsole and all Instances

Gestion modificacionusuarios.png

A user's editing form is the same as the creation form, but including the profile editor.

Gestion modificacionusuarios2.png

In the profile editor the user can be assigned profiles in certain groups besides limiting those privileges to the selected Tags. If Tags are not selected, the user will have access to all modules, whether they have associated Tags or not.

2.1.2 Profile Management

In this section we can see the list of profiles already created, modify their configuration, delete them or create new profiles.

Gestion perfiles.png

There are a series of ACL flags that will give access to the different Pandora FMS functionalities. To know which function enables each ACL flag of the profiles, visit section Perfiles en Pandora FMS in the user manual.

2.1.2.1 Create a new profile

To add a profile click on the "Create" button to see the following form, where we must fill in those permissions that we want to give with the new profile:

Gestion creacionperfil.png

Gestion creacionperfil2.png

Info.png

Some of these bits don't make sense in the Metaconsole. However, we may want to use the Metaconsole to synchronize profiles to Instances, where they could be useful.

 


2.1.2.2 Modify/Delete a profile

In the list of profiles you have options to:

  • Edit the profile
  • Delete a profile from Metaconsole

Dac2.1.png

2.1.3 Edit my user

In this section we can configure the user who is authenticated in the Metaconsole. The profiles assigned to the user will be merely informative. If the authenticated user is not an administrator, this will be the only section you can see.

Gestion editmyuser.png

Template wip.png

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

 


2.2 Agent management

The following actions can be performed in this section:

  • Migration of agents between instances
  • Self-provisioning of agents
  • Group management

For example, we are planning to manage 15 instances in the metaconsole, and we want the distribution of the agents to be organized according to the load of each instance, creating the agents so that they are always generated in the instance with the lowest load. To do this, we will go to auto-provisioning and activate the option indicated for it. Once done, if for example, we realize that certain agents should go together in the same instance, we will go to the migration of agents between instances, where we will choose which agents move to which other instances so that we don't have to delete and create the agents manually.

2.2.1 Agent Migration

Template warning.png

This feature requires a running Metaconsole server to work.

 


In this section we can migrate agents between the instances connected to our Metaconsole.

Gestion migagentes.png

In order for the historical data of the agents to be transferred, the "Discard history data" checkbox must be activated. Once we have everything selected and we press the "move" button, it will start to perform the following checks to be able to perform the migration.

The agents do not exist in the destination server
There must not exist any agent to migrate with the same agent name in the target server.


The necessary collections are synchronized with the destination server
To prevent the agent from attempting to download non-existent collections once migrated, verify that the collections exist on both servers (source and destination).
The necessary alert definitions are synchronized with the target server
Verify that the templates, actions and commands defined on the source server are also defined on the target server. The relations are made through ID, so these values must also be identical.
The configuration files of the software agents associated to the agents do not exist in the target server
There must not be configuration files with the same name as those associated to the agents that we are going to migrate in the target server. If so, we must remove them from the destination server.
Both servers have the same version
Verify that Pandora FMS versions are identical in both servers.
The address of the destination server is configured
Verify that the IP address of your destination server (Dataserver) is configured, you can access the following screen through Servers > Manage servers of the instance to which we want to move the agents:

Configurar serverIP.png

Configurar serverIP2.png

The necessary policies are synchronized with the target server
Verify that the source server policies are available on the target server. All relations are made through ID, so these values must also be identical.
The groups are synchronized with the destination server
Verify that the groups of the source server are defined in the destination server. All relations are made through ID, so these values must also be identical.
The remote plugins are synchronized with the destination server
Verify that the server plugins are defined in the destination server. All relations are made through ID, so these values must also be identical.
Inventory plugins are synchronized with the target server
Verify that the inventory plugins are defined on the target server. All relations are made through ID, so these values must also be identical.

Once all the checks are done, click on the "Next" button to continue with the migration, where a table with the status of the migration will appear.

Info.png

In order to avoid blocking the work queue, the agent to be transferred will always be processed with lower priority, this avoids the system being blocked by transferring an agent with a lot of data, giving priority to the migration of the agent over the migration of the data.

 


Info.png

In order to optimize the process the original agent will be deactivated and the automatic disable mode will be established. By default, this configuration will eliminate the original agent in 30 days.

 


Template warning.png

Defined prediction modules may lose functionality once the agent is migrated. Review definitions after migration.

 


2.2.2 Agent Autoprovisioning

When we deploy Pandora in big and complex environments with many Pandora nodes and Metaconsole environment, we find the problem of deciding how to deploy the agents: which server is assigned to them? how to balance the workload?

For this, the concept of agents auto-provisioning appears, which allows assigning an agent to one of the multiple Pandora servers that we have in our infrastructure.

Template warning.png

This feature requires a Metaconsole server with a Provisioning Server running in order to work.

 


Template warning.png

This functionality is used to manage the assignment initial of the agents to a given server. When you install your agents for the first time, select the IP address of the Metaconsole as server_ip.

 


To be able to use this feature we will have to configure the server and the Metaconsole.

2.2.2.1 Server Configuration

For the autoprovisioning system to work we must enable the ProvisioningServer at /etc/pandora/pandora_server.conf:

# Enables auto provisioning service
provisioningserver 1

Info.png

Verify that the IP address of your destination servers (Dataserver) is configured in each node. You can access the following screen through Servers > Manage servers

 


Configurar serverIP.png

Configurar serverIP2.png

2.2.2.2 Console Configuration

In this section we can choose between three different types of autoprovisioning, activating the one we want by means of a switch:

Configurar autorprovi.png

Round Robin
It uses the Round-robin planning method to distribute, in an equitable way and in a rational order, all the new Pandora software agents that reach the Metaconsole. The distribution of the agents will be done in a circular way, assigning the corresponding server to each new agent.
Less Loaded
The new agents will be dynamically assigned to those servers with less load.
Custom
In the customized classification, we will be able to define our own classification rules, based on certain parameters retrieved from the information reported by the agent (name of the agent and its IP address).

If we choose the Custom option, we will click on the "Create a custom entry" button where the following form will appear:

Configurar autorprovicustom.png

In the configuration section we will have to put the content that will be added to the configuration file. It is a way of customization that will be used to classify the agents; an example would be:

# Text contained here will be validated and inserted in the agent configuration
server_ip 192.168.80.164

Once created we will have to introduce the rules that we want the agents to comply with by hitting the "add" button.

Configurar autorprovicustom2.png

We will be able to specify the matching conditions in the form of rules using the following fields:

  • agent alias
  • agent address

We will be able to specify the operations using the following fields:

  • OR
  • AND

2.2.3 Autoconfiguration

In this section you can edit the autoconfigurations of the agents in a centralized way from the Metaconsole. In order to make this edition, we must have activated the "Centralized management".

For more information, visit this link.


2.2.4 Group Management

In this section we can manage, delete and create new groups in the Metaconsole.

Configurar gestiongrupo.png

2.2.4.1 Create a Group

To create a new group, click on the "create group" button and the following form will appear:

Configurar creargrupo.png

The parameters that require explanation are:

  • Parent: combo where another group can be defined as the parent of the group being created.
  • Propagate ACL: allows ACLs to be propagated to child subgroups..
  • Custom ID:the 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.

2.2.4.2 Modify/Delete a group

In the list of groups there are options for:

  • Editing the group
  • Deleting the Metaconsole group

Dac2.1.png

2.2.5 Tree group

In this section we can perform exactly the same actions as in the previous section, changing the display mode:

Tree group meta.png

2.2.6 Collections

From Pandora FMS OUM729 you can centralize the management of collections from the Metaconsole.

Mc col menu.png

The first time you access collection management, with centralized management enabled , an internal process of synchronization of the collections from the nodes to the Metaconsole will be performed:

Mc col message.png


From this moment on, you will have the collections in the Metaconsole. To avoid conflicts, you must manually copy the collection directories from the nodes to the Metaconsole:

Source location (node):


/var/www/html/pandora_console/attachment/collection/


Destination location (Metaconsole):

/var/www/html/pandora_console/attachment/collection/


Note: Remember to assign the correct permissions to the transferred files:

chmod apache. -R  /var/www/html/pandora_console/attachment/collection/*


Once the files are transferred, you can recreate the collection to force synchronization to nodes.

For more information about the collections, please visit this link.

2.3 Module Management

The following actions can be performed in this section:

  • Component Group Management
  • Local component management
  • Network Component Management
  • Plugin management

Before we start, let's explain what a component is: it is a "generic module" that can be applied repeatedly on an agent, being a kind of "master copy" of a module. This is very useful to monitor new agents with the components stored in the database.

For example, we have 12 instances where we want to create the same type of modules in each: we want to create 10 local modules, 5 network modules and 3 custom plugins. Thanks to the management in the Metaconsole we will be able to create these components, each one in its section, and then synchronize them to have them in the different instances without having to manually create them.

2.3.1 Component Group Management

In this section we can delete and create new groups of components.

Gestionar grupocompo.png

Gestionar grupocompo2.png

Gestionar grupocompo3.png

2.3.1.1 Group creation

To create a new group click on the "Create" button.

Gestionar crearcompogrupo.png

2.3.1.2 Group deletion

Gestionar borrarcompogrupo.png

2.3.2 Local component management

In this section we can delete, duplicate and create new local components. A local component is the elaboration of a module defined in the configuration of software agents, structured as "pieces" of text that can be cut and pasted in the configuration of agents.

Gestionar compolocal.png

2.3.2.1 Local component creation

In order to create a local component click on the "Create" button where the following form will appear:

Gestionar compolocalcrear.png

Gestionar compolocalcrear2.png

Gestionar compolocalcrear3.png

In order to see in detail more information about the parameters for the creation of a new local component you can visit Create user.

2.3.2.2 Duplicate/Delete a local component

In the list of local components you have options for:

  • Duplicating a local component
  • Deleting a local component of the Meta Console

Meta net component op col.png

2.3.3 Network Component Management

In this section we can delete, duplicate and create new network components. A network component groups all remote modules (wmi, tcp, snmp, icmp, plugin, web, etc).

Gestionar compored.png

2.3.3.1 Creating Network Component

There are three types of network components that can be created:

  • Network
  • Plugin
  • WMI

To create a new network component in the drop-down menu select a network component from the three possible (WMI, Network or Plugin): and click on the button Create. Next, we will see a screen to create a network component.


Gestionar comporedcrear.png

Gestionar comporedcrear2.png

Gestionar comporedcrear3.png

To see in detail more information about the parameters of creation of a new network component you can visit the section Network component.


2.3.3.2 Duplicating/Deleting a Network Component

In the list of network components you have options for:

  • Duplicating a network component
  • Deleting a network component from the Metaconsole


Meta net component op col.png

2.3.4 Plugin Management

In this section we will be able to delete, modify and create new plugins that will use plugin type network components.

Gestionar compoplugin.png

2.3.4.1 Creating a Plugin

To create a plugin click on the "Add" button and the following form will appear:

Gestionar compoplugincrear.png

Gestionar compoplugincrear2.png

The parameters that require explanation are:

  • Plug-in command: Where we will put the PATH to where the plugin is located
  • Plug-in parameters: Where we will put the parameters that we must write so that the plugin works correctly.

Gestionar compoplugincrear.png

2.3.4.2 Modifying/Deleting a Plugin

In the plugin list there are options for:

  • Modifying a plugin
  • Deleting a plugin from the Metaconsole

Certain plugins have a padlock in front of the Modify option, because these plugins cannot be modified or deleted.

Gestionar compopluginborrar.png

2.4 Alert Management

The following actions can be performed in this section:

  • Management of commands
  • Management of shares
  • Management of templates

Gestionar alertasgeneral.png

For example, in our meta console we have 5 instances with different clients and in all of them we need to measure in each agent the temperature of its CPU. With this information, we need an alert to be triggered when the CPU exceeds a certain temperature, and what we want is to create a command that will make the CPU eliminate certain services so as not to be used in an excessive way, causing it to rise in temperature. We would generate an alert that carries out this command and then synchronize it with all our instances so that we don't have to do it manually one by one.

In this section we will only talk about the management of templates, in particular, the differences with the management of alerts of the instances. To know more about its operation and configuration you can consult the Alert System section inside the Pandora FMS manual.

2.4.1 Template Management

The only difference with regard to the management of alerts of the instances, is in the creation of a new template. When creating a template we have an option called "Wizard level".

Gestionar alertas.png

This field will define which users will be able to use this template to create alerts from the Wizard.

  • No Wizard: This template will not be available in the Wizard.
  • Basic: Any user with access to the Wizard will be able to use this template to create alerts.
  • Advanced: Only users with advanced level of access to Metaconsole will be bale to use this template (see section Create user).

2.5 Event Alert Management

The following actions can be performed in this section:

  • Create event alert
  • Modify/Delete/Disable/Silence event alerts

Gestionar alertaseventos.png

For example, we have 4 instances where we have in one of the agents the monitoring of the apache server of each of the web pages located in the different instances. We will create an event alert that will warn us when this monitoring goes down to warn the administrator that the Apache service should be immediately fixed, so that it wouldn't be necessary to create one by one manually in the instances agents.

To find out more about its operation and configuration, please consult the section Alert System of the Pandora FMS manual.

2.6 Component Management

The following actions can be performed in this section:

  • Tag Management
  • Module group management
  • OS Management

Gestionar componentes.png

2.6.1 Manage tags

In this section we will be able to delete, modify, and create new tags.

2.6.1.1 Creating Tags

To create a new tag we click on the button “create tag” and then we will get the following form to fill in:

Gestionar tagscrear.png

2.6.1.2 Modify/Delete tags

In the list of tags we have options to:

  • Edit the tag
  • Delete the tag from the Metaconsole

Dac2.1.png

2.6.2 Module Groups Management

In this section we can delete and create new groups of modules.

Gestionar gruposmodulos.png

2.6.2.1 Group Creation

To be able to create a new module group we will click on the button “Create module group”:

Gestionar gruposmoduloscrear.png

2.6.2.2 Deletin a Module Group

Gestionar borrarcompogrupo.png

2.6.3 OS Management

In this section we can delete and create new OS.

Gestionar OS.png

Gestionar OS2.png

2.6.3.1 OS Creation

To create a new OS we click on the button “create OS” and a form will appear for us to fill in:

Gestionar OScrear.png

2.6.3.2 OS Deletion

Gestionar borrarcompogrupo.png

2.7 Policy Management

From this section we can create, modify, and delete policies.

Meta menu.png

For example, we have 7 instances in which 2 of them are going to be monitored in the same way, with the same name of agents and modules. We would create a policy that creates the modules in the agents automatically, which we will later synchronize with the different instances without having to create it one by one.

2.7.1 Policy Creation

New policies can be created by clicking on the "Create" button, where the following form is displayed:

Meta crear.png

For a better understanding of how to configure policies, please refer to the section Policy Management.

2.7.2 Modify/Delete policies

In the list of policies we have options to modify a policy and delete it. If a policy has agents, the "Delete" button will be disabled and a button to delete all its agents will appear next to it. This button will introduce the agent deletion into the queue, and as soon as it is processed, the policy deletion button will be active again.

Meta borrar.png

2.8 Category Management

In this section we can modify, delete and create new categories.

Gestionar categorias.png

2.8.1 Creating Categories

To create a new category click on the button “create category”:

Gestionar categoriascrear.png

2.8.2 Modify/Delete policies

In the list of categories we have options to:

  • Edit the category
  • Delete the category from the Metaconsole

Dac2.1.png

2.9 Server Management

In this section we will be able to delete the servers installed in the Metaconsole. In order to be able to use all the features, the Auto-provisioning and Migration servers should be activated.

Gestionar server.png

Back to Index of Documentation of Pandora FMS