Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16006 discussions

Checkmk Werk 7265: Fixed exception during subreport generation, fixed missing macros in subreports

by Andreas Boesl

ID: 7265 Title: Fixed exception during subreport generation, fixed missing macros in subreports Component: Reporting & Availability Level: 1 Class: Bug fix Version: 1.7.0i1 The $HOST_NAME$ and $SERVICE_DESCRIPTION$ macros were not correctly replaced within subreports.

5 years, 2 months

Checkmk Werk 8801: oracle_crs_res, oracle_crs_version, oracle_crs_voting: Fixed error in parameters view

by Marcel Arentz

ID: 8801 Title: oracle_crs_res, oracle_crs_version, oracle_crs_voting: Fixed error in parameters view Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The mentioned checks are not configurable at the moment. Yet the checks expected a ruleset and gave an error. With this fix the checks are still not configurable but do not expect to have a corresponding ruleset anymore.

5 years, 2 months

Checkmk Werk 7937: Fixed handling of old event console configurations

by Sven Panne

ID: 7937 Title: Fixed handling of old event console configurations Component: Event Console Level: 1 Class: Bug fix Version: 1.7.0i1 If SNMP trap translation is enabled and the Checkmk installation is upgraded to 1.6.0 or later, an "invalid SNMP trap translation" exception could happen. This has been fixed.

5 years, 2 months

Checkmk Werk 7972: Fix possible error when checking on command line with missing piggyback_sources directory

by Lars Michelsen

ID: 7972 Title: Fix possible error when checking on command line with missing piggyback_sources directory Component: Core & setup Level: 1 Class: Bug fix Version: 1.7.0i1

5 years, 2 months

Checkmk Werk 7445: Historic data views and painters for capacity management

by Óscar Nájera

ID: 7445 Title: Historic data views and painters for capacity management Component: Reporting & Availability Level: 2 Class: New feature Version: 1.7.0i1 Capacity management allows you to work with the service metrics historical data. When configuring a view you can select for a column the "Service Historic Metrics" option from the drop-down menu, available for the "All hosts" and "All services" data-sources. This customizable painter allows you to select, which service metric you want to analyze, over which time range should data be recovered from your RRD database, how data is to be consolidated and aggregated. Finally, you need to label this column to your best convenience. Some ideas you might want to consider when creating your views: List all your hosts Peak CPU utilization, over the last week, and also last month. Maybe you want also to create a new column corresponding to the to the times a new version of your software was deployed. Time ranges are completely flexible, and you can keep adding columns for any time window you prefer. Analyze over the same time window, the peak, average and minimum CPU utilization of all your hosts over the last week or last month. You can also get data from different services at the same time. For example showing CPU utilization, used memory and disk IO averaged over the last week. One last note. Because you will be querying from the RRD data of many hosts at the same time, query time will increase linearly with the volume of data you are processing.

5 years, 2 months

Checkmk Werk 7444: Rename metric name in Filesystem checks from mount point to fs_used

by Óscar Nájera

ID: 7444 Title: Rename metric name in Filesystem checks from mount point to fs_used Component: Core & setup Level: 3 Class: Bug fix Version: 1.7.0i1 Filesystem Nagios check plug-in stored the filesystem usage of every mount points in the RRD databases under the path of each mount point. Checkmk assigned to every mount point a service, still it kept naming the filesystem usage with the mount point path for compatibility. Our graphing system learned to deal with this unpractical convention, however new features in Checkmk performing bulk access to data can't. <ul> <li>All sites created with Checkm 1.6.0 onwards will automatically use the new naming convention and don't need to be migrated</li> <li> The migration is not mandatory, your Checkmk instance will continue working under the legacy mode until you migrate.</li> <li>If you use CRE, you don't need to de the migration</li> <li>If you don't plan to do bulk access to data as required by the Historic Data Views for filesystems (see Werk #7445), you don't need to migrate your RRD databases.</li> <li>If you want to use the Historic Data Views for Capacity Management on Filesystems, you need to do migration.</li> </ul> The incorporation of Historic Data Views, for Capacity Management, requieres querying the filesystem usage of all host in a given time window. It becomes prohibitive expensive to do such request since first every service is queried for its mount point name and then every RRD is individually queried again for the mount point name data. In this werk we provide a migration script that would edit all meta data files describing the RRDs that receive output from all our supported filesystem checks. It will also set a flag in your config so that Filesystem check plug-ins start delivering usage perfomance data under the static name of fs_used. You are advised to do a backup of your RRD files and journal files before performing the migration and your Checkmk instance needs to be stopped during the migration. Migration is one way and needs to be performed once per site any rollback has to be done from your own backup.

5 years, 2 months

Checkmk Werk 7928: zfsget: whitespace in name discovery bugfix

by Jonas Kluger

ID: 7928 Title: zfsget: whitespace in name discovery bugfix Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The check does not crash anymore if a mountpoint/name containes a whitspace. Multiple whitespaces in a mountpoint can now be possible.

5 years, 2 months

Checkmk Werk 8781: Fix traceback for builtin icon visibility

by Tom Baerwinkel

ID: 8781 Title: Fix traceback for builtin icon visibility Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1 If the "Builtin icon visibility" was configured for download_agent_output, but not for download_snmp_walk the action menu showed a traceback.

5 years, 2 months

Checkmk Werk 8781: Fix traceback for builtin icon visibility

by Tom Baerwinkel

5 years, 2 months

Checkmk Werk 7444: Rename metric name in Filesystem checks from mount point to fs_used

by Óscar Nájera

5 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1