Diferencias

Muestra las diferencias entre dos versiones de la página.

--- manuales:nagios:thruk [2015/04/23 19:54] – [Configuración de Thruk] cayu
+++ manuales:nagios:thruk [2015/10/22 14:46] (actual) – [API] cayu
@@ Línea 265: / Línea 265: @@
 ^info_popup_options|Options for the popup window used for long pluginoutput, downtimes and comments.\\ See http://www.bosrup.com/web/overlib/?Command_Reference for what options are available|info_popup_options = STICKY,CLOSECLICK,HAUTO,MOUSEOFF|
 ^show_notification_number|Display the current number of notification after the current / max attempts on the status details page.|show_notification_number = 0|
+^show_backends_in_table|Display the backend/site name in the status table. This is useful if you have same hosts or services on different backends and need to know which one returns an error.|Valid values are:\\ 1 - show site name at the end\\ 2 - put site name in front\\ \\ show_backends_in_table = 0|
+^show_config_edit_buttons|Show links to config tool for each host / service. You need to have the config tool plugin enabled and you need proper permissions for the link to appear.|show_config_edit_buttons = 1|
+^show_full_commandline|Display the full command line for host / service checks . Be warned, the command line could contain passwords and other confidential data. In order to replace the user macros for commands, you have to set the 'resource_file' in your peer config or a general resource_file option.\\ 0 = off, don’t show the command line at all\\ 1 = show them for contacts with the role: authorized_for_configuration_information \\ 2 = show them for everyone|show_full_commandline = 0|
+^show_full_commandline_source|Usually the source of your expanded check_command should be the check_command attribute of your host / service. But under certain circumstances you might want to use display expanded commands from a custom variable. In this case, set 'show_full_commandline_source' to '_CUST_VAR_NAME'.|show_full_commandline_source = check_command|
+^show_logout_button|Show additional logout button next to the top right preferences button. (works only together with cookie authentication)|show_logout_button=1|
+^show_long_plugin_output|When a plugin returns more than one line of output, the output can be displayed directly in the status table, as popup or not at all. Choose between popup, inline and off|show_long_plugin_output = popup|
+^status_color_background|Color complete status line with status colour or just the status itself.|status_color_background=0|
+^show_modified_attributes|Show if a host / service has modified attributes.|show_modified_attributes = 1|
+^show_host_attempts|Show check attempts for hosts too. The default is to show them on the problems page only. Use this value to force a value.|show_host_attempts = 1|
+^perf_bar_mode|This option enables a performance bar inside the status/host list which create a graph from the performance data of the plugin output. Available options are 'match', 'first', 'all', 'worst' and 'off'.\\ match: try to set graph which matches the output\\ all: graph all performance values available\\ first: graph only the first performance value\\ worst: graph only the graph for the worst state\\ off: graph no value at all|perf_bar_mode = match|
+^perf_bar_pnp_popup|Show pnp popup if performance data are available and pnp is used as graph engine.|perf_bar_pnp_popup = 1|
+^shown_inline_pnp|Show inline pnp graph if available. If a service or host has a pnp4nagios action or notes url set.\\ Thruk will show a inline graph on the extinfo page.\\ This works for /pnp4nagios/ urls and /pnp/.|shown_inline_pnp = 1|
+^graph_word|graph_word is a regexp used to display any graph on the details page. if a service or host has a graph url in action url (or notes url) set it can be displayed by specifying a regular expression that always appears in this url. You can specify multiple graph_words.When using pnp4nagios, no graph_word is required, just keep it empty.|graph_word = /render/ # for graphite|
+^show_custom_vars|Show custom vars in host / service ext info. List variable names to display in the host and service extinfo details page. Can be specified more than once to define multiple variables. You may use html in your variables. Use * as wildcard, ex.: _VAR*|show_custom_vars = _VAR1|
+^expand_user_macros|Expand user macros ($USERx$) for host / service commands and custom variables.\\ Can be specified more than once to define multiple user macros to expand.\\ Be warned, some user macros can contain passwords and expanding them could expose them to unauthorized users. Use * as wildcard, ex.: USER*\\ Defaults to 'ALL' which means all user macros are expanded, because its limited to admin users anyway.|expand_user_macros = USER1\\ expand_user_macros = USER10-20\\ expand_user_macros = PLUGIN*\\ expand_user_macros = ALL  # expands all user macros\\  expand_user_macros = NONE # do not expand user macros|
+^show_error_reports|Show link to bug reports when internal errors occur. Set to '1' to show a error icon which links to a error report mail. Set to 'server' to log js error server side. Set to 'both' to log server side but still show the icon.|show_error_reports = both|
+^skip_js_errors|don’t report some known harmless javascript errors|skip_js_errors = cluetip is not a function|
+^strict_passive_mode|Normally passive checks would be marked as disabled.\\ With this option set, disabled checks will only be displayed as disabled if their last result was active. Otherwise they would be marked as passive checks.\\ This option also changes the passive icon only to be shown when the last check was passive, otherwise the disabled icon will be displayed.|strict_passive_mode = 1|
+^hide_passive_icon|Normally passive checks whould be displayed with a passive icon if their last result is passive. With this option, passive icon will be hidden in status details.|hide_passive_icon = 0|
+^sitepanel|The sitepanel is used to display multiple backends/sites at a glance. With than 10 or more sites, the list of backends will be combined into the 'compact' site panel which just displays the totals of available / down / disabled sites. The 'compact' panel will also automatically be used if you use sections. With more than 50 backends, the 'collapsed' will be selected in 'auto' mode. Set sitepanel to list/compact/collapsed/auto/off to change the default behaviour.|sitepanel = auto|
+^apache_status|You can integrate the output of apache status into Thruk. The following list of apache status pages will be accessible from the performance info page.\\ Make sure the page is accessible from Thruk, credentials will be passed through. So both, basic authentication or ip based authentication would be possible.\\ Read more about Apaches mod_status here: http://httpd.apache.org/docs/current/mod/mod_status.html|<code><apache_status>
+  Site        http://127.0.0.1:5000/server-status
+  System      http://127.0.0.1/server-status
+  Other       http://127.0.0.1/server-status
+</apache_status></code>|
 === Opciones de conexión ===
+=== Cookie Authentication Settings ===
+=== Command Settings ===
+=== Cron Settings ===
+=== Action Menu Settings ===
+=== Icinga Settings ===
+=== Shinken Settings ===
+=== Other Settings ===
+=== Component Thruk::Backend ===
+=== Component Thruk::Plugin::ConfigTool ===
+=== Component Thruk::Plugin::Panorama ===
+=== Component Thruk::Plugin::Reports2 ===
+=== Component Thruk::Plugin::Statusmap ===
+=== Component Thruk::Plugin::Minemap ===
+=== Component Thruk::Plugin::BP ===
+=== User & Group Specific Overrides ===
 ==== Configuración de CGI ====
@@ Línea 594: / Línea 636: @@
 </code>
-=== Monitoring::Livestatus ===
-API de Perl para acceder a datos Nagios e Icinga por medio de check_mk livestatus
-<code perl>
-use Monitoring::Livestatus;
-    my $ml = Monitoring::Livestatus->new(
-      socket => '/var/lib/livestatus/livestatus.sock'
-    );
-    my $hosts = $ml->selectall_arrayref("GET hosts");
-</code>
-== new ([ARGS]) ==
-Creates an Monitoring::Livestatus object. new takes at least the socketpath. Arguments are in key-value pairs.
-Crea el objeto Monitoring::Livestatus. Toma la ruta del socket.
-^Argumentos^^
-^socket|Ruta al socket UNIX de check_mk livestatus|
-^server|Usar este servidor para una conexión TCP|
-^peer|Camino alternativo al socket o servidor, si se usa el valor ':' va a ser usado servidor sino socket|
-^name|Nombre para la conexión, default dirección socket/server|
-^verbose|Modo verbose|
-^line_seperator|Código ascii separador de líneas default 10, (newline)|
-^column_seperator|Código ascii separador de columnas, defaults 0 (null byte)|
-^list_seperator|Código ascii separador de listas, default 44 (comma)|
-^host_service_seperator|Código ascii separador host/service, default 124 (pipe)|
-^keepalive|keepalive. Default off|
-^errors_are_fatal|Errores con mensaje de caída. Default: on|
-^warnings|muestran advertencias en las consultas sin Columnas|
-^timeout|Tiempo de espera general. Usado para conexión y consultas|
-^query_timeout|set a query timeout. Used for retrieving querys, Default 60sec|
-^connect_timeout|Tiempo de espera de conexión inicial. Por defecto 5 s|
-== Limit ==
-<code perl>
-my $array_ref = $ml->selectcol_arrayref(
-       "GET hosts\nColumns: name contacts",
-       { Limit => "10,20" }
-    );
-</code>
-== Otros ejemplos ==
-<code perl>
-#!/usr/bin/perl
-use Monitoring::Livestatus;
-$filtergrp = 'NAGIOS_ARGENTINA';
-$ml = Monitoring::Livestatus->new(
-	socket => '/usr/local/nagios/var/rw/live'
-);
-my $up = $ml->selectscalar_value("GET hosts\nFilter: host_groups >= $filtergrp\nStats: state = 0");
-my $down = $ml->selectscalar_value("GET hosts\nFilter: host_groups >= $filtergrp\nStats: state = 1");
-my $unknown = $ml->selectscalar_value("GET hosts\nFilter: host_groups >= $filtergrp\nStats: state = 2");
-my $total = $up + $down + $unknown;
-print "$down\/$total \n";
-</code>
 ===== Acerca de la Guía =====
 Esta guía **no oficial** esta inspirada en la documentación original de Thruk. Está pensada para ir presentando casos de uso que se van dando en la operatoria día a dia.