Tagged articles
VictoriaMetrics
39 articles · Page 1 of 1
This article compares Thanos and VictoriaMetrics for Prometheus high availability, covering architecture differences, deployment steps, configuration details, compression ratios, query capabilities, cost models, migration paths, troubleshooting, and operational best practices to help teams choose the right solution based on scale, retention needs, and team capacity.
High AvailabilityKubernetesObservability
0 likes · 64 min read

The article explains how a single‑machine Prometheus TSDB initially works well but eventually hits five scalability walls—capacity, single‑point failure, short retention, lack of global view, and throughput limits—and then details the step‑by‑step evolution to remote_write with object‑storage‑backed Thanos and finally to native distributed TSDBs such as Cortex, Mimir, and VictoriaMetrics, including their trade‑offs, costs, and practical selection guidance.
CortexPrometheusTSDB
0 likes · 21 min read

This article walks through the challenges of scaling Prometheus storage, compares Thanos, Cortex, and VictoriaMetrics, and provides a complete step‑by‑step guide—including hardware requirements, configuration, deployment, tuning, multi‑tenant setup, and troubleshooting—to replace Prometheus local TSDB with VictoriaMetrics for long‑term, high‑performance monitoring.
PrometheusVictoriaMetricsdeployment
0 likes · 43 min read

This guide walks through the complete Prometheus monitoring lifecycle—from binary, Docker, and Kubernetes deployments to Ansible‑driven node_exporter rollout, SNMP switch and router monitoring, alert routing via WeChat, SMS and email, production‑grade tuning, high‑availability designs, and systematic troubleshooting.
AlertmanagerAnsibleKubernetes
0 likes · 25 min read

This guide explains why Prometheus’s local TSDB struggles at scale, compares alternative remote‑storage solutions, and provides a step‑by‑step walkthrough for deploying VictoriaMetrics (single‑node or clustered), configuring remote_write, tuning performance, handling multi‑tenant use cases, and troubleshooting common issues.
PrometheusTSDBVictoriaMetrics
0 likes · 42 min read

This article explains the scalability limits of Prometheus, introduces vmagent as a lightweight, high‑performance collector compatible with Prometheus, and provides a step‑by‑step guide—including configuration, systemd service setup, and verification—to deploy a resilient vmagent cluster in production.
PrometheusVictoriaMetricscloud-native
0 likes · 5 min read

This guide walks you through deploying a fault‑tolerant, scalable VictoriaMetrics monitoring cluster on bare‑metal or virtual machines, covering architecture, component setup, systemd services, HAProxy load balancing, and verification steps for a production‑grade observability solution.
HAProxyHigh AvailabilityObservability
0 likes · 8 min read

This article outlines practical strategies for protecting VictoriaMetrics storage under bursty metric traffic, covering communication with business teams, splitting deployments, choosing single‑node versus cluster setups, key monitoring metrics, separate storage for self‑monitoring, the VMUI Explore UI, and techniques for discarding high‑cardinality metrics.
MetricsStorageVictoriaMetrics
0 likes · 10 min read

VictoriaMetrics employs a modular, horizontally scalable architecture composed of vmagent, vminsert, vmstorage, vmselect, and vmalert, each handling data collection, ingestion, storage, querying, and alerting, while leveraging consistent hashing, LSM‑tree storage, TSID indexing, and multi‑tenant isolation to efficiently manage large‑scale time‑series workloads.
VictoriaMetricsquery optimizationscalable storage
0 likes · 11 min read

KubeDoor 1.0 introduces a new architecture for unified multi‑Kubernetes monitoring, offering components for master and agent, flexible deployment options, Helm‑based installation, configurable storage and alerting settings, and detailed guidance on integrating with existing Prometheus/VictoriaMetrics setups while providing automatic peak‑usage data collection.
ClickHouseHelmKubernetes
0 likes · 14 min read

This article details the end‑to‑end migration from Thanos to VictoriaMetrics, covering background analysis, architectural comparison, a phased migration plan, encountered configuration and performance issues, resolution strategies, and the resulting performance, cost, and scalability improvements for the monitoring system.
ThanosTime SeriesVictoriaMetrics
0 likes · 16 min read

This article compares Thanos and VictoriaMetrics as long‑term storage solutions for Prometheus, evaluating their architecture, write and read paths, reliability, consistency, performance, scalability, high‑availability, and hosting costs to help you choose the most suitable option for your monitoring stack.
Cost ComparisonLong‑term StorageThanos
0 likes · 18 min read

Bilibili rebuilt its monitoring platform to handle explosive metric growth by separating collection, storage, and compute, adopting VictoriaMetrics, zone‑based scheduling, and Flink‑driven pre‑aggregation, which together improved stability, query performance, cloud data quality, and overall observability.
FlinkObservabilityPrometheus
0 likes · 31 min read

The article details Bilibili's evolution of its monitoring platform, describing the stability and performance challenges of a Prometheus‑Thanos stack, the redesign using VictoriaMetrics, collection‑storage separation, unit‑level disaster recovery, query‑tree auto‑replacement, Flink‑based pre‑aggregation, Grafana upgrades, and future roadmap for observability.
FlinkMetricsObservability
0 likes · 30 min read

This article examines the migration from Thanos to VictoriaMetrics for large‑scale metric storage, detailing background challenges, VictoriaMetrics architecture and storage engine, data write and read processes, and a comparative analysis of performance, scalability, and operational costs between the two systems.
ObservabilityThanosVictoriaMetrics
0 likes · 15 min read


ITPUBAug 11, 2024 · Operations
This article details how Bilibili redesigned its monitoring system to overcome explosive metric growth by separating collection and storage, adopting VictoriaMetrics, implementing zone‑based scheduling, automating PromQL query replacement, and using Flink for efficient pre‑aggregation, resulting in dramatically lower latency and higher stability.
FlinkObservabilityPromQL
0 likes · 31 min read

The new Monitoring 2.0 architecture separates collection, compute and storage, adopts VictoriaMetrics for compact time‑series storage and a zone‑based scheduler, introduces push‑based ingestion, uses Flink for real‑time pre‑aggregation and automatic PromQL rewrite, delivering ten‑fold query speedups, sub‑300 ms p90 latency, and dramatically higher write and query throughput.
FlinkMetricsObservability
0 likes · 29 min read

This article compares Thanos and VictoriaMetrics as Prometheus long‑term storage solutions, evaluating their architectures, write and read paths, reliability, data consistency, performance, scalability, high‑availability, and cost to help you choose the best fit for your monitoring stack.
ThanosVictoriaMetricscloud
0 likes · 17 min read

The article explains how Helm simplifies deploying complex Kubernetes applications with a single YAML chart but cannot manage runtime operations, while Kubernetes Operators—built on custom resource definitions and webhook logic—automate tasks such as scaling, upgrades, and side‑car injection, offering higher‑level lifecycle management.
Application DeploymentCRDHelm
0 likes · 9 min read

This guide explains the architecture of VictoriaMetrics, details a step‑by‑step Helm deployment on a Kubernetes cluster, covers data collection from multiple clusters, storage persistence, Grafana dashboard setup, and alerting configuration using vmalert and webhook integration.
GrafanaHelmKubernetes
0 likes · 9 min read

Cloud Music’s middleware team built the Pylon APM monitoring system on VictoriaMetrics, combining exporters, vmagent, Nacos, Flink‑based pre‑aggregation recording rules and vminsert for collection with Grafana, a custom Proxy and vmselect for querying, achieving millisecond‑level latency, metric‑trace correlation, stability improvements, and cost‑effective storage for nearly 700 million active time series.
APM monitoringFlinkMetric Pre-aggregation
0 likes · 12 min read

This article details the complete redesign of our internal APM system, covering the motivations, architecture choices, metric collection pipeline, integration of VictoriaMetrics and VMAlert, metric and alert design principles, implementation steps, visualizations, performance gains, and future plans for scaling and SaaS‑ification.
APMMetricsObservability
0 likes · 17 min read

Xiaohongshu’s observability team rebuilt its Prometheus‑based metrics platform using vmagent, dual‑active HA clusters, query push‑down, high‑cardinality governance and multi‑cloud active‑active design, delivering ten‑fold collection speed, up to 70× query capacity, massive CPU‑memory‑storage savings and fully automated scaling.
MetricsTime SeriesVictoriaMetrics
0 likes · 35 min read

Facing exponential growth of time‑series data from 2017 to 2023, Didi migrated from InfluxDB to RRDtool, then to an in‑memory cache layer, and finally adopted VictoriaMetrics because its low‑cost commodity‑hardware operation, high write throughput, strong compression, and easy horizontal scaling solved the earlier storage, OOM, and scalability problems.
ObservabilityTSDBVictoriaMetrics
0 likes · 13 min read

This article details how Vivo's container platform faced exploding metric volumes, component overload, data gaps, and storage spikes, and explains the step‑by‑step architectural redesign, metric governance, performance tuning, cAdvisor redeployment, and VictoriaMetrics upgrade that restored high‑availability, low‑latency monitoring across a large Kubernetes fleet.
KubernetesObservabilityPrometheus
0 likes · 18 min read

The vivo Internet Container Team built a scalable, high‑availability container monitoring platform by deploying dual‑replica Prometheus clusters with a custom HA adapter, remoteWrite to VictoriaMetrics, and a Kafka forwarder, while cutting metric cardinality, tuning cAdvisor, and upgrading VictoriaMetrics to eliminate data loss and storage spikes, achieving stable, efficient monitoring.
KubernetesMetrics OptimizationPrometheus
0 likes · 16 min read

This article details Qunar's migration from Prometheus to VictoriaMetrics for large‑scale container monitoring, covering the shortcomings of Prometheus at massive data volumes, the architectural choices made, performance improvements achieved, and future optimization plans.
KubernetesPrometheusTime Series
0 likes · 13 min read


ITPUBDec 4, 2022 · Cloud Native
This article details Qunar's migration from a Prometheus‑based monitoring stack to VictoriaMetrics, describing the limitations they faced, the architectural redesign using vmagent, vmcluster, and vmalert, and the resulting performance improvements and operational benefits for large‑scale Kubernetes environments.
KubernetesPrometheusVictoriaMetrics
0 likes · 14 min read

This article details Qunar’s migration from a traditional Prometheus‑based monitoring stack to VictoriaMetrics, describing the challenges of large‑scale container metrics collection, the architectural redesign using VM‑Cluster, vmagent, and vmalert, and the performance improvements achieved after full replacement.
KubernetesPrometheusVictoriaMetrics
0 likes · 14 min read

Ctrip’s internal Dashboard monitoring platform, originally built on HBase, was redesigned by migrating its core writer and storage components to a hybrid VictoriaMetrics‑ClickHouse solution, delivering faster queries, higher write stability, and full Prometheus compatibility while keeping the user experience unchanged.
ClickHouseDashboardHBase
0 likes · 13 min read

This article presents a step‑by‑step solution for consolidating TiDB multi‑cluster monitoring by deploying Consul for service registration, configuring Prometheus to discover services via Consul, and optionally replacing Prometheus with VictoriaMetrics to achieve unified dashboards, scalable data collection, and easier health inspection across dozens or hundreds of instances.
GrafanaPrometheusTiDB
0 likes · 10 min read

This article details the evolution of NetEase's self‑built time‑series database EyesTSDB into a cloud‑native, second‑level monitoring solution, covering its architecture, core features, integration with VictoriaMetrics, custom plugin workflow, CMDB linkage, real‑world use cases, and future challenges.
CMDB integrationMetricsObservability
0 likes · 21 min read


ITPUBAug 29, 2022 · Backend Development
This article details Ctrip's internal Dashboard monitoring platform, explains why its HBase‑based TSDB became a bottleneck, and describes the step‑by‑step migration to a hybrid VictoriaMetrics‑ClickHouse solution with upgraded writers, unified query APIs, performance gains, and future roadmap.
ClickHouseHBaseMetrics
0 likes · 13 min read

This article details the redesign of Ctrip's internal Dashboard monitoring system, explaining why the original HBase‑based TSDB was replaced, the new architecture using VictoriaMetrics and ClickHouse, component upgrades, unified query layer, performance gains, and future roadmap for metrics handling.
ClickHouseHBaseMetrics
0 likes · 12 min read

This article describes Vivo's practical experience building a cloud‑native monitoring system for large‑scale container clusters, covering the shortcomings of traditional monitoring, the Prometheus‑centric ecosystem, high‑availability architecture, challenges faced, and future directions such as automation and AI‑driven operations.
ObservabilityPrometheusVictoriaMetrics
0 likes · 13 min read

Vivo’s cloud‑native monitoring solution combines high‑availability Prometheus clusters, VictoriaMetrics storage, Grafana visualization, and a custom leader‑election adapter to deduplicate data while forwarding metrics to Kafka and OLAP systems, addressing large‑scale performance, scalability, and integration challenges and paving the way for AI‑driven AIOps.
Cloud Native MonitoringHigh AvailabilityKubernetes
0 likes · 18 min read

This guide walks through using vmbackup to create snapshots, perform incremental and full backups to various storage backends, and restore data with vmrestore, including command examples, troubleshooting tips, and best practices for VictoriaMetrics data protection.
RestoreTimeSeriesDBVictoriaMetrics
0 likes · 14 min read

This guide explains what vmagent is, its key features, and provides step‑by‑step instructions to install, configure, and verify vmagent on a Kubernetes cluster, including namespace and RBAC setup, custom scrape configs, monitoring endpoints, and troubleshooting tips.
KubernetesMetricsVictoriaMetrics
0 likes · 15 min read

This article introduces VictoriaMetrics, a fast and cost‑effective time‑series monitoring solution that can replace Prometheus, covering its definition, key features, core components, and essential installation considerations for both binary and Kubernetes deployments.
MetricsPrometheus alternativeVictoriaMetrics
0 likes · 6 min read
