This has also been sent as part of the September Checkmk Newsletter. If you would like to subscribe to to monthly Checkmk updates via e-mail, please sign up here.
Dear Checkmk community,
For many months our development team has been pushing to deliver the next full version of our IT monitoring solution. In doing so, we have reworked many of Checkmk’s foundations. In fact, we have upgraded Checkmk so much, that we have decided to make the version step change to 2.0.
Here are some highlights of what’s new in Checkmk 2.0:
Easier usability with a new user experience incl. a new navigation, design overhaul, improved dashboards and data visualization
Higher performance with a new architecture of the Checkmk Micro Core (CMC) that increases its throughput while reducing its memory and CPU footprint
Improved automation capabilities with a REST-API that covers large parts of our current Web-API as well as operations data (‘Livestatus’)
Simpler development and maintenance of check plugins with the newCheck-API
In-depth visibility into networks with Network Flow Monitoring through an in-depth ntop integration
Higher configuration flexibility with expanded use of labels , which are discovered for more systems and can be used to filter views and set notification conditions
More insights with advancedforecasting for metrics
Improved performance through incremental configuration sync in distributed environments
Improved Grafana integration (now also available in the Checkmk Raw Edition)
Modern graphs for the Checkmk Raw Edition
Entire codebase rewrite, now in Python 3.8
And much more…
Since these changes are very significant, we want to make sure we have enough time for testing— both for usability as well as for quality. As such, we have decided to push back the release to the beginning of next year.
It’s important for us that you, as part of our user community, are involved in this process. Your early feedback is crucial to the success of Checkmk 2.0, that’s why we are doing an ‘Innovation Release’ at the end of October. It will not contain all of the aforementioned changes yet. We will share details of the content in the innovation release announcement.
This milestone is something big for us, and we want to talk to you more about it. We invite you to join us in an online Community Call approximately a week after the Innovation version’s release. This is the perfect opportunity to learn more about the release and ask your questions live! We will announce when and where it will happen here on the forum, as well as on our Twitter and LinkedIn accounts. If you’re subscribed to the newsletter, we will also send out a special newsletter for that topic.
For any feedback and thoughts you wanted to share regarding this announcement, feel free to leave a reply on this thread as usual.
This presentation at the last conference can give some impression. On the Innovation Release, we expect to be able to share the new UI so you can play with it and give your feedback
Hi,
does anyone happen to know if in version 2.0 the labels are transferred to the notification environment? This is currently not the case and unfortunately I can’t see any werks regarding this so far.
Thanks!
In my test site i see no conditions for the labels inside the notification system.
EDIT : a test inside the notification system shows no labels in the complete notification context.
If there is nothing in the context then there are also no NOTIFY_ variables
Hi @andreas-doehler ,
I do not mean labels as conditions. I mean labels in the Notification Environment.
The Variables which are transferred to any notification script.
All NOTIFY_ Variables.
I would like the host and service labels as NOTIFY_ variables. So I can use them in my event management system.
Hi,
Does version 2.0 also include this feature?
we were waiting for 1.7 release now it seems next release will 2.0. so just wanted to confirm we also get this feature in 2.0.
Most of the incident management systems like xmatters can be integrated with writing a notification plugin for checkmk that calls an API-URL of the system.