Ideas for Checkmk as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included. pr_jkexfcbuunesmzd 2025-11-05T15:32:45Z sug_6myocfil1k8eeyq 2026-06-30T09:56:16Z 2026-07-09T09:33:19Z At present, it is not possible to monitor certificates of an FTP proxy whose connection is initialised using StartTLS FTP. Although the certificate check offers the option to query several protocols via StartTLS, FTP is not included; see the attachment. I have posted a forum entry on this subject; see https://forum.checkmk.com/t/starttls-ftp-proxy-certificate-monitoring/59760. Please add “FTP StartTLS” to the list. sug_uzin6tbmpv8r94l 2026-06-16T10:31:03Z 2026-07-09T09:26:42Z Ability to create custom Nagios plugin scripts in the GUI that will be tested and added right away as an mkp package to simplify whats missing in Checkmk from the beginning. sug_d9an6o9szquj1xc 2026-07-06T14:13:48Z 2026-07-08T10:04:31Z If a user cannot be authenticated from the IDP, can the user be deleted out of CheckMK automatically. If not at the time, after X amount of days after they last logged into the system. i.e failed auth, been 14 days since last login, auto delete. This is ultimately to support Azure Life Cycle policy for groups, and removing the otherwise necessary manual delete of the user on the CheckMK side. sug_q7nsvvwonnaefmb 2026-06-29T12:13:14Z 2026-07-06T16:00:16Z Currently if you create / edit a multi page report it's a pain to do as every time you add / edit / delete an element the report UI snaps back to start. So it's a big scrolling each and every time. The should be no reload of it or it should automatically go to last position worked at sug_wvyxzv633uws4k0 2026-06-29T12:10:05Z 2026-07-06T15:55:31Z On responsive Dashboards the Widgets get auto positioned / aligned / so it fits different screen sizes. This is a great improvement. But it would make sense to have a lets call it Heading that will always stay on top being unaffected of the repositioning. Best would be to have multiple areas that do only get repositioned inside but not with each other sug_imeffnjqnitqbxi 2026-06-17T08:33:55Z 2026-07-06T10:17:00Z It would be great if it is possible to set parameter in the globalconfig for an supported way (without editing mk files) sug_fbstx1zezsmtkpc 2026-06-25T11:27:31Z 2026-07-06T09:14:22Z When an nfs mount becomes stale it makes the agent wait for that information for a long time on AIX systems: https://forum.checkmk.com/t/aix-agent-and-hard-mounted-nfs-shares/29350 https://forum.checkmk.com/t/stale-nfs-mounts-on-aix-leads-to-timeout-of-the-agent/51784/3 https://forum.checkmk.com/t/nfs-check-on-aix-7-2/17937 sug_vqipehrvebiv6re 2026-06-26T07:47:50Z 2026-07-06T06:41:46Z I don’t want monitoring to start in the middle of the night, forcing me to adjust the time repeatedly whenever I use downtime presets (e.g., Today, This Week, etc.). Please add a time picker to the downtime presets. sug_po3zehj4k9ggvor 2026-06-26T10:14:17Z 2026-07-06T06:39:19Z When applying filters on host lists, event views, or other filterable data, and the filter takes several seconds to execute, there is no visual indication that the system is processing the request. Users see a static page and cannot tell whether the query is still running or if the application has stalled. Impact: Users experience uncertainty and may unnecessarily refresh or retry, not knowing if their action is being processed. sug_0wvgqjd3oqns9vm 2026-06-17T09:05:01Z 2026-07-06T06:37:18Z Currently downtime preset button times default to 12 AM (e.g. "today" downtimes the service until 12AM the next day). So if we downtime a service, because we can not get to it right away, the on call engineer would be notified at midnight when the downtime ends. To not have to adjust the time every time we click on the presets, we have implemented a patch, which sets the defaults to 9 AM. We would like to see a feature where we can configure the downtime presets or at least that the presets are updated to a more work-hours like default. sug_ouicr0is00bart3 2026-06-26T10:15:01Z 2026-07-06T06:34:27Z The current email notification template is more elaborate but not necessarily more readable. Some teams prefer the simpler, more compact layout of the previous template for easier scanning and faster comprehension. Impact: Different organizations have different preferences for email density and layout. A template choice option would allow teams to select the format that works best for their workflow. sug_yya5acu3zw5sp7l 2026-06-30T11:38:07Z 2026-07-06T06:32:55Z Currently, the "Downtime comment (regex)" filter in custom views does not provide a Negate option, unlike several other view filters in Checkmk. This makes it impossible to create views such as: Show all scheduled downtimes except those with specific comments. For example, I would like to exclude automatically created downtimes with comments like: -Testing -Check -Development -Veeam Backups - tägliche Sicherung Because the view filter uses POSIX regular expressions, negative lookaheads are not supported. As a result, there is currently no way to express this requirement using the existing filter. Adding a simple Negate checkbox to the Downtime comment (regex) filter would: -Make the filter behavior consistent with other view filters that already support negation. -Eliminate the need for complex or impossible regular expressions. -Enable administrators to easily hide maintenance windows or other automatically created downtimes while still displaying all relevant manual downtimes. This would be a small UI enhancement with a significant improvement in usability and consistency. sug_dvbrxwmgnx4fgv9 2026-06-30T12:03:12Z 2026-07-06T06:31:35Z Hello, I would like to suggest a small improvement to the "Parameters for Email (HTML)" notification method. Currently, the generated HTML emails always place the Checkmk logo at the very beginning of the email body. While this looks nice in the email itself, it has an unwanted side effect on some mail clients. For example, on Apple Mail for iPhone, the email preview uses the first text elements of the HTML message. Since the logo's alt text ([Checkmk Logo]) appears first, every notification preview starts with: [Checkmk Logo] instead of immediately showing the relevant monitoring information, such as the event, host or service. As a result, the notification list becomes much harder to scan quickly, especially when receiving many alerts. Proposed enhancement Please add an option to the "Parameters for Email (HTML)" notification method to control the logo position, for example: Logo at the top (current behavior, default) Logo at the bottom No logo Moving the logo to the bottom would preserve the existing branding while allowing the notification preview in mail clients such as Apple Mail to begin with the most important information. This would improve readability without changing the default behavior, so existing installations would not be affected. Thank you for considering this enhancement. Best regards sug_ztt69enlcop8dug 2026-06-30T22:41:42Z 2026-07-06T06:30:43Z When defining notification rules based on Event Console alerts currently its not possible to define a rule using a rule pack as a condition. You can define individual rule IDs but you can't define an entire rule pack as a condition. sug_utj1qnwfnjmm58g 2026-07-01T20:01:16Z 2026-07-06T06:30:02Z At the moment when you receive a bulk notification e-mail for acknowledgements, at the top all services are shown with their previous state and current state and a date of state changed. That date and time is the only way of knowing that it isn't a recent notification. Only when scrolling down to the details of the service notification we can see that it's an acknowledgement. I think it would be clearer when the summary at the top shows Warn --> Acknowledgement instead of OK --> Warn (Date Time when this happened). Or maybe show OK --> Warn (Acknowledged) sug_23xh0xtquhglfuu 2026-06-26T08:48:08Z 2026-06-30T09:25:00Z Currently the implemented piggyback hub for syncing piggyback data across sites is limited for logical reasons on Ultimate with MT to only allow syncing data between sites of the same customer. This can pose a problem for MSP's as we sometimes have shared resources that can provide piggyback data to multiple customers from the provider customer. Two examples just from my point of view would be vCenter and Veeam. Both these checks provide piggyback data for VMs. Both these services would live in the Provider customer or a sub-customer for hosting services and as such the piggyback data that these servers could provide for customer VMs inside the different customers would not be usable currently due to the inability to sync piggyback data between customers. That would mean we would either resort to the legacy method of syncing piggyback files manually with some filter or not have it at all. It would be benificial to provide a filterable, limited way of selecting some data to sync to a different customers site still utilizing the piggyback hub but also respecting the data tenancy system provided by Ultimate with MT. sug_axhcsrfc9rpzeil 2026-06-24T10:27:23Z 2026-06-25T12:59:54Z General Search: example: LOGWATCH: show search string and log line of the found search string in the output In general a FeatureRequest for all search functions in Checkmk, show what and where it was found. That helps a lot in the analysis of text and log files per host, etc.. sug_i3lyxy4hg5zzxit 2026-06-25T12:43:35Z 2026-06-25T12:58:39Z When working in Event Console we need to be switching tabs because in Event Console there is no options to quickly open all messages from a given rule. We can check the number of messages and easily identify if a new message was received but we are not able to open those message from Event Console directly. Include an action item to view recent messages from a specific rule or add a preview button to show the latest message from a specific rule. sug_1sgkmii2z9dqspx 2026-06-20T06:42:33Z 2026-07-01T10:12:08Z - check-mk-agent-2.5.0p7-1.noarch.rpm doesn't install cmk-agent-ctl on ARM architecture - check-mk-agent-2.5.0p7-1.noarch.rpm installs the agent itself, but not the cmk-agent-ctl binary and service to change mTLS - package check-mk-agent-2.5.0p7-1.aarch64.rpm should work on ARM but is packaged for x86_64 instead #> rpm -qp --info check-mk-agent-2.5.0p7-1.aarch64.rpm warning: check-mk-agent-2.5.0p7-1.aarch64.rpm: Header OpenPGP V4 RSA/SHA512 signature, key ID 434dac48c4503261: NOKEY Name : check-mk-agent Version : 2.5.0p7 Release : 1 Architecture: x86_64 ... expected is to show: Architecture: aarch64 sug_impooarsx3hfysg 2026-06-21T10:40:58Z 2026-06-24T15:36:42Z Please add an option "Save ps snapshot" to the CPU and Memory checks which saves the actual ps section in the details. Use Case During periods of high server utilization, server owners and application managers often need to identify which processes consume the most CPU or memory. This information is especially useful for processes that are not regularly monitored but can unexpectedly cause issues, such as backup jobs, user processes or irregularly running tasks. Currently, it is often not possible to retrospectively determine which specific processes were responsible for performance degradation at a given time, nor to identify whether the same processes are repeatedly causing problems. Benefit The relevant process data is already collected by Checkmk. By adding an option to save snapshots, this information would finally become accessible in a structured way. It simplifies troubleshooting and allows teams to identify recurring performance patterns directly within Checkmk, without the need to access other tools, correlate external data sources or rely on AI-based analysis tools. sug_guodbwvytnkrud8 2026-06-01T13:22:58Z 2026-06-10T10:49:42Z The global setting “Use new service names” currently lacks transparency and makes it difficult to understand its impact. For each listed check plugin, it is not visible: - what the old service name was - what the new service name will be - whether there is a related Werk or documented change This makes it hard to assess the impact before enabling the option, especially in environments with: - existing rules based on service descriptions - integrations with external systems - reliance on historical data Suggested improvement: - Show old → new service name mapping per plugin - Provide a reference to the related Werk / documentation - Optionally include a short preview/example This would greatly improve usability and reduce the risk of unintended side effects. regards Christian sug_0bxpxdamrxtz3lx 2026-06-08T23:21:04Z 2026-06-10T05:49:11Z MSSQL Bakery rules don`t support the usage of domain credentials. Plugin supports that using a custom configuration file. sug_lzwnyrisx5pm9gw 2026-06-04T10:49:50Z 2026-06-08T07:25:04Z it would be nice to be able to use use the new Relay as a Gateway like system that is able to forward automatic Agent updates for Agents and eg. Webchecks inside a remote Network to limit Firewall roles for the Network in General. To be able to use it as a light weight distributed monitoring alternativ. sug_ll4iadn2nl4ybew 2026-06-01T05:27:09Z 2026-06-05T09:51:00Z In some cases, it is necessary to convert a regular Service Monitoring Rule into an Enforced Services Rule, or the other way around. This becomes especially cumbersome when dealing with a large number of services, as each rule has to be recreated manually. It would be very helpful to have a built-in option to convert or duplicate these rule types. Even if not all fields can be perfectly mapped (since some parameters may not exist in both rule types), having an initial conversion that pre-populates as much as possible would already save a significant amount of time. As an administrator, it is perfectly acceptable to manually adjust a few remaining fields afterward. The key goal is to reduce the repetitive effort required for recreating rules from scratch. Josef :) sug_jqgqmuvcmcmcmha 2026-06-01T11:19:51Z 2026-06-12T11:53:45Z There's a check for PoE consumption on switches, but it only has WARN and CRITICAL *upper* limits. We have had several occurences where the PoE part of a switch died and the rest of the switch kept working perfectly fine. PoE consumption was still reported by the switch but went to 0 - for which there's no WARN or CRITICAL. So it would be useful to have threshold settings / rules for the PoE consumption check to warn me when it's at a too low of a realistic level. sug_mtrmskmttshdwef 2026-05-28T10:45:23Z 2026-06-01T14:40:31Z HAProxy checks currently expose only the session rate metric. The agent output already contains additional metrics, so it would be great to expose more of them. Please add session-related metrics. sug_etoeiqqj0evjuko 2026-04-24T19:14:13Z 2026-05-28T14:16:24Z separate sitenames from usernames; allow site to run under generic usernames, do not mandate username to match sitename. this will allow more flexible deployment and management. this is more relevant in area where usernames are centrally managed and access to external resources are all tied to usernames and credentials. sug_uzib0d1rfonmlrp 2026-04-22T11:37:57Z 2026-05-28T14:10:05Z During Checkmk backend updates (e.g. stopping a site), users are frequently confronted with red error messages such as “Unhandled exception”. This creates the impression that Checkmk is broken, even though the behavior is expected during maintenance activities. Key issues: - The wording “Unhandled exception” is misleading and alarming for end users. - Similar messages appear in multiple places and give poor UX signals during planned maintenance, but also in general. - Existing downtime/maintenance mechanisms do not seem to cover backend or site-level maintenance properly. Suggested improvement: Introduce clearer, maintenance-aware status messages when a site or backend is intentionally stopped. Replace generic technical error messages with user-friendly explanations (e.g. “System is currently under maintenance”). Ideally provide a dedicated maintenance mode for Checkmk itself, not only for monitored hosts/services. This would significantly reduce confusion, false incident reports, and improve overall user experience during upgrades and maintenance windows. sug_w0nmnuhyehfaxwo 2026-05-08T09:21:28Z 2026-05-28T14:06:14Z At the moment it is not possible to configure how many backups should be kept. That would be a nice feature. At the moment we need to run a cronjob that delets old backups. Also a cool feature would be adding the date/time of the backup in the foldername. Another point is, if you export backup keys, the descrition is not used. So if you have more than one there alre names "key-1", "key-2". You have to rename it afterwards. If you would add the "description" to the filename that would be nice sug_iagc8bg3twt2xaw 2026-05-22T10:09:31Z 2026-05-28T11:27:54Z Add a function to temporarily show or hide columns in the current view (similar to adding/removing filters in filter menu), without having to edit the view each time. Sometimes I need to adjust the columns shown because certain information is missing or to hide columns that are not relevant and take up too much screen space, which results in unnecessary horizontal scrolling. Example: I am running a Quicksearch for all services starting with HTTP because I need to know which check is used for each service (e.g., custom, check_http, check_httpv2, etc.). In this case, the Summary, Perf-O-Meter, and some other columns are not relevant. However, I would like to display the Check command column, which is normally not shown in this view. This feature enables a faster and more focused view, especially when certain information is not relevant in the given context and occupies unnecessary space in the current view. sug_jlfw8o8gs0qktx3 2026-05-25T07:22:39Z 2026-05-27T10:04:49Z Reproduce in Checkmk Raw Edition 2.5.0-2025.11.04: Search: "Check_MK Agent" Search result of service and label e.g. "Local site cmk fedora-dev-host-212" are not in the same grey box. User assumes box combines label and service, but the current style combines the service and the label of next line. Also sort on "Summary" would be nice to quickly see if hosts run outdated agents. sug_fvrjwhmxsnvcp8a 2026-05-22T07:14:30Z 2026-05-26T07:14:20Z Hello Checkmk Team and Checkmk Community, some Versions ago (i'm not sure if it was during 1.X or still exists in 2.X) it was possible to edit the ID of a BI Pack/Rule/Aggregation directly in the rule. Since somwhen it is not possible anymore. So if i made a mistake in a Pack/Rule/Aggregation i need to re-create (in case of Packs create a new pack and move rules, else just copying) the ID i want to change. It would be nice if there would be an option to edit the ID again. Like on "older" Versions, in this case no other modification can be done in the same step. The most advantage would be to safe a lot of time if you don't have to copy everything - and adjust "Call a Rule" entries. For example it took me ~1h for 6 Packs to recreate Packs/Rules/Aggregation and re-linking the "Call a Rule", and this was a quite simple straight forward doing. i can imagine, in a more complex environment with a lot of "Call a Rule"s, it may take much longer. As mentioned, this already existed in older Versions. But since some time the ID is fixed after the first creation. Greetings Andreas sug_n6ywmfykscyqs1f 2026-05-20T11:15:51Z 2026-05-25T09:51:45Z When using subreports to include hosts in a parent report (e.g. "Switch details" subreport called from a template-based bundle), the hosts are currently returned in creation order — the order they were added to CheckMK — with no documented global setting or per-subreport override to change this behavior. This creates a poor end-user experience in customer-facing PDF reports, where hosts appear in an arbitrary, non-alphabetical sequence. Since the parent report cannot impose sort settings on child/subreport elements, and the subreport itself currently offers no persistent sort configuration, there is no supported way to produce a consistently ordered host list across report runs. An improvement would be to allow sort order to be configured for host elements within subreports — ideally supporting at minimum alphabetical (ascending/descending) sorting by hostname (or at least changing the default behaviour to this) — with the setting persisting as part of the subreport definition. Alternatively, allow the parent report to pass or override the sort order for included subreport elements. This affects any MSP or enterprise user generating automated, customer-facing reports via the Reporting module. Unpredictable host ordering in delivered PDF reports looks unprofessional and undermines confidence in the monitoring platform. sug_xewgvteubjqkdfn 2026-05-21T16:12:06Z 2026-05-25T07:30:45Z To make the use of HTML in check output safer and more controlled, the existing Escape HTML rule should be extended with an additional option called Sanitize HTML. Rendering modes: * Escape HTML: escaped plain text (existing) * Don't esacpe HTML: unescaped raw HTML (existing) * Sanitized HTML: sanitized HTML rendering (new) When the Sanitized HTML option is selected, the returned HTML code will be cleaned before display using a sanitizer such as DOMPurify or nh3, removing untrusted or potentially harmful content in accordance with best practices. This enhancement allows users to control how HTML content in the output is displayed, as plain text, basic HTML, or sanitized HTML, providing greater flexibility while maintaining security and stability across all components. Since this functionality operates between the checks and the GUI, it can be used uniformly for all checks without requiring any modifications to the checks themselves. sug_q5utmrdcvepv01u 2026-05-21T17:33:52Z 2026-05-22T16:05:39Z In many situations, it would be helpful to view the exact content displayed on the website when a check fails (similar to the --show-body option in check_http). Often, the returned page contains valuable information that can significantly support troubleshooting. For example, when the search string does not match or when an API returns an HTTP code other than 200, it would be beneficial to view the corresponding response content. I propose adding a configuration option that allows users to choose between the following modes: * Never – never show content * On Error – show content only when the check fails * Always – always show the returned content I understand that the displayed content may pose certain risks. However, the decision on whether this risk is acceptable should be left to me and not be restricted by default. An additional option "show simple HTML" that determines whether potentially harmful elements are removed or raw data is displayed could make the display both safer and more flexible. To address this potential issue more generally, please also refer to this suggestion about adding a sanitize HTML option for safer check output rendering: https://ideas.checkmk.com/suggestions/713053/add-sanitize-html-option-for-safer-check-output-rendering Since the error that triggered the alert often cannot be reproduced afterwards, this feature would significantly enhance the diagnostic capabilities for websites and HTTP-based APIs. sug_zani2ldfs9nilu5 2026-05-21T08:55:37Z 2026-05-22T16:02:35Z Cato Networks SD-WAN Monitoring needed to CheckMK, Cato has good status page https://status.catonetworks.com/ but for networ monitoring needed to own infra monitoring, incidents and issues from certain pops and customizable pops monitored, no need to be global. GraphQL API reference exists https://api.catonetworks.com/documentation/#introduction sug_vofwr1s4ylicfbm 2026-05-21T08:45:36Z 2026-06-01T14:46:09Z The current text is really verbose and when many of them are shown on the same page it’s really hard to read them E.g. "Cache generated 9 hours 53 minutes ago, cache interval: 1 day 0 hours, elapsed cache lifespan: 41.24%" It would be nice if it were shortened by also removing esoteric or zero-valued info. E.g. something similar to this: "Cached 9h 53m ago (update interval: 1d)" sug_xqzjuxagaoeqwug 2026-05-20T15:15:30Z 2026-05-22T15:53:06Z With the native Windows Task plugin in Checkmk, it is currently only possible to monitor all tasks, except for excluding the default Microsoft folder. It would be very helpful if it were possible to monitor only a specific folder instead. This way, tasks in the root folder would not be included, which is important because many automatically created Microsoft tasks reside there and usually do not require monitoring. Using rules to disable unwanted tasks is not an ideal solution, especially in larger environments with more than 10,000 hosts. This approach would result in a large number of disabled services, making the monitoring configuration harder to manage and less transparent. A possible solution could be to introduce an inclusion-based filtering mechanism (maybe by folder path or regex), allowing administrators to explicitly define which task folders should be monitored. This would greatly improve scalability, reduce noise, and simplify rule management in large environments. sug_6p7mk5q2thgjcrq 2026-05-18T06:25:03Z 2026-05-22T15:52:18Z At the moment there's only an option to set "State for connection refusal". Add an option for "State for connection established". That's sometimes very userfull if you want to check if an TCP port is NOT open. sug_r8gq13ad2vbadzt 2026-05-18T08:22:55Z 2026-05-20T14:16:50Z At the moment it's not posible to configure timing parameters for windows tasks. It would be nice if you could configure things like "task has to run every X hours/days". So that it's ok if the task failes once but next time the task runs without failure. sug_micubpc95oejxb4 2026-05-11T09:07:10Z 2026-05-19T14:43:44Z We have a weekly maintenance window for our hosts on Wednesday at 18:00. We currently use scheduled downtimes on services that receive a non-critical alert. This means we get the alert when an event occurs, but postpone those that don't need immediate action to the maintenance window. Works really well for us. But it's a nuisance to schedule the downtime, as I need to use the datepicker and manually edit the time. Downtime presets are very limited in that they only allow next next day/week/month/year. Would it be possible to add the possibility to add downtime presets such as "next Wednesday at 18:00"? sug_cstnt9usnyyfycy 2026-05-05T06:02:19Z 2026-05-13T12:39:43Z There are a few holidays that happen on the same date every year. Would it be possible to let us specify the year as 0000 when an exception happens on the same date every year? I.e. 0000-12-24. I suggest 0000 because the year 0 is a non existing year. The years go from 1 bc directly to 1 ad. sug_zbyfwxwy0ov4pzn 2026-05-12T13:23:13Z 2026-05-13T12:38:43Z There are many variables that can be included in notifications, but ‘Custom host notes’ is not one of them. Please add this variable to the list. It would also be useful if this variable could be enabled directly within the WATO GUI for notification rules. sug_bwikkwns4ggkphl 2026-04-28T14:00:03Z 2026-05-06T08:52:53Z Hi all, based on our recent problem, it is currently quite easy for owners and users of k8s to quickly fill up nearly any space on checkmk /omd filesystem by just quickly deploying and killing again objects in k8s. Autoscaling, autopilot GKE cluster can easily start and kill nodes, pods and other objects in massive numbers. DCD thus constantly creates new hosts and removes inactive ones from config. The catch is that RRDs that are created for each remain in place after the DCD removes the host. This leads to /omd filling rapidly on the site with no longer active hosts. Rapidly meaning a constant growth 80GB space/day or more. This way, k8s or anything else of the kind, like podman, docker, VMware etc could basically DoS the site just by running such workload. Because of that, the ordinary disk cleanup will not do - it works with days at least and it is not possible to tell it "remove only RRD's of hosts based on this label/pattern that had not been written to for more than X hours or Y days". Proposal is threefold: 1 - DCD could have an option for removing RRD's (and perhaps the inventory) of the host as well on host removal or after configurable delay. Perhaps even optionally based on the regex of the hostname, that would really help. 2 - It would be great to have in DCD the possibility to hint a renaming scheme of object like pod to provide constant naming. Like, deployment having always pod_deployment_a_1 to pod_deployment_a_X pods in it, regardles off true object names. Either by plugin, or by calling user-provided code to do a "standardisation". 3 - diskspace cleanup could have again an option to configure patterns for hosts with different "retention periods", not just a single period for everything on the site. So far, I was forced to whip up a bit dirty script to cleanup specific ballast that tends to accumulate and cause problems, but it is still working from the crontab and cannot help with filesystem filling in less than two days. sug_jx2qo9aka4bcpdv 2026-04-23T09:31:02Z 2026-05-08T08:25:43Z Only Pure Flasharrays can be monitored, integration of Pure Flashblades would be great sug_fnjelro0smj0ept 2026-04-22T22:25:48Z 2026-05-04T15:24:25Z When monitoring SUSE Virtualization nodes via SSH using a shell-based Checkmk agent script, service discovery produces an unmanageable number of irrelevant services: ephemeral container overlay mounts, KubeVirt internal devices, transient filesystems, and similar artifacts inherent to the platform. Some of these default to CRITICAL, requiring significant manual effort to reach a clean and meaningful monitoring baseline. This problem is compounded by the fact that SUSE Virtualization runs on SLE Micro, an immutable operating system using transactional updates and snapshot-based rollbacks. Any manual configuration applied to the node can be lost after an OS update, forcing administrators to repeat the cleanup process from scratch. The result is a lack of stable monitoring baselines, persistent false alerts, and ongoing operational overhead with every update cycle. Proposed solution: an official SUSE Virtualization Node Monitoring Profile shipped with Checkmk, defining: - Which mountpoints and devices to exclude by default on SLE Micro based nodes - Meaningful default thresholds appropriate for SUSE Virtualization workloads - A curated service discovery ruleset that produces a clean baseline on any fresh node Developing this profile requires collaboration with SUSE to define what a healthy SUSE Virtualization node looks like from a monitoring perspective. We have established relationships on the SUSE side and are confident the right people can be brought to the table should Checkmk be interested in pursuing this. Who benefits: any organization running Checkmk on SUSE Virtualization nodes. sug_qwrugujj5sckjfs 2026-04-22T16:21:58Z 2026-05-04T15:21:15Z Add the possibility to configure an execution interval together with simple time windows during which custom queries are allowed to run - for example, every 30 minutes between 08:00 and 17:00 from Monday to Friday, or once daily at 08:00. When the current time falls outside the defined window, instead of executing the custom query, mk-oracle could return a standardized message such as: “Skipping execution: outside check period.” Benefits: * Increased flexibility in query scheduling. * More efficient use of resources by limiting checks to relevant time periods. * Transparent and predictable query behaviour through clear feedback when executions are skipped intentionally. Example Yaml configuration: Schedule: Mon: - "0800-1100" - "1300-1700" Tue: - "0900-1100" Wed: - "0900-1100" - "1300-1700" Sat: - "0800-0805" sug_qpwqnfyzaft2hcg 2026-04-22T16:05:46Z 2026-05-04T15:20:09Z Use regular expressions in both the include and exclude for discovered CDBs, and extend this capability to allow regex‑based inclusion and exclusion of PDBs detected within those CDBs. This enhancement makes the discovery process more flexible and reduces manual configuration effort by enabling dynamic filtering of instances and databases based on naming patterns. sug_2k6zqoyvctxvqtb 2026-04-20T13:04:14Z 2026-04-28T15:48:53Z REST API: Please return the ID for each rule implemented via the API to ensure that further processing always takes place (Delete, tracing, logging, etc.) Showing all rules and searching by text for the ID is no solution at all in 2026. (Downtimes, Notifications, etc. in general at all rules we add) sug_5r6p597iv239xoi 2026-04-16T12:17:18Z 2026-04-20T19:18:55Z Allow agent to send data to a failover destination when the original destination is not reachable. The idea is to be able to easily switch the monitoring destination without having to redeploy agent configurations. If a disaster happens at the original IP which makes it not reachable we could easily restore the site backup in the secondary site (failover) and have everything working. Agents will try to connect to the original IP and then after failure will send the data to the secondary one.