You can disable user-specific status calculation to ensure that all users see the same status for the services that are assigned to them. If user-specific status calculation is disabled, all users see the global service status, even if not all messages that contribute to that status are available to them.
A user's map view displays only the services that are assigned to the user through user roles. User roles also determine the nodes, and therefore the messages a user is responsible for. Because the status of the services in a user's map view is calculated based on the user's subordinate services and messages, it is user-specific. Another user with a different set of responsibilities may see a different status for the same services. If you want all users to see the same status for all assigned services, you can disable user-specific status calculation.
OvEpStatusEngine
service.Use operational status calculation to see how a service hierarchy would look if all owned messages were acknowledged; in other words, if the problems were solved.
The status of a service is determined by the status of its subordinate services and by the status of the messages for that service. In general, when you acknowledge all messages for a service, the status of the service changes to reflect the status of its subordinate services.
You can change the role of messages in status calculation by enabling operational status calculation. In operational status calculation, the ownership state of messages determines how the messages influence status calculation, so that owned messages are considered acknowledged and do not affect the severity status of a service.
OvEpStatusEngine
service.Related Topics: