Verify VAST Telemetry Flow

This section outlines the steps to verify VAST telemetry data in VictoriaMetrics.

View Collected VAST Telemetry Data using VictoriaMetrics UI (VMUI) - Cluster Mode Deployment

After applying the telemetry.yml configuration using the VictoriaMetrics deployment mode as cluster, use the VictoriaMetrics UI (VMUI) to validate that VAST telemetry data is being collected and stored successfully in a cluster mode VictoriaMetrics deployment. For more details, see VictoriaMetrics Cluster deployment documentation.

Run the following command to verify that the VictoriaMetrics pod is running:
```
kubectl get pods -n telemetry -o wide | grep vm
```

Run the following command to verify that the VictoriaMetrics service is running:
```
kubectl get service -n telemetry -o wide | grep vm
```

Run the following command to verify VMagent logs for VAST scraping to view recent logs:

VMAGENT_POD=$(kubectl get pods -n telemetry -l app.kubernetes.io/name=vmagent -o jsonpath='{.items[0].metadata.name}')
kubectl logs $VMAGENT_POD -n telemetry -c vmagent --tail=10

Note the External IP and port number of the VictoriaMetrics service. The external IP and port number will be used to access the VictoriaMetrics UI (VMUI):
```
kubectl get svc -n telemetry | grep vmselect
```

Access the VMUI in a web browser using:

https://<external vmselect loadbalancer IP>:8481/select/0/vmui

Key VAST Metrics

Key VAST Metrics
Metric Name	Description	Unit
vast_volume_read_throughput	Read throughput per volume	bytes/sec
vast_volume_write_throughput	Write throughput per volume	bytes/sec
vast_volume_read_iops	Read IOPS per volume	operations/sec
vast_volume_write_iops	Write IOPS per volume	operations/sec
vast_volume_read_latency	Read latency per volume	milliseconds
vast_volume_write_latency	Write latency per volume	milliseconds
vast_capacity_total	Total storage capacity	bytes
vast_capacity_used	Used storage capacity	bytes
vast_capacity_available	Available storage capacity	bytes
vast_volume_state	Volume operational state	state
vast_device_health	Device health status	state
vast_cluster_node_status	Cluster node status	state
vast_alarm_count	Active alarm count by severity	count

View VAST Logs using VictoriaLogs

Configure the VLAgent LoadBalancer IP address for syslog delivery. Retrieve the VLAgent LoadBalancer IP and configure it on the VAST appliance by following the steps outlined in the prerequisites section above:
```
kubectl get svc -n telemetry | grep -E "(vlagent|victoria-logs)"
```

Retrieve the external IP and port of the vlselect service:
```
kubectl get svc -n telemetry | grep vlselect
```

Access the VictoriaLogs UI in a web browser using:

https://<external vlselect loadbalancer IP>:9471/select/vmui

If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.