VictoriaMetrics is a fast, cost-effective and scalable time-series database and monitoring solution, designed for collecting and analyzing metrics data in distributed systems.
Why this server?
Allows querying VictoriaMetrics metrics from Kubernetes clusters for monitoring and visualization.
Why this server?
Planned direct integration as a Prometheus-compatible backend, allowing the same bounded metrics query and evidence contract as Prometheus without requiring Grafana.
Why this server?
The /metrics endpoint can be scraped by VictoriaMetrics for monitoring purposes.
Why this server?
Provides tools for reading and writing time series data to VictoriaMetrics, including capabilities for querying data over specific time ranges, importing Prometheus format data, and retrieving label information.
Why this server?
Allows querying pipeline metrics and custom PromQL queries against VictoriaMetrics, enabling monitoring of throughput, latency, dead-letter queue rate, and other operational metrics.
Why this server?
Integrates with VictoriaMetrics vmanomaly for health monitoring, model management, configuration generation, alert rule generation, and documentation search.
Why this server?
Provides a comprehensive interface for traces, observability, and debugging tasks related to VictoriaTraces instances, allowing querying, exploring, and analyzing traces data through MCP tools.
Why this server?
Provides access to a VictoriaMetrics monitoring system, enabling querying metrics, exploring data, analyzing alerts/rules, viewing instance parameters, exploring data cardinality, analyzing queries, and debugging relabeling rules and retention configurations.
Why this server?
Provides access to VictoriaLogs instance APIs for querying logs, exploring log data, showing instance parameters, listing available streams/fields/field values, and querying log statistics as metrics.
