Verify VAST Telemetry¶

This page provides verification steps for the VAST telemetry data flow to VictoriaMetrics and VictoriaLogs.

Prerequisites¶

The Configure VAST Telemetry procedure is complete.
The service Kubernetes cluster is running with telemetry pods deployed.

Verify VAST Telemetry Pods¶

Verify that the VictoriaMetrics pods are running:
Run on K8s control plane
```
kubectl get pods -n telemetry -o wide | grep vm
```
Verify that the VictoriaMetrics service is running:
Run on K8s control plane
```
kubectl get service -n telemetry -o wide | grep vm
```

Verify VMagent logs for VAST scraping to view recent logs:

Run on K8s control plane

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

View VAST Metrics in VictoriaMetrics UI (VMUI)¶

Use the VMUI to validate that VAST telemetry data is being collected.

Note the External IP and port number of the VictoriaMetrics service:
Run on K8s control plane
```
kubectl get svc -n telemetry | grep vmselect
```

Access the VMUI in a web browser:

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

View VAST Logs in VictoriaLogs¶

Retrieve the VLAgent LoadBalancer IP and configure it on the VAST appliance:
Run on K8s control plane
```
kubectl get svc -n telemetry | grep -E "(vlagent|victoria-logs)"
```
Retrieve the external IP and port of the vlselect service:
Run on K8s control plane
```
kubectl get svc -n telemetry | grep vlselect
```

Access the VictoriaLogs UI in a web browser:

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