[Rebranding] en help
This commit is contained in:
parent
477fc9d22a
commit
ce946c1093
|
@ -6,4 +6,4 @@
|
|||
|
||||
<h1>Alert commands</h1>
|
||||
|
||||
<p>Pandora FMS's reaction to a value stating "out of range" can be diverse: it can be recorder on the syslog, an email or SMS alert can be sent, or the execution of any script found on the Pandora FMS device and that can be properly processed.</p>
|
||||
<p><?php echo get_product_name();?>'s reaction to a value stating "out of range" can be diverse: it can be recorder on the syslog, an email or SMS alert can be sent, or the execution of any script found on the <?php echo get_product_name();?> device and that can be properly processed.</p>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
<b>Name:</b> Name assigned to the action.<br>
|
||||
<b>Group:</b> Group the action belongs to. <br>
|
||||
<b>Command:</b> In this field the command that will be used in case the alert is triggered can be defined. Users can choose from the different commands that are defined on Pandora. Depending on the command chosen a variable group of fields will be shown (specific to each command) <br>
|
||||
<b>Command:</b> In this field the command that will be used in case the alert is triggered can be defined. Users can choose from the different commands that are defined on <?php echo get_product_name();?>. Depending on the command chosen a variable group of fields will be shown (specific to each command) <br>
|
||||
<b>Threshold:</b> The action’s execution threshold. <br>
|
||||
<b>Command Preview:</b> In this field, which can’t be edited, the command that will be run on the system will appear automatically. <br>
|
||||
<b>Field X:</b> In these fields:<br><br>
|
||||
|
@ -48,7 +48,7 @@ Apart from the defined module macros, the following macros are also available:
|
|||
<li>_data_: Module data that caused the alert to fire.</li>
|
||||
<li>_email_tag_: Emails associated to the module’s tags.</li>
|
||||
<li>_event_cfX_: (Only event alerts) Key of the event custom field that fired the alert. For example, if there is a custom field whose key is IPAM, its value can be obtained using the _event_cfIPAM_ macro.</li>
|
||||
<li>_event_description_: (Only event alerts) The textual description of the Pandora FMS event.</li>
|
||||
<li>_event_description_: (Only event alerts) The textual description of the <?php echo get_product_name();?> event.</li>
|
||||
<li>_event_extra_id_ : (Only event alerts) Extra id.</li>
|
||||
<li>_event_id_: (Only event alerts) ID of the event that triggered the alert.</li>
|
||||
<li>_event_text_severity_: (Only event alerts) Event text severity (Maintenance, Informational, Normal Minor, Warning, Major, Critical).</li>
|
||||
|
@ -71,7 +71,7 @@ Apart from the defined module macros, the following macros are also available:
|
|||
<li>_groupcustomid_: Group custom ID.</li>
|
||||
<li>_groupother_: Other information about the group. Configured when the group is created.</li>
|
||||
<li>_homeurl_ : It is a link of the public URL this must be configured in the general options of the setup.</li>
|
||||
<li>_id_agent_: Agent’s ID, useful for building a direct URL that redirects to a Pandora FMS console webpage.</li>
|
||||
<li>_id_agent_: Agent’s ID, useful for building a direct URL that redirects to a <?php echo get_product_name();?> console webpage.</li>
|
||||
<li>_id_alert_: Alert’s numeric ID (unique), used to correlate the alert with third party software.</li>
|
||||
<li>_id_group_ : Agent group ID.</li>
|
||||
<li>_id_module_: Module ID.</li>
|
||||
|
|
|
@ -33,7 +33,7 @@ Besides the defined module macros, the following macros are available:
|
|||
<li>_data_: Module data that caused the alert to fire.</li>
|
||||
<li>_email_tag_: Emails associated to the module’s tags.</li>
|
||||
<li>_event_cfX_: (Only event alerts) Key of the event custom field that fired the alert. For example, if there is a custom field whose key is IPAM, its value can be obtained using the _event_cfIPAM_ macro.</li>
|
||||
<li>_event_description_: (Only event alerts) The textual description of the Pandora FMS event.</li>
|
||||
<li>_event_description_: (Only event alerts) The textual description of the <?php echo get_product_name();?> event.</li>
|
||||
<li>_event_extra_id_: (Only event alerts) Extra id.</li>
|
||||
<li>_event_id_: (Only event alerts) ID of the event that triggered the alert.</li>
|
||||
<li>_event_text_severity_: (Only event alerts) Event text severity (Maintenance, Informational, Normal Minor, Warning, Major, Critical).</li>
|
||||
|
@ -56,7 +56,7 @@ Besides the defined module macros, the following macros are available:
|
|||
<li>_groupcustomid_: Group custom ID.</li>
|
||||
<li>_groupother_: Other information about the group. Configured when the group is created.</li>
|
||||
<li>_homeurl_ : It is a link of the public URL this must be configured in the general options of the setup.</li>
|
||||
<li>_id_agent_: Agent’s ID, useful for building a direct URL that redirects to a Pandora FMS console webpage.</li>
|
||||
<li>_id_agent_: Agent’s ID, useful for building a direct URL that redirects to a <?php echo get_product_name();?> console webpage.</li>
|
||||
<li>_id_alert_: Alert’s numeric ID (unique), used to correlate the alert with third party software.</li>
|
||||
<li>_id_group_ : Agent group ID.</li>
|
||||
<li>_id_module_: Module ID.</li>
|
||||
|
|
|
@ -5,4 +5,4 @@
|
|||
?>
|
||||
<h1>Alert recovery</h1>
|
||||
|
||||
It defines whether Pandora FMS launches another alert when the alert’s condition is recovered. It has the same “field1”, but adds "[RECOVER]" to “field2” and “field3”. It is disabled by default.
|
||||
It defines whether <?php echo get_product_name();?> launches another alert when the alert’s condition is recovered. It has the same “field1”, but adds "[RECOVER]" to “field2” and “field3”. It is disabled by default.
|
||||
|
|
|
@ -7,9 +7,9 @@
|
|||
|
||||
There are some preset alerts, on which it’s very likely you will have to make adjustments, in case your system does not provide the internal commands needed to execute those alerts. The development team has tested these alerts with Red Hat Enterprise Linux (RHEL), CentOS, Debian and Ubuntu Server.
|
||||
<ul>
|
||||
<li><b>eMail</b>: Sends an e-mail from Pandora FMS’ Server. It uses your local sendmail. If you have installed another kind of local mailer or do not have one, you should install and configure sendmail or any equivalent (and check the syntax) to be able to use this service. Pandora FMS relies on system tools to execute almost every alert, it will be necessary to check that those commands work properly on your system.</li>
|
||||
<li><b>Internal audit</b>: This is the only "internal" alert, it writes the incident in Pandora FMS’ internal auditing system. This is stored on Pandora FMS’ Database and can be reviewed from the web console with the Pandora FMS audit viewer.</li>
|
||||
<li><b>Pandora FMS’ Alertlog</b>: Saves information about alerts inside a text file (.log). Use this type of alert to generate log files using the format you need. To do so, you will need to modify the command so that it will use the format and file you want. Note that Pandora FMS does not handle file rotation, and that Pandora FMS’ Server process that executes the alert will need access to the log file in order to write on it.</li>
|
||||
<li><b>Pandora FMS Events</b>: This alert creates an special event on the Pandora FMS event manager.</li>
|
||||
<li><b>eMail</b>: Sends an e-mail from <?php echo get_product_name();?> Server. It uses your local sendmail. If you have installed another kind of local mailer or do not have one, you should install and configure sendmail or any equivalent (and check the syntax) to be able to use this service. <?php echo get_product_name();?> relies on system tools to execute almost every alert, it will be necessary to check that those commands work properly on your system.</li>
|
||||
<li><b>Internal audit</b>: This is the only "internal" alert, it writes the incident in <?php echo get_product_name();?>'s' internal auditing system. This is stored on <?php echo get_product_name();?>'s Database and can be reviewed from the web console with the <?php echo get_product_name();?> audit viewer.</li>
|
||||
<li><b><?php echo get_product_name();?> Alertlog</b>: Saves information about alerts inside a text file (.log). Use this type of alert to generate log files using the format you need. To do so, you will need to modify the command so that it will use the format and file you want. Note that <?php echo get_product_name();?> does not handle file rotation, and that <?php echo get_product_name();?>'s' Server process that executes the alert will need access to the log file in order to write on it.</li>
|
||||
<li><b><?php echo get_product_name();?> Events</b>: This alert creates an special event on the <?php echo get_product_name();?> event manager.</li>
|
||||
</ul>
|
||||
These alerts are predefined and cannot be deleted, however the user can define new ones that can use custom commands, and add them using Alert management.
|
||||
|
|
|
@ -14,7 +14,7 @@
|
|||
|
||||
<li><b>Alert type:</b> This can be selected from the previously generated alert list.</li>
|
||||
<li><b>Max. Value:</b> Defines the maximum value for a module. Any value above that threshold will trigger the alert.</li>
|
||||
<li><b>Min. Value:</b> Defines the minimum value for a module. Any value below that will trigger the alert. The ”max." & "min." couple are key values when defining an alert, since they define the range for normal values. Outside that range Pandora FMS will trigger the alert.</li>
|
||||
<li><b>Min. Value:</b> Defines the minimum value for a module. Any value below that will trigger the alert. The ”max." & "min." couple are key values when defining an alert, since they define the range for normal values. Outside that range <?php echo get_product_name();?> will trigger the alert.</li>
|
||||
<li><b>Alert text:</b> In the case of string modules you can define a regular expression or a substring to match the contents of a data module in order to trigger the alert.</li>
|
||||
<li><b>Time from / Time to:</b> This defines a “valid” timespan to trigger alert.</li>
|
||||
<li><b>Description:</b> Describes the function of the alert, and it is useful to identify the alert among the others in the general view of alerts.</li>
|
||||
|
|
|
@ -3,22 +3,22 @@
|
|||
* @package Include/help/es
|
||||
*/
|
||||
?>
|
||||
<h1>Pandora FMS’ Quick Guide to Alert Configuration </h1>
|
||||
<h1><?php echo get_product_name();?>'s Quick Guide to Alert Configuration </h1>
|
||||
<br>
|
||||
<b>Introduction to the Current Alert System</b><br>
|
||||
<br>
|
||||
People usually complain about the complexity of defining alerts on
|
||||
Pandora FMS. Before, until version 2.0, alerts were easier to
|
||||
<?php echo get_product_name();?>. Before, until version 2.0, alerts were easier to
|
||||
configure. For each alert the condition and what it did when the action was not completed was defined for each case. It was a more "intuitive"
|
||||
thing (but it also had fields such as the "threshold" alert that caused
|
||||
many headaches to more than one person!). It was very simple, but, was
|
||||
it worth it ?<br>
|
||||
<br>
|
||||
One of our “star” users (we mention this because he had A LOT of agents installed, and also knew the inner workings of Pandora FMS quite well) mentioned that creating an alert for 2000 modules was tremendously complicated, especially when it was necessary to modify something for all of them. Due to this, and other issues, we decided to modify the alert system so that it could be modular, so that the alert’s definition and its triggering condition (template) could be separated from the action that has to be executed when the alert is triggered (alert action) and from the command that is run within the action (Alert command). The combination of an alert template with a module triggers the alert itself.<br><br>
|
||||
One of our “star” users (we mention this because he had A LOT of agents installed, and also knew the inner workings of <?php echo get_product_name();?> quite well) mentioned that creating an alert for 2000 modules was tremendously complicated, especially when it was necessary to modify something for all of them. Due to this, and other issues, we decided to modify the alert system so that it could be modular, so that the alert’s definition and its triggering condition (template) could be separated from the action that has to be executed when the alert is triggered (alert action) and from the command that is run within the action (Alert command). The combination of an alert template with a module triggers the alert itself.<br><br>
|
||||
|
||||
This way, if I have 1000 devices with a module named “Host Alive” and all of them have a related alert template named “Host Down” that when triggered executes an action named “Warn the Operator”, and I wish to change the minimum number of alerts that must be fired before the Operator is warned, I only have to change the definition on the template instead of going one by one over the 1000 alerts to modify that specific condition.<br><br>
|
||||
|
||||
Many users only manage a few dozen devices, but there are many users with hundreds—even thousands—of systems monitored with Pandora FMS, and we have to try and make it so that with Pandora FMS all types of environments can be managed.<br>
|
||||
Many users only manage a few dozen devices, but there are many users with hundreds—even thousands—of systems monitored with <?php echo get_product_name();?>, and we have to try and make it so that with <?php echo get_product_name();?> all types of environments can be managed.<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
@ -118,9 +118,9 @@ html_print_image("images/help/alert07.png", false,
|
|||
array('width' => '550px'));
|
||||
?>
|
||||
<br>
|
||||
We’ve now made it so that the system can discriminate when something is right (OK status, marked in GREEN) and when something is wrong (CRITICAL status, marked in RED). Now what we have to do is make the system send us an email when the module reaches that status. For this we’ll use Pandora FMS’ alert system.<br>
|
||||
We’ve now made it so that the system can discriminate when something is right (OK status, marked in GREEN) and when something is wrong (CRITICAL status, marked in RED). Now what we have to do is make the system send us an email when the module reaches that status. For this we’ll use <?php echo get_product_name();?>'s alert system.<br>
|
||||
<br>
|
||||
For this we need to make sure there is a command available that can do what we need it to (in this case, send an email). This example is easy because there is a predefined command on Pandora FMS that is meant to automate email sending, meaning this is already done.<br>
|
||||
For this we need to make sure there is a command available that can do what we need it to (in this case, send an email). This example is easy because there is a predefined command on <?php echo get_product_name();?> that is meant to automate email sending, meaning this is already done.<br>
|
||||
<br>
|
||||
<b>Configuring the Alert</b><br>
|
||||
<br>
|
||||
|
@ -133,7 +133,7 @@ html_print_image("images/help/alert08.png", false,
|
|||
array('width' => '550px'));
|
||||
?>
|
||||
<br>
|
||||
This action uses the “send email” command, and is really simple, since only one field from the form needs to be filled out (Field1) leaving the other two empty. This is one of the most confusing parts of the alert system on Pandora FMS: what are field1, field2 and field3?<br>
|
||||
This action uses the “send email” command, and is really simple, since only one field from the form needs to be filled out (Field1) leaving the other two empty. This is one of the most confusing parts of the alert system on <?php echo get_product_name();?>: what are field1, field2 and field3?<br>
|
||||
<br>
|
||||
These fields are the ones used to “pass” the information on from the alert template to the command, and at the same time from that command to the next. This way both the template and the command can provide different information to the command. In this case, the command only establishes field1 and leaves field2 and field3 to be filled by the template, like what is shown next.<br>
|
||||
<br>
|
||||
|
@ -163,19 +163,19 @@ The most critical parameters here are the following:<br>
|
|||
<br>
|
||||
<i>Time threshold:</i> Set to one day by default. If a module is constantly down during, for example, one day and and we have set a value of 5 minutes here, it means that alerts would be sent every 5 minutes. If we leave it at one day (24hrs.), it’ll only send the alert once, when it goes down. If the module recovers, and drops again, it’ll send another alert, but if it remains down from the second drop, it won’t send more alerts until 24hrs have gone by.<br>
|
||||
<br>
|
||||
<i>Min. Number of alerts:</i> The minimum number of times that a condition will have to be met (in this case, that the module is in CRITICAL status) before Pandora FMS runs the actions linked to the alert template. It’s a way to avoid false positives “flooding” you with alerts, or so that an erratic behaviour doesn’t lead to multiply alerts going off. If we place a ‘1’ here it means that until this doesn’t happen at least once, it won’t be taken into account. If i set a value of ‘0’ the first time the module returns an error, the alert will go off.<br>
|
||||
<i>Min. Number of alerts:</i> The minimum number of times that a condition will have to be met (in this case, that the module is in CRITICAL status) before <?php echo get_product_name();?> runs the actions linked to the alert template. It’s a way to avoid false positives “flooding” you with alerts, or so that an erratic behaviour doesn’t lead to multiply alerts going off. If we place a ‘1’ here it means that until this doesn’t happen at least once, it won’t be taken into account. If i set a value of ‘0’ the first time the module returns an error, the alert will go off.<br>
|
||||
<br>
|
||||
<i>Max. Number of alerts:</i> A value of 1 means that it’ll only execute the action once. If we have ’10’ set here, it’ll run the action 10 times. This is a way to limit the number of times an alert can go off.<br>
|
||||
<br>
|
||||
Again, we can see the fields “field1, field2, field3”. Now we can see that field1 is blank, which is precisely the one we’ve defined when configuring the action. Field2 and Field3 are used for the “send mail” action to define the subject and the message’s body, whilst Field1 is used to define the recipient(s) of said message (addresses must be separated by commas). Therefore the template, combined with the use of some macros, is defining the subject and alert message in a way that, in our case, we would receive a message like the following (supposing the agent where the module is placed is named “Farscape”):<br>
|
||||
<br>
|
||||
<i>To: sancho.lerena@notexist.ocm<br>
|
||||
Subject: [PANDORA] Farscape cpu_sys is in CRITICAL status with a value
|
||||
Subject: [MONITORING] Farscape cpu_sys is in CRITICAL status with a value
|
||||
of 20<br>
|
||||
Message body:<br>
|
||||
<br>
|
||||
This is an automated alert generated by Pandora FMS<br>
|
||||
Please contact your Pandora FMS operator for more information. *DO NOT* reply to
|
||||
This is an automated alert generated by <?php echo get_product_name();?><br>
|
||||
Please contact your <?php echo get_product_name();?> operator for more information. *DO NOT* reply to
|
||||
this email.<br>
|
||||
</i><br>
|
||||
Given that the default action is the one we have defined previously, all
|
||||
|
@ -229,7 +229,7 @@ Alerts in standby are useful because they can be viewed without interfering with
|
|||
<br>
|
||||
<b>Using Alert Commands other than the “send email” command</b><br>
|
||||
<br>
|
||||
The email, as a command is internal to Pandora FMS and can’t be configured, this means Field1, Field2 and Field3 are fields that are preset to be used as the recipient, subject and body for the email alert. But, what happens when we want to execute a different, more customised alert?<br>
|
||||
The email, as a command is internal to <?php echo get_product_name();?> and can’t be configured, this means Field1, Field2 and Field3 are fields that are preset to be used as the recipient, subject and body for the email alert. But, what happens when we want to execute a different, more customised alert?<br>
|
||||
<br>
|
||||
We’ll define a new, totally customised command. Imagine that we want to generate a log file with each alert we find. The format for that log file has to be something like:<br>
|
||||
<br>
|
||||
|
@ -262,9 +262,9 @@ We can see that the alert was fired at 18:17:10 because of the " farscape"
|
|||
agent, in the "cpu_sys" module, with a data value of "23.00" and with the
|
||||
description that we chose when we defined the action.<br>
|
||||
<br>
|
||||
Since the command’s execution, the field order and other affairs can make it so we don’t really understand how it’s executed at the end of the command, the easiest thing to do is to activate the Pandora server debug traces (verbose 10) in the configuration file for the Pandora server ‘/etc/pandora/pandora_server.conf’, and then reset the server
|
||||
Since the command’s execution, the field order and other affairs can make it so we don’t really understand how it’s executed at the end of the command, the easiest thing to do is to activate the <?php echo get_product_name();?> server debug traces (verbose 10) in the configuration file for the <?php echo get_product_name();?> server ‘/etc/pandora/pandora_server.conf’, and then reset the server
|
||||
(/etc/init.d/pandora_server restart). After, we take a look at the file
|
||||
/var/log/pandora/pandora_server.log and look for the exact line with the
|
||||
alert command execution that we've defined, to see how the Pandora FMS
|
||||
alert command execution that we've defined, to see how the <?php echo get_product_name();?>
|
||||
server is launching and executing the command.<br>
|
||||
<br>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
</div>
|
||||
<br>
|
||||
<p>
|
||||
This option should be assigned to avoid an “alert storm” that can come in because a group of agents are unreachable. This type of behaviour occurs when an intermediary device, like for example a router, is down and all devices behind it, therefore, cannot be reached. Probably these devices aren’t down and chances indicate that they’re working with another router in HA mode. But, if nothing is done, it’s likely for Pandora FMS to think that they’re down since they can’t be tested using a Remote ICMP Proc test (a Ping check).
|
||||
This option should be assigned to avoid an “alert storm” that can come in because a group of agents are unreachable. This type of behaviour occurs when an intermediary device, like for example a router, is down and all devices behind it, therefore, cannot be reached. Probably these devices aren’t down and chances indicate that they’re working with another router in HA mode. But, if nothing is done, it’s likely for <?php echo get_product_name();?> to think that they’re down since they can’t be tested using a Remote ICMP Proc test (a Ping check).
|
||||
<br><br>
|
||||
When you enable <i>cascade protection</i> for an agent, this means that if any of its parents has a CRITICAL alert fired, then the agent’s alerts <strong>WILL NOT BE</strong> fired. If the agent's parent has a module in CRITICAL or several alerts with less criticality than CRITICAL, alerts from the agent will be fired as normal if needed. Cascade protection checks parent alerts with CRITICAL priority, including the correlated alerts assigned to the parent.
|
||||
<br><br>
|
||||
|
@ -23,7 +23,7 @@ If you want to use an advanced cascade protection system, just use correlation a
|
|||
<br>
|
||||
</div>
|
||||
<p>
|
||||
This option should be assigned to avoid an “alert storm” that can come in because a group of agents are unreachable. This type of behaviour occurs when an intermediary device, like for example a router, is down and all devices behind it, therefore, cannot be reached. Probably these devices aren’t down and chances indicate that they’re working with another router in HA mode. But, if nothing is done, it’s likely for Pandora FMS to think that they’re down since they can’t be tested using a Remote ICMP Proc test (a Ping check).
|
||||
This option should be assigned to avoid an “alert storm” that can come in because a group of agents are unreachable. This type of behaviour occurs when an intermediary device, like for example a router, is down and all devices behind it, therefore, cannot be reached. Probably these devices aren’t down and chances indicate that they’re working with another router in HA mode. But, if nothing is done, it’s likely for <?php echo get_product_name();?> to think that they’re down since they can’t be tested using a Remote ICMP Proc test (a Ping check).
|
||||
<br><br>
|
||||
When you enable <i>cascade protection</i> for an module, this means that if this parent agent module has a CRITICAL alert fired, then agent alerts <strong>WILL NOT BE</strong> fired.
|
||||
<br><br>
|
||||
|
|
|
@ -3,6 +3,6 @@
|
|||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Categories in Pandora FMS</h1>
|
||||
<h1>Categories in <?php echo get_product_name();?></h1>
|
||||
On the system some categories can be created and configured to later be assigned to any module desired. <br>
|
||||
The only user that has the permits to create and configure these categories is the administrator and they can be used to apply a “fee” to modules depending on the category the are sorted into.
|
||||
|
|
|
@ -10,14 +10,14 @@ This page is the place to configure a GIS Map.
|
|||
</p>
|
||||
<h2>Map Name</h2>
|
||||
<p>
|
||||
Each map has a desciptive name used to recognice the map within Pandora FMS.
|
||||
Each map has a desciptive name used to recognice the map within <?php echo get_product_name();?>.
|
||||
</p>
|
||||
<h2>Select Connections</h2>
|
||||
<p>
|
||||
The first step is to select the main <strong>connection</strong> used in this GIS Map. At least one connection must be selected to configure the GIS Map, but it's possible to add more by pressing the <?php html_print_image("images/add.png", false, array("alt" => "Add")); ?> (Add) icon.
|
||||
</p>
|
||||
<p>
|
||||
When the firs connection is set, Pandora FMS asks if you want to use the default values of the connection for the map, to avoid to write again all the information. Also if the default connection for the map is changed (using the radio button), Pandora FMS will ask again if you want to use the values of the new default connection.
|
||||
When the firs connection is set, <?php echo get_product_name();?> asks if you want to use the default values of the connection for the map, to avoid to write again all the information. Also if the default connection for the map is changed (using the radio button), <?php echo get_product_name();?> will ask again if you want to use the values of the new default connection.
|
||||
</p>
|
||||
<h2>Map Paramteres</h2>
|
||||
<p>
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Unknown modules in Pandora</h1>
|
||||
<h1>Unknown modules in <?php echo get_product_name();?></h1>
|
||||
<p>
|
||||
You may have unknown modules for many reasons. Unknown module is a special status for a module/monitor which means “I dont have recent data for this monitor and I should have data”. A monitor goes to unknown status when doesnt receive nothing in at least its interval (for example, 300 seconds) multiplied by two, in this case, if you doesn't receive nothing in ten minutes, monitor goes to unknown.
|
||||
</p>
|
||||
|
@ -11,10 +11,10 @@ You may have unknown modules for many reasons. Unknown module is a special statu
|
|||
These are a few cases where you can get unknown modules:
|
||||
</p>
|
||||
<ul style="list-style-type: disc; margin-left: 30px;">
|
||||
<li>Your pandora server is down. Restart it, dont forget to check /var/log/pandora/pandora_server.log to see why was down.</li>
|
||||
<li>Your tentacle server is down, and cannot get data from your Pandora FMS agents installed in your remote servers.</li>
|
||||
<li>Your <?php echo get_product_name();?> server is down. Restart it, dont forget to check /var/log/pandora/pandora_server.log to see why was down.</li>
|
||||
<li>Your tentacle server is down, and cannot get data from your <?php echo get_product_name();?> agents installed in your remote servers.</li>
|
||||
<li>You have a network problem between your agents and your server.</li>
|
||||
<li>Your pandora fms agent is stopped and is not sending information to your server.</li>
|
||||
<li>Your <?php echo get_product_name();?> agent is stopped and is not sending information to your server.</li>
|
||||
<li>Your network is down, or the remote device you are trying to ask is down or changed it's IP address (for example for numerical SNMP remote queries).</li>
|
||||
<li>Your agent is reporting a badly synchronized date. Means reports a timedate in the past and that messup everything.</li>
|
||||
<li>The script / module before works now doesn't, that can be because something is happing in the agent, check it out.</li>
|
||||
|
|
|
@ -3,14 +3,14 @@
|
|||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Config the Pandora Server for email alerts</h1>
|
||||
<p>You must to edit the <i>"Pandora Server conf file"</i>, normaly it is in:
|
||||
<h1>Config the <?php echo get_product_name();?> for email alerts</h1>
|
||||
<p>You must to edit the <i>"<?php echo get_product_name();?> conf file"</i>, normaly it is in:
|
||||
<pre>
|
||||
/etc/pandora_server/pandora_server.conf
|
||||
</pre>
|
||||
And you must set these values:
|
||||
<pre>
|
||||
# mta_address: External Mailer (MTA) IP Address to be used by Pandora FMS internal email capabilities
|
||||
# mta_address: External Mailer (MTA) IP Address to be used by <?php echo get_product_name();?> internal email capabilities
|
||||
|
||||
mta_address localhost
|
||||
|
||||
|
@ -33,6 +33,6 @@ mta_auth LOGIN
|
|||
# mta_from Email address that sends the mail, by default is pandora@localhost
|
||||
# probably you need to change it to avoid problems with your antispam
|
||||
|
||||
mta_from Pandora FMS <pandora@mydomain.com>
|
||||
mta_from <?php echo get_product_name();?> <monitoring@mydomain.com>
|
||||
</pre>
|
||||
</p>
|
|
@ -12,5 +12,5 @@ To create an Agent, you must fill this form. Please fill all the fields you need
|
|||
"Interval" refers to the agent's execution interval. The interval is how often the agent sends data to the server.
|
||||
</p>
|
||||
<p>
|
||||
"Server" refers to the Pandora Server that will read data send by the agent.
|
||||
"Server" refers to the <?php echo get_product_name();?> Server that will read data send by the agent.
|
||||
</p>
|
||||
|
|
|
@ -9,7 +9,7 @@ Using the configuration parameter sets <b>Cron from</b> and <b>Cron to</b> makes
|
|||
it possible for a module to run only for certain periods of time.
|
||||
The way in which it is configured is similar to the syntax of
|
||||
<a style="font-size:14px;" href="https://en.wikipedia.org/wiki/Cron">cron</a>.
|
||||
Just as they appear in the Pandora console, each one of the parameters
|
||||
Just as they appear in the <?php echo get_product_name();?> console, each one of the parameters
|
||||
has three options.
|
||||
|
||||
<h4>Cron from: any</h4>
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
?>
|
||||
<h1>Custom logo (Branding)</h1>
|
||||
|
||||
This option is used to display your own logo in the Pandora FMS header. You can use any kind of graphic in PNG format. There is a fixed width/height for any image displayed here of 206x47 pixels.
|
||||
This option is used to display your own logo in the <?php echo get_product_name();?> header. You can use any kind of graphic in PNG format. There is a fixed width/height for any image displayed here of 206x47 pixels.
|
||||
<br><br>
|
||||
Upload your custom branding logo, using the file manager to /images/custom_logo directory.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<h2>Dynamic threshold Interval</h2>
|
||||
|
||||
<p>
|
||||
Introduce a time period in the Dynamic Threshold Interval field and the module will return the data obtained during the interval. This allows Pandora to establish minimum thresholds of critical and warning status according to the server configuration.
|
||||
Introduce a time period in the Dynamic Threshold Interval field and the module will return the data obtained during the interval. This allows <?php echo get_product_name();?> to establish minimum thresholds of critical and warning status according to the server configuration.
|
||||
<br><br>
|
||||
The default setting will <b>only</b> give minimums, so if maximum = 0 it will read from the configured minimum to infinite.
|
||||
<br><br>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<h1>Event Alerts</h1>
|
||||
|
||||
From Pandora FMS 4.0 version, it is possible to define alerts on events, that allows to work from a completely new approach much more flexible. This is an Enterprise feature.<br>
|
||||
It is possible to define alerts on events, that allows to work from a completely new approach much more flexible. This is an Enterprise feature.<br>
|
||||
|
||||
To create the new event alerts, click on the Create button in the Event alerts menu from the Administration menu. <br><br>
|
||||
|
||||
|
@ -61,6 +61,6 @@ For example, we could configure a rule that matches with the events generated by
|
|||
<?php html_print_image ("images/help/event04.png", false, array('width' => '550px')); ?>
|
||||
|
||||
<br>
|
||||
<p>Given the high number of events that the Pandora FMS database could store, the server works on an event window that is defined in the pandora_server.conf configuration file through the parameter event_window. The events that have been generated out of this time window won't be processed by the server, so it doesn't make sense to specify in a rule a time window higher to the one configured in the server </p>
|
||||
<p>Given the high number of events that the <?php echo get_product_name();?> database could store, the server works on an event window that is defined in the pandora_server.conf configuration file through the parameter event_window. The events that have been generated out of this time window won't be processed by the server, so it doesn't make sense to specify in a rule a time window higher to the one configured in the server </p>
|
||||
|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
*/
|
||||
?>
|
||||
|
||||
<p> When the history events are enabled, the purging script (pandora_db.pl) will copy the not validated or in process events (only new ones) to the history table before delete it.
|
||||
<p> When the history events are enabled, the purging script (DB Tool) will copy the not validated or in process events (only new ones) to the history table before delete it.
|
||||
<br><br>These events can be consulted in the history events view. This view can be accessed in a new tab in the events section.
|
||||
</p>
|
||||
|
||||
|
|
|
@ -5,10 +5,10 @@
|
|||
?>
|
||||
<h1>Export server</h1>
|
||||
|
||||
<p>Pandora FMS Enterprise Version implements, through the export server, a data scaling device that allows you to do a virtually distributed implementation able to monitor an unlimited number of information, as long as you design it properly and break it up into different information profiles.</p>
|
||||
<p><?php echo get_product_name();?> Enterprise Version implements, through the export server, a data scaling device that allows you to do a virtually distributed implementation able to monitor an unlimited number of information, as long as you design it properly and break it up into different information profiles.</p>
|
||||
|
||||
<ul>
|
||||
<li type="circle">Name: Pandora FMS server name.</li>
|
||||
<li type="circle">Name: <?php echo get_product_name();?> server name.</li>
|
||||
<li type="circle">Export server: Combo to choose the server petition of export server that will be used to export the data.</li>
|
||||
<li type="circle">Prefix: Prefix that is used to add to the agent name that send the data. For example, when the data of an agent named "Farscape" is resent, and its prefix in the export server is "EU01",the resent agent data will be seen in the destination server with the agent name EUO1-Farscape.</li>
|
||||
<li type="circle">Interval: Define the time interval, and how often (in seconds) you want to send the data that is unresolved.</li>
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
<br>
|
||||
<br>
|
||||
|
||||
The Threshold parameter FF (FF = FlipFlop) is used to "filter" the continuous changes of state in the generation of events / states, so that you can tell Pandora FMS until an element is not at least X times in the same state after changing from an original state, not considered to have changed.
|
||||
The Threshold parameter FF (FF = FlipFlop) is used to "filter" the continuous changes of state in the generation of events / states, so that you can tell <?php echo get_product_name();?> until an element is not at least X times in the same state after changing from an original state, not considered to have changed.
|
||||
<br><br>
|
||||
Take a classic example: A ping to a host where there is packet loss. In an environment like this, might give results as:
|
||||
<br>
|
||||
|
@ -24,7 +24,7 @@ Take a classic example: A ping to a host where there is packet loss. In an envir
|
|||
1
|
||||
</pre>
|
||||
<br>
|
||||
However, the host is alive in all cases. What we really want is to tell Pandora that until the host does not say you are at least three times down, not marked as such, so that in the previous case and would never be dropped, and only in this case it would be:
|
||||
However, the host is alive in all cases. What we really want is to tell <?php echo get_product_name();?> that until the host does not say you are at least three times down, not marked as such, so that in the previous case and would never be dropped, and only in this case it would be:
|
||||
<pre>
|
||||
1
|
||||
1
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<h1>GIS Map builder</h1>
|
||||
|
||||
<p>
|
||||
This page shows a list of the defined maps, and let you edit, delete or view any of them. Also from this page is where the <strong>default Map</strong> of Pandora FMS is set.
|
||||
This page shows a list of the defined maps, and let you edit, delete or view any of them. Also from this page is where the <strong>default Map</strong> of <?php echo get_product_name();?> is set.
|
||||
</p>
|
||||
To create a map a connection to a map server is needed, the connections are created by the Adminstrator in the <strong>Setup</strong> menu.
|
||||
<p>
|
||||
|
|
|
@ -11,7 +11,7 @@ This page is the place where the admin can configure <strong>a connection to a G
|
|||
|
||||
<h2>Connection types</h2>
|
||||
<p>
|
||||
Currently Pandora FMS support 3 differet kinds of connections: OpenStreetMap, Google Maps and Static Image.
|
||||
Currently <?php echo get_product_name();?> support 3 differet kinds of connections: OpenStreetMap, Google Maps and Static Image.
|
||||
</p>
|
||||
<h3>Open Street Maps</h3>
|
||||
<p>
|
||||
|
@ -33,5 +33,5 @@ ABQIAAAAZuJY-VSG4gOH73b6mcUw1hTfSvFQRXGUGjHx8f036YCF-UKjgxT9lUhqOJx7KDHSnFnt46qn
|
|||
</pre>
|
||||
<h3>Static Image</h3>
|
||||
<p>
|
||||
It's also possible to use a static image (a PNG for example) as the only source of the map. To use it, the<strong>url</strong>, the <strong>positional information</strong> of the image and the <strong>height</strong> and <strong>width</strong> must be filled.
|
||||
It's also possible to use a static image (a PNG for example) as the only source of the map. To use it, the <strong>url</strong>, the <strong>positional information</strong> of the image and the <strong>height</strong> and <strong>width</strong> must be filled.
|
||||
</p>
|
||||
|
|
|
@ -48,11 +48,11 @@ div.img_title {
|
|||
</style>
|
||||
|
||||
<body class="hlp_graphs">
|
||||
<h1>INTERPRETING GRAPHS IN PANDORA FMS</h1>
|
||||
<h1>INTERPRETING GRAPHS IN <?php echo get_product_name();?></h1>
|
||||
|
||||
|
||||
<p>In Pandora FMS, graphs represent the values a module has had during a given period.</p>
|
||||
<p>Due to the large amount of data that Pandora FMS stores, two different types of functionality are offered</p>
|
||||
<p>In <?php echo get_product_name();?>, graphs represent the values a module has had during a given period.</p>
|
||||
<p>Due to the large amount of data that <?php echo get_product_name();?> stores, two different types of functionality are offered</p>
|
||||
|
||||
|
||||
<h2>NORMAL GRAPHS</h2>
|
||||
|
@ -98,7 +98,7 @@ div.img_title {
|
|||
<dd>Shows indicator points with triggered alert information at the top.</dd>
|
||||
|
||||
<dt>Show percentile</dt>
|
||||
<dd>Adds a graph that indicates the percentile line (configurable in general visual options of Pandora).</dd>
|
||||
<dd>Adds a graph that indicates the percentile line (configurable in general visual options of <?php echo get_product_name();?>).</dd>
|
||||
|
||||
<dt>Time comparison (superimposed)</dt>
|
||||
<dd>Displays the same graphic overlay, but in the period before the selected one. For example, if we request a period of one week and activate this option, the week before the chosen one will also be shown superimposed.</dd>
|
||||
|
@ -107,7 +107,7 @@ div.img_title {
|
|||
<dd>Displays the same graph, but in the period before the selected one, in a separate area. For example, if we request a period of one week and activate this option, the week before the chosen one will also be shown.</dd>
|
||||
|
||||
<dt>Display unknown graphic</dt>
|
||||
<dd>It shows boxes in grey shading covering the periods in which Pandora FMS cannot guarantee the module's status, either due to data loss, disconnection of a software agent, etc.</dd>
|
||||
<dd>It shows boxes in grey shading covering the periods in which <?php echo get_product_name();?> cannot guarantee the module's status, either due to data loss, disconnection of a software agent, etc.</dd>
|
||||
|
||||
<dt>Show Full Scale Graph (TIP)</dt>
|
||||
<dd>Switches the creation mode from "normal" to "TIP". In this mode, the graphs will show real data rather than approximations, so the time it will take to generate them will be longer. More detailed information on this type of graphs can be found in the following section.</dd>
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
?>
|
||||
<h1>History database</h1>
|
||||
|
||||
A history database is a database where old module data is moved to make the main Pandora FMS database more responsive for everyday operations. That data will still be available seamlessly to the Pandora FMS console when viewing reports, module charts etc.
|
||||
A history database is a database where old module data is moved to make the main <?php echo get_product_name();?> database more responsive for everyday operations. That data will still be available seamlessly to the <?php echo get_product_name();?> console when viewing reports, module charts etc.
|
||||
<br><br>
|
||||
<b>SETTING UP A HISTORY DATABASE</b>
|
||||
<br><br>
|
||||
|
@ -14,7 +14,7 @@ To configure a history database follow these simple steps:
|
|||
<ol>
|
||||
<li>Create the new history database.
|
||||
<br><br>
|
||||
<li>Create the necessary tables in the new database. You can use the pandoradb.sql script provided with the Pandora FMS console:
|
||||
<li>Create the necessary tables in the new database. You can use the DB Tool script provided with the <?php echo get_product_name();?> console:
|
||||
<br><br>
|
||||
<i>cat pandoradb.sql | mysql -u user -p -D history_db</i>
|
||||
<br><br>
|
||||
|
@ -22,7 +22,7 @@ To configure a history database follow these simple steps:
|
|||
<br><br>
|
||||
<i>Mysql Example: GRANT ALL PRIVILEGES ON pandora.* TO 'pandora'@'IP' IDENTIFIED BY 'password'</i>
|
||||
<br><br>
|
||||
<li>In your Pandora FMS console navigate to Setup->History database and enter the host, port, database name, user and password of the new database.
|
||||
<li>In your <?php echo get_product_name();?> console navigate to Setup->History database and enter the host, port, database name, user and password of the new database.
|
||||
</ol>
|
||||
<br><br>
|
||||
<?php html_print_image ("images/help/historyddbb.png", false, array('width' => '550px')); ?>
|
||||
|
|
|
@ -5,9 +5,9 @@
|
|||
?>
|
||||
<h1>IP Address Management (IPAM)</h1>
|
||||
<br>
|
||||
Using IPAM extension, we can manage, discover and get event on changes on hosts in a given network. We can know if a given IP address (IPv4 or IPv6) change it's availability (answer to a ping) or hostname (using dns resolution). We also can detect its OS and link a IP address to a current Pandora FMS agent, adding the IP address to their currently assigned addresses. IPAM extension uses the recon server and a recon script on the low level, but you don't need to configure nothing, IPAM extension do everything for you.
|
||||
Using IPAM extension, we can manage, discover and get event on changes on hosts in a given network. We can know if a given IP address (IPv4 or IPv6) change it's availability (answer to a ping) or hostname (using dns resolution). We also can detect its OS and link a IP address to a current <?php echo get_product_name();?> agent, adding the IP address to their currently assigned addresses. IPAM extension uses the recon server and a recon script on the low level, but you don't need to configure nothing, IPAM extension do everything for you.
|
||||
<br><br>
|
||||
IP Management works in parallel to the monitoring you currently manage with Pandora FMS agents, you can associate a IP address managed with IPAM extension or not, it depends on you. Managed IP addresses can optionally generate event on change.
|
||||
IP Management works in parallel to the monitoring you currently manage with <?php echo get_product_name();?> agents, you can associate a IP address managed with IPAM extension or not, it depends on you. Managed IP addresses can optionally generate event on change.
|
||||
|
||||
<h2>IPs Detection</h2>
|
||||
We can setup a network (using a bit mask or a prefix), and this network will be automatically sweeped or setup to have a on-request manual execution. This will execute a recon script task, searching for active IP (using nmap for IPv4 and ping for IPv6). You see the progress on network sweep in the status view and also in the recon server view.
|
||||
|
@ -76,7 +76,7 @@ When you click on the main icon, a modal window will be opened showing all the I
|
|||
<h3>Edition view</h3>
|
||||
If you have enought permission, you will have access to setup view, where IP address are shown as a list. You can filter to show only the IP's you are interested into, make changes and update all at once.<br><br>
|
||||
|
||||
Some fields, are automatically filled by the recon script, like hostname, if it have a Pandora FMS agent and the operating system. You can mark that fields as "manual" and edit them.<br><br>
|
||||
Some fields, are automatically filled by the recon script, like hostname, if it have a <?php echo get_product_name();?> agent and the operating system. You can mark that fields as "manual" and edit them.<br><br>
|
||||
|
||||
<table width=100%>
|
||||
<tr>
|
||||
|
|
|
@ -6,4 +6,4 @@
|
|||
|
||||
<h1>Local Component</h1>
|
||||
|
||||
<p>Local Components are elements that can be applied to agents like templates. With Pandora FMS Enterprise, this can be applied authomatically and remotely with policies or one by one.</p>
|
||||
<p>Local Components are elements that can be applied to agents like templates. With <?php echo get_product_name();?> Enterprise, this can be applied authomatically and remotely with policies or one by one.</p>
|
||||
|
|
|
@ -3,10 +3,10 @@
|
|||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Pandora FMS - Help index</h1>
|
||||
<h1><?php echo get_product_name();?> - Help index</h1>
|
||||
<h3>Introduction</h3>
|
||||
<p>
|
||||
This is the online help for Pandora FMS console. This help is -in best cases- just a "brief" contextual help, not intented to teach you how to use Pandora FMS. Official documentation of Pandora FMS is about 900 pages, and you probably don't need to read it entirely, but sure, you should download it and take a look.
|
||||
This is the online help for <?php echo get_product_name();?> console. This help is -in best cases- just a "brief" contextual help, not intented to teach you how to use <?php echo get_product_name();?>. Official documentation of <?php echo get_product_name();?> is about 900 pages, and you probably don't need to read it entirely, but sure, you should download it and take a look.
|
||||
|
||||
<br><br>
|
||||
<a href="http://pandorafms.com/pandora/doc/"><b>Download the official documentation</b></a>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<h1>Alerts</h1>
|
||||
|
||||
<p>
|
||||
Alerts in Pandora FMS react to an "out of range" module value. The alert can consist of sending an e-mail or an SMS to the administrator, sending a SNMP trap, write the incident into the system log or into Pandora FMS log file, etc. Basically, an alert can be anything that can be triggered by a script configured in the Operating System where Pandora FMS Servers run.
|
||||
Alerts in <?php echo get_product_name();?> react to an "out of range" module value. The alert can consist of sending an e-mail or an SMS to the administrator, sending a SNMP trap, write the incident into the system log or into <?php echo get_product_name();?> log file, etc. Basically, an alert can be anything that can be triggered by a script configured in the Operating System where <?php echo get_product_name();?> Servers run.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
?>
|
||||
<h1>Alerts</h1>
|
||||
|
||||
Alerts in Pandora FMS react to an "out of range" module value. The alert can consist of sending an e-mail or an SMS to the administrator, sending a SNMP trap, write the incident into the system log or into Pandora FMS log file, etc. Basically, an alert can be anything that can be triggered by a script configured in the Operating System where Pandora FMS Servers run.
|
||||
Alerts in <?php echo get_product_name();?> react to an "out of range" module value. The alert can consist of sending an e-mail or an SMS to the administrator, sending a SNMP trap, write the incident into the system log or into <?php echo get_product_name();?> log file, etc. Basically, an alert can be anything that can be triggered by a script configured in the Operating System where <?php echo get_product_name();?> Servers run.
|
||||
<br /><br />
|
||||
The values "_field1_", "_field2_" and "_field3_" of the customized alerts are used to build the command line that will be executed.
|
||||
<br /><br />
|
||||
|
|
|
@ -96,7 +96,7 @@ The total of seconds, agent will wait for the execution of the module, so if it
|
|||
<br><br>
|
||||
<b>module_postprocess 'factor'</b>
|
||||
<br><br>
|
||||
Same as in the definition of post processing of a module that is done from the console, here could be defined a numeric value of floating comma that will send this value to Pandora FMS in order the server will use it to multiply the received (raw) by the agent.
|
||||
Same as in the definition of post processing of a module that is done from the console, here could be defined a numeric value of floating comma that will send this value to <?php echo get_product_name();?> in order the server will use it to multiply the received (raw) by the agent.
|
||||
<br><br>
|
||||
<b>module_save 'variable name'</b>
|
||||
<br><br>
|
||||
|
@ -245,7 +245,7 @@ module_end<br>
|
|||
<br>
|
||||
<b>Processes Watchdog</b>
|
||||
<br><br>
|
||||
A Watchdog is a system that allows to act immediately when an agent is down, usually picking up the process that is down . The Pandora FMS Windows agent could act as Watchdog when a process is down. This is called watchdog mode for the process:
|
||||
A Watchdog is a system that allows to act immediately when an agent is down, usually picking up the process that is down . The <?php echo get_product_name();?> Windows agent could act as Watchdog when a process is down. This is called watchdog mode for the process:
|
||||
<br><br>
|
||||
Executing a process could need some parameters, so there are some additional configuration options for these kind of modules. It is important to say that the watchdog mode only works when the module type is asynchronous. Let's see an example of configuration of a module_proc with watchdog.
|
||||
<br><br>
|
||||
|
@ -268,7 +268,7 @@ This is the definition of the additional parameters for module_proc with watchdo
|
|||
<br><br>
|
||||
<i>module_startdelay:</i> Number of milliseconds the module will wait before starting the process by first time. If the process takes lot of time at starting , then it will be a great idea to order the agent through this parameter that it "wait" until start checking again if the process has got up. In this example wait 3 seconds.
|
||||
<br><br>
|
||||
<i>module_retrydelay:</i> Similar to the previous one but for subsequent falls/reattempts, after having detect a fall. When Pandora detects a fall, relaunch the process, wait the nº of milliseconds pointed out in this parameter and check again if the process is already up.
|
||||
<i>module_retrydelay:</i> Similar to the previous one but for subsequent falls/reattempts, after having detect a fall. When <?php echo get_product_name();?> detects a fall, relaunch the process, wait the nº of milliseconds pointed out in this parameter and check again if the process is already up.
|
||||
<br><br>
|
||||
<b>module_cpuproc 'process'</b>
|
||||
<br><br>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<h1>Networkmap console</h1>
|
||||
|
||||
<p>With Pandora FMS Enterprise we have the possibility of create editable network maps that are more interactive comparing with the Open version that is currently on the "See agents" submenu.</p>
|
||||
<p>With <?php echo get_product_name();?> Enterprise we have the possibility of create editable network maps that are more interactive comparing with the Open version that is currently on the "See agents" submenu.</p>
|
||||
|
||||
<p>On the contrary to the Open version, the Networkmap Enterprise provide us with more features, such as: </p>
|
||||
|
||||
|
@ -38,7 +38,7 @@
|
|||
|
||||
<h2>Minimap</h2>
|
||||
|
||||
<p>This minimap gives us a global view that shows all the map extension, but in a smaller view, and besides, in contrast with the map view, all the nodes are shown, but without status and without relationships. Except the Pandora fictitious point, that is shown in green. And a red box is also shown of the part of the map that is being shown. </p>
|
||||
<p>This minimap gives us a global view that shows all the map extension, but in a smaller view, and besides, in contrast with the map view, all the nodes are shown, but without status and without relationships. Except the <?php echo get_product_name();?> fictitious point, that is shown in green. And a red box is also shown of the part of the map that is being shown. </p>
|
||||
|
||||
<p>It's on the upper left corner, and could be hidden pressing on the arrow icon.
|
||||
</p>
|
||||
|
@ -72,7 +72,7 @@
|
|||
|
||||
|
||||
<p>It shows a box which rim will be of the same color that the agent status. <br>
|
||||
The agent name is a link to the Pandora agent page. <br>
|
||||
The agent name is a link to the <?php echo get_product_name();?> agent page. <br>
|
||||
Inside the box are all the modules that are not in unknown status, which, depending if the module status is green or red. <br>
|
||||
It's possible to click on these modules and they shown a tooltip with the module main data. <br>
|
||||
In the box rim are the modules kind SNMP Proc,that use to be for network interfaces when an agent related with network systems is monitored. <br></p>
|
||||
|
@ -107,7 +107,7 @@
|
|||
<li><b>Creating the network map from:</b> option only available in the creation. It's the way to create the network map if we do it from the agents that are in the previously selected group, or on the contrary we want an empty network map. </li>
|
||||
<li><b>Size of the network map:</b> where it's possible to define the size of the network map, by default it's of 3000 width and 3000 high. </li>
|
||||
<li><b>Method for creating of the network map:</b> the method of distribution of the nodes that will make up the network map, by default it's radial, but there are the following ones: </li>
|
||||
<p>- <i>Radial:</i> In which all the nodes will be placed around the fictitious node that the Pandora represents. <br>
|
||||
<p>- <i>Radial:</i> In which all the nodes will be placed around the fictitious node that the <?php echo get_product_name();?> represents. <br>
|
||||
- <i>Circular:</i> In which the nodes will be placed in concentric circles en el cual se dispondrá los nodos en círculos concentricos. <br>
|
||||
- <i>Flat:</i> In which the nodes with tree shape will be placed. <br>
|
||||
- <i>spring1, spring2:</i> are variations of the Flat. <br>
|
||||
|
|
|
@ -62,5 +62,5 @@ Agent access graph, renders the number of agent contacts per hour in a graph wit
|
|||
<br><br>
|
||||
Maximum number of days before delete unknown modules.
|
||||
<br><br>
|
||||
<i>**All these parameters are made when running the pandora_db.pl tool</i>
|
||||
<i>**All these parameters are made when running the DB Tool</i>
|
||||
|
||||
|
|
|
@ -12,5 +12,5 @@ This tool is used to plan non-monitoring periods of time. This is useful if you
|
|||
It's very easy to setup, you specify start date/time of a scheduled downtime and an end date/time. After setting the first fields you must save the Scheduled downtime and edit it, to set the agents which are going to be disconnected. You can also edit the rest of the fields once editing the Scheduled downtime entry.
|
||||
</p>
|
||||
<p>
|
||||
When scheduled downtime starts, Pandora FMS automatically disable all agents assigned to this downtime and no alerts or data are processed. When downtime ends, Pandora FMS will be enable all agents assigned to this downtime. You cannot delete or modify a downtime instance when it's fired, you need to wait for ending before doing anything in this downtime instance. Of course you can manually, enable an agent using the agent configuration dialog.
|
||||
When scheduled downtime starts, <?php echo get_product_name();?> automatically disable all agents assigned to this downtime and no alerts or data are processed. When downtime ends, <?php echo get_product_name();?> will be enable all agents assigned to this downtime. You cannot delete or modify a downtime instance when it's fired, you need to wait for ending before doing anything in this downtime instance. Of course you can manually, enable an agent using the agent configuration dialog.
|
||||
</p>
|
||||
|
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
<p>
|
||||
The date format must be year/month/day and the time format must be hour:minute:second.
|
||||
It's possible to create a scheduled downtime with a past date, if that option aren't disabled by the admin of Pandora FMS.
|
||||
It's possible to create a scheduled downtime with a past date, if that option aren't disabled by the admin of <?php echo get_product_name();?>.
|
||||
</p>
|
||||
|
||||
<h2>Periodically execution</h2>
|
||||
|
|
|
@ -5,9 +5,9 @@
|
|||
?>
|
||||
<h1>Plugin registration</h1>
|
||||
|
||||
Unlike with the rest of components, in a default way Pandora FMS does not include any pre-configured complement, so first you should create and configure a complement to could after add it to the module of an agent. But Pandora FMS includes plugins in the installation directories, but as have already been said, they are not configured in the database.
|
||||
Unlike with the rest of components, in a default way <?php echo get_product_name();?> does not include any pre-configured complement, so first you should create and configure a complement to could after add it to the module of an agent. But <?php echo get_product_name();?> includes plugins in the installation directories, but as have already been said, they are not configured in the database.
|
||||
<br><br>
|
||||
To add a plugin that already exists to Pandora FMS, go to the console administration section, and in it, click on Manage servers. After doing this, click on Manage plugins:
|
||||
To add a plugin that already exists to <?php echo get_product_name();?>, go to the console administration section, and in it, click on Manage servers. After doing this, click on Manage plugins:
|
||||
<br><br>
|
||||
Once you are in the screen of the plugin management, click on Create a new plugin, so there will be no one.
|
||||
<br><br>
|
||||
|
@ -18,7 +18,7 @@ Fill in the plugin creation form with the following data:
|
|||
Name of the plugin, in this case Nmap.
|
||||
<br><br>
|
||||
<b>Plugin type </b><br>
|
||||
There are two kinds of plugins, the standard ones and the kind Nagios. The standard plugins are scripts that execute actions and accept parameters. The Nagios plugins are, as their name shows, Nagios plugins that could be being used in Pandora FMS.The difference is mainly on that the Nagios plugins return an error level to show if the test has been successful or not.
|
||||
There are two kinds of plugins, the standard ones and the kind Nagios. The standard plugins are scripts that execute actions and accept parameters. The Nagios plugins are, as their name shows, Nagios plugins that could be being used in <?php echo get_product_name();?>.The difference is mainly on that the Nagios plugins return an error level to show if the test has been successful or not.
|
||||
<br><br>
|
||||
If you want to use a plugin kind Nagios and you want to get a data, not an state (good/Bad), then you can use a plugin kind Nagios is the "Standard" mode.
|
||||
<br><br>
|
||||
|
@ -38,7 +38,7 @@ Plugin description. Write a short description, as for example:Test # UDP open po
|
|||
|
||||
It is the path where the plugin command is. In a default way, if the installation has been an standard one, there will be in the directory /usr/share/pandora_server/util/plugin/. Though it could be any path of the system. For this case, writte /usr/share/pandora_server/util/plugin/udp_nmap_plugin.shin the field.
|
||||
<br><br>
|
||||
Pandora server will execute this script, so this should have permissions of access and execution on it.
|
||||
<?php echo get_product_name();?> server will execute this script, so this should have permissions of access and execution on it.
|
||||
<br><br>
|
||||
<b>Plug-in parameters</b><br>
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ The following macros are available:
|
|||
<li>_modulegroup_ : Module group name.</li>
|
||||
<li>_moduledescription_ : Description of the module.</li>
|
||||
<li>_modulestatus_ : Status of the module.</li>
|
||||
<li>_id_agent_ : Id of agent, useful to build direct URL to redirect to a Pandora FMS console webpage.</li>
|
||||
<li>_id_agent_ : Id of agent, useful to build direct URL to redirect to a <?php echo get_product_name();?> console webpage.</li>
|
||||
<li>_id_group_ : Id of agent group.</li>
|
||||
<li>_policy_ : Name of the policy the module belongs to (if applies).</li>
|
||||
<li>_interval_ : Execution interval of the module. </li>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<h1>Agent Plugins</h1>
|
||||
|
||||
<p>Since Pandora FMS 5.0, with the plugins editor in policies is possible propagate the agents plugins easily.
|
||||
<p>With the plugins editor in policies is possible propagate the agents plugins easily.
|
||||
<br><br>
|
||||
Is possible to add agent plugins in a policy to be created in each local agent when be applied.
|
||||
<br><br>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<h1>Profile</h1>
|
||||
|
||||
<p>Pandora FMS is a Web management tool that allows multiple users to work with different permissions in multiple defined agent groups. The permissions an user can have are defined in profiles.</p>
|
||||
<p><?php echo get_product_name();?> is a Web management tool that allows multiple users to work with different permissions in multiple defined agent groups. The permissions an user can have are defined in profiles.</p>
|
||||
|
||||
<p>The following list defines what ACL control allows in each feature at the console:</p>
|
||||
|
||||
|
|
|
@ -25,7 +25,7 @@ Network where you want to do the recognition. Use the network format/ bits mask.
|
|||
|
||||
<b>Interval</b>
|
||||
<br>
|
||||
Repetition interval of systems search. Do not use intervals very shorts so Recon explores a network sending one Ping to each address. If you use recon networks very larges (for example a class A) combined with very short intervals (6 hours) you will be doing that Pandora FMS will be always bomb the network with pings, overloading it and also Pandora FMS unnecessarily.<br><br>
|
||||
Repetition interval of systems search. Do not use intervals very shorts so Recon explores a network sending one Ping to each address. If you use recon networks very larges (for example a class A) combined with very short intervals (6 hours) you will be doing that <?php echo get_product_name();?> will be always bomb the network with pings, overloading it and also <?php echo get_product_name();?> unnecessarily.<br><br>
|
||||
|
||||
<b>Module template</b><br>
|
||||
|
||||
|
@ -33,7 +33,7 @@ Plugins template to add to the discovered systems. When it detects a system that
|
|||
|
||||
<b>OS</b><br>
|
||||
|
||||
Operative system to recognize. If you select one instead of any (Any) it will only be added the systems with this operative system.Consider that in some circumstances Pandora FMS can make a mistake when detecting systems, so this kind of "guess" is done with statistic patterns, that depending on some other factors could fail (networks with filters, security software, modified versions of the systems).To could use this method with security, you should have installed Xprobe2 in your system. <br><br>
|
||||
Operative system to recognize. If you select one instead of any (Any) it will only be added the systems with this operative system.Consider that in some circumstances <?php echo get_product_name();?> can make a mistake when detecting systems, so this kind of "guess" is done with statistic patterns, that depending on some other factors could fail (networks with filters, security software, modified versions of the systems).To could use this method with security, you should have installed Xprobe2 in your system. <br><br>
|
||||
|
||||
<b>Ports</b><br>
|
||||
|
||||
|
|
|
@ -6,4 +6,4 @@
|
|||
|
||||
<h1>SLA Wizard</h1>
|
||||
|
||||
<p>Allows to measure the service level (Service Level Agreement) of any monitor of Pandora FMS. In this wizard you can create a SLA report of several agents.</p>
|
||||
<p>Allows to measure the service level (Service Level Agreement) of any monitor of <?php echo get_product_name();?>. In this wizard you can create a SLA report of several agents.</p>
|
||||
|
|
|
@ -18,7 +18,7 @@ The accepted macros are:
|
|||
<li><b>Event ID:</b> _event_id_</li>
|
||||
<li><b>Event instructions:</b> _event_instruction_</li>
|
||||
<li><b>Event severity ID:</b> _event_severity_id_</li>
|
||||
<li><b>Event severity (translated by Pandora console):</b> _event_severity_text_</li>
|
||||
<li><b>Event severity (translated by <?php echo get_product_name();?> console):</b> _event_severity_text_</li>
|
||||
<li><b>Event source:</b> _event_source_</li>
|
||||
<li><b>Event status (new, validated or event in process):</b> _event_status_</li>
|
||||
<li><b>Event tags separated by commas:</b> _event_tags_</li>
|
||||
|
|
|
@ -6,11 +6,11 @@
|
|||
|
||||
<h1>Server management</h1>
|
||||
|
||||
<p>The Pandora FMS servers are the elements in charge of performing the existing checks. They verify them and change their status depending on the results. They are also in charge of triggering the alerts established to control the status of data.</p>
|
||||
<p>The <?php echo get_product_name();?> servers are the elements in charge of performing the existing checks. They verify them and change their status depending on the results. They are also in charge of triggering the alerts established to control the status of data.</p>
|
||||
|
||||
<p>Pandora FMS's data server can work in high availability and/or load balancing modes. In a very large architecture, various Pandora FMS servers can be used at the same time, in order to handle large volumes of functionally or geographically distributed information.</p>
|
||||
<p><?php echo get_product_name();?>'s data server can work in high availability and/or load balancing modes. In a very large architecture, various <?php echo get_product_name();?> servers can be used at the same time, in order to handle large volumes of functionally or geographically distributed information.</p>
|
||||
|
||||
<p>Pandora FMS servers are always on and permanently verify if any element has any problem. If there is any alert linked to the problem, then it'll run the pre-set action such as sending an SMS, an email, or activating a script execution.</p>
|
||||
<p><?php echo get_product_name();?> servers are always on and permanently verify if any element has any problem. If there is any alert linked to the problem, then it'll run the pre-set action such as sending an SMS, an email, or activating a script execution.</p>
|
||||
|
||||
<ul>
|
||||
<li type="circle">Data Server</li>
|
||||
|
|
|
@ -6,4 +6,4 @@
|
|||
|
||||
<h1>SNMP alert</h1>
|
||||
|
||||
<p>It's possible to associate an alert to a trap, so Pandora FMS warns us on arrival of a specific trap. SNMP traps have got nothing to do with the rest of the system alerts, even if both reuse the actions' system.</p>
|
||||
<p>It's possible to associate an alert to a trap, so <?php echo get_product_name();?> warns us on arrival of a specific trap. SNMP traps have got nothing to do with the rest of the system alerts, even if both reuse the actions' system.</p>
|
||||
|
|
|
@ -5,4 +5,4 @@
|
|||
?>
|
||||
<h1>SNMP OID</h1>
|
||||
|
||||
Module's SNMP OID. If there is a MIB able to resolve the name in Pandora FMS Network Server, then you can use alphanumeric OIDs (i.e. SNMPv2-MIB::sysDescr.0). Numeric OID can always be used (i.e. 3.1.3.1.3.5.12.4.0.1), even if there is no specific MIB.
|
||||
Module's SNMP OID. If there is a MIB able to resolve the name in <?php echo get_product_name();?> Network Server, then you can use alphanumeric OIDs (i.e. SNMPv2-MIB::sysDescr.0). Numeric OID can always be used (i.e. 3.1.3.1.3.5.12.4.0.1), even if there is no specific MIB.
|
||||
|
|
|
@ -5,6 +5,6 @@
|
|||
?>
|
||||
<h1>SNMP walk</h1>
|
||||
|
||||
Pandora FMS has also a simple SNMP browser that allows to walk the MIB of a remote device by a SNMP Walk.
|
||||
<?php echo get_product_name();?> has also a simple SNMP browser that allows to walk the MIB of a remote device by a SNMP Walk.
|
||||
<br /><br />
|
||||
Walking ("SNMP Walk") over a device will make all MIB variables available, so you can choose one. You can also enter a MIB using numerical OID or human understandable format, if you have the correct MIB installed in your Pandora FMS Network Server.
|
||||
Walking ("SNMP Walk") over a device will make all MIB variables available, so you can choose one. You can also enter a MIB using numerical OID or human understandable format, if you have the correct MIB installed in your <?php echo get_product_name();?> Network Server.
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
* @package Include/help/en
|
||||
*/
|
||||
?>
|
||||
<h1>Tags in Pandora FMS</h1>
|
||||
<h1>Tags in <?php echo get_product_name();?></h1>
|
||||
|
||||
The access to the modules can be configurated with a Tags system. A tags are configurated on the system, and be assigned to the choosed modules. In this way the access of the user can be limited to the modules with certain tags.
|
||||
<br><br>
|
||||
|
|
|
@ -38,7 +38,7 @@ If you type something, like "none" and press enter, they reply you the following
|
|||
<br /><br />
|
||||
Protocol mismatch
|
||||
<br /><br />
|
||||
So to "code" this conversation in a Pandora FMS TCP module, you need to put in TCP Send:
|
||||
So to "code" this conversation in a <?php echo get_product_name();?> TCP module, you need to put in TCP Send:
|
||||
<br /><br />
|
||||
|none^M
|
||||
<br /><br />
|
||||
|
|
|
@ -9,9 +9,9 @@
|
|||
What source to use for the time. This can be (for now) either the local system (System) or database (Database).<br />
|
||||
</p>
|
||||
<p>
|
||||
This is useful when your database is not on the same system as your webserver or your Pandora FMS servers.
|
||||
This is useful when your database is not on the same system as your webserver or your <?php echo get_product_name();?> servers.
|
||||
In that case any time difference will miscalculate the time differences and timestamps.
|
||||
You should use NTP to sync all your pandora servers and your MySQL server.
|
||||
You should use NTP to sync all your <?php echo get_product_name();?> servers and your MySQL server.
|
||||
By using these preferences you don't have to sync your webserver but it's still recommended.
|
||||
</p>
|
||||
<p>
|
||||
|
|
|
@ -17,7 +17,7 @@ defined:
|
|||
<li>the work area (where you will "draw" the visual console)</li>
|
||||
<li>the option palette ( that is not visible in this screen shot)</li>
|
||||
</ul>
|
||||
In the version Pandora 5.0.1 you can set the label with a rich text.
|
||||
You can set the label with a rich text.
|
||||
And the item "Simple value" you can use the macros to set inner the text
|
||||
with (_VALUE_).
|
||||
</p>
|
||||
|
|
|
@ -6,4 +6,4 @@
|
|||
|
||||
<h1>Preview</h1>
|
||||
|
||||
<p>This tab is useful to see the result of your work in a quick way, avoiding surfing between the Pandora Console menus. The visual console view is an static view, so, if the state of the elements contained there, they will not be drawing again as it happens with the visual console view that hangs on the Visual Console menu.</p>
|
||||
<p>This tab is useful to see the result of your work in a quick way, avoiding surfing between the <?php echo get_product_name();?> Console menus. The visual console view is an static view, so, if the state of the elements contained there, they will not be drawing again as it happens with the visual console view that hangs on the Visual Console menu.</p>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<h1>WEB Monitoring</h1>
|
||||
|
||||
<p>
|
||||
Advanced WEB Monitoring is a feature done by the Goliat/WEB Server in Pandora FMS Enterprise version.
|
||||
Advanced WEB Monitoring is a feature done by the Goliat/WEB Server in <?php echo get_product_name();?> Enterprise version.
|
||||
<br /><br />
|
||||
This is a sample of GOLIAT Webcheck module:
|
||||
<br />
|
||||
|
@ -43,7 +43,7 @@ The following macros are available:
|
|||
<li>_moduledescription_ : Description of the module who fired the alert.</li>
|
||||
<li>_modulestatus_ : Status of the module.</li>
|
||||
<li>_moduletags_ : Tags associated to the module.</li>
|
||||
<li>_id_agent_ : Id of agent, useful to build direct URL to redirect to a Pandora FMS console webpage.</li>
|
||||
<li>_id_agent_ : Id of agent, useful to build direct URL to redirect to a <?php echo get_product_name();?> console webpage.</li>
|
||||
<li>_policy_ : Name of the policy the module belongs to (if applies).</li>
|
||||
<li>_interval_ : Execution interval of the module. </li>
|
||||
<li>_target_ip_ : IP address of the target of the module.</li>
|
||||
|
|
|
@ -2,11 +2,11 @@
|
|||
<h2>Introducción</h2>
|
||||
|
||||
<p>
|
||||
Pandora WUX es un componente interno de Pandora FMS que permite a los usuarios automatizar sus sesiones de navegación web. Genera en Pandora FMS un informe con los resultados de las ejecuciones, tiempos empleados, y capturas con los posibles errores encontrados. Es capaz de dividir las sesiones de navegación en fases para simplificar la vista y depurar posibles cuellos de botella.
|
||||
<?php echo get_product_name();?> WUX es un componente interno de <?php echo get_product_name();?> que permite a los usuarios automatizar sus sesiones de navegación web. Genera en <?php echo get_product_name();?> un informe con los resultados de las ejecuciones, tiempos empleados, y capturas con los posibles errores encontrados. Es capaz de dividir las sesiones de navegación en fases para simplificar la vista y depurar posibles cuellos de botella.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Pandora WUX utiliza el robot de navegación de Pandora (PWR - Pandora Web Robot) para automatizar las sesiones de navegación
|
||||
<?php echo get_product_name();?> WUX utiliza el robot de navegación de <?php echo get_product_name();?> (PWR - <?php echo get_product_name();?> Web Robot) para automatizar las sesiones de navegación
|
||||
</p>
|
||||
|
||||
<h2>Grabar una sesión de navegación web</h2>
|
||||
|
@ -114,13 +114,13 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Una vez verificada la validez de la secuencia de navegación, la guardaremos (Archivo -> Save Test Case) para ejecutarla posteriormente con Pandora WUX. El fichero resultante será un documento HTML que Pandora WUX interpretará.
|
||||
Una vez verificada la validez de la secuencia de navegación, la guardaremos (Archivo -> Save Test Case) para ejecutarla posteriormente con <?php echo get_product_name();?> WUX. El fichero resultante será un documento HTML que <?php echo get_product_name();?> WUX interpretará.
|
||||
</p>
|
||||
|
||||
<h4>Grabar una sesión transaccional con Pandora WUX PWR</h4>
|
||||
<h4>Grabar una sesión transaccional con <?php echo get_product_name();?> WUX PWR</h4>
|
||||
|
||||
<p>
|
||||
Pandora WUX en modo PWR (Pandora Web Robot) permite dividir la monitorización de la navegación de un sitio web en múltiples módulos, que representarán cada uno de los pasos realizados.
|
||||
<?php echo get_product_name();?> WUX en modo PWR (<?php echo get_product_name();?> Web Robot) permite dividir la monitorización de la navegación de un sitio web en múltiples módulos, que representarán cada uno de los pasos realizados.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -186,7 +186,7 @@
|
|||
En esta vista podemos encontrar toda la infomación que el sistema WUX ha obtenido de la sesión de navegación configurada:
|
||||
</p>
|
||||
<p>
|
||||
<b><u>Nota</u>:</b> Si hemos definido fases en nuestra sesión de navegación, se mostrarán en esta vista de una forma sencilla y clara (ver apartado de grabación <i>sesión transaccional con Pandora WUX PWR)</i>.
|
||||
<b><u>Nota</u>:</b> Si hemos definido fases en nuestra sesión de navegación, se mostrarán en esta vista de una forma sencilla y clara (ver apartado de grabación <i>sesión transaccional con <?php echo get_product_name();?> WUX PWR)</i>.
|
||||
</p>
|
||||
|
||||
<p style="text-align: center">
|
||||
|
|
Loading…
Reference in New Issue