The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization is complete. One or more workflows were affected by this. Workflow name: %2 Instance name: %3 Instance ID: %4 Management group: %1
The Author profile includes a set of privileges designed for authoring of monitoring configuration. A role based on the Authors ...
The availability monitoring of entity "%2" has been disabled. Entity Id: %1 Management Group Name: %3 Management Group Id: ...
The availability monitoring of health service %1 running on host %2 and serving management group %3 with id %4 has been disabled. ...
The availability of one or more members of the pool has changed. The ownership for all managed objects assigned to the pool ...
The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health ...
The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health ...
The baseline could not be paused. This could happen for the following reasons: - The baseline was already paused - The target ...
The baseline could not be paused. This could happen for the following reasons: - The baseline was already paused - The target ...
The baseline could not be reset. This could happen for the following reasons: - There was no baseline to reset - The target ...