VictoriaMetrics
VictoriaMetrics is maintained in the observability catalog as metrics platform with an explicit evidence and lifecycle record.
The current entry and its direct relationships are prominent; every other catalog technology and concept remains visible as muted background context.
23 directly connected nodes · 25 typed relationships · 196 muted catalog entries
List direct catalog relationships
- CatalogObservability Technology
- HierarchyVictoriaMetrics MCP Server
- Hierarchyvmctl
- RelatedPrometheus
- RelatedGrafana
- RelatedOpenTelemetry
- TelemetryMetrics
- TelemetryLogs
- TelemetryDatabase-Telemetry
- TelemetryDeployment-Events (CI/CD)
- ArchitectureHost Observability
- ArchitectureMicroservices Observability
- ArchitectureCloud Observability
- ArchitectureDatabase Observability
- ArchitectureOn-Premise Observability
- ArchitectureLinux
- FunctionAd-Hoc Functions
- FunctionQuerying
- FunctionData Collection
- FunctionTelemetry Storage
- FunctionMetrics Analysis
- FunctionDeployment Automation
- FunctionIntegrations
- RelatedVictoriaMetrics MCP Server
- Relatedvmctl
Catalog position
VictoriaMetrics is maintained by VictoriaMetrics and classified as metrics platform in the telemetry pipeline research cohort [1]. This establishes a stable catalog identity and a canonical starting source; it does not independently validate product outcomes, pricing, availability, or fit.
| Field | Catalog record |
|---|---|
| Entity type | Product |
| Signals | Metrics, Logs |
| Deployment | Self Hosted, Saas |
| License model | open source and commercial |
| Origin | United States / Ukraine |
Shared technology-map evidence
The product family covers six of twelve families across metrics, logs, preview traces, querying, alerting, and recording rules [1], [2]. The cost uses the published $225 monthly managed single-node starting point [2]. The bubble reflects 17,500-plus stars and 1,700-plus forks in the official repository when reviewed [3].
Research stance
Treat this page as a maintainable evidence record, not an endorsement or direct ranking. Challenge the stance when the classification, evidence, or stated limits no longer match current primary evidence.
Technology-map evidence
How this tool is positioned
- Capability coverage
- 50% 6 of 12 families
- Reference cost
- $38per capability / month
- Market breadth
- 80/100 bounded evidence index
- Confidence
- documenteddocumented inputs
Managed single-node starting price; traces remain preview in the reviewed product family.
Axis sources: VictoriaMetrics documentation · VictoriaMetrics Cloud · VictoriaMetrics/VictoriaMetrics
Source record
Bibliography
VictoriaMetrics, “VictoriaMetrics documentation.” [Online]. Available: https://docs.victoriametrics.com/. [Accessed: Aug. 12, 2026].
Canonical first-party or project documentation used for catalog identity and stated scope.Canonical source ↗Return to article ↑VictoriaMetrics, ‘VictoriaMetrics Cloud.’ [Online]. Available: https://victoriametrics.com/products/cloud/. [Accessed: Aug. 14, 2026].
Publishes the managed single-node starting price and included metrics alerting and integration scope.Canonical source ↗Return to article ↑VictoriaMetrics, ‘VictoriaMetrics/VictoriaMetrics.’ GitHub. [Online]. Available: https://github.com/VictoriaMetrics/VictoriaMetrics. [Accessed: Aug. 14, 2026].
Public repository stars forks and activity used as community-breadth signals.Canonical source ↗Return to article ↑VictoriaMetrics, “VictoriaMetrics Enterprise pricing and product website.” [Online]. Available: https://victoriametrics.com/products/enterprise/. [Accessed: Aug. 14, 2026].
Official price-list or product-site reference. Availability: published.Canonical source ↗Return to article ↑VictoriaMetrics, “Official GitHub repository.” GitHub. [Online]. Available: https://github.com/VictoriaMetrics/VictoriaMetrics. [Accessed: Aug. 14, 2026].
VictoriaMetrics, “VictoriaMetrics Cloud Terraform Provider.” Terraform Registry. [Online]. Available: https://registry.terraform.io/providers/VictoriaMetrics/victoriametricscloud/latest. [Accessed: Aug. 20, 2026].
Known limits
Unresolved unknowns
- Current editions, pricing, availability, and independently measured outcomes require dated verification.
Public review
Discuss and correct
Comments are public. Proposed factual corrections must be incorporated into version-controlled research before they are treated as published.
Local preview does not have Giscus configured. Native comments and Giscus are never presented as competing primary systems on the same page.