As we continue Beta Testing, we want to share an exciting change in this release—a major rework of notifications!
What’s new?
New notification overview: Find everything related to notifications in one place with increased visibility and quick access.
New rule wizard: A setup that guides you through the configuration making it straightforward while reducing the mistakes.
Updated major notification methods: Improved security and expanded configuration options, so that you receive all information that you need with the method of your choice.
Redesigned email notifications: A modern look to help you find information more quickly.
New notification parameters: Set up a method once and reuse it in any global notification rule.
Since these changes are quite big, we’d love your help in testing them during a Bug Bash Community Call that will also include a quick overview of the new features by the initiative owner – @theyken
Goal: Find as many bugs as possible during the session. Prerequisite: Checkmk 2.4 Beta installed. Prizes: A small Checkmk souvenir for the person who files the most bugs and another for the most “unique” bug (as chosen by the development team). We can send souvenirs within the US and EU. When? April 8th, on Zoom (not recorded) at 2pm Berlin time. The session will last about 1.5 hours.
Looking forward to testing (and breaking things!) together!
Upd: A calendar invite is bug_bash.ics (1015 Bytes)
I give others a chance to find them instead. (read: currently, I don’t have the available resources for the prerequisite)
Edit:
Wild idea …
Maybe if there are beta play.checkmk.com environments set up, prerequisite falls away, opening it up for broader audience. Then suddenly almost anyone can help catch spring critters. (-;
I used the play area in the past to check some differences between my raw and the play edition. I was a bit sad back then that no edits were possible. But on the other hand, it’s totally understandable that you don’t want that setup open to anyone.
Your wish is my command
I’ve added one and will do so in the future.
Another question – we were thinking about maybe creating a sign-up for community events – so that we could remind about them in a day or so. What do you think?
It is likely we will not be able to set this up for this event, but we have a solution that would allow the Community to sign up for a specific Community Event from the next one on!
Last week’s Bug Bash was not only fun but super valuable! Thanks to your sharp eyes and dedication, we uncovered 19 bugs in total!
Luckily, none of them were critical or blockers, but still very helpful findings that will further improve the user experience and robustness of the new notifications.
Some of the issues are already fixed, and we’re actively working on the rest. One of the most annoying bugs, called out by Patrick, was that popup warning about unsaved changes when leaving the Setup, even if nothing had actually changed. We felt your pain, and jumped on it right away. It’s already fixed, so no more unnecessary interruptions!
A special shout-out goes to Lukas from comNET, our top bug hunter, with 7 bugs found.
If you’re curious about the details, you can find a full overview in the PDF by Sara.
Lastly, we’d love to hear how you experienced the format—what worked well, what didn’t, and how we might improve it for next time. Your feedback helps us make these community activities even better.
