View Health Status

You can view the health status of the Monitoring Session on the Monitoring Session details page. The health status of the Monitoring Session is healthy only if both the configuration health and traffic health are healthy.

View Health Status of an Application

To view the health status of an application across an entire Monitoring Session,

  1. Go to Traffic > Virtual > Orchestrated Flows and select your cloud platform.
  2. Select a Monitoring Session and navigate to the TRAFFIC PROCESSING tab.
  3. Select the application for which you wish to see the health status and select Details. The quick view page appears.
  4. Select the HEALTH STATUS tab.

This displays the application's Configuration Health, Traffic Health, and the Operational Health, along with the thresholds applied to each.

Note:  The secure tunnel status is refreshed every 5 minutes, and the GigaVUE‑FM does not display UCT-V secure tunnel status that is older than 7 minutes. If the secure tunnel in the UCT-V is removed, it takes up to 7 minutes to reset the status on the GigaVUE‑FM.

View Operational Health Status of an Application

When you configure the Application Metadata Exporter to use Kubernetes as the workload platform, the V Series Node transmits failure and error events to GigaVUE‑FM, which processes them and updates the node's health status on the Monitoring Session page. When interacting with Kubernetes workloads, the system may encounter errors while retrieving resources such as pods, services, nodes, or endpoints. Refer to Errors for additional error details.

Operational events for Exporter:

Refer below for message format and messages that indicate common issues that can occur during the operations:

Format: <Server Type>_<Message>

Server Types: CLOUD EXPORT, KAFKA

Message

Description

UPLOAD_MAX_TRIES_EXCEED

Upload retries exceeded the maximum limit

Example: CLOUDEXPORTER_UPLOAD_MAX_TRIES_EXCEED

REACHABILITY_FROM_AMX_TO_TOOLS

AMX failed to reach the tool (Cloud Exporter server or Kafka server)

Example: CLOUDEXPORTER_REACHABILITY_FROM_AMX_TO_TOOLS

NO_IP_ADDRESS

No IP address was configured on the interface

Example: CLOUDEXPORTER_NO_IP_ADDRESS

EXPORTER_UPLOAD_ERROR

Upload to the exporter failed

Example: CLOUDEXPORTER_EXPORTER_UPLOAD_ERROR
EXPORTER_ERR_EVENT_CONTEXT_DEADLINE_EXCEEDED

The exporter health-monitor probe or upload to the tool timed out.

Example:
CLOUDEXPORTER_EXPORTER_ERR_EVENT_CONTEXT_DEADLINE_EXCEEDED
KAFKA_EXPORTER_ERR_EVENT_CONTEXT_DEADLINE_EXCEEDED
EXPORTER_ERR_EVENT_CONTEXT_CANCELED

The exporter health-monitor probe or upload was canceled before completion, typically due to shutdown or reconfiguration.

Example:
CLOUDEXPORTER_EXPORTER_ERR_EVENT_CONTEXT_CANCELED

KAFKA_EXPORTER_ERR_EVENT_CONTEXT_CANCELED
EXPORTER_ERR_EVENT_DNS_LOOKUP_FAIL

The hostname of the configured Kafka broker or Cloud Exporter endpoint could not be resolved due to a DNS failure.

Example:
CLOUDEXPORTER_EXPORTER_ERR_EVENT_DNS_LOOKUP_FAIL

KAFKA_EXPORTER_ERR_EVENT_DNS_LOOKUP_FAIL
EXPORTER_ERR_EVENT_NETWORK_UNREACHABLE

The exporter probe failed at the network layer, for example, due to no route to the host or an unreachable network.

Example:

CLOUDEXPORTER_EXPORTER_ERR_EVENT_NETWORK_UNREACHABLE

KAFKA_EXPORTER_ERR_EVENT_NETWORK_UNREACHABLE
EXPORTER_ERR_EVENT_TRASPORT_LAYER_ERR

The exporter probe failed at the transport layer, such as connection refusal, TCP reset, or TLS handshake failure.

Example:

CLOUDEXPORTER_EXPORTER_ERR_EVENT_TRASPORT_LAYER_ERR

KAFKA_EXPORTER_ERR_EVENT_TRASPORT_LAYER_ERR

Operational events for Enrichment:

Refer below for message format and messages that indicate common issues that can occur during the operations:

Format: <Operation Type>_<Message>

Operation Types: GETSERVICES, GETPODS, GETNODES, GETENDPOINTSLICES, WATCHALL

Message

Description

K8S_AUTHORIZATION_FAILURE

The request was denied due to insufficient permissions

Example: GETPODS_K8S_AUTHORIZATION_FAILURE

K8S_AUTHENTICATION_FAILURE

Authentication failed. Verify your credentials

Example: GETPODS_K8S_AUTHENTICAION_FAILURE

K8S_UNHANDLED_ERROR

An unspecified error occurred. Check the error description

Example: GETPODS_K8S_UNHANDLED_ERROR

View Health Status for Individual GigaVUE V Series Nodes

You can also view the health status of an individual GigaVUE V Series Node. To view the configuration health status and traffic health status of the V Series Nodes:

  1. On the Monitoring Session page, select the required Monitoring Session from the list view.
  2. In the Overview tab, view the health status of the required GigaVUE V Series Node from the chart options.

View Application Health Status for Individual V Series Nodes

To view the application configuration and traffic health status of the GigaVUE V Series Nodes:

  1. On the Monitoring Session page, select the required Monitoring Session from the list view.

  2. On the Overview tab, select the GigaVUE V Series Node from the All V Series Nodes drop-down menu.

    The list view displays the list of applications for the selected GigaVUE V Series Node and the health status of each application.