VictoriaLogs
VictoriaLogs stores container logs, Kubernetes events and Falco alerts. Grafana reads it through its Loki plugin. Upstream docs.
| Namespace | victoria-logs |
| Source | victoria_logs.go |
| Exposure | LAN · victorialogs.madhan.app (built-in UI) |
| Storage | 100Gi on the default longhorn class |
| Auth | None |
Configuration
Section titled “Configuration”| Setting | Value | Why |
|---|---|---|
retentionPeriod | 30d | |
retentionDiskSpaceUsage | 40 GiB | Each replica shares a worker disk with every other Longhorn volume, so cap by size as well as age |
| Limits | 1000m / 1Gi |
| Endpoint | Used by |
|---|---|
http://victoria-logs-victoria-logs-single-server.victoria-logs.svc.cluster.local:9428/insert/opentelemetry | OTel otlp_http/logs exporter, which appends /v1/logs |
…:9428/select | Grafana Loki datasource |
Operate
Section titled “Operate”Query in Grafana’s Explore with the VictoriaLogs datasource (main org only):
{namespace="ollama"} |= "error"{namespace="falco"} |= "Terminal shell in container"Or directly: curl "https://victorialogs.madhan.app/select/logsql/query?query=*&limit=5".
Troubleshooting
Section titled “Troubleshooting”No logs in Grafana
Section titled “No logs in Grafana”Check VictoriaLogs runs and the agents export without errors:
kubectl get pods -n victoria-logskubectl logs -n opentelemetry -l app.kubernetes.io/instance=otel-agent --tail=50Every log query returns 404
Section titled “Every log query returns 404”The datasource URL has /loki appended. It must end at /select.