- Blog /
- Q1/2022 Release Roundup: Announcing VictoriaMetrics v1.76 & More
Since the beginning of the year, our team has been busy working with the open source community of VictoriaMetrics users and our customers as we continuously enhance and improve Vicky!
Thanks to everyone who has contributed with their feedback, questions, feature requests, bug reports, etc.
We push out a new release every 3-4 weeks, sometimes more, to make sure that the user community and our customers can benefit as quickly as possible from the new features and improvements that are being requested by users and customers alike.
We publish release notes for each new release on GitHub and will now also be publishing a release roundup blog every quarter that presents a summary of the releases published in the previous three months.
This is our first release roundup blog and the past quarter saw some great additions to VictoriaMetrics, including:
With this release roundup blog post we’re happy to announce the availability of our latest release, VictoriaMetrics v1.76.0.
vminsert
and vmstorage
under high ingestion rate.Read the release notes for all the details on the new v1.76 release: https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.76.0
And see below the summaries of all of our Q1/2022 releases:
indexdb/dataBlocks
, indexdb/indexBlocks
, storage/indexBlocks
. This should reduce the increased memory usage starting from v1.73.0. See this and this issue for more information.-datasource.url
, -notifier.url
and -remoteRead.url
. See the corresponding command-line flags containing oauth2
in their names here.-notifier.url
via -notifier.bearerToken
and -notifier.bearerTokenFile
command-line flags. See this issue.if
filterstorage/tsid
- the cache speeds up lookups of internal metric ids by metric_name{labels...}
during data ingestion. The size for this cache can be tuned with -storage.cacheSizeStorageTSID
command-line flag.indexdb/dataBlocks
- the cache speeds up data lookups in <-storageDataPath>/indexdb
files. The size for this cache can be tuned with -storage.cacheSizeIndexDBDataBlocks
command-line flag.indexdb/indexBlocks
- the cache speeds up index lookups in <-storageDataPath>/indexdb
files. The size for this cache can be tuned with -storage.cacheSizeIndexDBIndexBlocks
command-line flag. See also cache tuning docs. See this issue.-influxDBLabel
command-line flag for overriding db label name for the data imported into VictoriaMetrics via InfluxDB line protocol. Thanks to @johnatannvmd for the pull request.X-Influxdb-Version
HTTP header in responses to InfluxDB write requests. This is needed for some InfluxDB clients. See this comment and this issue.Amongst other things, we’re now publishing VictoriaMetrics binaries for MacOS amd64 & MacOS arm64 (aka MacBook M1) in our release notes.
From this release onwards, performance for arm64 builds of VictoriaMetrics components improved by up to 15%!
Further Highlights include:
indexdb
rotation once per -retentionPeriod
. See this issue.-dropSamplesOnOverload
command-line flag for vminsert
. If this flag is set, then vminsert
drops incoming data if the destination vmstorage
is temporarily unavailable or cannot keep up with the ingestion rate. The number of dropped rows can be monitored via vm_rpc_rows_dropped_on_overload_total
metric at vminsert
.vmstorage
nodes are temporarily unavailable and/or accept data at slower rate than other vmstorage
nodes. Also significantly reduce possible re-routing storm when vminsert
runs with -disableRerouting=false
command-line flag. This should help the following issues: one, two, three, four, five.*_info labels
. For example: kube_pod_created{namespace="prod"} * on (uid) group_left(node) kube_pod_info
now automatically adds the needed filters on uid
label to kube_pod_info
before selecting series for the right side of *
operation. This may save CPU, RAM and disk IO resources. See this article for details on *_info
labels. See this issue.And as reminder, some feature highlights from release v1.71.0:
This sums up our release roundup for the beginning of 2022!
You can find all our release notes here: https://github.com/VictoriaMetrics/VictoriaMetrics/releases
If you need support, please visit our support page: https://victoriametrics.com/support/
And if you’re interested in finding out more about our Enterprise offering, please visit: https://victoriametrics.com/products/enterprise/
The OpenTelemetry Astronomy Shop demo has long served as a reference environment for exploring observability in distributed systems, but until now it shipped with only a Prometheus datasource. VictoriaMetrics forked the demo and extended it with VictoriaMetrics, VictoriaLogs, and VictoriaTraces, providing insights into VictoriaMetrics’ observability stack where metrics, logs, and traces flow into a unified backend.
Proper alerting is an art. It is all about foreseeing bad scenarios before they happen, so you can prepare for them. In this article, we go through practical recommendations of approaching the alerting to reduce alerting fatigue and avoid false positives.
Tech Talk: In this post, we explore vmanomaly through the eyes of its creators. Learn how this AI-powered alerting system helps cut through noise, avoid static rule spaghetti, and deliver actionable insights directly from your monitoring data.
VictoriaLogs uses three core concepts: message, time, and stream fields to structure log data. Too few streams create fat streams that are slow to query, while too many unique stream combinations create high cardinality problems…