====== Glossary of terms ======

{{indexmenu_n>3}}

<WRAP center round todo 60%>

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

</WRAP>

<wrap #ks1 />
===== Basic Access and Advanced Access =====

These are two types access granted to users, module components and alerts.

   * Users with **basic access** will only be able to use the components and alerts **of this level**.
   * Users with **advanced access** will be able to use components and alerts **at any level**.

On the other hand, the Advanced type components are more configurable than the Basic type:

   * With the possibility of renaming them.
   * They offer the configuration of the actions in the alerts. In the basic type, the alerts will be created with the default actions.
   * More fields appear in your issue such as advanced fields. For example: units, macros in the case of local or network components of the plugin type, among others.

<wrap #ks2 />
===== Action =====

   * Execution that is carried out when an alert is triggered.
   * They can be parameterized through a series of fields.
   * It is possible to execute several actions for a single alert.

<wrap #ks3 />
===== ACL =====

   * Determine user permissions.
   * In Pandora FMS they are defined by assigning a user a profile over a group.

<wrap #ks4 />
===== Service Level Agreement (SLA) =====

   * The SLA is a negotiated agreement between two parties where one of them is the customer and the other is a service provider.
   * In Pandora FMS the breach of an SLA is reported when any component is outside the values considered normal. It takes into account the data stored in the database, but not the status changes of the modules, so the configuration of the FF Threshold of the modules is not taken into account to calculate their SLA.
   * In the presentation of reports, their reliability must also be defined to avoid problems, and also establish the **prioritization mode** ([[:en:documentation:pandorafms:management_and_operation:08_data_presentation_reports#items_de_sla|prioritization of the OK or prioritization of the a stranger]]).

<WRAP center round tip 90%>

All the SLAs understand the **unknown** periods as valid, since Pandora FMS cannot guarantee the status of the module if it does not have data from it. All periods in **planned stop** are also considered valid (since being in a planned stop situation it is assumed that the module situation is controlled and accepted) and periods in **warning status** (the service continues to be provided even in a non-optimal state).

</WRAP>

<wrap #ks5 />
===== Agent =====

An Agent in Pandora FMS is an organizational entity, usually a machine, system or host, which contains information from different checks called [[#module|Modules]], and belongs to a single group. It may be related to other agents ("parent-child").

<wrap #ks6 />
===== Software Agent =====

   * Service installed on computers to collect local information.
   * Stays running in the system to collect and send information from time to time, called an interval.
   * The Software Agent generates XML data files and sends them to the assigned PFMS server using the default [[:en:documentation:pandorafms:technical_reference:09_tentacle|Tentacle]] protocol.

<wrap #ks7 />
===== Alert =====

   * It has two possible states: triggered or not triggered.
   * Automatically perform actions such as sending email messages and other forms of notification.

<wrap #ks8 />
===== Module Creation Wizard =====

With the **Command Center (Metaconsole) module creation assistant** (Wizard) it will be possible to create modules of different types in the Instances in a simple and transparent way, using the module components and the alert templates. In the Wizard the different instances are not distinguished. All agents and modules will appear mixed up as if they were from the same source.

<wrap #ks9 />
===== Database =====

   * It is a set of data belonging to the same context and systematically stored for later use.
   * Pandora FMS accesses this data set through a standard query structured language (SQL).

<wrap #ks10 />
===== TCP Checks =====

   * They allow queries to be made to devices and computers through open ports.
   * They are used in the [[:en:documentation:pandorafms:introduction:01_introduction#monitorizacion_remota|Remote monitoring]] .

<wrap #ks11 />
===== SNMP Checks =====

   * They are [[#tcp_checks|TCP checks]] that use the SNMP protocol.

<wrap #ks12 />
===== Command =====

A command or order is an instruction that is carried out in an operating system, by request.tion of a user or by an application.

<wrap #ks13 />
===== Alert Command =====

   * Execution at system level carried out by the server when an [[#alert|alert]] is triggered.
   * External commands or custom scripts can be used.

<wrap #ks14 />
===== Comment or uncomment a parameter =====

Commenting is the process of placing **the parameter itself as a comment** by adding the special character to the start of its line (or uncommenting, thus activating the parameter by removing the special character).

<WRAP center round box 90%>

# This line is a comment. parameter1 value1

# The following parameter is "commented out" and will not be read or taken into account: # parameter2 value2

</WRAP>

<wrap #ks15 />
===== Component =====

A **component ** is a template to create a module.

Could be:

  * Local.
  * Network:
    * Network type.
    * Plugin type.
    * WMI type.

<wrap #ks16 />
===== Console =====

The Pandora FMS Console (Web Console) is the interface that allows you to manage PFMS through the browser.

<wrap #ks17 />
===== DAEMON =====

A DAEMON (short for "Disk And Execution Monitor") is a non-graphical interface program that runs at the operating system level with little or no interaction from users.

<wrap #ks18 />
===== Dependency =====

Set of files, generally compiled into machine language, with common functions that can be used by one or more applications in an operating system.

<wrap #ks19 />
===== Downgrade =====

   * Generally an update or **upgrade** contains improved components compared to the one it replaces, but sometimes there is a problem.
   * For these unique cases, there is talk of a **downgrade** for [[:en:documentation:pandorafms:installation:02_anexo_upgrade#actualizacion_a_una_versión_anterior|return a PFMS server]] to the previous version installed.

<wrap #ks20 />
===== *nix environments =====

Abbreviation to indicate Unix® and GNU/Linux® environments.

<wrap #ks21 />
===== State CRITICAL, WARNING =====

   * NORMAL, WARNING and CRITICAL are the three possible states of a Module.
   * The WARNING and CRITICAL states usually indicate error conditions of different severity.
   * Pandora FMS allows you to independently define different thresholds for the WARNING and CRITICAL states of each module.

<wrap #ks22 />
===== Status UNKNOWN =====

Status of a Module that has not received data for more than twice its interval.

<wrap #ks23 />
===== Event =====

   * Any incident that occurs in monitored systems.
   * The information it displays ranges from any change in the status of a module, alerts launched or recovered, to system reboots.

<wrap #ks24 />
===== False positive/negative =====

   * When a check returns an error and this has not really occurred, we are talking about a false positive.
   * When it does not return any error and it has occurred, we are talking about a false negative.

<wrap #ks25 />
===== Data files / Data XML =====

   * Data files generated by Pandora FMS Software Agents.
   * In addition to the information on the Agent modules, it contains information about the Agent itself (version, operating system, etc.).

<wrap #ks26 />
===== Hibernate or hibernate =====

Used in computing to describe the process of completely saving whatever is in RAM (data and/or running programs) to a fixed storage device by an operating system.

<wrap #ks27 />
===== Instance =====

Normal installation of Pandora FMS configured to enable its access through the **Command Center** (Metaconsole) and optionally to replicate its events to it.

<wrap #ks28 />
===== Reverse Interval =====

   * It is used to define non-contiguous ranges in the [[#threshold|thresholds]].
   * In string type modules, the threshold is defined as a substring.

<wrap #ks29 />
===== Kernel =====

It is the software that communicates the hardware with the rest of the software installed on a computer and constitutes the essence of an operating system.

<wrap #ks30 />
===== Merging (code) =====

   * Used to refer to merging of source code, such as a new feature.
   * It can also be applied to other similar processes such as merging two databases from different servers into a third server.

<wrap #ks31 />
===== Metaconsole =====

Now called **Command Center**, Web console that allows centralized management of many of the functions of the PFMS nodes (users, agents, etc.).

<wrap #ks32 />
===== Debug Mode =====

Provides detailed step-by-step process and parameter information when an application or operating system is running to make it easier to fix code exceptions ("errors").

<wrap #ks33 />
===== Module =====

   * A Module is a bound entitymica of information that stores numerical or alphanumeric/text type values.
   * Each Module only stores data from an individual check (CPU, RAM, traffic...).
   * The modules are contained within the agents, and always associated to a single Agent.
   * An Agent in turn can contain multiple modules.

<wrap #ks34 />
===== Asynchronous monitoring =====

A module is asynchronous when it returns data based on changes or events, which may or may not occur. In these cases we then speak of asynchronous monitoring.

<wrap #ks35 />
===== Synchronous monitoring =====

We say that a module is synchronous when it returns data at regular intervals. For example, a temperature measurement every 5 minutes.

<wrap #ks36 />
===== Mosaic =====

   * It is a simultaneous appearance, generally minimized and on the same plane, of different documents or parts of them.
   * Used in the GIS Console (Geographic Information System).

<wrap #ks37 />
===== OpenSSH =====

Set of applications that allow encrypted communications over a network, using the SSH protocol.

<wrap #ks38 />
===== Pandora Web Robot Daemon =====

**PWRD** provides the [[http://pandorafms.com/library/pandora-ux-and-wux-pwr-recorder/|necessary tools]] to automate web browsing sessions for later monitoring with [[:en:documentation:pandorafms:monitoring:13_user_monitorization|WUX]].

<wrap #ks39 />
===== Package =====

A package contains a program or its suite packaged in a certain format ready to be installed on a certain operating system and version.

<wrap #ks40 />
===== Profile =====

   * Defines the permissions on the different possible operations in Pandora FMS: view an Agent, modify it, assign alerts, etc.
   * Profiles are associated with users for certain groups.

<wrap #ks41 />
===== Alert Template =====

It specifies the trigger conditions for the alert, which may depend on the value or status of a Module, and other details such as the maximum number of times that it will be triggered in a given interval or an operating hour range.

<wrap #ks42 />
===== SNMP Polling =====

It is the consultation process on a regular basis and [[:en:documentation:pandorafms:monitoring:03_remote_monitoring#introduccion_a_la_monitorizacion_snmp|via SNMP]] from PFMS to the monitored devices.

<wrap #ks43 />
===== FlipFlop Protection =====

   * FlipFlop (FF) is known as a usual phenomenon in monitoring: when a value oscillates frequently between alternative values (BAD/GOOD) that make its interpretation difficult.
   * The flip flop protection of a Module indicates the number of times the state change condition must occur for the state change to occur.
   * This allows to protect a Module from false positives/negatives.

<wrap #ks44 />
===== Record Rotation =====

   * Log rotation (**log rotation**) is an automated process used in system administration in which log files are compressed, moved (archived), renamed, or deleted
   * New incoming log data is directed to a new file, usually in the same location.

<wrap #ks45 />
===== Server =====

   * The PFMS server processes the information, collected in different ways.
   * Run alerts, apply policies and send the information to the database.
   * The Pandora FMS server also contains different components that perform their own functions (eg [[:en:documentation:pandorafms:introduction:02_architecture#data_server|Data server]]) and can be enabled or disabled depending on the needs.

<wrap #ks46 />
===== Remote Server =====

Server that is on the network and is not the local server.

<wrap #ks47 />
===== Shell or command line =====

Interface that allows the introduction of commands on a machine through the keyboard.

<wrap #ks48 />
===== Native Software =====

Native software or native data formats are those that were designed to run and/or process on a particular operating system.

<wrap #ks49 />
===== Superadmin =====

As in [[:en:documentation:pandorafms:technical_annexes:15_security_architecture#superuser_access|GNU/Linux there is a superuser]] named **root** , in Pandora FMS there is also a superuser named **superadmin**:

   * When installing a full PFMS server, by default, two users are included: ''admin'' and ''internal_API''.
   * This ''admin'' user is the first **superadmin** but not the only one.
   * In addition to superadmin, administrator users can be created in Pandora FMS, [[:en:documentation:pandorafms:management_and_operation:11_managing_and_administration#list_of_profiles|through the PM access bit]].
   * Users with PM bit are practically the same as a super administrator, with the exception that, for example, they cannot create Alert Commands, and other limitations, such as not being able to define other users as **superadmin**.

<WRAP center round important 90%>

For security reasons there are functions that only a super admin can access.

</WRAP>

<wrap #ks50 />
===== SVN/Subversion/Repocode site =====

Version control system that keeps a repository with the different versions of the files that make up a project throughout its life.

<wrap #ks51 />
===== Tarball=====

Like a [[#package|package]], it contains a program or set of programs packaged in TAR format, but unlike this one it does not contain information on how to install it and in principle they are not specific for a given operating system.

<wrap #ks52 />
===== Tentacle =====

It is the data transfer protocol used by the Software Agents and the Satellite Server to send data to the Pandora FMS server.

[[:en:documentation:pandorafms:technical_reference:09_tentacle|Tentacle]] is cross-platform and uses port 41121 (assigned by IANA) by default.

<wrap #ks53 />
===== Threshold =====

Minimum or maximum value of a module from which a change of state occurs.

<wrap #ks54 />
===== Alert threshold =====

It is the time interval in which the restrictions defined when configuring the alert template apply.

<wrap #ks55 />
===== root user =====

In [[#nix_environments|*nix environments]] is the user dedicated to the administration of an operating system, with special privileges to install, configure and maintain the software, among other tasks. Other users can inherit these privileges if they belong to the same **root** user group.

<wrap #ks56 />
===== Watchdog =====

Within Pandora FMS there is a functionality that verifies if a system is running and if it is down, it restarts it.

<wrap #ks57 />
===== Widget =====

   * A graphical widget provides a single point of interaction for direct manipulation of a given type of data.
   * Any widget displays a user-modifiable arrangement of information, such as a window or text box.
   * Combined in one application, they house all the data processed by the same and the interactions available on this data.

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