Don’t miss next week’s community call, where we will talk about creating dashboards in Checkmk! We unfortunately had to cancel the call last month, but now we’re back with a new date. Hope you can make it!
As there have been a couple of discussions around the topic, it might be useful if we can gather all your feedback about inconsistencies in the Checkmk UI and hear how you think we can make it better. Share your thoughts directly to our Director of Product, Thomas Lippert (@TLI) in this thread.
How did we do in addressing your needs as a part of the Checkmk community? Let us know what you think in by filling out this survey! Your feedback is a crucial input for our 2022 community strategy, to ensure that we can do better. Another than your thoughts about how we’re running the community and your motivations to keep engage, we also want to learn how can we do better in creating content for you to learn about Checkmk.
It will just take a few minutes and you can skip questions you’re not comfortable to answer. Hope you can share your feedback with us!
Community members whose reply got marked as a solution for the first time. Welcome aboard!
Community members who got 5 replies marked as the solution. Thank you for continuing to help other Checkmk users!
This month, we have someone new joining the ranks of our most helpful community members. Thank you for all the time you have spent helping the Checkmk community @tosch!
These are the people who have contributed packages to the Exchange published last month.
fsearkalex: Notifications via Vonage
gpochiscan: Infoblox DNS Latency and Count
Contributors whose PR got merged/included in the commit on the Checkmk GitHub repo last month. Also included are PRs that were not directly merged, but an action was taken by someone from tribe29 to apply the PR (e.g. creating internal tickets)