Checkmk werks level1 March 2019

checkmk-werks-lvl1@lists.checkmk.com

13 participants
108 discussions

Check_MK Werk 7235: WATO now stores host/folder creation meta information

by Lars Michelsen

ID: 7235 Title: WATO now stores host/folder creation meta information Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 When either a host or folder is being created in WATO it now stores the creation time and creator ina meta data attribute. This attribute is shown at the bottom of the the host or folder edit dialog. Hosts or folders created before 1.6 don't have such information stored and will show something like "Created sometime before 1.6".

5 years, 6 months

Check_MK Werk 7236: Deterministic rules.mk when "Use GIT version control for WATO" is enabled

by Lars Michelsen

ID: 7236 Title: Deterministic rules.mk when "Use GIT version control for WATO" is enabled Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 When "Use GIT version control for WATO" is enabled to keep track of the changes that have been made to the Check_MK configuration, the history of the rules.mk files was problematic because several contents of that file were not saved in a deterministic way. This means that loading and saving the configuration without chaning anything resulted in a changed file, e.g. because attributes of dictionaries were not sorted. The rules.mk is now stored in a deterministic way when "Use GIT version control for WATO" is enabled.

5 years, 6 months

Check_MK Werk 7233: Network scan: Multiple time ranges can be configured

by Lars Michelsen

ID: 7233 Title: Network scan: Multiple time ranges can be configured Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 The network scan can be configured to operate only in a specific time range. With this change it is possible to define multiple independent time ranges.

5 years, 6 months

Check_MK Werk 7024: BI aggregation list now shows icons for the aggregation config options

by Lars Michelsen

ID: 7024 Title: BI aggregation list now shows icons for the aggregation config options Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 The aggregation list of WATO now shows icons for the aggregation option flags (enabled/disabled, single/multiple hosts, hard/all states, downtime aggregate WARN/CRIT).

5 years, 6 months

Check_MK Werk 7234: Fixed broken event cancelling by priority (1.5.0p12 regression)

by Lars Michelsen

ID: 7234 Title: Fixed broken event cancelling by priority (1.5.0p12 regression) Component: Event Console Level: 1 Class: Bug fix Version: 1.6.0i1 When a EC rule is configured to cancel an open event by priority and the lower priority level is the left of the priority range, the cancelling was not working. For example EMERG to CRIT worked while CRIT to EMERG did not work. This has been fixed. The order of both levels should not be relevant for the processing of the rules.

5 years, 6 months

Check_MK Werk 7214: Interface checks: Introduce scan function API

by Moritz Kiemer

ID: 7214 Title: Interface checks: Introduce scan function API Component: Checks & agents Level: 1 Class: New feature Version: 1.6.0i1 In the past conflicting check plugins with services called "Interface <ITEM>" could lead to a "duplicate services" warning on the discovery page. To avoid this issue in the future, all scan functions for those plugins are now located in the file "if.include". If you add a new "Interface <ITEM>"- service, please add the corresponding scan function to the file "if.include", and list in the dictionary <tt>_SPECIFIC_IF_SCANS</tt>. You can then access the scan function by specifying <tt> 'snmp_scan_function': get_snmp_if_scan_function('my_if_check')</tt> in your check plugin. The matching devices will then be automatically excluded from the generic if and if64 check plugin.

5 years, 6 months

Check_MK Werk 7215: Avoid duplicate services for if_fortigate check

by Moritz Kiemer

ID: 7215 Title: Avoid duplicate services for if_fortigate check Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 This fixes the duplicate services warning displayed on the discovery page for if/if_fortigate checks. Services of the if checkplugin are no longer discovered if the if_fortigate plugin already found interfaces.

5 years, 6 months

Check_MK Werk 7195: Jira: Notification plugin

by Ronny Bruska

ID: 7195 Title: Jira: Notification plugin Component: Notifications Level: 1 Class: New feature Version: 1.6.0i1 Check_MK now supports integration with Jira. You can create issues for Host an Service Problems and optional set a resolution on recovery notifications. In Jira you have to add two custom fields to your project screen as described [https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-9388… here]. In Check_MK, under "WATO - Notifications", create a new notification rule and select Jira. Parameters to set: JIRA URL: The URL to your Jira environment User Name: Jira username Password: Jira password Project ID: The Project ID the issues should be created in Issue type ID: The issue type ID Host custom field ID: The first custom field ID you created in Jira Service custom field ID: The second custom field ID you created in Jira Monitoring URL: URL of your Check_MK environment to create hyperlinks back to Check_MK (eg. https://server/site) Priority ID: The priority ID (optional) Summary for host notifications: The summary the created host issue should use (optional) Summary for service notifications: The summary the created service issue shoud use (optional) Label: Label for Jira issues. If not set, 'monitoring' will be used. (optional) Activate resultion with following resolution transistion ID: If set, the created issue will be resolved with the configured resolution ID (optional) Set optional timeout for connections to JIRA: Timeout in seconds, default is 10 (optional) You need different Jira IDs to open/resolve issues. There are different ways to get this IDs: LI: [https://confluence.atlassian.com/jirakb/how-to-get-project-id-from-the-jira… Jira_support] LI: Retrieve with the a script (example: project_id): F+:#!/usr/bin/env python F+: F+:import requests F+: F+:USER = "JIRA_USERNAME" F+:PW = "JIRA_PASSWORD" F+:PROJECT_KEY = "JIRA_PROJECT_NAME" F+:JIRA_SERVER = "https://jira.server.your-domain.de" F+: F+:sess = requests.Session() F+:sess.auth = (USER, PW) F+:resp = sess.get("%s/rest/api/2/project" % JIRA_SERVER, verify=False) F+: F+:project_id = [item["id"] for item in resp.json() if item["key"] == PROJECT_KEY][0] F+:print(project_id) For issuetype and priority ID use: F+:resp = sess.get("%s/rest/api/2/issuetype" % JIRA_SERVER) F+:resp = sess.get("%s/rest/api/2/priority" % JIRA_SERVER) More information about the Jira API can be found [https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0 here]. CMK-1185

5 years, 6 months

Check_MK Werk 7232: Fixed wrong sorting of view titles on "edit view page"

by Lars Michelsen

ID: 7232 Title: Fixed wrong sorting of view titles on "edit view page" Component: Multisite Level: 1 Class: Bug fix Version: 1.6.0i1

5 years, 6 months

Check_MK Werk 7198: Solaris Agent: fixed wrong path for top command

by Ronny Bruska

ID: 7198 Title: Solaris Agent: fixed wrong path for top command Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 The agent tried to use /usr/local/top instead of /usr/local/bin/top. This has been fixed.

5 years, 6 months

← Newer
1
...
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2019