Reccomended Action or Friendly Output
Provide clear, actionable details about issues and resolutions in the manual of checks, notifications, and UI.
Components:
Manual of Checks: Add a section with step-by-step instructions for resolving issues, specially known issues. In some cases suggestions of what could be the problem or where to start the investigation could be helpful.
Notifications: Include recommended actions in alerts.
User Interface: Display recommended actions directly in the UI.
Examples:
Notification Spooler Warning:
Issue: Warning due to corrupted files.
Action: You can look inside “~/var/check_mk/notify/corrupted/” cleanup the files and you should have no corrupted messages anymore.
Filesystem Space:
Issue: Low space.
Action: Identify large files with du -sh * | sort -rh | head -n 10, clean up, consider expanding filesystem.
Benefits:
Improved clarity, reduced downtime, enhanced user experience. Regarding the Notification Spooler Warning I have to google about the location of the folder every time.
Comments: 4
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
20 Mar, '25
Mohamed Saleh AdminHi Paulo,
Thank you for posting your idea!
The description is clear and you describe the idea very well. However, the scope of the idea as it is now is too broad. We need the scope of each idea on the portal to cover a specific suggestion or feature. This will make it easier for other users to vote and comment on specific use cases, and it will make the idea more actionable for us when we do discovery on the topic.
So lets formulate the idea's title to focus on improving the notification spooler warning, since that is the most prominent of the other examples. We can still include the rest of the text for more context, and you can always create another idea for the other cases. Could you provide a screenshot of this warning or the service itself so we can get an idea of the place where the new info would be most helpful?
Best,
Saleh
Of course, you can always create another idea for the other cases later, for example, improving the information in the Filesystem service. -
21 Mar, '25
Paulo SantanaHi Mohamed,
Thanks for your reply. I believe that limiting the scope might not deliver what I expect but I understand your statement.
The idea was to provide a capability to allow developers or administrators to use a custom field to add information about how to fix the issue or provide a friendly message explaining about the problem and avoid new users raising requests like the following ones in the forum:
https://forum.checkmk.com/t/notification-spooler-currupted-files-what-to-do/25779
https://forum.checkmk.com/t/fetcher-helper-usage/38133
https://forum.checkmk.com/t/fetcher-checker-helper-vs-generic-helper/25266
https://forum.checkmk.com/t/fetcher-problem/37085
https://forum.checkmk.com/t/active-checks-and-fetchers/44183 -
01 Apr, '25
Mohamed Saleh AdminThanks Paulo,
As the solution would be different depending on the service and the problem that caused the alert, is the suggestion that we (Checkmk) add helpful text in the output for the most common problems into the product, or rather to allow some way for the admins to add custom text as notes for any service? If you can describe how you would use the feature we could reach a more confined scope.
Looking forward to hearing back from you! -
03 Nov, '25
Martin Hirschvogel AdminMoving to in progress as we are working on an AI-powered feature to explain issues.
This MIGHT solve this need.