If you are monitoring your systems with the Checkmk Raw Edition (CRE), you may be at the point where you are ready to move to the Checkmk Enterprise Edition (CEE). The CEE includes all the benefits of the CRE, but also offers more power and is specifically designed for scalability. Moreover, many additional features, such as numerous automation options, will make your life easier.
In this blog, I'll discuss the key differences between both editions and help you decide whether it makes sense for you to switch. I'll also explain a few things that you should keep in mind when migrating.
Value of your time and hardware costs are the most important factors
The performance of your monitoring depends to a large extent on the monitoring core. It is the central engine of a monitoring system and, for example, initiates checks, provides status information to the GUI or detects status changes.
Here, the CEE relies on the Checkmk Micro Core (CMC), a high-performance engine with a high-performance software architecture developed by tribe29. The CRE, on the other hand, uses the core of the open source project Nagios. This is a kind of standard engine for monitoring that works reliably but lags behind modern approaches, especially in terms of performance.
When the monitoring reaches a certain size, users notice performance problems and switch to the Checkmk Enterprise Edition to save the budget for new hardware resources. Before and after comparisons of operational monitoring environments show that after switching to the CMC, CPU utilization of Checkmk host servers dropped from about 80% to less than 20%.
If you notice that your monitoring host server is reaching its resource limit, this might be a good time to switch to the CEE. Despite the basic optimization, however, the CMC is compatible with all Nagios legacy checks. So you can continue to use your monitoring plug-ins.
The CMC can run more checks per second, which makes the CEE optimal for monitoring Kubernetes. The CRE can also monitor dynamic assets, but due to is architecture its capabilities are limited.
Additional features of the Checkmk Enterprise Edition
Another argument for switching to the CEE are the extensive automation features and better management options. For example, Checkmk's reporting feature can create custom reports for you in PDF format and comes with a number of pre-built templates. If you currently take screenshots of dashboards or hosts manually, you can completely automate this process, saving you valuable time.
With the CEE, you can also take advantage of the Agent Bakery. This allows you to create (or "bake") customized agent packages and to automatically update the configuration of your Checkmk agents. When it comes to server monitoring, the Agent Bakery therefore takes a lot of manual work off your hands.
The CEE comes with many other additional features. For example, you can use a large set of integrations with other enterprise solutions such as Jira, ServiceNow, ntop or DataDog. It also offers better dashboarding and the ability to automatically create hosts in your monitoring via dynamic host configuration.
Upgrade comes as an update – without any risk
If you are considering a switch, you do not need to worry about the workload. Upgrading is no different from the normal update process to a new Checkmk version. The steps are described in detail in the Checkmk user guide. There are only some default settings for modules and features that you need to adjust once. For example, for Checkmk sites that you created with the Checkmk Raw Edition, you will need to adjust the monitoring core after switching to the CEE.
Visually, the CRE and the CEE user interfaces are almost identical, and you will easily find your way around. You can continue using the configuration of your monitoring, and the changing process will be quick. This allows you to make a risk-free switch without needing additional training.
You can also migrate from the Checkmk Enterprise Edition back to the Raw Edition, but you must first ensure that you do not use any features in the configuration that do not exist in the CRE.
Go for a test
How beneficial the enterprise features are for you depends on your individual monitoring environment. Therefore, the safest and most reliable option is a personal trial run. You can use the Checkmk Trial to test all the capabilities of the Checkmk Enterprise Edition. Often, only the practical test shows how much time and resources you save with the CEE.
Most advantages of the many small things only reveal themselves in a test run. For example, there is already an Ansible collection, which you can use to further automate the management of Checkmk agents. The Checkmk Enterprise Edition also offers the notification spooler, which eliminates notification delays.
With the CEE, you also have the option to book a support package. This allows you to benefit from the experience of our Checkmk consultants. For example, if you have set up a large monitoring environment with the CRE or another monitoring solution, we can help you migrate to the CEE.
Best practices for migrating from Raw to Enterprise
If you are considering a migration to the Checkmk Enterprise Edition, you should keep the following points in mind.
Check the number of your monitoring services
You purchase an annual CEE subscription, and get an invoice based on the number of services monitored. The Checkmk sales team usually audits the number of services once a year to avoid under- or over-licensing. You can check the necessary budget on the pricing page and also order a subscription directly on the website.
Make backups of your configuration before the migration
The upgrade is simple, nevertheless you should make a backup of your Checkmk configuration before you make some changes.
Update all Checkmk sites to the latest version
Since you are ideally migrating to the latest version of the CEE, your current monitoring environment with the CRE must also be up-to-date. The latest version ensures that known vulnerabilities are fixed and that you can use all new features. Under no circumstances should you use a Checkmk version that tribe29 no longer actively maintains. An overview of the supported Checkmk versions can be found in the Checkmk manual.
In order to migrate your configuration safely, all Checkmk sites of your current monitoring environment must be up-to-date with the CRE. Especially for distributed monitoring, you should not use different Checkmk versions at the same time. Do not skip versions, or you may experience compatibility issues. For example, if you are using Checkmk version 1.6, you must first update to Checkmk 2.0 before you can switch to Checkmk 2.1.
Reconsider your monitoring processes
Especially when switching to the CEE, you should say goodbye to outdated approaches. For example, many users use outdated plug-ins in Checkmk. If you still used Nagios plug-ins in the CRE, for instance, you should check if there is an official check plug-in when switching to the CEE. These work more efficiently and are regularly maintained by the Checkmk development team.
Also, some users manually configure steps that Checkmk can do automatically. Especially if you are considering a switch to the CEE, you should keep an eye on options for automatic configuration. For example, you can configure Checkmk via the Rest API.
Conclusion: the CRE and the CEE have their advantages
There are good reasons to choose the Checkmk Raw Edition. Thanks to 100% open source technology, it offers maximum control and unparalleled extensibility. The Checkmk Enterprise Edition additionally offers better performance, numerous automation options and other advantages. In the end, it is up to you to decide. However, with the Checkmk Trial, you have a good opportunity to test all enterprise features in advance.