惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Microsoft Azure Blog
Microsoft Azure Blog
Engineering at Meta
Engineering at Meta
A
About on SuperTechFans
T
The Blog of Author Tim Ferriss
I
InfoQ
博客园_首页
G
Google Developers Blog
爱范儿
爱范儿
Last Week in AI
Last Week in AI
量子位
阮一峰的网络日志
阮一峰的网络日志
雷峰网
雷峰网
酷 壳 – CoolShell
酷 壳 – CoolShell
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
GbyAI
GbyAI
月光博客
月光博客
The GitHub Blog
The GitHub Blog
V
Visual Studio Blog
N
Netflix TechBlog - Medium
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 聂微东

VictoriaMetrics: Simple & Reliable Monitoring for Everyone on VictoriaMetrics

Operator now has Long-Term Support (LTS) version Multi-tiered Observability: A Practical Way to Handle Diverse Workloads VictoriaMetrics April 2026 Ecosystem Updates Not All Telemetry Requires Premium Pricing VictoriaMetrics at KubeCon Amsterdam: Community Highlights What's new in VictoriaMetrics Anomaly Detection (Q1 2026) What's New in VictoriaMetrics Cloud Q1 2026? Logs, MCP Server, Better Alerting, and... a Secret Project VictoriaMetrics at KubeCon: Optimizing Tail Sampling in OpenTelemetry with Retroactive Sampling VictoriaMetrics March 2026 Ecosystem Updates Observability Lessons From OpenAI Benchmarking Kubernetes Log Collectors: vlagent, Vector, Fluent Bit, OpenTelemetry Collector, and more VictoriaMetrics February 2026 Ecosystem Updates VictoriaMetrics at FOSDEM, Cloud Native Days France, and CfgMgmtCamp Ghent VictoriaLogs in VictoriaMetrics Cloud: Fast, Cost-Effective Log Management is Here What’s new in VictoriaMetrics Anomaly Detection (2025) VictoriaMetrics January 2026 Ecosystem Updates VictoriaLogs Basics: What You Need to Know, with Examples & Visuals What's New in VictoriaMetrics Cloud Q4 2025? New tiers, more deployment options, IaC and alerting rules. Vibe coding tools observability with VictoriaMetrics Stack and OpenTelemetry How a US Software Provider Improved Traffic Alerting with VictoriaMetrics Anomaly Detection VictoriaMetrics 2025 Developer Experience: A Year in Review Spotify’s performance & control across large monitoring environments with VictoriaMetrics VictoriaMetrics Achieves Red Hat OpenShift Operator Certification Our latest updates across the VictoriaMetrics Observability ecosystem New Capacity Tiers in VictoriaMetrics Cloud Announcing 1B+ Downloads & Product Development With Logs, Traces, Metrics AI Agents Observability with OpenTelemetry and the VictoriaMetrics Stack Discarding gRPC-Go: The Story Behind OTLP/gRPC Support in VictoriaTraces What's New in VictoriaMetrics Cloud Q3 2025? From new region in Asia to proactive alerts How DreamHost Slashed Memory Usage by 80% and Scaled to 76 Million Time Series
Sensedia & VictoriaMetrics: API-compatible Efficient Storage
2001-01-01 · via VictoriaMetrics: Simple & Reliable Monitoring for Everyone on VictoriaMetrics

“VictoriaMetrics Just Works - and Uses Fewer Hardware Resources Compared to Other Tools!”

Sensedia logo

  • Technology
  • Brazil

Sensedia is a leading integration solutions provider with more than +120 enterprise clients across a range of sectors. Its world-class portfolio includes: an API Management Platform, Adaptive Governance, Events Hub, Service Mesh, Cloud Connectors and Strategic Professional Services teams.

Main Benefits of Using VictoriaMetrics

  • Recommendation icon representing software that just works

    Software That Just Works

  • Documentation icon representing great documentation

    Great Documentation

  • Expert support icon representing community support

    Good Community Support

Challenge

The requirement is that the metrics be stored for 15 days, be scalable and offer high availability of the metrics.

The solution needed to be integrated into Grafana and allow for the use of PromQL when creating/editing dashboards in Grafana to obtain metrics from the Prometheus read_remote API.

The solution also needed to receive data from Prometheus using HTTPS and to request a login and password to write/read the metrics.

Read More From the Sensedia Team Here

Solution

We read the VictoriaMetrics documentation and watched other use cases, including the lecture given by an adidas employee at PromCon 2019 (https://www.youtube.com/watch?v=OsH6gPdxR4s). We presented our first impressions to the Cloud Architects team and together we decided to do a Proof of Concept (PoC) in our testing environment.

We analyzed the performance for one month.

The next step was the implementation of the solution in our production environment days before the start of BlackFriday in 2020 which is the period of highest use of the Sensedia API-Platform by customers in the whole year.

We set a record in the generation of metrics with no instability in the monitoring stack.

Read More From the Sensedia Team Here

Why VictoriaMetrics Was Chosen Over Other Solutions

  • Recommendation icon representing open source software

    Open Source

  • Database icon representing SaaS and on-premise options

    SaaS & On-Premise Offer

  • Documentation icon representing great documentation

    Great Documentation

  • Expert support icon representing Slack community support

    Good Community Support in Slack

  • It is efficient and uses fewer hardware resources compared with other tools
  • Installation supported in Docker containers
  • Helm chart available for installation in Kubernetes cluster
  • Compatible with the Prometheus query syntax so we didn't need to redo our dashboards in Grafana
  • Compatibility with the Prometheus write_remote API
  • Support for TLS encryption when writing and reading metrics
  • Authentication for writing or reading metrics using the vmauth module

Technical Stats

  • Active Time Series

    sum(vm_cache_entries{type="storage/hour_metric_ids"})

    N/A

  • Ingestion Rate

    sum(rate(vm_rows_inserted_total[5m]))

    68.684

  • Total Number of Datapoints

    sum(vm_rows{type=~"storage/.+"})

    112.464.000.000

  • Total Number of Entries in Inverted Index

    sum(rate(vm_rows_inserted_total[5m]))

    1.043.263.000

  • Daily Time Series Churn Rate

    sum(increase(vm_new_timeseries_created_total[24h]))

    3.257.900

  • Data Size on Disk

    sum(vm_data_size_bytes{type=~"storage/.+"})

    82.253.000.000

  • Index Size on Disk

    sum(vm_data_size_bytes{type="indexdb"})

    30.725.800.000

  • Average Datapoint Size on Disk

    sum(vm_data_size_bytes) / sum(vm_rows{type=~"storage/.+"})

    1.00461

  • Range Query Rate

    sum(rate(vm_http_requests_total{path=~".*/api/v1/query_range"}[5m]))

    0.0300

  • Instant Query Rate

    sum(rate(vm_http_requests_total{path=~".*/api/v1/query"}[5m]))

    0

  • Range Query Duration Quantiles

    max(vm_request_duration_seconds{path=~".*/api/v1/query_range"}) by (quantile)

    {quantile="1"} 0.492 {quantile="0.5"} 0.265 {quantile="0.9"} 0.430 {quantile="0.97"} 0.492 {quantile="0.99"} 0.492

  • Instant Query Duration Quantiles

    max(vm_request_duration_seconds{path=~".*/api/v1/query"}) by (quantile)

    N/A