Pandora: Documentation en: Data Presentation/Reports

From Pandora FMS Wiki
Revision as of 16:03, 23 October 2018 by Irene (talk | contribs) (Reports)
Jump to: navigation, search

Contents

1 Reports

Pandora FMS offers you the possibility of presenting the monitored data in an orderly way in the form of reports.


Within a report, the information to be presented is organized in 'report elements. There are many different types of elements, which perform calculations and present the information in very different ways. For example, we can choose a "simple graph" type element that makes individual graphs or an "SLA" type element that shows us the degree of compliance of a number of monitors.


Although they generally have a very similar configuration form, each type of element will be configured independently.


You can have as many elements as you want, of the type you want.

1.1 Creating a Report

In order to add a report, please click on Reporting -> Custom reporting.

Report menu.png

It's going to show you a list which contains all the reports. In order to create a report, please click on "Create Report".

Pre18.png

There is one window within which the name of the report, the group it belongs to, whether it's private or not and the description is defined and contained.

Once the fields have been filled out, please click on "Create Report".

Pre19.png

Once done, it will appear a blank report, where we will continue its edition including new elements.

1.2 Editing a Report

In order to edit a report, please click on Reporting -> Custom Reporting. It contains a list in which all the reports so far are listed. In order to edit a report, please click on the report's name.

Pre43.png

1.3 Deleting a Report

In order to delete a report, please click on 'Reporting' -> 'Custom Reporting' and 'Report Builder'. It contains a list in which all the reports so far are listed. In order to delete a report, please click on the trash icon which is located on the right side of the report's name.

Pre44.png

1.4 Tabs

1.4.1 Main Tab

The main tab is the only one available within a new report, so this one defines the report's basic data (name, access group and description). After storing it properly, you're able to access the rest of the tabs.

Main tab reporting builder.png

The fields pertaining to this particular tab are the following:

  • Name: Intended to define the name of the form.
  • Group: Intended to define the access group that is visualized within the report.
  • Description: Intended for providing more report information to the users (which is also going to be shown within the report's list). It's also going to be shown within the visualization of the report as XML and PDF.

1.4.2 The 'List Items' Tab

By this tab, you're going to obtain a global visualization of all items the report is composed of. The items contained in the list will be displayed in the same order they're going to have within the report later. Within this tab, you have the following options:

  • To modify the item (by clicking on the adjustable spanner).
  • To modify the order with the right side boxes "sort" and the pannel below "Sort items".
  • To modify the order manually by the green arrows on the left.
  • To delete the item by clicking on the red x-shaped icon.

If it's a big report which contains several items, it has a form on the top in order to filter the items by different criteria.

List items tab reporting builder.png

The columns pertaining to this particular tab are the following:

  • P.: The items appear exactly in this column's order within the report.
  • Type: The column in which the item's type is displayed.
  • Agent: The column in which the agent's name is mentioned. It's also allowed to leave it blank for item types like SLAs, custom graphs, import texts from URLs, SQL queries, simple graphs and texts.
  • Module: The column in which the module's name will be extracted from the data in order to generate the report. It's also allowed to leave it blank for item types like detailed agent view, alert report agent, custom graph, event report agent, import text from URL, SLA, SQL queries and text.
  • Period: The time period that it's going to receive in the specific moment the report is generated.
  • Description: The column which displays the description you've given the item in order to render the work with it a little easier.
  • Options: The column which displays the buttons and icons to edit or to delete it.

1.4.3 The 'Item Editor' Tab

The Item Editor tab is more complex than the others, because you'll be able to create the form items or to edit them by it. The form is dynamically designed, depending on the type of item you intend to create. In the editing process, all fields except the type are editable. If you e.g. need to change the type, the way to do it is to delete the current and to generate a new one along with a similar configuration.

The common fields for all types are the following:

  • Type: The pop-up list containing the types of items intended for the report which determines the appropriate fields to configure this type of item by selecting the type: Agents, Modules, Agent Detailed View, Alert Report Agent, Alert Report Module, Avg. Value, Custom Graph, Event Report Agent, Event Report Module, Import text from URL, MTBF, MTTR, Max. Value, Min. Value, Monitor Report, SLA, SQL query, Serialized Data, Simple Graph, Summary, TTO, TTRT and Text
  • Description: The text box intended for a description of the reported item.

1.4.4 Types of Items

We can include different elements into out report, which can be:

1.4.4.1 Graph Items
1.4.4.1.1 Simple graph

It shows the simple graph of a module.

Simple graph - item editor tab - reporting builder.png



This form's fields are:

  • Period: Time interval over which the report will be calculated (from the current point in time).
  • Agent: the intelligent control to choose the agent for this item.
  • Module: lista desplegable que se carga de forma dinámica con los módulos del agente seleccionado en el control previo.
  • Time comparison (overlapped): activado te muestra solapada encima la gráfica del módulo en ese margen de tiempo, por ejemplo si la gráfica muestra un tramo de 1 mes, la gráfica solapada encima es el mes anterior.

Vista de ejemplo de este tipo de informe:

Pre39.png



1.4.4.1.2 Simple Baseline Graph

By this type of graph, you're able to display future estimation values for the selected module. Let's assume for a moment you e.g. select a period of a week and today would be Tuesday, this particular graph provides real data from Monday through Tuesday and estimation values for all other days within the selected week.

Baseline-form.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A drop-down list which is dynamically loaded by the agent's modules selected in the control above.

Within the HTML version of the report, an item of this type is generated as you can see below.

Baseline-result.png


Template warning.png

This type of graph has the potential to overload Pandora FMS if you're utilizing too much data to generate future estimations.

 


1.4.4.1.3 The Custom Graph

It's a user-defined combined graph. A field is added with a combo to select the graph we intend to add.

Custom graph - item editor tab - reporting builder.png

The fields within this form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Custom Graph: A deployable list containing the user-defined graphs. In order to create theses graphs, please click on 'Administration' -> 'Manage Reports'
    and 'Graph Builder'.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre26.png

1.4.4.1.4 Gráficas definidas desde SQL

Este tipo de elemento de informe permite que se puedan definir gráficas personalizadas para usarlas en los informes. Estas graficas se crearán usando código SQL introducido por el usuario. Este código SQL deberá devolver siempre una variable llamada "label" para las etiquetas de texto o nombre de los elementos a visualizar y un campo llamado "value" para almacenar el valor numérico a representar. Este es un ejemplo de SQL usado para crear gráficas de este tipo:

SELECT a.nombre as `label`, count(st.id_agente_modulo) as `value`
FROM tagente_estado st, tagente a
WHERE a.id_agente=st.id_agente AND (unix_timestamp(now()) - st.utimestamp) > st.current_interval * 2 group by 1;

En este ejemplo, mostraremos una gráfica en la que mostraremos el número de módulos en estado desconocido por agente. Es bastante similar a una consula SQL, pero no utiliza cabeceras, y sólo necesita el código SQL:

Sql graph pie.png




Estos son algunos ejemplos de cada uno de los tres tipos de graficas que se pueden dibujar con esta herramienta: gráficas circulares, de barras verticales y de barras horizontales. En este ejemplo se usan varios juegos de caracteres UTF (western latin, Japanese and Arabic) simplemente para mostrar las capacidades multiidioma de Pandora FMS.


Template warning.png

Debido a restricciones de seguridad, hay algunas palabras reservadas que no se pueden usar: *, DELETE, DROP, ALTER, MODIFY, password, pass, INSERT ó UPDATE

 


Info.png

Este tipo de items han de usarse con cuidado ya que pueden sobrecargar en exceso Pandora FMS

 


1.4.4.1.5 SQL pie graph

Ejemplo gráfico circular para informes basados en consulta SQL

Report piegraph.png



1.4.4.1.6 SQL Vertical bar graph

Ejemplo gráfica de barras verticales para informes basados en consulta SQL

Report vgraph.png



1.4.4.1.7 SQL horizonal bar graph

Ejemplo gráfica de barras horizontales para informes basados en consulta SQL

Report hgraph.png


1.4.4.1.8 Availability graph

Informe de disponibilidad, muestra un informe detallado de los estados alcanzados de un módulo en un intervalo de tiempo dado.

Nos indicará toda la información relevante acerca del tiempo que este módulo ha estado disponible.

Podremos elegir el rango de tiempo del que queremos el informe (por ejemplo, el último mes) y el tiempo de trabajo si por ejemplo necesitamos indicar que sólo nos interesa el estado de nuestro módulo en un horario determinado (por ejemplo, 8x5, de 8:00 a 16:00 de lunes a viernes).

También es posible determinar un modo de priorización. Al elegir el modo de priorización del OK, si se solapan en el tiempo datos en el rango de cumplimiento del SLA y algún otro estado (como por ejemplo una parada planificada) pintará ese tramo en verde. Si se opta por la opción de modo de priorización del desconocido, siempre se mostrará el color correspondiente al otro estado .

Availability builder.png


Tras guardar los datos del elemento del informe, agregaremos los módulos que queramos en la parte inferior:

Availability builder item.png

Nota: Puede utilizar los campos SLA min. y max. (value) para indicar que el cálculos se haga en relación a los valores alcanzados por el módulo en ese rango. SLA limit % indicará el mínimo aceptable (dentro de ese rango).

Por defecto, si no especifica un mínimo ni un máximo para el valor, se utilizarán los valores de umbrales definidos en el módulo (límites dinámicos).


Visualizando el informe veremos la gráfica de disponibilidad del módulo elegido en el rango de tiempo seleccionado:

Availability graph.png

1.4.4.1.9 Module Histogram graph

Mostrará una gráfica con el histograma de estados del módulo elegido.

Ejemplo de definición de módulo:

Histogram build.png

Ejemplo de visualización:

Histogram sample.png

1.4.4.2 S.L.A Items

Todos los informes de SLA muestran información sobre el cumplimiento de una métrica, es decir, nos indican el porcentaje de tiempo que el módulo ha tenido un valor válido conocido.

Todos los SLA entienden como válido los períodos desconocidos, dado que Pandora no puede garantizar el estado del módulo si no tiene datos del mismo. También se consideran válidos todos los períodos en parada planificada (ya que al estar en una situación de parada planificada asumimos que se controla y acepta la situación del módulo) y los períodos en estado de advertencia (el servicio se sigue prestando aun en un estado no óptimo).

Como se verá posteriormente, algunos de los informes de SLA presentan datos agrupados por periodos de tiempo y se calcula el estado general de estos periodos. Al tratarse de periodos largos, el módulo del que se está haciendo el informe puede haber pasado por muchos estados: irse a desconocido, pasar por una parada planificada... En estos informes, hay un parámetro de configuración llamado modo de priorización que determina qué estados tienen preferencia al efectuar el resumen. Tiene dos opciones:

  • Modo de priorización del OK: Prima el valor de cumplimiento de SLA por encima del tiempo de no funcionamiento del informe, paradas planificadas, tiempo de desconocido y no iniciado.
  • Modo de priorización de desconocido: Cualquier valor distinto de OK primará. De esta forma, se verán los tiempos de no funcionamiento del informe, paradas planificadas, tiempo de desconocido y no iniciado aunque en haya algún dato que haga que se cumpla el SLA.

Por supuesto, si en algún momento no se alcanza el valor de cumplimiento del SLA, se pintará en rojo en cualquiera de los modos.

1.4.4.2.1 S.L.A

It allows you to measure the SLA (Service Level Agreement) of any monitor of Pandora FMS.

S.L.A. - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Working time: The time frame during which the S.L.A. will be functioning. The graph will be shown as is, but will only be calculated with the data within said working time frame. The S.L.A will appear as unknown (N/A) if the interval to be shown is excluded from the work interval.
  • Agent: A combo box intended to select the agent to use in the SLA.
  • Module: A combo box intended to select the module to use in the SLA.
  • SLA min (value): A field intended to determine the SLA's minimum value. The minimum values are going to trigger the SLA.
  • SLA max (value): A field intended to determine the SLA's maximum value. The maximum values are also going to trigger the SLA.
  • SLA Limit (%): A field intended to set the time percentage which is going to trigger the SLA. If the module has been within the minimum and maximum limit values during this particular time percentage, the SLA will be shown as right and as wrong if not.

It's also possible to add new modules to the SLA to create combined module-SLAs from the same or different systems.


Template warning.png

In case of combined SLAs, the SLA performance is going to depend heavily on the performance of all the SLAs configured so far.

 


We can set planned downtimes (future or past) to be taken into consideration when the calculation of the SLA report, misestimating any falls that occur in this interval. It will OK value in all intervals affected by the planned shutdown, as if in this interval there were no critical situations.

SLA 2.png

In this example we can see it better, In the first image we can see a module data history with two interval in critical status. Without scheduled downtime the SLA value is 93%.

SLA sinsch.png

If we add a scheduled downtime covering the first drop, because it was caused by external problems, the final estimation will be calculated as in all scheduled downtime interval the value is OK

SLA consch.png

1.4.4.2.2 Monthly SLA

This feature is only available to Enterprise Versions of Pandora FMS. It's a variation of the SLA feature. Instead of measuring the service level periodically, it's going to conduct it on every day of the months contained in this period.

Examples:

  • In a report of the May 5, it's going to calculate the SLA of every day in May.
  • In a report between February 13 and April 4, it's going to calculate the SLA of every day in February, March and April.

Each module on each month is going to contain the same data of a standard SLA, except that its compliance won't be the month's level. It will be the percentage of days that accomplish it. There is also a bar that's going to display all days of the month by the following color code:

  • Green: The SLA was accomplished.
  • Red: The SLA wasn't accomplished.
  • Gray: Unknown. There is insufficient data on this day.


Info.png

Days in unknown will be taken into account as valid data for the percentage of days that meet the SLA

 


If there are days which don't accomplish the SLA they will be put in a summary table.

S.L.A. Monthly - view.png

On the picture above, we observe a monthly SLA for two modules. The first one passes 100% of the days with data, and the second one doesn't in 3 out of 22 days. That gives us an accomplishment of 86.36%. For day 23 there is no data, because it's the current date. These days are not going to affect the calculations.


Info.png

The periods in which a planned downtime affects the measured element aren't taken into account. If this happen, the planned downtimes will appear in a special table.

 


1.4.4.2.3 S.L.A. Semanal

Muestra el SLA de los módulos elegidos por semanas a lo largo del período seleccionado (por defecto mes actual)

Sla weekly.png


Nos permite editar el working time por si tuviéramos un horario de servicio personalizado (p.e. 8x5)

En la parte inferior podemos agregar múltiples módulos a este ítem.

Ejemplo de visualización:

Sla weekly sample.png

1.4.4.2.4 S.L.A. Hora a hora

Muestra el SLA de los módulos elegidos por hora a lo largo del período seleccionado (por defecto mes actual)

Sla hourly.png


Nos permite editar el working time por si tuviéramos un horario de servicio personalizado (p.e. 8x5)

En la parte inferior podemos agregar múltiples módulos a este ítem.

Ejemplo de visualización:

Sla hourly sample.png

1.4.4.2.5 Service S.L.A.

It allows you to measure the SLA (Service Level Agreement) of any service created in Pandora FMS

S.L.A servicios.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Working Time: Time to be taken into account for the SLA calculation.

This form is different from the calculation of normal SLA. In this case only we will allow us to choose the service they want to show in which there created. The SLA limit will be extracted directly from the service configuration.

S.L.A servicios2.png

We can set planned downtimes (future or past) to be taken into consideration when the calculation of the SLA report, misestimating any falls that occur in this interval. These scheduled downtimes may be assigned to the modules it depends on the service selected, or inferior services. In all intervals in which there is configured planned downtimes, states has been within that service will not be taken into account that period for the calculation of the SLA is ignored.

In this example, we can see a schema of final En este ejemplo podemos observar an outline of the final calculation of the service depending on the planned stops (white) and the critical states (red) of the modules of which depends on the state of the final service for SLA calculation. Looking at the image when any of the modules have a downtime directly affects the final service and this interval is omitted for final calculation.

S.L.A total.png

1.4.4.3 Prediction Items
1.4.4.3.1 Prediction Date

This type of item returns a date in the future in which a module reaches its interval. It utilizes the Least Squares Method like the projection graph.

Projection graph3.png

In order to configure this item, you're required to provide the information shown below.

Projection graph5.png

  • Period: The relevant time frame for estimation creation.
  • Data Range: The interval the module requires to return the associated date.

Example: Just assume for a moment you would have taken the module named 'FreeDisk_SpoolDir', picked '15 days' as a time frame and searched for the date on which the module would reach its interval [3200-0]. The result would have been '03 Nov 2013 19:07:18'. Please take a look on the picture below to get a graphical explanation.

Prediction date.png

1.4.4.3.2 Projection Graph

This type of graph is going to project a future estimation of the module's data. This estimation is based on Linear Regression and is implemented by means of the Least Squares Method.

Projection graphs.png

In order to configure this graph, you're required to provide the following information:

Projection graph6.png

  • Period: The relevant time frame for the estimation.
  • Projection Period: The relevant time frame in the future for which the module data is going to be used to create the projection.

Projection graph periods.png

1.4.4.4 Module Items
1.4.4.4.1 Avg. Value

It's the average value for a module within a predefined period. This period is calculated in the moment of visualizing the report. Within the configuration menu, the fields for the source agent are added, where the agent and modules are selected. Subsequently, the module's average value is shown.

Avg value - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: The intelligent control to select the appropriate agent for this item.
  • Module: A list which is dynamically loaded by the agent's modules selected in the control above.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre24.png

1.4.4.4.2 Max. Value

It's the maximum value of a module within a predefined period. This period is calculated in the moment of the report's viewing.

Max. Value - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A deployable list which is dynamically loaded by the agent's modules selected in the control above.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre29.png

1.4.4.4.3 Min. Value

It's the minimum value of a module within a predefined period. This period is calculated in the moment of the report's viewing.

Min. Value - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A deployable list which is dynamically loaded by the agent's modules selected in the control above.
  • Calculate for custom intervals: Habilita la posibilidad de mostrar el informe en múltiples sub intervalos.
  • Time lapse intervals: Duración de cada sub intervalo.
  • Table | graph | both: Mostrar los datos de cada valor de cada sub intervalo en una tabla o una gráfica o ambos elementos.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre30.png

1.4.4.4.4 Monitor Report

It shows the percentage of time a module has been right or wrong within a predefined period.

Monitor report - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A deployable list which is dynamically loaded by the agent's modules selected in the control above.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre32.png

1.4.4.4.5 Serializing Data

It displays an item in the table format report from the data stored within the table named 'tagente_datos_stringin' the Pandora FMS Database. For it, the agent should serialize the data separating them with a line-separating character and another which separates the fields. All lines should contain all fields. This type of item is e.g. used for the agent which is designed to extract management data from the SAP Platform.

Serialize data - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A drop-down list which is dynamically loaded by the agent's modules selected in the control above.
  • Serialized Header: A text field intended to define the table headers which are going to be shown in the report, separated by the '|' (pipe) character. Each column is going to be shown as a result within the SQL query.
  • Field Separator: A separator intended for different fields within the serialized text chain.
  • Line Separator: A separator intended for different lines (composed by fields) of the serialized text chain.
1.4.4.4.6 Summatory

It displays a summation of a single module's values within a specific time frame.

Sumatory - item editor tab - reporting builder.png

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.
  • Module: A drop-down list which is dynamically loaded by the agent's modules selected in the control above.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre40.png


1.4.4.4.7 Historical Data

Este tipo de elemento nos servirá para recibir un volcado de los datos almacenados del módulo que indiquemos en la configuración del informe.

Configuraremos los siguientes campos:

  • Period: Intervalo de tiempo sobre el que se calculará el informe (desde el momento actual).
  • Agent: el control inteligente para elegir el agente para este item.
  • Module: lista desplegable que se carga de forma dinámica con los módulos del agente seleccionado en el control previo.

Historical.png


Ejemplo de visualización del informe:

Historical sample.png

1.4.4.4.8 Increment

Utilizaremos este tipo de elemento de informe para mostrar un breve análisis en el que se nos indicará la variación de valor del módulo indicado.

Configuraremos los siguientes campos:

  • Period: Intervalo de tiempo sobre el que se calculará el informe (desde el momento actual).
  • Agent: el control inteligente para elegir el agente para este item.
  • Module: lista desplegable que se carga de forma dinámica con los módulos del agente seleccionado en el control previo.

Increment.png


Ejemplo de visualización del informe:

Increment sample.png

1.4.4.5 Grouped Items
1.4.4.5.1 General

Muestra valores de diferentes módulos ordenados (ascendentemente, descendentemente o por nombre de agente) o/y agrupados por agente.

Configuraremos los siguientes campos:

  • Time lapse: Intervalo de tiempo sobre el que se calculará el informe (desde el momento actual).
  • Last value: Mostrar únicamente la última lectura de los módulos elegidos.
  • Agent: el control inteligente para elegir el agente para este item.
  • Module: lista desplegable que se carga de forma dinámica con los módulos del agente seleccionado en el control previo.
  • Group by agent: Agrupar las métricas del informe por agente.
  • Order: Orden en el que mostrar las métricas.
  • Show summary: Mostrar un resumen final con los valores promedio, máximos y mínimos.
  • Show in the same row: Mostrar todas las operaciones (max,min,avg o sum) en la misma fila.

Grouped general.png


Ejemplo de visualización del informe:

Grouped general sample.png

1.4.4.5.2 The Group Report

It displays a table containing the below mentioned information of a predefined group:

  • Agents
    • The total number of agents
    • The number of agents holding an 'unknown' status
  • Modules
    • The total number of modules
    • The number of modules holding a 'normal' status
    • The number of modules holding a 'critical' status
    • The number of modules holding a 'warning' status
    • The number of modules holding an 'unknown' status
    • The number of modules holding a 'not initiated' status
  • Alerts
    • The number of defined alerts
    • The number of fired alerts
  • Events
    • The number of this group's events within the last 8 hours.

Group-report-from.png

The fields pertaining to this particular form are the following:

  • Group: A combo intended to select the group.
  • Recurse: Analyze recursively the child groups of the choosen group.

Within the HTML version of the report, an item of this type is generated as you can see below.

Group-report-result.png

1.4.4.5.3 Exceptions

Muestra valores de diversos módulos que cumplen operaciones lógicas (mayor o igual, menor, OK o No OK).

Report last value exc.png

Podremos configurar los siguientes campos:

  • Time lapse: Intervalo de tiempo sobre el que se calculará el informe (desde el momento actual).
  • Last value: Mostrar únicamente la última lectura de los módulos elegidos.
  • Order: Orden en el que mostrar las métricas.
  • Value: valor que se considerará con la condición elegida.
  • Condition: Condición con la que cribar los datos del informe, everything ignora el cribado.
  • Show summary: Mostrar un resumen final con los valores promedio, máximos y mínimos.
  • Show in the same row: Mostrar todas las operaciones (max,min,avg o sum) en la misma fila.

En la parte inferior podremos agregar tantos módulos como necesitemos una vez guardado el elemento de informe:

  • Agent: el control inteligente para elegir el agente para este item.
  • Module: lista desplegable que se carga de forma dinámica con los módulos del agente seleccionado en el control previo.

Ejemplo de visualización del informe:

Exception - item editor tab - reporting builder.png

1.4.4.5.4 Agents / Modules

It displays a matrix of agents and modules of a specific module group along with its associated states.

Agents-modules - item editor tab - reporting builder.png

1.4.4.5.5 Consultas SQL

Este item muestra en los informes datos de la BD de datos de Pandora de en tabla para disponer en el informe de datos personalizados extraidos directamente de la BD.

Template warning.png

Este tipo de items han de usarse con cuidado ya que pueden sobrecargar en exceso Pandora FMS

 



Los campos de este formulario son:

  • Query SQL: caja de texto donde escribir la consulta SQL para extraer los datos de la BD de Pandora.
  • Serialized header: campo de texto donde poner separados por | para definir las cabeceras de la tabla que se mostrará en el informe, por cada columna que saliera de resultado en la consulta SQL.
  • Custom SQL template: lista desplegable que contiene las plantillas de SQL de consultas guardadas para su fácil uso. Estas se pueden gestionar por medio de Administration, Manage reports en Custom SQL.
  • Query History Database: Casilla de chequeo que al ser marcada hará que la consulta sql editada recoja también los datos de la base de datos histórica.

Podemos personalizar las consultas que aparecerán en informe eligiendo una opción de las siguientes:

  • Escribir manualmente en el campo de texto la consulta a realizar.

Nota: Debido a restricciones de seguridad, hay algunas palabras reservadas que no se pueden usar: *, DELETE, DROP, ALTER, MODIFY, password, pass, INSERT ó UPDATE.


Custom sql report.png


  • O bien, podemos seleccionar una consulta de la lista utilizando el desplegable Custom SQL template:

Custom sql template report.png


Ejemplo de visualización de informe:

Custom sql report sample.png



Nota: Puede definir sus propias plantillas en el menú Reporting > Custom SQL

Custom sql menu.png


En la vista de la lista de consultas, puede crear su nueva consulta almacenada pulsando el botón Create custom SQL:

Custom sql list.png


Defina su consulta y un nombre para identificarla y presione "save" para que aparezca en la lista:

Custom sql new.png

1.4.4.5.6 Top N

It displays N values discriminated by maximum, minimum or the average of the selected modules, ordered ascending, descending or by the agent's name.

Report topn.png

Report topn sample.png

1.4.4.5.7 Network interfaces

Este tipo de elemento de informe nos generará las gráficas de interfaces de todos aquellos dispositivos que pertenecen al grupo seleccionado.

Report net interfaces.png


Podemos indicar:

  • Time lapse: Rango de tiempo hacia atrás sobre el que se elaborará el informe (p.e. un mes desde la fecha elegida).
  • Group: Grupo donde se buscarán agentes con módulos de tráfico de interfaz.
  • Full resolution graph (TIP): Usar el sistema de pintado de datos reales TIP en vez del motor estándar.


Nota: Se considerará que un agente tiene datos de tráfico de interfaz cuando tenga módulos con el siguiente formato:

  • Nombre de interfaz_ifInOctects
  • Nombre de interfaz_ifOutOctects
  • Nombre de interfaz_ifOperStatus

Nota: Los contadores de octetos de entrada/ salida también pueden recogerse de los contadores HC (hcOctets).


Ejemplo de visualización de informe:

Report net interfaces sample.png

1.4.4.5.8 Availability

Se ha mejorado enormemente la funcionalidad de este tipo de informe, logrando que los datos representados en él ya no sean aproximaciones, sino reflejo exacto de la situación de los módulos a lo largo del período seleccionado.

Este ítem muestra un tabla con los datos de disponibilidad de una lista de agentes y módulos seleccionada.

También ofrece la posibilidad de mostrar un resumen en el que mostrarán aquellos módulos con mayor y menor disponibilidad, así como un análisis del promedio.

Report availability.png


Puede personalizar los siguientes campos:

Los campos de este formulario son:

  • Period: Intervalo de tiempo sobre el que se calculará el informe (desde el momento actual).
  • Working time: el periodo de tiempo en el que el módulo debería haber estado funcionando. La gráfica se mostrará completa, pero solo se calculará con los datos dentro del tiempo de trabajo. La disponibilidad será desconocida (N/A) si el intervalo a mostrar está fuera del intervalo de trabajo.
  • Show address instead of module name.Show the agent's main address.: Mostrará la IP principal del agente en vez del nombre.
  • Show summary: Mostrar un resumen final.
  • Orden: Ordenar los items disponibilidad según el criterio elegido.
  • Hide not init agents: Ocultar de la vista aquellos agentes no iniciados.


Una vez hemos seleccionado estas opciones, agregaremos cada uno de los módulos objetivos sobre los que queramos calcular SLA:

Report availability add module.png

  • Agent: Combo donde puede indicar el agente sobre el que aplicar el informe.
  • Module: En un combo se elige el módulo del agente previamente fijado sobre el que calculará el SLA.


Ejemplo de visualización de informe:

Report availability sample.png


Muestra la siguiente información:

  • Agente: agente.
  • Module / Dirección IP: al configurar el item puedes elegir que muestre la dirección ip primaria del agente en vez módulo, muy útil para informes que pongan una lista agentes e ips en vez de por agentes y módulos ping.
  • Total time: Tiempo total a analizar.
  • Time failed: Tiempo en estado crítico.
  • Time OK: Tiempo en estado OK o advertencia.
  • Time Unknown: Tiempo en estado desconocido.
  • Time Not init: Tiempo no iniciado.
  • Time downtime: Tiempo en parada planificada.
  • %OK: Porcentaje de tiempo en estado correcto.
  • Total checks: número de chequeos totales realizados durante el lapso de tiempo configurado para el informe.
  • Checks failed: número de chequeos que han fallado (críticos).
  • Checks OK: número de chequeos correctos.
  • Checks Unknown: Aproximación basada en eventos y la lógica de Pandora FMS que permite indicar el número de chequeos que deberían haberse realizado, pero de los que no consta una respuesta.
1.4.4.6 HTML and Text Items
1.4.4.6.1 Text

This item displays a formatted text within the reports to add e.g. more information of the company to the report.

Text report module - item editor tab - reporting builder.png

The field pertaining to this particular form is the following:

  • Text: A text box intended to format the text and to add links and images from a remote server.

An example of the window in which the link is added is shown below.

Edit link - report builder.png

An example of the window in which the image is added is shown below.

Edit image - report builder.png

1.4.4.6.2 Importing Text from an URL

This item shows the text extracted from an external server to which the Pandora FMS Console has access to. In the HTML report format, it's important to keep in mind that it's going to display the text like it really is, but in the PDF version of the report, it's only going to show the text in a plain-text format.

Import text from URL - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • URL: The text field intended to insert the external server address in order to extract the text.
1.4.4.7 Alert Items
1.4.4.7.1 The Alert Report Agent

It displays a list containing the agent's fired alerts of a specified report group within a predefined period.

Alert report agent - item editor tab - reporting builder.png

The fields within this form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control for selecting the appropriate agent for this item.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre23.png

1.4.4.7.2 The Alert Report Module

It displays a list containing the module's fired alerts within a predefined period intended for the report.

Alert report module - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: The intelligent control to select the appropriate agent for this item.
  • Module: A list which is dynamically loaded by the agent's modules selected in the control above.
1.4.4.7.3 Alert report group

Muestra un listado con las alertas lanzadas en cualquier elemento del grupo definido en el informe en el periodo definido.

ReportGroupAlert.png



Los campos de este formulario son:

  • Time lapse: el rango de tiempo hacia atrás sobre el que se elaborará el informe (p.e. un mes desde la fecha elegida).
  • Group: Grupo sobre el que se analizará la información de disparo de alertas.
  • Recursion: Analizar los grupos hijo del grupo definido de manera recursiva.

ReportGroupAlertExample.png

1.4.4.8 Event Items
1.4.4.8.1 The Event Report Agent

It displays a list containing the events which occurred within the agents in the predefined time frame.

Event report agent - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: The intelligent control to select the appropriate agent for this item.
  • Severity, event type, event status: Selecct the types of events to see.
  • Event graphs: Show event summary graphs.

Within the HTML version of the report, an item of this type is generated as you can see below.

Pre27.png

1.4.4.8.2 The Event Report Module

It displays a list containing the events occurred within an agent's module in the report of a predefined time frame.

Event report module - item editor tab - reporting builder.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Agent: An intelligent control to select the appropriate agent for this item.
  • Module: A deployable list that is dynamically loaded with the agent's modules selected in the control above.
  • Severity, event type, event status: Select the type of events to see.
  • Event graphs: Show event summary graphs.

Report module events sample.png

1.4.4.8.3 The Event Report Group

It displays a list containing the events which occurred in the report group's agents within a predefined time frame.

Event-report-group-from.png

The fields pertaining to this particular form are the following:

  • Period: The time frame it takes to get back to the temporary point within which the report is generated.
  • Group: A combo intended to select the group.
  • Severity, event type, event status: Select the type of events to see.
  • Event graphs: Show event summary graphs.

Within the HTML version of the report, an item of this type is generated as you can see below.

Event-report-group-result.png

1.4.4.9 Inventory Items
1.4.4.9.1 Inventory

This item is contained in the Enterprise version of Pandora FMS. It displays the selected inventory of one or various hosts pertaining to a specific date or its last known data.

Inventory item form.png

The fields pertaining to this particular form are the following:

  • Description: A text field intended for the item's description.
  • Group: A combo which filters the agents appearing within the next field. It doesn't appear in the report, it's only a form tool.
  • Agents: The agents of the hosts in which the inventory will be gathered. Only the agents which contain inventory modules are going to appear in this field.
  • Modules: The common inventory modules of the selected agents.
  • Date: The date of the displayed data. If the youngest date is selected here, only the latest inventory data of the selected modules will be gathered.

Inventory report sample.png

1.4.4.9.2 Inventory Changes

This item displays the changes of the inventory registered in one of various hosts within a predefined time frame.

Inventory changes form.png

The fields pertaining to this particular form are the following:

  • Description: A text field intended for the item's description.
  • Period: A field to determine the interval for registering the changes.
  • Group: A combo which filters the agents which appear within the next field. It doesn't appear in the report, it's only a form tool.
  • Agents: The agents of the hosts in which the inventory will be gathered. Only the agents containing inventory modules are going to appear within this field.
  • Modules: The common inventory modules of the selected agents.


Info.png

The data for this item is solely provided by inventory changing events. If they have a too large number of them, you may delete some of those events manually to reduce them.

 


Inventory changes report sample.png

1.4.4.10 Configuration Items
1.4.4.10.1 Configuración de agente

Este tipo de informe nos mostrará una fotografía del estado del agente:

Agent configuration report.png


Ejemplo de visualización

Agent configuration report sample.png




1.4.4.10.2 Opciones de grupo

Este tipo de informe nos mostrará una fotografía del estado de los agentes que pertenecen al grupo seleccionado:

Group configuration report.png


Ejemplo de visualización:

Group configuration report sample.png

1.4.4.11 Netflow Items
1.4.4.11.1 Netflow area chart

Este elemento de informe mostrará una gráfica con el análisis del tráfico utilizando filtros ya creados en la vista de Netflow.

Netflow area.png


Ejemplo de visualización de este tipo de informe:

Netflow area sample.png



1.4.4.11.2 Netflow pie chart

Este elemento muestra un gráfico circular con los resultados de aplicar el filtro indicado por el usuario.

Netflow pie.png


Ejemplo de visualización de este tipo de informe:

Netflow pie sample.png



1.4.4.11.3 Netflow data chart

Este elemento muestra los datos obtenidos al aplicar el filtro indicado por el usuario en una tabla ordenando por fecha y origen.

Netflow datachart.png


Ejemplo de visualización de este tipo de informe:

Netflow datachart sample.png



1.4.4.11.4 Netflow statistics chart

Este elemento de informe mostrará una tabla con el valor agrupado del tráfico, utilizando filtros ya creados en la vista de Netflow.

Netflow statistics.png


Ejemplo de visualización de este tipo de informe:

Netflow statistics sample.png



1.4.4.11.5 Netflow summary chart

Este elemento de informe mostrará una tabla con información resumida del tráfico que coincida con el filtro de Netflow indicado en .

Netflow summary.png


Ejemplo de visualización de este tipo de informe:

Netflow summary sample.png

1.4.4.12 Log Items
1.4.4.12.1 Informe de log

Este tipo de informe mostrará las entradas de log en el período seleccionado.

Log report build.png

  • Search: Cadena de texto a buscar.
  • Log number: Máximo número de entradas de bloque de logs que se mostrarán al generar este informe.
  • Time lapse: el rango de tiempo hacia atrás sobre el que se elaborará el informe (p.e. un mes desde la fecha elegida).
  • Source: Origen de logs.
  • Agents: Agentes para el filtrado.


Ejemplo de visualización de informe:

Log report.png

1.4.5 The Wizard Tab

This tab is a feature of the Enterprise Version of Pandora FMS. It allows you to automatically combine several items containing common configurations all at once and by a few clicks which are getting applied to several agents and modules for a report.

Once the type, the period, the agents and the modules have been selected, all you need to do is to click on the 'Add' button and it's going to generate as many items as agents or modules have been selected for the report.

Wizard-tab-reporting builder.png

The fields pertaining to this particular form are the following:

  • Type: A deployable list in which you're able to select the type of item that's going to be massively generated. Not all item types are contained in here, because there are certain item types which require a more detailed configuration. The available item types within this form are the following: Alert Report Agent, Alert Report Module, AVG Module, Event Report Agent, Event Report Module, Monitor Report, Simple Graph and Availability
  • Period: An intelligent control to provide the time period or data-time segment to represent the report item from the moment it's generated. If the time frame is e.g. 'one month' and you're generating the report in the current moment, the items are going to provide data from today to one month in the past.
  • Agents: The list of agents you're allowed to access according your permission group. On this list, you may select one or several agents. The modules which are defined as common for the selected agents are shown within the module control for each selection.
  • Modules: This common module list of the selected agents is available for one or several agents.
  • Filter Group: A field intended to filter the agents by group.
  • Elements to apply: The list intended for the selected modules to add.

Example of visualization of report (availability):

Wizard report availability sample.png



1.4.6 The SLA Wizard Tab

Este asistente nos permite crear ítems de informe SLA de manera automática.

Podemos elegir diferentes análisis de SLA:

  • SLA: mostrará un elemento de informe SLA estándar, indicando el % de cumplimiento en el período seleccionado.
  • Monthly SLA: mostrará un análisis día a día del mes seleccionado, indicando el % de cumplimiento.
  • Weekly SLA: mostrará un análisis del % de cumplimiento semana a seamana, indicando en todo momento el valor diario.
  • Hourly SLA: mostrará un análisis hora a hora del período seleccionado.
  • Availability graph: se generará una gráfica con los datos de disponibilidad de los módulos seleccionados.
  • SLA services: se creará un nuevo elemento de informe que representa el cálculo de los SLA de los servicios seleccionados.


Podrá elegir los rangos de validez de valor de los módulos a seleccionar. Esta característica le permitirá comprobar el % de tiempo que un módulo ha mantenido valores dentro de rangos específicos.

Si no define umbrales, estos se ajustarán dinámicamente a los umbrales de criticidad de cada módulo.


Puede encontrar otras opciones:

  • Hide not init agents: sólo SLA básico, ocultará los elementos no iniciados del informe.
  • Show graph: sólo SLA básico, permite elegir si mostrar una tabla con los datos, una gráfica, o ambos.


Wizard sla skel.png



Ejemplo de visualización de informe:

Report avail1.png



1.4.7 The Global Tab

This tab is a feature of the Enterprise Version of Pandora FMS and allows us to create Exception, General or Top N reports easily by a wizard.

With this section you can add different modules from different agents, while you can also choose the operation to do in each module: addition, media, min and max.

Global2.jpg


Example of visualization of a report:

Wizard global sample.png

1.4.8 The Advanced Options Tab

This tab is a feature of the Enterprise Version of Pandora FMS. This tab was designed to make the reports much more customizable. Among other things, you're now able to select the font the PDF report is going to be generated with, to select the logo which will be shown in the PDF header, to edit the header and the PDF footer and the report's front page.

Advance options-tab-reporting builder.png

The fields pertaining to this particular form are the following:

  • Font Family: It's a deployable list, containing all the fonts you've installed within your Pandora Console in the directory '<pandoraconsole>/enterprise/include//mpdf50b/ttfonts'. The default font is 'Times New Roman'. If you want to make the font range bigger, it's important to consider that it's required to have read access to the apache group and the fonts are required to be in TTF format.


Info.png

If you intend to use Arabic, Chinese, Japanese or another UTF8 text within your PDF, you're required to utilize a supported TTF font for doing so. We're providing the 'code' font which actually contains all language characters.

 


  • Custom Logo: It's a deployable list containing all possible logs which could be shown in the header of each PDF page. The logo images are stored under '<pandora_console>/images/custom_logo/'. The default image is 'pandora_logo.jpg'. You're able to see a preview in conjunction with your form by clicking on it.
  • Header: It's a complete editor within which you're able to copy and paste the formatted text of an application into or to edit it by the 'box' button. This text is going to be the one shown in the header.
  • First Page: Like the header field, this is another complete text editor, intended to create and to edit the PDF's front cover page.
  • Footer: It's the same like the two other fields, but for editing and creating each PDF page's footers.
1.4.8.1 Macros

It's also possible to use macros within the first page, the header and footer. The available implemented macros are the following:

  • (_DATETIME_): In the data format configured within the Pandora Console options, this value is replaced by the date in the moment the report is generated.
  • (_REPORT_NAME_): This value is going to be replaced by the report's name.

1.4.9 The Preview Tab

This tab displays the report as if it's generated in HTML format to be able to easily review the results. It's going to display the report exactly as the one you're going to see if you click on 'Operation' and 'View Report' within the menu.

1.5 Visualizing a Report

In order to visualize an already created report, please click on Operation -> Reporting.

Report menu.png

In this section you can see the created reports or create new.

Report list.png

Reports can be visualized in HTML, XML, CSV or PDF formats. Reports can be sent by email:

Send email.png

In order to see a report in the HTML format, please click on the Pre46.png icon. Once the report is opened in HTML, it's possible to select the date and hour it was generated.

Pre47.png

In order to see a report in the XML format, please click on the Pre48.pngicon.

Pre49.png



In order to see a report in the PDF format, please click on the Pre50.pngicon.

Pre51.png

1.6 Programación automática de informes

En la versión Enterprise de Pandora FMS dispone de la extensión CRON. Esta extensión nos permite programar diferentes tipos de acciones para ser ejecutadas con una periodicidad configurable.

Entre las múltiples opciones que ofrece, nos permite configurar el envío de informes en formato PDF a través de correos electrónicos.

Encontraremos esta funcionalidad en la entrada de menú Servers > Cron Jobs.


Cron menu.png


1.6.1 Envío automático de un informe por correo electrónico

Para enviar un informe a través de correo electrónico de forma programada, utilizaremos la extensión de consola enterprise CRON con las siguientes opciones:

Task
Seleccionaremos send custom report by e-mail. Nos permitirá programar la generación y envío de un informe ya existente.
Scheduled
En este campo especificaremos la frecuencia con que se enviara el informe.
First Execution
En este campo estableceremos la fecha y hora de la primera ejecución.
Report build
En este campo seleccionaremos el informe que se quiere enviar
Send to mail
En este campo se pone la dirección de mail a la que se enviará el informe.

Pre52.png

Una vez se han rellenado los datos se pulsa en create y aparece la tarea en la lista de tareas programadas.

Pre53.png


Una vez se ha creado la tarea, es posible forzar su ejecución pulsando en el icono circular que hay a la izquierda de la tarea programada. También podremos editar o borrar la tarea programada utilizando los botones situados a la derecha.




1.6.2 Aplicación y envío de plantilla de informe por correo electrónico

Para aplicar una plantilla y enviar el resultado a través de correo electrónico de forma programada, utilizaremos la extensión de consola enterprise CRON con las siguientes opciones:

Task
Seleccionaremos Send custom report (from template) by e-mail: Nos permitirá aplicar una plantilla de informe sobre agentes a nuestra elección, y programar su generación y envío.
Scheduled
En este campo especificaremos la frecuencia con que se enviara el informe.
Next Execution
En este campo estableceremos la fecha y hora de la siguiente ejecución.
Template to build
En este campo seleccionaremos la plantilla del informe que se quiere generar.
Agents
Seleccionaremos los agentes sobre los que aplicar la plantilla.
Send to mail
En este campo se pone la dirección de mail a la que se enviará el informe.

Cron report template.png



1.6.3 Configuración

Para que funcione el envío del email, debe configurarse previamente en las opciones de Pandora FMS.

Para editar esta configuración acceda a Configuration > Setup > Enterprise

Menu config enterprise.png

Deberá configurar correctamente la sección del correo electrónico situada al final de la página:

Menu config enterprise mail.png

2 Report Templates

Report templates are components which allow you to parametrize the report's creation. It also allows you to apply them onto a set of agents and to easily create a lot of reports.

The report templates are components which allow you to parametrize the report creation that could be applied onto a group of agents and to quickly and easily create a big number of reports. Each element of the templates is going to match to an agent or module by a regular expression or substring, rendering this system very flexible.

Templates1.png

As you can see on the previous image, a report template will be created, containing elements or items. Each one of them is going to generate one or more report items. If they're applied, they fit to some agents or modules of the ones selected within that application.


The type of template items will be almost all the ones that are available within the reports, e.g. 'average value', 'SLA', 'agent events', etc.

Now we're going to describe three examples of template items.

2.1 Examples

In order to access the template's administration menu, please click on 'Operation' -> 'Reporting' -> 'Custom Reporting' and click on the 'list templates' button:

Template main.png

This template examples are containing three template items mentioned below:

  • An automated combined graph which allows you to create graphs on the modules which coincide within the application.
  • A 'Top N' report.
  • An agent event report.

Templates list items1.jpeg

2.2 Example 1: The Automated Combined Graph

This element is going to generate graphs to display the incoming network traffic of the selected agents. In order to do this, it's going to create combined graphs for each agent which holds a module name like "Network Traffic (Incoming)" and "Network Traffic (Outgoing)". Besides creating combined graphs, it's going to add them to the generated report.

Template automatic graph.png

Within this example, we've decided to select a form to control the target modules. It's also possible to select the modules by using a regular expression, filling out the field 'Modules to match (Free text)'. For example, the regular expression .*cpu.* would be applied on modules like e.g. 'cpu_user', 'total_cpu_usage', 'cpu', etc.

Another important control for this type of template item is 'Create a graph for each agent' which allows the creation of a combined graph for each agent or to create a combined graph for all the agents an modules that coincide once it has been selected.

2.3 Example 2: Top N

This item is going to generate a report of the 'Top N' type, showing the most demanded 5 CPUs of the last day. This item applies to all agents with modules which contain the literal "CPU User" element.

Template topn.png

As you can see on the image, the modules are not going to be searched literally, but a regular expression is used here. This performance is selected by clicking on the box next to the agent's name ('exact match'). If you leave it blank, the agent's name is going to match on all agents selected during the application.

2.4 Example 3: Agent Events

This element is going to generate a report of the events generated on the last day for all selected agents.

Template agentevent.png

As you can see in the 'Agent' field, the regular expression '.*' has been used. It symbolizes any alphanumeric string, so it will be applied on any selected agent.

2.5 Aplicando una plantilla

Una vez hayamos definido todos los ítems de plantilla que necesitemos podemos aplicar o instanciar esta plantilla a través de dos métodos:

2.5.1 Aplicación directa.

Podremos aplicar y visualizar directamente un informe de plantilla haciendo clic en cualquiera de los iconos de formato que aparecen en la fila que ocupa nuestra plantilla:

Template direct.png

Se nos mostrará un pop-up donde podremos elegir los agentes sobre los que se aplicará esta plantilla de informe:

Template direct2.png

2.5.2 Asistente de plantillas

Podemos hacer uso del asistente de plantillas - Template Wizard si necesitamos instanciar nuestra plantilla de informe en un informe real para tenerlo disponible en la lista de informes de Pandora FMS.


Template application.png


Podremos activar la casilla de verificación Create report per agent si queremos que se genere un informe por cada agente seleccionado. Si no lo activamos, se generará un informe general con toda la información.

  • En caso de que se genere un informe por agente el título del informe será de la forma: [título de la plantilla] - [nombre agente] ([nombre agente])
  • En caso de que se genere un informe total el título será de la forma: [título del informe] - agents ([número de agentes]) - [fecha]


Template application1.png


Para la gráfica combinada automática se creó un elemento de tipo "custom_graph". Esta gráfica tiene dos elementos para los módulos "Read Disk Latency" y "Write Disk Latency".



Template application custom graph1.png



Editando la gráfica personalizada se ve que tiene los dos módulos:



Template application custom graph.png



Para el informe Top N se creó un elemento con una expresión basada en el texto cpu

Template topn.png

Visualizando el informe renderizado se ven las diez CPUs con mayor carga:



Template application top n1.png



Para el informe de eventos del agente se crearán tres elementos (recordemos que se seleccionaron todos los agentes mediante .*):



Template application eventagent.png

2.6 Editing the Template

Within the templates you're able to modify the general parameters of the template as shown on the picture below.

Template general.png

2.7 List of Templates

In order to access the template's list, please click on 'Administration' -> 'Manage Reports' -> 'Report Builder' and on the 'List Templates' button:

Template main.png

In this section, you may create new templates, edit existing ones, copy and delete them.

2.8 The Items List

In this section, you're able to review, edit, assort and delete items within a report template.

Template list item.png

2.9 The Item Editor

This editor was designed to create new items. The item types are the same as in the report section, but with two differences: The agent's name is a regular expression, e.g. 'oracle_agent[.]*'. It's going to match to the agent's names 'oracle_agent_1', 'oracle_agent_2', etc. If you leave it blank, this item is going to be applied onto all selected agents within the The Template Wizard.

The module's name can be filled out by activating the check box named 'Module exact match' or by a regular expression without activating this particular check box.

Template agentevent.png

2.10 Advanced Options

You may edit visual aspects for the results report like fonts, logos, headers, the first page or the report footer within this section.

Template advance.png

2.11 The Template Wizard

You can do the instructions explained here.

Template application.png



2.12 Limpieza de informes

Para borrar los informes creados en aplicaciones anteriores de una plantilla desde el Wizard se puede seleccionar una plantilla y hacer clic en el botón para borrar (botón de la escoba).

Template wizard cleanup.png



Esta acción eliminará todos los informes creados basados en esta plantilla automáticamente.

Go back to Pandora FMS Documentation Index