Werk #22435: esx_vsphere_datastores: Monitor datastores that share a name
| Component | Checks & agents | ||||||
| Title | esx_vsphere_datastores: Monitor datastores that share a name | ||||||
| Date | Nov 3, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
vSphere only requires datastore names to be unique within a datacenter. When a vCenter with several datacenters reported several datastores with the same name, for example the local datastore1 of ESX hosts in different datacenters, Checkmk created a single Filesystem service for all of them. That service showed the values of only one of these datastores, and the others were not monitored at all.
Each of these datastores now gets its own service. Their items consist of the datastore name followed by the volume ID from the datastore URL, for example Filesystem datastore1 563b3611-f9333855-cfa1-00215e221152. Datastores with a unique name keep their items and services.
Affected setups require a service discovery on the vCenter hosts. The previous service of a shared name disappears and is replaced by one service per datastore. Its history is not carried over to the new services. Rules that refer to the previous service by its item need to be adjusted.
The same happens later if a datastore with an already used name is added in another datacenter: on the next discovery, all datastores with that name get the volume ID appended. Until then the previous service reports that its item was not found.