Exploring vuSiteManager

Overall Health

Here, the overall health of the vuSmartMaps cluster is displayed for the selected time range, indicating the availability of all VM hosts and K8s cluster components. If any VM host or K8s component is down, it will be shown under active alerts currently in vuSmartMaps, as well as all alerts that have ended (inactive alerts).

The first panel at the top represents the total number of alerts, indicating the quantification and severity of alerts in critical and warning states.

The overall health panel displays a bar graph representing the status of the vuSmartMaps cluster. Each bar represents the cluster’s status for an hour within the selected time range of the past 24 hours. If the health status is above 80%, the bar is shown in green, indicating good health. If the health status is below 80%, the bar is displayed in red, indicating critical health status for the vuSmartMaps cluster.

The Active Alerts panel showcases a table representing information related to the active alerts.

The following fields will be displayed as follows

• Alert Name: The name or description of the active alert
• Alert Type: The category or classification of the alert
• Severity: The level of severity associated with the alert
• Start Time: The timestamp indicating when the alert was triggered
• End Time: The timestamp indicating when the alert was resolved (This field is empty, as the alerts remain unresolved)
• Alert ID: A unique ID assigned to the alert for tracking and reference purposes.

Inactive alerts showcase a table representing information related to alerts that have been resolved. These alerts typically indicate the issues that were previously active but have since been resolved.

Availability

Availability provides a graphical depiction of the vuSmartMaps URL availability in the selected time range. It ensures accessibility by performing an HTTP request to the vuSmartMaps URL every minute.

The first panel at the top represents the total number of alerts, indicating how many are in the critical state and how many are in the warning state.

The availability panel displays a bar graph representing the availability of the vuSmartMaps cluster’s URL. For example, each bar represents the availability for an hour within the selected time range of the past 24 hours. If the availability is above 80%, the bar is shown in blue, indicating that the vuSmartMaps cluster has been available. If it is below 80%, the bar is displayed in red, indicating a reduction in the availability of the vuSmartMaps cluster URL.

VM Hosts

VM Hosts provide the user’s VM data in a tabular format. The following are the details displayed in this section:

1. System: This displays the status of all the hosts
2. CPU: This shows the CPU percentage usage and CPU load average (for 1 min and 5 min) for all hosts.
3. Memory: Details of memory usage and availability for all hosts.
4. Network IO: This tab presents network details such as data packets transferred and received by the hosts, along with the type of interface used.
5. Disk IO: This section details disk read and write operations.
6. Disk: This displays disk path and usage for respective hosts

Clicking on each of these tabs will take you to the corresponding table, where you can find detailed information.

Above the table, you’ll find a search box and an ‘Add Filter’ option, designed to streamline your search process.

In the search box, simply input the hostname or IP address of the system to initiate your search. Additionally, you have the option to add filters, such as Hostname and status, to further refine your search

💡Note: You can add more than one filter at a time. Filter options vary by VM Host type.

Alerts

The Status Alerts are triggered by vuSiteManager and created when any host or other Kubernetes resources go down. The severity of these alerts will be critical. The alerts section lists the details of these alerts in a tabular format.

VM Host Alert

The VM Host Alert section outlines the details of the alert triggered when the VM Host goes down.

The following are the fields displayed in the table:

• Alert Name: Name or description of the alert
• Alert Type: Category or classification of the alert
• Severity: Level of severity associated with the alert
• Start Time: Timestamp indicating when the alert was triggered.
• End Time: Timestamp indicating when the alert was resolved
• Alert ID: A unique ID assigned to the alert for tracking and reference purposes.

K8s Metrics

K8s (Kubernetes) Metrics outline the details of the alert triggered when any K8s metric goes down. It has individual tables for the following:

• K8s Pods
• K8s Deployment
• K8s DaemonSet
• K8s StatefulSet

Services

This section offers a comprehensive view of the status of all vuSmartMaps services operational within the user’s environment in the tabular format.

The following are the fields displayed in the table:

• Timestamp: The date and time when the status information was recorded.
• Name: The name of the vuSmartMaps service
• Type: The type or category of the service (e.g., application, deployment).
• Namespace: The namespace or logical grouping within which the service operates
• Created time: The timestamp indicates when the service was created.
• Pods: The number of pods associated with the service.
• Status: The current operational status of the service.
• Logs: A button that allows users to access the logs associated with the service

Users can access service logs directly by clicking the Logs button.

On clicking, it will showcase the log associated with a particular service

You can download this log by clicking the Download button located at the top left. Once clicked, the log file will be downloaded to your local system.

The refresh button enables you to update the status information, ensuring that you have the most recent and accurate data regarding the operational status of vuSmartMaps services within your environment.

K8s Metrics

Under the K8s (Kubernetes) Metrics section, you’ll find detailed information about the various health and performance metrics of your Kubernetes cluster.

K8s Pods

In Kubernetes, a pod is the smallest deployable unit. Think of it as a wrapper that encapsulates one or more containers, storage resources, a unique network IP, and configuration options. Pods are ephemeral by nature, meaning they can be easily created, destroyed, or replicated.

This section provides insights into the status and performance of the Kubernetes pods within your Kubernetes cluster, offering details such as their operational status and other relevant information.

K8s Pods have two tabs

• • Pods Status
  • Pods Performance

Pods Status

Under Pod status, the following are the fields displayed in the table:

• Timestamp: Indicates the time at which the status information was last updated.
• Pod Name: Specifies the name of the pod.
• Namespace: Identifies the namespace in which the pod is deployed.
• Hostname: Specifies the hostname of the node where the pod is running
• Status: Describes the current operational status of the pod, such as “Running,” or “Not Running.”

Pod Performance

Under Pod Performance, the following are the fields displayed in the table:

• Timestamp: Indicates the time at which the status information was last updated.
• Pod Name: Specifies the name of the pod.
• Namespace: Identifies the namespace in which the pod is deployed.
• Hostname: Specifies the hostname of the node where the pod is running
• CPU Usage: Provides information about the CPU usage of the pod, indicating the amount of CPU resources consumed
• Memory Usage: Indicates the memory usage of the pod, specifying the amount of memory resources utilized.
• Disk IO (MB): This shows the amount of disk input/output (I/O) operations in megabytes (MB) performed by the pod, indicating disk usage and data read/write volume.

K8S DaemonSet

DaemonSets in Kubernetes ensures that a specific pod runs on every node within the cluster. They’re like background processes that run on each machine, providing services such as logging, monitoring, or networking. 

Here, you can view the status of the DaemonSets running across all nodes in your cluster. DaemonSets ensure that specific pods (or daemons) are running on all or a subset of nodes in the cluster.

The following are the fields displayed in the table:

• Timestamp: Indicates the time at which the status information was last updated.
• Name: Represents the name of the DaemonSet.
• Namespace: Specifies the namespace in which the DaemonSet is deployed.
• Host: Identifies the node (host) within the cluster where the DaemonSet is running.
• Created at: Denotes the time when the DaemonSet was initially created.
• Replicas: Indicates the desired number of replicas (instances) of the DaemonSet pods.
• Status: Describes the current status of the DaemonSet, such as whether it is running as expected or encountering any issues (Not Running).

K8s Deployment

Deployments in Kubernetes are used to manage sets of identical pods, typically for stateless applications. They ensure a specified number of pod replicas are running at any given time, and handle scaling, updates, and rollbacks automatically.

This section offers a status overview of Kubernetes Deployments, which manage the rollout and scaling of applications across the vuSmartMaps cluster.

The following are the fields displayed in the table:

• Timestamp: Indicates the time at which the status information was last updated
• Name: Specifies the name of the deployment.
• Namespace: Identifies the namespace in which the deployment is deployed.
• Host: Specifies the host or node where the deployment is running.
• Created Time: Denotes the time when the deployment was initially created.
• Replicas: Indicates the desired number of replicas (instances) of the deployment.
• Status: Describes the current status of the deployment, such as whether it is successfully running, scaling, or encountering any issues.

K8S StatefulSet

StatefulSets are used for managing stateful applications, such as databases or key-value stores, in Kubernetes. Unlike stateless applications, stateful applications require unique identities and stable network addresses. StatefulSets ensure that each instance of a pod maintains its identity and can be managed effectively, making it suitable for databases or applications that require persistent storage.

In this segment, you’ll find information about StatefulSets, a controller used to manage stateful applications such as databases. Specifically, it outlines the status and management of stateful applications, ensuring stability and predictability.

The following are the fields displayed in the table:

• Timestamp: Indicates the time at which the status information was last updated.
• Name: Specifies the name of the StatefulSet.
• Namespace: Identifies the namespace in which the StatefulSet is deployed.
• Host: Specifies the host or node where the StatefulSet is running.
• Created Time: Denotes the time when the StatefulSet was initially created.
• Replicas: Indicates the desired number of replicas (instances) of the StatefulSet.
• Status: Describes the current status of the StatefulSet, such as whether it is “Running” or “Not Running”.

Upcoming Enhancements

Here are the future enhancements planned for vuSiteManager that users will soon be able to access:

1. License Information and Management:

1. • Users will be provided with complete license information, including time-to-expire, number of nodes, number of apps, etc.
   • They will also have access to scope details from the license file to aid with installations.

2. Data Usage:

1. • Users will have visibility into data ingestion in GB/day and the number of documents/rows for each data source.

3. Agent Status:

1. • Users will be able to view the status of each Agent, the TCP connectivity for each agent, and the data ingestion status from each.

4. User Engagement:

1. • Insights into user activities such as accessed objects, modifications, etc., will be provided.
   • Users will have access to analytics on the number of users and the frequency of user logins.
   • A more detailed user engagement dashboard with drill-down capabilities will be available.

5. Alert Engagement:

1. • Users will gain access to the Alert Engagement dashboard, which will display granular details on alert interactions, including clicked alerts, opened alert emails, and IP addresses that interacted with alerts.

6. Internal Orchestration:

1. • Service Orchestration: Users will have access to and decide when to start a service, where this service should run, and when to stop a service.
   • ContextStream Orchestration: Users will have access to monitor the orchestration of  ContextSream modules like I/O streams, pipelines, and connectors.
   • O11ySources Configuration Orchestration: Users will also have access to monitor the orchestration components when an O11ySource is configured (e.g. Agents like Telegraf, pipelines, etc.)

7. One-Click Upgrade:

1. • A convenient one-click upgrade or patching mechanism for vuSmartMaps services or the entire platform will be introduced, allowing users to easily bring in new functionalities/releases.