Werk #973: Renaming of hosts via WATO
| Component | Setup | ||||||||||||||||||
| Title | Renaming of hosts via WATO | ||||||||||||||||||
| Date | May 20, 2014 | ||||||||||||||||||
| Level | Prominent Change | ||||||||||||||||||
| Class | New Feature | ||||||||||||||||||
| Compatibility | Compatible - no manual interaction needed | ||||||||||||||||||
| Checkmk versions & editions |
|
WATO has now a new function Rename Host. You will find a button with that name in the Properties of a host. It allows a renaming of an existing host. Before you can use that feature you need to have all changes activated, so nothing is pending.
Renaming a host is a complex precedure that will not only rename the host in WATO, but also in:
- all rules from Host & Service Parameters
- cluster's node definitions
- a host's parent definitions
- Business Intelligence rules
- notification rules (both rule based and flexible notifications)
- internal Check_MK data like caches and performance counters
- auto-disovered services of the host
- logfile information of logwatch plugin
- stored SNMP walks
- RR databases with performance data
- RRD updates in journal of RRD Cache
- spool files of PNP4Nagios
- NagVis maps
- monitoring history entries (events and availability)
- the current monitoring state (including ackowledgements and downtimes)
Please note that renaming of a host involves a temporary stop of the monitoring core. This is neccessary in order to avoid situation where the old and the new name of a host is being used at the same time.