mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-30 15:50:07 +01:00
ee1da35071
Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
14 KiB
14 KiB
sort | weight | title | menu | aliases | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
17 | 17 | Articles |
|
|
Articles
See also case studies.
Third-party articles and slides about VictoriaMetrics
- The (Almost) Infinitely Scalable Open Source Monitoring Dream
- Monitoring at scale with Victoria Metrics
- Optimizing Linkerd metrics in Prometheus
- Optimizing the Storage of Large Volumes of Metrics for a Long Time in VictoriaMetrics
- How do We Keep Metrics for a Long Time in VictoriaMetrics
- Announcing Asserts
- Choosing a Time Series Database for High Cardinality Aggregations
- Scaling to trillions of metric data points
- VictoriaMetrics vs. OpenTSDB
- Monitoring of multiple OpenShift clusters with VictoriaMetrics
- Fly's Prometheus Metrics
- Ultra Monitoring with Victoria Metrics
- Infrastructure monitoring with Prometheus at Zerodha
- Sismology: Iguana Solutions’ Monitoring System
- Prometheus High Availability and Fault Tolerance strategy, long term storage with VictoriaMetrics
- Monitoring with Prometheus, Grafana, AlertManager and VictoriaMetrics
- How we improved our Kubernetes monitoring at Smarkets, and how you could too
- Kubernetes and VictoriaMetrics in Mist v4.6
- Foiled by the Firewall: A Tale of Transition From Prometheus to VictoriaMetrics
- Observations on Better Resource Usage with Percona Monitoring and Management v2.12.0
- Better Prometheus rate() function with VictoriaMetrics
- Percona monitoring and management migration from Prometheus to VictoriaMetrics FAQ
- Compiling a Percona Monitoring and Management v2 Client in ARM: Raspberry Pi 3 Reprise
- Making peace with Prometheus rate()
- Monitoring K8S with VictoriaMetrics
- CMS monitoring R&D: Real-time monitoring and alerts
- The CMS monitoring infrastructure and applications
- Disk usage: VictoriaMetrics vs Prometheus
- Benchmarking time series workloads on Apache Kudu using TSBS
- What are Open Source Time Series Databases?
- Evaluating performance and correctness
- Running VictoriaMetrics on Raspberry PI
- Calculating the Error of Quantile Estimation with Histograms
- Monitoring private clouds with VictoriaMetrics at LeroyMerlin
- Monitoring Kubernetes with VictoriaMetrics+Prometheus
- High-performance Graphite storage solution on top of VictoriaMetrics
- Cloud Native Model Driven Telemetry Stack on OpenShift
- Observability, Availability & DORA’s Research Program
- Tame Kubernetes Costs with Percona Monitoring and Management and Prometheus Operator
- Prometheus VictoriaMetrics On AWS ECS
- API Monitoring With Prometheus, Grafana, AlertManager and VictoriaMetrics
- Solving Metrics at scale with VictoriaMetrics
- Monitoring Kubernetes clusters with VictoriaMetrics and Grafana
- Multi-tenancy monitoring system for Kubernetes cluster using VictoriaMetrics and operators
- Monitoring as Code на базе VictoriaMetrics и Grafana
- Push Prometheus metrics to VictoriaMetrics or other exporters
- Install and configure VictoriaMetrics on Debian
- Superset BI with Victoria Metrics
- VictoriaMetrics Source Code Analysis - Bloom filter
- How we tried using VictoriaMetrics and Thanos at the same time
- Prometheus, Grafana, and Kubernetes, Oh My!
- Explaining modern server monitoring stacks for self-hosting
- Brewblox: InfluxDB to Victoria Metrics
- VictoriaMetrics static scraper
- VictoriaMetrics and Open Cosmos boldly takes edge computing to the edge of space
- Evaluating Backend Options For Prometheus Metrics
Our articles
Announcements
- Open-source strategy at VictoriaMetrics
- Open-sourcing VictoriaMetrics
- VictoriaMetrics — creating the best remote storage for Prometheus
- Anomaly Detection in VictoriaMetrics
Benchmarks
- Grafana Mimir and VictoriaMetrics: performance tests
- When size matters — benchmarking VictoriaMetrics vs Timescale and InfluxDB
- High-cardinality TSDB benchmarks: VictoriaMetrics vs TimescaleDB vs InfluxDB
- Insert benchmarks with inch: InfluxDB vs VictoriaMetrics
- Measuring vertical scalability for time series databases in Google Cloud
- Billy: how VictoriaMetrics deals with more than 500 billion rows
- First look at performance comparison between InfluxDB IOx and VictoriaMetrics
- Prometheus vs VictoriaMetrics benchmark on node-exporter metrics
- Promscale vs VictoriaMetrics: resource usage on production workload
Technical articles
- How VictoriaMetrics makes instant snapshots for multi-terabyte time series data
- WAL Usage Looks Broken in Modern TSDBs
- mmap may slow down your Go app
- VictoriaMetrics: achieving better compression than Gorilla for time series data
- Stripping dependency bloat in VictoriaMetrics Docker image
- Speeding up backups for big time series databases
- Improving histogram usability for Prometheus and Grafana
- Why irate from Prometheus doesn't capture spikes
- VictoriaMetrics: PromQL compliance
Tutorials, guides and how-to articles
- Monitoring VictoriaMetrics
- PromQL tutorial for beginners and humans
- How to optimize PromQL and MetricsQL queries
- Analyzing Prometheus data with external tools
- Prometheus Subqueries in VictoriaMetrics
- How to migrate data from Prometheus to VictoriaMetrics
- VictoriaMetrics: how to migrate data from Prometheus. Filtering and modifying time series.
- How to use relabeling in Prometheus and VictoriaMetrics
- How to monitor Go applications with VictoriaMetrics
- Prometheus storage: tech terms for humans
- Cardinality explorer
- Rules backfilling via vmalert
Other articles
- How ClickHouse inspired us to build a high performance time series database. See also slides
- OSA Con 2022: Specifics of data analysis in Time Series Databases
- OSMC 2022. VictoriaMetrics: scaling to 100 million metrics per second. See also slides
- CNCF Paris Meetup 2022-09-15 - VictoriaMetrics - The cost of scale in Prometheus ecosystem. See also slides
- VictoriaMetrics Meetup December 2022. See also slides for "VictoriaMetrics 2022: new features" talk.
- Comparing Thanos to VictoriaMetrics cluster
- Evaluation performance and correctness: VictoriaMetrics response