VictoriaStack unifies metrics, logs and traces for AI-assisted investigation
Open-source VictoriaStack combines metrics, logs and traces with purpose-built engines while giving AI agents read-only incident investigation access.
AT A GLANCE
Key points
- VictoriaMetrics, VictoriaLogs and VictoriaTraces are packaged together.
- Components can scale independently while ingesting OpenTelemetry data.
- MCP and agent skills provide read-only incident investigation.
What is changing?
VictoriaMetrics announced VictoriaStack on November 10. The open-source observability stack combines VictoriaMetrics for metrics, VictoriaLogs for logs and VictoriaTraces for traces under a shared deployment model. Components can ingest OpenTelemetry data and scale independently, allowing teams to use purpose-built engines instead of forcing every signal into the same database.
According to the product page, official MCP servers and agent skills can give AI systems read-only access to investigate incidents, examine high-cardinality sources and identify unused metrics. Engineers still decide whether any changes are applied. Its KubeCon-week debut brings AI-assisted operations closer to the observability layer, but production adoption should still test authorization scope, tenant isolation, query cost, retention and human approval.
Explore the original sources
Source date: 10 November 2026.
Published by AI Radar: 11 Nov 2026, 01:12 (Istanbul, UTC+3).
FOLLOW THE TOPIC
Topics and tags
Share your discovery.
Send this story to a friend.
Reader comments
What do you think about this development? Share your experience or question. Comments are published after editorial approval.
Your name/nickname and comment become public if approved. Read: Privacy notice.
Loading comments…