Removing a retired host from Checkmk clears the host object from Setup and stops it from appearing in monitoring after activation. Use this when a server, appliance, cloud object, or test host should no longer be monitored and should not keep stale services in views or notifications.
Host deletion starts in Setup → Hosts → Hosts because Checkmk separates saved configuration from the running monitoring environment. The host remains active until the pending deletion is activated, so the Changes bundle must be reviewed before applying it to the selected site.
Deleting the host object does not uninstall a Checkmk agent from the retired system or remove external DNS, cloud, or CMDB records. If the host was created by network scanning, auto-registration, dynamic host management, or an automatic host removal rule, check that the source automation will not recreate it.
Related: How to add a host in Checkmk
Related: How to rename a host in Checkmk
Use Display → Search hosts from Main when the folder is unknown. Setup search can find configuration hosts that may not yet exist in monitoring.
Select only the retired or mistaken host. The Hosts menu can apply bulk actions to every selected host in the current folder.
Checkmk records saved Setup changes as pending until activation. A host deletion may share the same activation bundle with unrelated changes from the same site.
The host should no longer appear in host views, service views, or the monitoring search results for the selected site.
$ sudo su - mysite OMD[mysite]:~$
Replace mysite with the site name.
OMD[mysite]:~$ cmk -l db01 router01 web02
cmk -l lists host names configured in Setup. If the removed host still appears, check for unactivated changes or an automation rule that recreated it.