Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 1397: juniper_screenos_cpu, juniper_screenos_fan, juniper_screenos_mem, juniper_screenos_temp, juniper_screenos_vpn: new checks for Juniper ScreenOS Firewalls

by Mathias Kettner

ID: 1397 Title: juniper_screenos_cpu, juniper_screenos_fan, juniper_screenos_mem, juniper_screenos_temp, juniper_screenos_vpn: new checks for Juniper ScreenOS Firewalls Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i6

10 years

Check_MK Werk 1383: oracle_asm_diskgroup: Account for offline disks and required mirror free space

by Bruhns＠mathias-kettner.de

ID: 1383 Title: oracle_asm_diskgroup: Account for offline disks and required mirror free space Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i6 New rule in WATO is requirred to account this change. The old filesystem_default_levels is replaced by asm_diskgroup_default_levels. WATO use the new rulename but old values must be migrated to asm_diskgroup_default_levels.

10 years

Check_MK Werk 1384: oracle_jobs: new WATO rules, changed service name to SID.OWNER.NAME

by Bruhns＠mathias-kettner.de

ID: 1384 Title: oracle_jobs: new WATO rules, changed service name to SID.OWNER.NAME Component: check Level: 2 Class: New Feature Version: 1.2.5i6 The name of the services have changed. This change is required, because a job in ORACLE is only unique with the owner. New format: <tt>ORA</tt> <tt>SID.JOB_OWNER.JOB_NAME</tt> <tt>Job<tt> Disabled jobs are no longer ignored at inventory. New rules are added to configure the behaviour of disabled jobs and run duration. A reinventory of all ORACLE jobs is required!

10 years

Check_MK Werk 1383: Offline disks and rewuired mirror free space are accounted in oracle_asm_diskgroup

by Bruhns＠mathias-kettner.de

ID: 1383 Title: Offline disks and rewuired mirror free space are accounted in oracle_asm_diskgroup Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i6 New rule in WATO is requirred to account this change. The old filesystem_default_levels is replaced by asm_diskgroup_default_levels. WATO use the new rulename but old values must be migrated to asm_diskgroup_default_levels.

10 years

Check_MK Werk 1395: Event Console can now create notifications via Check_MK RBN

by Mathias Kettner

ID: 1395 Title: Event Console can now create notifications via Check_MK RBN Component: Event Console Level: 2 Class: New Feature Version: 1.2.5i6 The Event Console has now the new builtin action Send monitoring notification that can be used in all three situations where actions are possible: <ul> <li>When an event is being opened</li> <li>When an event is being cancelled</li> <li>By a user executing an action on an open event</li> </ul> This new action creates a monitoring notification just as the ones that happen, when in normal (non-EC) monitoring a service goes from OK to CRIT or vice versa. This notification is being process by the rule based notifications and is handled just like a monitoring notification. Why whould you want to do that? <ul> <li>You can use the same notification plugins for alarms triggered by the monitoring and by the Event Console. No need for an extra SMS script in the Event Console.</li> <li>You can use all of the flexiblity of existing notification plugins - including configuring their parameters via WATO.</li> <li>All notifications from your Check_MK environment are now controlled by a common set of notification rule. For example if a user wants to disable all of his notifications then there is just one place for doing that.</li> </ul> There is nothing you need to setup. Just check the action Send monitoring notification in your event rules and that's it. Note: Because events are not exactly the same as services and because of the nature of distributed monitoring there are a few specialities in notifications that come from the Event Console: <ul> <li>EC notifications have only limited information about the host. There is no information about host tags or WATO folders. Do not use matching criteria on those or otherwise that match will always fail.</li> <li>EC notifications currently have no information about contacts or groups of a host. This would need an online Livestatus query, but that would fail if the host is being monitored by a remote system.</li> <li>EC notifications do not have a previous host or service state, since the Event Console is a stateless monitoring. Do not set any matching criteria on the event type since none of these can be fullfilled currently.</li> <li>All EC notifications are sent as service notifications. The name of the event's application is taken as service description.</li> </ul> The notification rules have got a new matching option especially for EC notifications: Event Console alerts. Here you can make a notification rule deal only with EC notifications or exclude just those. You can also match on EC specific fields like the event's rule id, syslog priority, syslog facility and event comment. Most of the event's special fields are available as notification context variables - to be used in custom notification scripts or template definitions. Please use the standard debugging methods for displaying all variables. At least defined are <tt>EC_ID</tt>, <tt>EC_RULE_ID</tt>, <tt>EC_PRIORITY</tt>, <tt>EC_FACILITY</tt>, <tt>EC_PHASE</tt>, <tt>EC_COMMENT</tt>, <tt>EC_OWNER</tt>, <tt>EC_PID</tt>, <tt>EC_MATCH_GROUPS</tt>, and <tt>EC_CONTACT_GROUPS</tt>.

10 years

Check_MK Werk 1394: HTML notifications have a new content field for debugging variables

by Mathias Kettner

ID: 1394 Title: HTML notifications have a new content field for debugging variables Component: Notifications Level: 2 Class: New Feature Version: 1.2.5i6 When configuring notifications and customizing templates then you might often wonder, which variables are present and which values they have. In the HTML email notifications you can now enable the new field Complete variable list in the Information to be displayed in the email body. This adds a table with all avaiable variables and their current settings in the notification in question.

10 years

Check_MK Werk 1150: netstat: new check for monitoring TCP/UDP connections and Linux and AIX

by Mathias Kettner

ID: 1150 Title: netstat: new check for monitoring TCP/UDP connections and Linux and AIX Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i6 The check does the same as <tt>win_netstat</tt> and also uses the same WATO rule. You need to deploy the agent plugin <tt>netstat.linux</tt> or <tt>netstat.aix</tt>.

10 years

Check_MK Werk 1148: Allow execution of actions when cancelling events

by Mathias Kettner

ID: 1148 Title: Allow execution of actions when cancelling events Component: Event Console Level: 2 Class: New Feature Version: 1.2.5i6 The Event Console now allows to attach actions to the cancelling of events. This can for example be helpful if you have an action that opens a trouble ticket in an external system. When a cancelling event arrives you can have executed an action that also cancels the according trouble ticket. When events are cancelled then several data fields of the event are being replaced with data from the new event before the action is being executed. That way relevant data from the new event is available in the action script. Also the event phase is being set to <tt>closed</tt> and the state is set to 0 (OK). That way your action script can distinguish between a normal and a cancelling situation. The following fields are taken from the new (i.e. cancelling) event: <ul> <li>The text</li> <li>The time</li> <li>The time of the last occurance</li> <li>The syslog priority</li> </ul> All other fields are unchanged - including the original ID of the cancelled event.

10 years

Check_MK Werk 1100: WATO backup domains: fixed bug were excluded files still got deleted on snapshot restore

by Andreas Boesl

ID: 1100 Title: WATO backup domains: fixed bug were excluded files still got deleted on snapshot restore Component: WATO Level: 2 Class: Bug Fix Version: 1.2.5i6 It is possible to configure a backup domain so that certain files are not packed into the snapshot. As a result, upon restore these file should not get deleted.. This mechanism did not work correctly.

10 years

Check_MK Werk 1147: upc_capacity, ups_socomec_capacity: Fix checking of battery left levels

by Mathias Kettner

ID: 1147 Title: upc_capacity, ups_socomec_capacity: Fix checking of battery left levels Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.5i6 The fixes the execution of the levels for Time left on battery. These levels where internally compared against the <t>Time running on battery - which is obviously quite the opposite. Example: If you configure a warning level of <tt>50</tt> minutes for Time left on battery then the check gets critical if the estimated remaining battery time is 50 minutes or less.

10 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2