...
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Communication between Server and Agent
...
Within Checkmk, you can define your own roles and restrict them to specific permissions (https://docs.checkmk.com/latest/en/wato_user.html#roles)
Distributed Monitoring
- Communication from the central to a remote site via TLS is possible and recommended.
- Centralized configuration via HTTPS is possible and recommended
- Restriction of IP addresses allowed querying remote sites is possible and recommended
- If your remote site is not directly accessible via the central Server, you can push the data from the remote to the central Server (https://docs.checkmk.com/latest/en/distributed_monitoring.html#cmcdump)
- This is only for viewing. No actions/Notifications are possible on the central site for this remote site
Distributed Notifications
- The remote site and (notification-)central notification spoolers communicate with each other via TCP. Notifications are sent from the remote site to the central site. The central site acknowledges to the remote site that the notifications have been received, which prevents notifications from being lost even if the TCP connection is broken.
There are two alternatives for the construction of a TCP-connection:
A TCP-connection is configured from the central site to a remote site: Here, the remote site is the TCP-server.
A TCP-connection is configured from a remote site to the central site: Here, the central site is the TCP-server.
- Notification spooler connections can be encrypted with Checkmk 2.1 → https://checkmk.com/werk/13610
...