Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 4568: mk_inventory.vbs: fixed getNetworkAdpater function to prevent errors caused by null arrays

by Marcel Schulte

ID: 4568 Title: mk_inventory.vbs: fixed getNetworkAdpater function to prevent errors caused by null arrays Component: HW/SW Inventory Level: 2 Class: Bug fix Version: 1.5.0i1

7 years, 4 months

Check_MK Werk 4689: Fixed buffer overflow when importing cmcdump data

by Sven Panne

ID: 4689 Title: Fixed buffer overflow when importing cmcdump data Component: Core & setup Level: 2 Class: Bug fix Version: 1.5.0i1 When importing data from cmcdump into the Check_MK Micro Core, a buffer for the long plugin output was too small, leading to a buffer overflow with unpredictable consequences. The affected COMMANDs on the Livestatus interface were UPDATE_SHADOW_HOST_STATE and UPDATE_SHADOW_SERVICE_STATE. This has been fixed.

7 years, 4 months

Check_MK Werk 4733: Check_MK graphs can now be exported as PNG images

by Lars Michelsen

ID: 4733 Title: Check_MK graphs can now be exported as PNG images Component: metrics Level: 2 Class: New feature Version: 1.5.0i1 It is now possible to export the Check_MK graphs as static PNG images. This mechanism can be used to to integrate the graphs in 3rd party tools. For example, you can use it to add graphs to NagVis maps or to the hover menu of NagVis. The new page is named <tt>graph_image.py</tt>. The page is receiving a single request parameter that is structured equal to the JSON/python graph API (See werk #8643). The request object is structured like this: F+: { "specification": [..., ...], "data_range": { "time_range" : [..., ...], } } F-: The specification is using the Check_MK internal graph specification format. The first element is the specification type (<tt>template</tt>, <tt>custom</tt> or <tt>explicit</tt>. The structure of the second element depends on the type. Please take a look at the examples below to get an idea of it. The time range is given in two unix timestamps, the start time and the end time. But the whole <tt>data_range</tt> specification is optional. In case you don't provide it, the 25h graph will be rendered. The answer to this request is a single, dynamically rendered, PNG image. Please note that this request is done in the context of the currently logged in user. So the user that opens a page containing this snippet needs to be authenticated with the Check_MK GUI and able to see the image. Otherwise the user won't be able to see the image. The most common use case will be to add the image generated by this. The following snippets show how it can be embedded: F+: <img src="http://mycmkserver/mysite/check_mk/graph_image.py?request={%22specification…"> F-: This will try to open the image from the Check_MK site <tt>mysite</tt> on the server <tt>mycmkserver</tt>. The graph is specified by the following request object in URL encoded form: F+: { "specification": ["template", { "service_description": "CPU load", "site": "mysite", "host_name": "myhost" }] } F-: It is also possible to adapt the rendering attributes of the graph using the <tt>render_options</tt> data structure. This example hides the legend and the title of the graph and sets a custom image size: F+: <img src="http://mycmkserver/mysite/check_mk/graph_image.py?request={%22specification…"> F-: Again, the human friendly formated request object: F+: { "specification": ["template", { "service_description": "CPU load", "site": "mysite", "host_name": "myhost" }], "render_options": { "show_legend": false, "show_title": false, "size": [ 50, 15 ] } } F-: In case you want to render custom graphs, you can use a specification like this in your request. Replace <tt>custom_graph_1</tt> with the ID of the custom graph you like to see: F+: ["custom", "custom_graph_1"] F-:

7 years, 4 months

Check_MK Werk 4725: Significant improvement of Check_MK check helper memory usage

by Lars Michelsen

ID: 4725 Title: Significant improvement of Check_MK check helper memory usage Component: Core & setup Level: 2 Class: Bug fix Version: 1.5.0i1 The memory usage of the Check_MK check helpers, especially the growth that occures during runtime, has been reduced significantly. One example which has been measured in a single site with 30 Check_MK check helpers configured and a large configuration (a lot of hosts, services, tags and rulesets): Before this change it was executing 1000 service checks per second with a total memory usage of about 15 GB. After this change it is now performing 1100 service checks per second with a total memory usage of 3.5(!) GB. The exact memory reduction highly depends on the Check_MK configuration, but should be measurable in all medium to large environments.

7 years, 4 months

Check_MK Werk 4718: Fixed memory leak in Check_MK check helpers when started in verbose mode

by Lars Michelsen

ID: 4718 Title: Fixed memory leak in Check_MK check helpers when started in verbose mode Component: Core & setup Level: 2 Class: Bug fix Version: 1.5.0i1 When the Check_MK helpers are configured with a higher log level than the default Notice log level the Check_MK helpers were leaking memory. This can be configured by changing the option "Check_MK check helpers" of the global setting "Logging of the core" to e.g. Informational. In this mode the helper gathers information about some changed variables during runtime and the memory usage. It also allows to debug different mechanics of the helpers. If you enabled this, each reload of the core (not restart) was triggering the memory leak in the helpers. In extreme situations this could lead to duplication of the memory usage on each reload.

7 years, 4 months

Check_MK Werk 4673: Agent bakery creates Solaris PKG packages now

by Lars Michelsen

ID: 4673 Title: Agent bakery creates Solaris PKG packages now Component: agents Level: 2 Class: New feature Version: 1.5.0i1 The agent bakery can now pack solaris "pkg" packages now. With this change it is now also possible to use the agent updater on solaris systems.

7 years, 4 months

Check_MK Werk 4672: Activation: Discard of changes is now possible again

by Lars Michelsen

ID: 4672 Title: Activation: Discard of changes is now possible again Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1 The "discard changes" button which could be used to revert the pending changes in WATO to the last activated configuration was removes during 1.4 development. The main reason for this is that the snapshot feature of WATO is being dropped and replaced in Check_MK 1.5 by some better mechanism.

7 years, 4 months

Check_MK Werk 4668: Fixed editing of cluster properties

by Lars Michelsen

ID: 4668 Title: Fixed editing of cluster properties Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1 Editing of cluster host properties (except nodes) was not possible. When loading and saving a cluster the set attributes of the cluster were lost.

7 years, 4 months

Re:

by Jennifer Lankford

Hi , Get your low interest loans today. with interest rate as low as 8% per annum we're hard to beat bad credit score? no problem! we have a solution for everyone. just send us an email to: jennylan388(a)gmail.com for more information.

7 years, 4 months

Check_MK Werk 4608: Agent bakery creates Solaris TGZ packages now

by Lars Michelsen

ID: 4608 Title: Agent bakery creates Solaris TGZ packages now Component: agents Level: 2 Class: New feature Version: 1.5.0i1 The agent bakery can now create agent packages for Solaris in TGZ format. Most agent plugins that are relevant for solaris should be packageable now with these new packages.

7 years, 4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2