In-Progress
Checkmk can already be deployed in the cloud and provide monitoring for most cloud services.
We plan to take this even further and enable cloud-native Checkmk deployment by enabling the installation of Checkmk directly via the AWS marketplace.
To improve the usability of the Checkmk agent in the cloud and in dynamic environments, we plan to allow agents to register themselves at the monitoring server. We will also introduce a standard for push agent data to the Checkmk server.
All data send from the Linux and Windows Checkmk agent can be encrypted and compressed to maintain privacy and save bandwidth costs over public networks.
New check for AWS Lambda serverless computing.
Completetly rewritten support for Kubernetes monitoring will monitor the cluster and all nodes and is simple to setup and configure.
A dashlet that shows the event statistics in a hexagon view.
New dashlet type shows host and service state with various customization options.
Finetuning the new V2.0 UI for consistency and best usablity.
Simplify the workflow for service discovery and improve the respective view for a better presentation of information.
Comprehensive dashboard for all metrics of a Linux server.
The Windows agent created by the bakery will be signed to better deploy in high-security Windows environments.
With the introduction of the REST-API in Checkmk 2.0 we extended the coverage even beyond the scope of the existing APIs. Our goal is however completeness of the new REST-API: Everything can be done via an API.
Significant enhancements to the MS-SQL check.
Significant enhancements to the SAP HANA check.
Significant enhancements to the MS Internet Information Service.
Various performance improvements to the AIX agent.
Significant enhancements to the Cisco ASA check.
Native export of metrics data to InfluxDB.
We improve the existing integration with Grafana, which was initially delivered in Checkmk 1.6.
Furthermore, the Grafana integration will also support Grafana 8.
Integration of Datadog with Checkmk.
Planned
New checks for AWS Elastic Container Service, general AWS health of the customer's region, AWS Route 53, and AWS ElasticCache for Redis.
New checks for Azure health of the customer's region, Azure Load Balancer, Azure Database based on MySQL and PostgreSQL, and Azure Traffic Manager.
Kubernetes specific application dashboard.
New dashlet type shows information from the inventory (e.g. number of CPUs, memory, etc.).
Simplification of the way, views and dashboards can recieve their parameters.
Simplify the workflow to activate changes, especially for small changes, e.g. local to one folder.
Comprehensive dashboard for all metrics of a Windows server.
Comprehensive dashboard for all metrics of a vSphere cluster.
We increase the performance for activating changes for very large configurations and with a large number of configuration users.
Several concepts are being considered, e.g. activating changes for individual folders instead of the entire configuration.
We plan to support SAML for Single Sign-On.
New check for Meraki access points.
Under Consideration
Discovering dependencies using information from physical and virtual networks and application configurations (e.g. vSphere, Oracle, Kubernetes) and visualizing these dependencies.
This will help in
- resolving issues quicker
- preventing issues from happening
- reducing unnecessary notifications
Automatic correlation of metrics to find systems which experience similar atypical behaviour and powerful visualizations intelligently highlighting anomalies using large amounts of data to find root causes quicker.
Distributed tracing across microservices, hosts, and containers via integration of major APM tools (e.g. Jaeger)
We consider support for OpenMetrics, a cloud-native highly scalable protocol for applications to expose their metrics.
We plan to build a special agent similar to AWS and Azure:
- Ready-built for dynamic configuration
- Checks for standard services
- Cloud Storage
- Compute Engine
- Cloud SQL
- Cloud Load Balancing
Additional checks are possible based on feature requests.
We consider to extend the JMX monitoring to enable in-depth monitoring of Java Application Servers.
“Blackbox” services increase importance of testing from user perspective: Synthetic monitoring (aka E2E).
We plan to provide a standard solution for synthetic monitoring with Checkmk: either by integration with another solution or by providing needed guides
Redfish has been established as the new standard for managing servers.
We plan to build a special agent and check plug-ins for vendor-independent server monitoring.
We consider extending our monitoring capabiltites to tools common in the Kubernetes ecosystem
- Improve monitoring for interfaces and toolchain typical in Kubernetes, e.g. CSI, CNI, nginx, Cassandra, Kafka
- Further integration into Kubernetes ecosystem, e.g. Istio