Checkmk git commits October 2013

checkmk-commits@lists.checkmk.com

6 participants
384 discussions

Check_MK Git: check_mk: Fixed usage docs of inventory automation

by Mathias Kettner

Module: check_mk Branch: master Commit: ed4249b20e90865b1c1be809a6765501e0272f72 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ed4249b20e9086… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 21:04:40 2013 +0200 Fixed usage docs of inventory automation --- modules/automation.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/automation.py b/modules/automation.py index b5fd676..37d4ea2 100644 --- a/modules/automation.py +++ b/modules/automation.py @@ -90,7 +90,7 @@ def do_automation(cmd, args): # "refresh" - drop all services and reinventorize def automation_inventory(args): if len(args) < 2: - raise MKAutomationError("Need two arguments: [new|remove|fixall|refresh] HOSTNAME") + raise MKAutomationError("Need two arguments: new|remove|fixall|refresh HOSTNAME") how = args[0] hostname = args[1]

10 years, 11 months

Check_MK Git: check_mk: Updated bug entries #0982

by Mathias Kettner

Module: check_mk Branch: master Commit: 1c59067d777e8c4fe82931c2a02740ce4a7f2cc9 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=1c59067d777e8c… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 20:40:26 2013 +0200 Updated bug entries #0982 --- .bugs/982 | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.bugs/982 b/.bugs/982 new file mode 100644 index 0000000..f7b3731 --- /dev/null +++ b/.bugs/982 @@ -0,0 +1,9 @@ +Title: WATO: Hostlist in folder: enable checkboxes -> all should be checked +Component: wato +State: open +Date: 2013-10-09 20:39:38 +Targetversion: 1.4.0 +Class: nastiness + +When you enable the checkboxes in a WATO folder host list, +then all boxes should initially be checked.

10 years, 11 months

Check_MK Git: check_mk: WATO: feature for restricting bulk inventory to hosts with failed inv checks

by Mathias Kettner

Module: check_mk Branch: master Commit: a8b704d5d1a1be60d01cc1b2db153a45b8b27cc5 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=a8b704d5d1a1be… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 20:42:51 2013 +0200 WATO: feature for restricting bulk inventory to hosts with failed inv checks --- ChangeLog | 4 +++- web/htdocs/wato.py | 20 +++++++++++++++++++- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 3a639fc..267e43f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -39,11 +39,13 @@ WATO: * Rule "State and count of processes": New configuration options: virtual and resident memory levels + * Added title of tests to LDAP diagnose table + * Bulk inventory: new checkbox to only include hosts that have a failed + inventory check. * FIX: The rule "State and count of processes" is no longer available in "Parameters for inventorized check". This rule was solely intented for "Manual checks" configuration * FIX: Trying to prevent auth.php errors while file is being updated - * Added title of tests to LDAP diagnose table 1.2.3i2: Core: diff --git a/web/htdocs/wato.py b/web/htdocs/wato.py index 744d1ee..34d6e0e 100644 --- a/web/htdocs/wato.py +++ b/web/htdocs/wato.py @@ -2656,6 +2656,11 @@ def mode_bulk_inventory(phase): config.need_permission("wato.services") + if html.get_checkbox("only_failed_invcheck"): + failed_invcheck_hosts = find_hosts_with_failed_inventory_check() + else: + failed_invcheck_hosts = None + # 'all' not set -> only inventorize checked hosts if not html.var("all"): complete_folder = False @@ -2666,7 +2671,8 @@ def mode_bulk_inventory(phase): hostnames = get_hostnames_from_checkboxes(filterfunc) items = [ "%s|%s" % (g_folder[".path"], hostname) - for hostname in hostnames ] + for hostname in hostnames + if (failed_invcheck_hosts == None or hostname in failed_invcheck_hosts) ] for hostname in hostnames: check_host_permissions(hostname) @@ -2677,6 +2683,8 @@ def mode_bulk_inventory(phase): items = [] hostnames = [] for hostname, folder in entries: + if failed_invcheck_hosts != None and hostname not in failed_invcheck_hosts: + continue check_host_permissions(hostname, folder=folder) items.append("%s|%s" % (folder[".path"], hostname)) hostnames.append(hostname) @@ -2720,11 +2728,21 @@ def mode_bulk_inventory(phase): html.checkbox("recurse", True, label=_("Include all subfolders")) html.write("<br>") html.checkbox("only_failed", False, label=_("Only include hosts that failed on previous inventory")) + html.write("<br>") + html.checkbox("only_failed_invcheck", False, label=_("Only include hosts with a failed inventory check")) # Start button forms.end() html.button("_start", _("Start")) +def find_hosts_with_failed_inventory_check(): + hosts = html.live.query_column( + "GET services\n" + "Filter: description = Check_MK inventory\n" + "Filter: state > 0\n" + "Columns: host_name") + return hosts + #. # .-Bulk-Edit------------------------------------------------------------. # | ____ _ _ _____ _ _ _ |

10 years, 11 months

Check_MK Git: check_mk: Removed some out commented log messages

by Mathias Kettner

Module: check_mk Branch: master Commit: 452be13a2810f3f7090f7c67dfd6c7acd6eddba1 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=452be13a2810f3… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 20:14:38 2013 +0200 Removed some out commented log messages --- doc/treasures/liveproxy/liveproxyd | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/doc/treasures/liveproxy/liveproxyd b/doc/treasures/liveproxy/liveproxyd index a3f9d0e..2a7fe33 100755 --- a/doc/treasures/liveproxy/liveproxyd +++ b/doc/treasures/liveproxy/liveproxyd @@ -269,8 +269,6 @@ def get_new_requests(readable): client["state"] = "wait_for_channel" client["since"] = time.time() client["request"] = request - # log("Get new request from %s/%d (%d bytes)" % - # (sitename, client["socket"].fileno(), len(request))) except Exception, e: if opt_debug: raise @@ -302,8 +300,6 @@ def distribute_requests(): def forward_request(sitename, client, channel): cls = client["socket"] chs = channel["socket"] - # log("Forwarding request [%s] from client %s/%d to channel %s/%d" % ( - # client["request"].replace("\n","\\n"), sitename, cls.fileno(), sitename, chs.fileno())) try: chs.send(client["request"]) if not client["request"].startswith("COMMAND"): @@ -356,14 +352,10 @@ def receive_request(sitename, client): # Note: Multisite can send several requests at once. For example # a command and a wait query (reschedule button) request = client.get("nextrequest", "") - # if request: - # log("HIRN: client %s/%d noch ein Rest vom letzten mal: [%s]" % ( - # sitename, client["socket"].fileno(), request.replace("\n", "\\n"))) client["nextrequest"] = "" while "\n\n" not in request: try: chunk = client["socket"].recv(65536) - # log("HIRN: CHUNK von client: [%s]" % chunk.replace("\n", "\\n")) request += chunk except socket.error, e: if e.errno == 104: # Connection reset by peer @@ -374,12 +366,9 @@ def receive_request(sitename, client): if not chunk: log("Client %s/%d closed connection." % (sitename, client["socket"].fileno())) return None - # log("HIRN: VOR DEM SPLITTEN: [%s]" % request) end = request.index("\n\n") client["nextrequest"] = request[end+2:] request = request[:end+2] - #log("HIRN: Diesesmal: [%s], naechstes Mal: [%s]" % ( - # request.replace("\n", "\\n"), client["nextrequest"].replace("\n", "\\n"))) return request

10 years, 11 months

Check_MK Git: check_mk: FIX: liveproxyd: honor wait time after failed connect

by Mathias Kettner

Module: check_mk Branch: master Commit: 7d4dca557c0bc66a4eace76d7a7db22ed9b399e3 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=7d4dca557c0bc6… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 20:23:49 2013 +0200 FIX: liveproxyd: honor wait time after failed connect --- ChangeLog | 4 ++++ doc/treasures/liveproxy/liveproxyd | 3 +++ web/htdocs/wato.py | 2 +- 3 files changed, 8 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 2d238bd..2d7daf9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -29,6 +29,10 @@ * FIX: avoid duplicate output of log message in log tables * FIX: fixed problem with ldap userid encoding + Livestatus-Proxy: + * FIX: fix exception when printing error message + * FIX: honor wait time (now called cooling period) after failed TCP connection + WATO: * Rule "State and count of processes": New configuration options: virtual and resident memory levels diff --git a/doc/treasures/liveproxy/liveproxyd b/doc/treasures/liveproxy/liveproxyd index 2a7fe33..11c857c 100755 --- a/doc/treasures/liveproxy/liveproxyd +++ b/doc/treasures/liveproxy/liveproxyd @@ -108,6 +108,7 @@ def initiate_connections(): s.connect(siteconf["socket"]) except socket.error, e: if e.errno != 115: # "Operation now in progress" + sitestate["last_failed_connect"] = time.time() if opt_debug: raise else: @@ -115,6 +116,7 @@ def initiate_connections(): break except Exception, e: + sitestate["last_failed_connect"] = time.time() if opt_debug: raise log("Error: cannot create TCP channel to %s:%d: %s" % (siteconf["socket"] + (e,))) @@ -135,6 +137,7 @@ def do_heartbeats(): if age >= timeout: log("Heartbeat timeout after %.1f sec on channel %s/%d" % ( age, sitename, channel["socket"].fileno())) + sitestate["last_failed_connect"] = now disconnect_from_site(sitename) else: if now - since >= rate: diff --git a/web/htdocs/wato.py b/web/htdocs/wato.py index 61992b4..744d1ee 100644 --- a/web/htdocs/wato.py +++ b/web/htdocs/wato.py @@ -6890,7 +6890,7 @@ def mode_edit_site(phase): ), ( "connect_retry", Float( - title = _("Wait time after failed connect"), + title = _("Cooling period after failed connect/heartbeat"), minvalue = 0.1, unit = _("sec"), default_value = 4.0,

10 years, 11 months

Check_MK Git: check_mk: Filtering in views by Hostalias is possible now too

by Bernd Stroessenreuther

Module: check_mk Branch: master Commit: 265774a99d93de96dd23183a598ebaab8501bb46 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=265774a99d93de… Author: Bernd Stroessenreuther <bs(a)mathias-kettner.de> Date: Wed Oct 9 19:02:58 2013 +0200 Filtering in views by Hostalias is possible now too --- ChangeLog | 3 +++ web/plugins/views/filters.py | 3 +++ 2 files changed, 6 insertions(+) diff --git a/ChangeLog b/ChangeLog index 2d238bd..1ee5e64 100644 --- a/ChangeLog +++ b/ChangeLog @@ -28,6 +28,9 @@ * FIX: ldap attribute plugins: fixed crash when parameters are None * FIX: avoid duplicate output of log message in log tables * FIX: fixed problem with ldap userid encoding + * Filtering in views by Hostalias is possible now too + (however the filter is not displayed in any standard view - user needs + to enable it by customizing the needed views himself) WATO: * Rule "State and count of processes": New configuration options: diff --git a/web/plugins/views/filters.py b/web/plugins/views/filters.py index 958e950..5b36e3c 100644 --- a/web/plugins/views/filters.py +++ b/web/plugins/views/filters.py @@ -59,6 +59,9 @@ declare_filter(100, FilterText("hostregex", _("Hostname"), "host", declare_filter(101, FilterText("host", _("Hostname (exact match)"), "host", "host_name", "host", "="), _("Exact match, used for linking")) +declare_filter(102, FilterText("hostalias", _("Hostalias"), "host", "host_alias", "hostalias", "~~"), + _("Search field allowing regular expressions and partial matches")) + declare_filter(200, FilterText("serviceregex", _("Service"), "service", "service_description", "service", "~~"), _("Search field allowing regular expressions and partial matches"))

10 years, 11 months

Check_MK Git: check_mk: Updated bug entries #0981

by Mathias Kettner

Module: check_mk Branch: master Commit: ae41433f99cfdc755a8e7e048a25be78b18a742f URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=ae41433f99cfdc… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 18:51:36 2013 +0200 Updated bug entries #0981 --- .bugs/981 | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/.bugs/981 b/.bugs/981 new file mode 100644 index 0000000..931e24f --- /dev/null +++ b/.bugs/981 @@ -0,0 +1,15 @@ +Title: liveproxyd: keep site closed for a while after an error +Component: livestatus +State: open +Date: 2013-10-09 18:48:24 +Targetversion: 1.2.3i3 +Class: todo + +When the livestatus proxy daemon cannot connect to a site +for any reason, or if a heartbeat fails, it should mark +that site dead for a certain time (e.g. 30 seconds). Maybe +we even binary backoff this time each time a problem +occurrs. That way we tackle: + +- flapping connections +- problems with permament errors (cannot resolve hostname)

10 years, 11 months

Check_MK Git: check_mk: liveproxyd: fix exception in error message

by Mathias Kettner

Module: check_mk Branch: master Commit: c533dca0c2c8c4d3b883c5cf7d3773de5b9a360d URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c533dca0c2c8c4… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 18:48:18 2013 +0200 liveproxyd: fix exception in error message --- doc/treasures/liveproxy/liveproxyd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/treasures/liveproxy/liveproxyd b/doc/treasures/liveproxy/liveproxyd index da924c1..a3f9d0e 100755 --- a/doc/treasures/liveproxy/liveproxyd +++ b/doc/treasures/liveproxy/liveproxyd @@ -111,13 +111,13 @@ def initiate_connections(): if opt_debug: raise else: - log("Error: cannot create TCP channel to %s:%d: %d" % siteconf["socket"] + (e,)) + log("Error: cannot create TCP channel to %s:%d: %s" % (siteconf["socket"] + (e,))) break except Exception, e: if opt_debug: raise - log("Error: cannot create TCP channel to %s:%d: %d" % siteconf["socket"] + (e,)) + log("Error: cannot create TCP channel to %s:%d: %s" % (siteconf["socket"] + (e,))) break channels.append({ "socket" : s, "state" : "connecting", "since": time.time()})

10 years, 11 months

Check_MK Git: check_mk: FIX: df: correctly hilight WARN/CRIT markers

by Mathias Kettner

Module: check_mk Branch: master Commit: 9a76fbf907dbd91a9c07f789d50f672806076e0c URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9a76fbf907dbd9… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 17:40:12 2013 +0200 FIX: df: correctly hilight WARN/CRIT markers --- checks/df.include | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/checks/df.include b/checks/df.include index 28d67a2..477dbe6 100644 --- a/checks/df.include +++ b/checks/df.include @@ -310,12 +310,13 @@ def df_check_filesystem_single(hostname, mountpoint, size_mb, avail_mb, params): wa, cr = trend_mb warn_perf, crit_perf = wa, cr if trend >= wa: - problems.append("growing too fast (levels at %s/%s per %.1fh)!" % + problems.append("growing too fast (levels at %s/%s per %.1fh)(!" % ( get_bytes_human_readable(wa * MB), get_bytes_human_readable(cr * MB), range)) status = max(1, status) if trend >= cr: status = 2 problems[-1] += "!" + problems[-1] += ")" else: wa, cr = None, None @@ -331,12 +332,13 @@ def df_check_filesystem_single(hostname, mountpoint, size_mb, avail_mb, params): else: warn_perf, crit_perf = wa, cr if trend >= wa: - problems.append("growing too fast (levels at %.3f%%/%.3f%% per %.1fh)!" % + problems.append("growing too fast (levels at %.3f%%/%.3f%% per %.1fh)(!" % ( wa_perc, cr_perc, range)) status = max(1, status) if trend >= cr: status = 2 problems[-1] += "!" + problems[-1] += ")" if levels.get("trend_perfdata"): # New in 1.1.13i3: output trend not as MB / trend_range, but as @@ -357,10 +359,10 @@ def df_check_filesystem_single(hostname, mountpoint, size_mb, avail_mb, params): wa, cr = timeleft if hours_left <= cr: status = 2 - problems.append("only %.1fh until disk full!!" % hours_left) + problems.append("only %.1fh until disk full(!!)" % hours_left) elif hours_left <= wa: status = max(status, 1) - problems.append("only %.1fh until disk full!" % hours_left) + problems.append("only %.1fh until disk full(!)" % hours_left) elif hours_left <= wa * 2: problems.append("time left: %.1fh" % hours_left)

10 years, 11 months

Check_MK Git: check_mk: Translated draft for rule based notifications

by Mathias Kettner

Module: check_mk Branch: master Commit: 00bedd4ae4902ae556204d00c232c50888d62e5a URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=00bedd4ae4902a… Author: Mathias Kettner <mk(a)mathias-kettner.de> Date: Wed Oct 9 17:32:48 2013 +0200 Translated draft for rule based notifications --- doc/drafts/README.rule_based_notifications | 189 ++++++++++++++++++++++++++++ 1 file changed, 189 insertions(+) diff --git a/doc/drafts/README.rule_based_notifications b/doc/drafts/README.rule_based_notifications new file mode 100644 index 0000000..49f5775 --- /dev/null +++ b/doc/drafts/README.rule_based_notifications @@ -0,0 +1,189 @@ +Michael Gorn. + +Starting point: Check_MK's "Flexible Notifications" are to a decent +degree more flexible than Nagios' builtin notification system. +There are some situations' however, where even more flexiblity +is desirable. Furthermore - if you have a larger number of users +then the configuration of the notification profiles for each user +is very inconveniant. + +This white pager suggest a new notificatin system that tackles +these problems and is easily extendable for the future. + +RULE BASED NOTIFICATIONS +------------------------ +The basic idea is that notifications are processed by a rule +based engine - very similar to the "Event Console". A notifcation +is in the first place independent of an actual user. It goes +as follows: + +1. The monitoring Core (Nagios/Icinga/CMC) creates a host or service *Alert*. + +2. That alert is being notified by a general global contact calles "checkmk-notify". + +3. That contact has "cmk --notify" configured as its notification command. By + means of an environment variable it gets the list of contacts of the object + for later reference. The actual contacts themselves have notifications disabled. + This avoid duplicate notifications. + +4. Now the notifications goes through a chain of notification rules, which + can be edited via WATO (similar to the one in the Event Console). One difference + to the EC is, that in the notification system *all* rules will be applied, + even if a previous rule already matched. That is important in order to have + more then one notification being sent. + + +RULES +----- +The rules have a structure similar to those in the Event Console. There are +being edited by a dedicated WATO mdule. Each rule consits of a condition +and a notification action. + +The condition can be formed of: +* whether a certain timeperiod is currenlty active +* the notification number (i.e. phase of escalation) +* the service level (a number that can be attached to each host/service) +* the event type (up, down, ok, crit, etc.) +* a host specification like in WATO rules (using host tags, etc.) +* a service specification using regular expressions (like in WATO rules) + +Further kinds of conditions that we can think of are: +* The original state or the complete state transition (e.g. CRIT -> WARN vs. OK -> WARN) +* the type of the check plugin, e.g. only checks of type "if" or "if64" +* whether the host or service is contained in a certain host/service group +* whether it's contained in a certain contact group +* whether it has a certain contact +* the value of a certain user defined custom variable + +When all conditions of a rule are fullfilled, then it matches +and its action is executed. The action consist of: + +* Who should be notified? + a) all contacts of the host/service + b) an explicit list of contacts + c) all members of a certain contact group + d) an explicit email/pager address + e) all contacts + +* Which plugin should be used for notification? (email, sms, pager, etc.) + +* The parameters of that plugin + +Note: the action is not immediately executed but added to the +list of planned notifications. This list contains of triples +of the following strucute: + + Contact, Plugin, Parameters + +Also each rule has a checkbox: + [ ] allow users to deactivate this notification + + +CANCELLING RULES +---------------- +In ord to be able to better configure exceptions there could be +a second type of rules: cancelling rules. They have the same +structure as the normal rules when in comes to conditions. +Also the selection of the contacts is the same. The plugins +section is now not a choice of once, but a list of checkboxes +where several plugins can be selected. No plugin parameters +need to be confiured here. + +When a cancelling rule matches then all previously selected +notifications to the specified users with the specified +plugins are cancelled. Such a rule could mean e.g. +"Do not notifiy Hubert during the Weekend via SMS". + +The order of the normal and cancelling rules is honored. +Example: + +Rule 1 ... +Rule 2 ... +Rule 3 -> create Notification to A and B with plugin P +Rule 4 ... +Rule 5 -> cancel notifcation to B via plugin P + +--> only A is going to be notified with P + +Note: Since always *all* Rules are applied - even if one already +matched - you need to specify the exceptions *after* the general +case. This is the opposite way as in the Event Console. + +Normal rules and cancelling rules can follow each other in an +arbitrary order. That way you can first create a notifcation +to all contacts, then remove a list of contacts and finally +add again one single contact to the notification list. + +After all rules have been tries and the notifcation table +is finalized, all notifications are being sent out. Duplicates +are removed, of course. + +USER-RULES +---------- +We want to keep the current feature that a user is able to configure +is notifications himself. Therefore each user has his/her own chain +of notification rules. They have the same structure as the global +ones except that the user cannot specify any contact other then +himself as a target. + +The user rules are always executed after the global rules. As +state above a notification created by a global rule can be locked +against a cancelling by the user. + +User user can: +- add notifications +- cancell notifications that have their origin in global rules + +Note: that way a user can "subscribe" to notifications +of certain hosts and services - regardless of whether he is +a contact of that object in the monitoring. + + +FALLBACK +-------- +When a notification is matched by no rule then - as a fallback - an +email is being sent to a globally configured address - to make sure +that no notifiation is being lost due to a misconfiguration. + + +IMPLEMENTATION IN WATO +---------------------- +Within WATO the new notifcation system looks like this: + +* A new global option enabled the "Rule based Notifications". + In some future release that option might be removed together + with the current "Flexible Notifications". In the first version + this defaults to "off". + +* If they are enabled, then the notification options in the users + settings of all users change. The current block of options is + completely being removed. Instead a new button "Notifications" + will bring the user/admin to the user-owned chain of notification + rules. There is no switch for enabling/disabling notifications + anymore. This can be done by a rule, if needed. + +* If currently there are alrady flexible notifications configured, + they will *not* be converted. But they are kept in the configuration + in case you switch the rule based system off again later. + +* A new WATO module shows the global notification rules. That is + almost identical with that of the user specific rules. + + In the module you can create, modify and delete rules and change + their order - just like in the Event Console. We also can create + a simulation field for trying out the rule chain. + + +IMPLEMENTATION IN CHECK_MK +-------------------------- +cmk --notify needs to detetec a rule based notifcation. This could +be tied to the special contact name "checkmk-notify". It is then +executing the chain of rules, which is saved the usual way in +configuration variable of check_mk (like in main.mk). In addtion +all user specify rules are being applied. + +In notify.log you get an exact documentation, why which rule triggered +or not (presumed you have a high enough log level). + +During the configuration generation for Nagios/CMC a special user +needs to be created who is contact for everything.

10 years, 11 months

← Newer
1
...
28
29
30
31
32
33
34
...
39
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Checkmk git commits October 2013