Oceana Dashboard provides a consolidated view of the health of Avaya Oceana® services. The dashboard also provides access to context-sensitive troubleshooting documentation for any active problems. The Traffic Light view displays different functions of Avaya Oceana® covering Channels, Agent Operations, Authorization, LDAP connection health, Engagement Designer health, and EDM connectivity health.
The list of channels and features that the Oceana Dashboard monitors is configured using the OceanaConfiguration service, and values are pushed down to all instances of Dashboard service located on all clusters. Changes using the configuration service are dynamic and do not require reboot.
Avaya Oceana® The Oceana Dashboard page provides information about the service status and displays the current high-level state of Avaya Oceana® features. Each feature is displayed as a color-coded card based on the state of the services which that feature requires. Each feature card contains colored boxes representing the status of a service which that feature requires to operate. Clicking on one of the cards, automatically filters the service list to only display the services which are required for the selected service.
The Oceana Dashboard page displays the following:
The name of the service.
The time that the last heartbeat
The name of the cluster where the service is installed.
The name of the node inside the cluster.
The latest heartbeat message.
The heartbeat message includes the node reporting the heartbeat, the status level of the heartbeat, and the time since the last update.
There are four levels of colors displayed for each service:
Green: Indicates that all nodes running the service has returned a healthy heartbeat.
Yellow: Indicates that one or more service nodes in the cluster returned a warn heartbeat.
Orange: Indicates that one or more service nodes either returned an error heartbeat, or is not responding. There are some service nodes remaining in operation which can provide partial service.
Red: Indicates that all the nodes for a service are either reporting an error or not responding, indicating that the entire service is down.
