Hi,

Du kannst auch eine Master Site aufsetzen ohne die Konfiguration zentral machen 
zu müssen. Einfach die Remote Site unter Distributed Monitoring hinzufügen.
In den Wato Optionen sagt man dann "no replication with this site" und fertig.

Genau genommen brauchst Du nicht mal eine Master Site, sondern kannst das in 
jeder Site machen, um dort die Stati der anderen Site zu "importieren".


Gruß

Udo


----- Ursprüngliche Mail -----
Von: "Aleksej Baer" <b...@citkomm.de>
An: "Ralf Prengel" <ralf.pren...@rprengel.de>, 
checkmk-de@lists.mathias-kettner.de
Gesendet: Freitag, 2. Februar 2018 15:47:52
Betreff: Re: [Check_mk (deutsch)]  andere Site auf host Status prüfen

>CEE
Hallo Ralf, gibt es dann einen Grund wieso ihr keine zentrale Master-Site habt?
Oder wollt ihr bewusst keine zentrale Verwaltung für eure Sites und Hosts haben?

Wir haben aktuell 12 Sites als Slave und eine Site als Master (alles auf 
unterschiedlichen Servern).
Jede Site überwacht halt ihre eigene Hosts, wobei alle Hosts auf dem Master zu 
sehen sind, da die Slave-Sites an den Master die Infos per Livestatus senden. 
Welcher User was sehen und machen darf, wird über Rollen, Kontaktgruppen und 
Ansichten festgelegt.
Die Konfiguration für alle Sites lässt sich über die WATO auf der Master-Site 
regeln. So hat man dann alles Zentral und daher einfacher zu verwalten.

Falls ihr die Sites aus irgendeinem Grund doch separat halten wollt, dann kann 
man die Sites trotzdem per Livestatus abfragen.
z.B. listet folgender Befehl alle Hosts mit nicht-OK-Status auf einem 
bestimmten CheckMK-Server/Site:
echo -e 'GET hosts\nColumns: host_name state\nFilter: state != 0' | netcat 
DNS-NAME-DEINES-CMK-SERVERS 6557 | sort

Auf die Weise kannst zu die Ergebnisse der Überwachung von anderen Sites 
auslesen. Was du damit machst ist dann dir überlassen.
Du kannst z.B. einen einfachen Check schreiben der die Ausgabe nach dir 
interessanten Hosts parst und dann die Ergebnisse, z.B. auf einen Dummy-Host 
auf deiner Site per Piggyback anhängt. (also einen ping-only-Host mit lokalen 
Site-IP anlegen und per Piggyback auf diesen die neue Services anhängen, welche 
die Status von dir ausgewählten Hosts anzeigen).

Hier sind die Felder die man per Livestatus abfragen kann:
Bei Host-Abfrage:
accept_passive_checks;acknowledged;acknowledgement_type;action_url;action_url_expanded;active_checks_enabled;address;alias;check_command;check_command_expanded;check_flapping_recovery_notification;check_freshness;check_interval;check_options;check_period;check_type;checks_enabled;childs;comments;comments_with_extra_info;comments_with_info;contact_groups;contacts;current_attempt;current_notification_number;custom_variable_names;custom_variable_values;custom_variables;display_name;downtimes;downtimes_with_info;event_handler;event_handler_enabled;execution_time;filename;first_notification_delay;flap_detection_enabled;flappiness;groups;hard_state;has_been_checked;high_flap_threshold;icon_image;icon_image_alt;icon_image_expanded;in_check_period;in_notification_period;in_service_period;initial_state;is_executing;is_flapping;last_check;last_hard_state;last_hard_state_change;last_notification;last_state;last_state_change;last_time_down;last_time_unreachable;last_time_up;latency;long_plugin_output;low_flap_threshold;max_check_attempts;metrics;mk_inventory;mk_inventory_gz;mk_inventory_last;mk_logwatch_files;modified_attributes;modified_attributes_list;name;next_check;next_notification;no_more_notifications;notes;notes_expanded;notes_url;notes_url_expanded;notification_interval;notification_period;notifications_enabled;num_services;num_services_crit;num_services_hard_crit;num_services_hard_ok;num_services_hard_unknown;num_services_hard_warn;num_services_ok;num_services_pending;num_services_unknown;num_services_warn;obsess_over_host;parents;pending_flex_downtime;percent_state_change;perf_data;plugin_output;pnpgraph_present;previous_hard_state;process_performance_data;retry_interval;scheduled_downtime_depth;service_period;services;services_with_fullstate;services_with_info;services_with_state;smartping_timeout;staleness;state;state_type;statusmap_image;total_services;worst_service_hard_state;worst_service_state;x_3d;y_3d;z_3d

Bei Service-Abfrage:
accept_passive_checks;acknowledged;acknowledgement_type;action_url;action_url_expanded;active_checks_enabled;cache_interval;cached_at;check_command;check_command_expanded;check_flapping_recovery_notification;check_freshness;check_interval;check_options;check_period;check_type;checks_enabled;comments;comments_with_extra_info;comments_with_info;contact_groups;contacts;current_attempt;current_notification_number;custom_variable_names;custom_variable_values;custom_variables;description;display_name;downtimes;downtimes_with_info;event_handler;event_handler_enabled;execution_time;first_notification_delay;flap_detection_enabled;flappiness;groups;hard_state;has_been_checked;high_flap_threshold;host_accept_passive_checks;host_acknowledged;host_acknowledgement_type;host_action_url;host_action_url_expanded;host_active_checks_enabled;host_address;host_alias;host_check_command;host_check_command_expanded;host_check_flapping_recovery_notification;host_check_freshness;host_check_interval;host_check_options;host_check_period;host_check_type;host_checks_enabled;host_childs;host_comments;host_comments_with_extra_info;host_comments_with_info;host_contact_groups;host_contacts;host_current_attempt;host_current_notification_number;host_custom_variable_names;host_custom_variable_values;host_custom_variables;host_display_name;host_downtimes;host_downtimes_with_info;host_event_handler;host_event_handler_enabled;host_execution_time;host_filename;host_first_notification_delay;host_flap_detection_enabled;host_flappiness;host_groups;host_hard_state;host_has_been_checked;host_high_flap_threshold;host_icon_image;host_icon_image_alt;host_icon_image_expanded;host_in_check_period;host_in_notification_period;host_in_service_period;host_initial_state;host_is_executing;host_is_flapping;host_last_check;host_last_hard_state;host_last_hard_state_change;host_last_notification;host_last_state;host_last_state_change;host_last_time_down;host_last_time_unreachable;host_last_time_up;host_latency;host_long_plugin_output;host_low_flap_threshold;host_max_check_attempts;host_metrics;host_mk_inventory;host_mk_inventory_gz;host_mk_inventory_last;host_modified_attributes;host_modified_attributes_list;host_name;host_next_check;host_next_notification;host_no_more_notifications;host_notes;host_notes_expanded;host_notes_url;host_notes_url_expanded;host_notification_interval;host_notification_period;host_notifications_enabled;host_num_services;host_num_services_crit;host_num_services_hard_crit;host_num_services_hard_ok;host_num_services_hard_unknown;host_num_services_hard_warn;host_num_services_ok;host_num_services_pending;host_num_services_unknown;host_num_services_warn;host_obsess_over_host;host_parents;host_pending_flex_downtime;host_percent_state_change;host_perf_data;host_plugin_output;host_pnpgraph_present;host_previous_hard_state;host_process_performance_data;host_retry_interval;host_scheduled_downtime_depth;host_service_period;host_services;host_services_with_fullstate;host_services_with_info;host_services_with_state;host_smartping_timeout;host_staleness;host_state;host_state_type;host_statusmap_image;host_total_services;host_worst_service_hard_state;host_worst_service_state;host_x_3d;host_y_3d;host_z_3d;icon_image;icon_image_alt;icon_image_expanded;in_check_period;in_notification_period;in_service_period;initial_state;is_executing;is_flapping;last_check;last_hard_state;last_hard_state_change;last_notification;last_state;last_state_change;last_time_critical;last_time_ok;last_time_unknown;last_time_warning;latency;long_plugin_output;low_flap_threshold;max_check_attempts;metrics;modified_attributes;modified_attributes_list;next_check;next_notification;no_more_notifications;notes;notes_expanded;notes_url;notes_url_expanded;notification_interval;notification_period;notifications_enabled;obsess_over_service;pending_flex_downtime;percent_state_change;perf_data;plugin_output;pnpgraph_present;previous_hard_state;process_performance_data;retry_interval;scheduled_downtime_depth;service_period;staleness;state;state_type

VG,
Aleksej
_______________________________________________
checkmk-de mailing list
checkmk-de@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-de
_______________________________________________
checkmk-de mailing list
checkmk-de@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-de

Antwort per Email an