We have some cdm alerts on few robots that mention a different server name in the message than the actual robot name (which is set to automatically detect it is not hardcoded).
The server was recently migrated to a new datacenter and thus has a new hostname which the controller probe picked up but cdm is still alarming using old name.
The server is configured correctly at the OS level to reflect the new correct hostname so not sure where cdm is getting this from.
Release : 20.4.x
probe: cdm
Clearing the niscache of the robot resolves the issue