2010-01-05 Juan Manuel Ramon <juanmanuel.ramon@artica.es>

* include/help/en/help_create_agent.php
	include/help/en/help_reconscript_definition.php
	include/help/en/help_warning_status.php
	include/help/en/help_manage_alert_list.php
	include/help/en/help_critical_status.php
	include/help/es/help_create_agent.php
	include/help/es/help_reconscript_definition.php
	include/help/es/help_warning_status.php
	include/help/es/help_manage_alert_list.php
	include/help/es/help_critical_status.php: Added new help menus. 

	* include/functions.php: Added new constants.

	* godmode/agentes/module_manager_editor_common.php
	godmode/agentes/agent_manager.php
	godmode/servers/manage_recontask_form.php
	godmode/alerts/configure_alert_template.php: Added contextual helps.



git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@3722 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
juanmanuelr 2011-01-05 17:49:52 +00:00
parent 5249b239fd
commit 63b15d13db
16 changed files with 222 additions and 7 deletions

View File

@ -1,3 +1,23 @@
2010-01-05 Juan Manuel Ramon <juanmanuel.ramon@artica.es>
* include/help/en/help_create_agent.php
include/help/en/help_reconscript_definition.php
include/help/en/help_warning_status.php
include/help/en/help_manage_alert_list.php
include/help/en/help_critical_status.php
include/help/es/help_create_agent.php
include/help/es/help_reconscript_definition.php
include/help/es/help_warning_status.php
include/help/es/help_manage_alert_list.php
include/help/es/help_critical_status.php: Added new help menus.
* include/functions.php: Added new constants.
* godmode/agentes/module_manager_editor_common.php
godmode/agentes/agent_manager.php
godmode/servers/manage_recontask_form.php
godmode/alerts/configure_alert_template.php: Added contextual helps.
2010-12-28 Sancho Lerena <slerena@artica.es>
* pandoradb_data.sql: Fixed link for current documentation page at

View File

@ -205,7 +205,8 @@ if (!$new_agent) {
$table->data[3][1] = date ("F d Y H:i:s", fileatime ($filename['md5']));
// Delete remote configuration
$table->data[3][1] .= '<a href="index.php?sec=gagente&amp;sec2=godmode/agentes/configurar_agente&amp;tab=main&amp;disk_conf_delete=1&amp;id_agente='.$id_agente.'">';
$table->data[3][1] .= print_image ("images/cross.png", true).'</a>';
$table->data[3][1] .= print_image ("images/cross.png", true, array ('title' => __('Delete remote configuration file'), 'style' => 'vertical-align: middle;')).'</a>';
$table->data[3][1] .= '</a>'.print_help_tip (__('Delete this conf file implies that for restore you must reactive remote config in the local agent.'), true);
}
else
$table->data[3][1] = '<em>'.__('Not available').'</em>';

View File

@ -165,14 +165,14 @@ $table_simple->data[1][3] = print_select_from_sql ('SELECT id_mg, name FROM tmod
'id_module_group', $id_module_group, '', __('Not assigned'), '0',
true, false, true, $disabledBecauseInPolicy);
$table_simple->data[2][0] = __('Warning status');
$table_simple->data[2][0] = __('Warning status').' '.print_help_icon ('warning_status', true);
$table_simple->data[2][1] = '<em>'.__('Min.').'</em>';
$table_simple->data[2][1] .= print_input_text ('min_warning', $min_warning,
'', 5, 255, true, $disabledBecauseInPolicy);
$table_simple->data[2][1] .= '<br /><em>'.__('Max.').'</em>';
$table_simple->data[2][1] .= print_input_text ('max_warning', $max_warning,
'', 5, 255, true, $disabledBecauseInPolicy);
$table_simple->data[2][2] = __('Critical status');
$table_simple->data[2][2] = __('Critical status').' '.print_help_icon ('critical_status', true);
$table_simple->data[2][3] = '<em>'.__('Min.').'</em>';
$table_simple->data[2][3] .= print_input_text ('min_critical', $min_critical,
'', 5, 255, true, $disabledBecauseInPolicy);
@ -208,7 +208,7 @@ $table_advanced->data[1][1] = print_input_text ('custom_id', $custom_id,
$table_advanced->data[2][0] = __('Interval');
$table_advanced->data[2][1] = print_input_text ('module_interval', $interval,
'', 5, 10, true, $disabledBecauseInPolicy);
'', 5, 10, true, $disabledBecauseInPolicy).print_help_tip (__('Module execution time interval (in secs).'), true);
$table_advanced->data[2][2] = __('Post process').' '.print_help_icon ('postprocess', true);
$table_advanced->data[2][3] = print_input_text ('post_process',
@ -221,6 +221,6 @@ $table_advanced->data[3][3] = print_input_text ('max', $max, '', 5, 15, true, $d
$table_advanced->data[4][0] = __('Export target');
$table_advanced->data[4][1] = print_select_from_sql ('SELECT id, name FROM tserver_export ORDER BY name',
'id_export', $id_export, '',__('None'),'0', true, false, false, $disabledBecauseInPolicy);
'id_export', $id_export, '',__('None'),'0', true, false, false, $disabledBecauseInPolicy).print_help_tip (__('In case you use an Export server you can link this module and export data to one these.'), true);
$table_advanced->colspan[4][1] = 3;
?>

View File

@ -415,7 +415,7 @@ if ($step == 2) {
$table->data[4][0] = __('Default action');
$table->data[4][1] = print_select_from_sql ('SELECT id, name FROM talert_actions ORDER BY name',
'default_action', $default_action, '', __('None'), 0,
true, false, false);
true, false, false).print_help_tip (__('In case you fill any Field 1, Field 2 or Field 3 above, those will replace the corresponding fields of this associated "Default action".'), true);
} else if ($step == 3) {
/* Alert recover */
if (! $recovery_notify) {

View File

@ -156,7 +156,7 @@ $table->data[9][1] = print_select_groups(false, "AR", false, 'id_group', $id_gro
$values = array (0 => __('No'), 1 => __('Yes'));
$table->data[10][0] = "<b>".__('Incident');
$table->data[10][1] = print_select ($values, "create_incident", $create_incident,
'','','',true);
'','','',true).' '.print_help_tip (__('Choose if the discovery of a new system creates an incident or not.'), true);
// SNMP default community
$table->data[11][0] = "<b>".__('SNMP Default community');

View File

@ -27,6 +27,15 @@ require_once('functions_io.php');
define ('ENTERPRISE_NOT_HOOK', -1);
/* Events state constants */
define ('EVENT_NEW', 0);
define ('EVENT_VALIDATE', 1);
define ('EVENT_PROCESS', 2);
/* Agents disabled status */
define ('AGENT_ENABLED',0);
define ('AGENT_DISABLED',1);
/**
* Cleans an object or an array and casts all values as integers
*

View File

@ -0,0 +1,16 @@
<?php
/**
* @package Include/help/en
*/
?>
<h1>Agent Manager</h1>
<p>
To create an Agent, you must fill this form. Please fill all the fields you need (Agent's name is required) paying special attention to <b>"IP Address"</b> and <b>"Server"</b>, remember you must choose one value for each, so the agent will be assigned to the server and it will run. IP Address default value is localhost.
</p>
<p>
"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.
</p>

View File

@ -0,0 +1,21 @@
<?php
/**
* @package Include/help/en
*/
?>
<h1>Critical Status</h1>
<p>
These field have two values, minimum and maximum. Configuring them correctly you will get that some values will show a module as critical status.
</p>
<p>
To understand better these options is better to see an example. The CPU module will be always on green in the agent status , so it simply informs of a value between 0% and 100%. If we want that the module of CPU usage will be shown in red (critical) when they pass the 90% of its use. We should configure:
</p>
<li>Critical status:90.</li>
<p>
With this, if its value is greater 90 it will be in yellow (CRITICAL), and under 90 in green (NORMAL).
</p>

View File

@ -0,0 +1,21 @@
<?php
/**
* @package Include/help/en
*/
?>
<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.
</p>
<p>
When a new alert is created the following fields must be filled in:
</p>
<ul>
<li>Agent name: The name of the agent associated with the alert.</li>
<li>Module: Alert get module value and test if it is "out of range". In afirmative case it will raise an event (seding e-mail, etc.).</li>
<li>Template: Alerts width all parameters defined. They are used to do the administrator management easier.</li>
<li>Action: Allows to choose between all the alerts that have been configured. The selected action will be added to the action that is defined in the template.</li>
</ul>

View File

@ -0,0 +1,14 @@
<?php
/**
* @package Include/help/en
*/
?>
<h1>Recon script definition</h1>
<p>The "ReconScripts" allows to work with more flexible capabilities. The recon scripts are developped in an individual way with completely specific targets, such as the network plugins or the agent plugins. Each ReconScript is different and has one purpose.</p>
<p>Its basic idea consist on "detect" things in the system it recognizes and automatically log in one monitoring (network, plugin or wmi) so in a completely customized way we could automatically log in requests in an Oracle database, new virtual host in a VmWare that is managed with VirtualCenter or we also can detect new requests in an WebLogic application Server. It is possible to do an script or application that does the task that are wanted and schedule its execution through the Recon Server.</p>
<p>A field with importance is:</p>
<p><b>Script fullpath:</b> Path to the executable script.</p>

View File

@ -0,0 +1,21 @@
<?php
/**
* @package Include/help/en
*/
?>
<h1>Warning Status</h1>
<p>
These field have two values, minimum and maximum. Configuring them correctly you will get that some values will show a module as warning status.
</p>
<p>
To understand better these options is better to see an example. The CPU module will be always on green in the agent status , so it simply informs of a value between 0% and 100%. If we want that the module of CPU usage will be shown in yellow (warning) when they reached the 70% of its use. We should configure:
</p>
<li>Warning status:70.</li>
<p>
With this, if its value is greater 70 it will be in yellow (WARNING), and under 70 in green (NORMAL).
</p>

View File

@ -0,0 +1,16 @@
<?php
/**
* @package Include/help/es
*/
?>
<h1>Gestor de Agentes</h1>
<p>
Para crear un Agente, debes rellenar este formulario. Por favor rellena todos los campos que necesites (El nombre del Agente es necesario) prestando especial atención a la <b>"IP Address"</b> y <b>"Server"</b>, recuerda que debes elegir un valor para cada uno, asi el Agente será asignado al servidor y se ejecutará. El valor por defecto de IP Address es localhost.
</p>
<p>
"Interval" se refiere al intervalo de ejecución del agente. El intervalo es cada cuanto el agente envía datos al servidor.
</p>
<p>
"Server" se refiere al Servidor de Pandora que leerá los datos enviados por el agente.
</p>

View File

@ -0,0 +1,21 @@
<?php
/**
* @package Include/help/es
*/
?>
<h1>Critical Status</h1>
<p>
Estos campos tiene dos valores, mínimo y máximo. Configurandolos correctamente se conseguirá que algunos valores se muestren en estado crítico.
</p>
<p>
Para entender mejor estas opciones mejor se puede usar un ejemplo. El módulo de CPU estará siempre en verde en el estado del agente, asi que simplemente informará de un valor entre 0% y 100%. Si se quiere que el módulo de uso de la CPU se muestre como rojo (crítico) cuando se llegue al 90% de uso. Se debería configurar:
</p>
<li>Critical status:90.</li>
<p>
Con esto, si el valor es mayor que 90 el indicador estatá en rojo (CRÍTICO), y por debajo de 70 estatá en verde (NORMAL).
</p>

View File

@ -0,0 +1,21 @@
<?php
/**
* @package Include/help/es
*/
?>
<h1>Alerts</h1>
<p>
Las Alertas en Pandora FMS reacionan a un valor "fuera de rango" de un módulo. La alerta consiste en enviar un e-mail o un SMS al administrador, enviando un trap SNMP, escribir el indcidenete en el log del sistema en el fichero de log de Pandora FMS, etc. Basicamente, una alerta puede ser cualquier cosa que pueda ser disparada por un script configurado en el Sistema Operativo donde los servidores de Pandora FMS se ejecutan.
</p>
<p>
Cuando una alerta es creada los siguiente campos deben de rellenarse:
</p>
<ul>
<li>Agent name: El nombre del agente asociado a la alarma.</li>
<li>Module: La alerta recogerá el valor del módulo y comprobará si está "fuera de rango". En caso afirmativo creará un evento (sending, e-mail, etc.).</li>
<li>Template: Alertas con todos los parámetros predefinidos. Son usadas para hacer más sencilla la gestión de las alertas porel administrador.</li>
<li>Action: Permite elegir entre todas las alertas que están configuradas. La acción seleccionada será añadida a la acción definida por el template.</li>
</ul>

View File

@ -0,0 +1,14 @@
<?php
/**
* @package Include/help/es
*/
?>
<h1>Definicion de recon script</h1>
<p>Los "ReconScripts" permiten trabajar con cosas mucho mas flexibles. Los scripts recon son desarrollados individualmente para objetivos especificos, como plugins de red o otros plugins de agentes. cada ReconScript es diferentes a la vez que sus propositos.</p>
<p>La idea basica es "detectar" cosas en el sistema que reconoce y automaticamente trazarlo en un monitor (red, plugin o wmi) asi de una manera customizada podremos trazar en una base de datos Oracle, un nuevo host virtual en VmWare gestionado con VirtualCenter o se puede detectar nuevas peticiones en un servidor de aplicaciones WebLogic. Es posible hacer un script o aplicacion que haga las tareas que queremos hacer y planificarlas a traves del servidor Recon.</p>
<p>Un campo con importancia es:</p>
<p><b>Ruta completa al Script:</b> Ruta al script ejecutable.</p>

View File

@ -0,0 +1,20 @@
<?php
/**
* @package Include/help/es
*/
?>
<h1>Warning Status</h1>
<p>
Estos campos tiene dos valores, mínimo y máximo. Configurandolos correctamente se conseguirá que algunos valores se muestren en estado de alerta.
</p>
<p>
Para entender mejor estas opciones mejor se puede usar un ejemplo. El módulo de CPU estará siempre en verde en el estado del agente, asi que simplemente informará de un valor entre 0% y 100%. Si se quiere que el módulo de uso de la CPU se muestre como amarillo (alerta) cuando se llegue el 70% de uso. Se debería configurar:
</p>
<li>Warning status:70.</li>
<p>
Con esto, si el valor es mayor que 70 el indicador estatá en amarillo (ALERTA), y por debajo de 70 estatá en verde (NORMAL).
</p>