Werk #22392: netapp_ontap_snapvault: Configurable monitoring state for the transfer state
| Component | Checks & agents | ||||
| Title | netapp_ontap_snapvault: Configurable monitoring state for the transfer state | ||||
| Date | Sep 29, 2026 | ||||
| Level | Trivial Change | ||||
| Class | New Feature | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
The rule NetApp Snapvaults / Snapmirror Lag Time is now called NetApp SnapVault / SnapMirror. Existing rules are kept. The item of the rule is now called "Destination" instead of "Source path", because the item has always been the destination path of the relationship.
Previously, the Snapvault services showed the SnapMirror transfer state, but this result was always OK (see werk #17937). A failed transfer therefore did not raise an alert.
The service now evaluates the transfer state. By default:
- "failed", "aborted" and "hard_aborted" are CRIT
- "queued", "success" and "transferring" are OK
- any other transfer state reported by ONTAP is UNKNOWN
The service also shows whether ONTAP reports the relationship as unhealthy, together with the reasons from ONTAP. An unhealthy relationship is CRIT by default.
You can change these states with the rule NetApp SnapVault / SnapMirror.
Compatibility
This werk is incompatible because the update changes your monitoring without any change to your configuration:
- Snapvault services can go CRIT after the update. This happens if the relationship reports a failed or aborted transfer, or if ONTAP reports the relationship as unhealthy. If you do not want these alerts, set the matching states to OK in the rule NetApp SnapVault / SnapMirror.
- Relationships without a lag time now also get a service, for example a relationship whose first transfer failed. Run a service discovery on the affected NetApp hosts to add these services.