Project Summary
Check_mk adopts a new a approach for collecting data from operating systems and network components. It obsoletes NRPE, check_by_ssh, NSClient and check_snmp. It has many benefits, the most important of which are:
* Significant reduction of CPU usage on the Nagios host.
* Automatic inventory of items to be checked on hosts.
The larger your Nagios installation is, the more important get these points. In fact check_mk enables you to implement a monitoring environment exceeding 20.000 checks/min on the first hand.
In a Nutshell, CheckMK...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a very large development team
with stable Y-O-Y commits -
...
took an estimated 390 years of effort (COCOMO model)
starting with its first commit in March, 2002
ending with its most recent commit 5 months ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
learn about Open Hub updates and features on the Open Hub blog
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummaryJan 1 2025 — Jan 31 2025
|
12 Month SummaryJan 31 2024 — Jan 31 2025
|
