v1.102.0

Released at 2024-07-17

Update note 1: support for snap packages was removed due to lack of interest from community. See this pull request for details. Please read about supported package types here.

Update note 2: stream aggregation config now prevents setting multiple identical outputs. For example, outputs: [total, total] will fail the validation phase. In addition, outputs: ["quantiles(0.5)", "quantiles(0.9)"] will fail the validation as well - use outputs: ["quantiles(0.5, 0.9)"] instead.

• SECURITY: upgrade Go builder from Go1.22.4 to Go1.22.5. See the list of issues addressed in Go1.22.5.

• SECURITY: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1. See alpine 3.20.1 release notes.

• FEATURE: streaming aggregation: expose the following metrics at /metrics page of vmagent and single-node VictoriaMetrics:

  • vm_streamaggr_matched_samples_total - the number of input samples matched by the corresponding aggregation rule
  • vm_streamaggr_output_samples_total - the number of output samples produced by the corresponding aggregation rule
  • vm_streamaggr_samples_lag_seconds - histogram with the lag between the current time and the timestamp seen in the aggregated input samples

• FEATURE: steaming aggregation: add new labels to vm_streamaggr_* metrics:

  • name - the name of the streaming aggregation rule, which can be configured via name option - see these docs.
  • url - -remoteWrite.url for the corresponding -remoteWrite.streamAggr.config
  • path - path to the corresponding streaming aggregation config file
  • position - the position of the aggregation rule in the corresponding streaming aggregation config file

• FEATURE: streaming aggregation: prevent having duplicated aggregation function as outputs in one aggregation config. It also prevents using outputs: ["quantiles(0.5)", "quantiles(0.9)"] instead of outputs: ["quantiles(0.5, 0.9)"], as the former has higher computation cost for producing the same result.

• FEATURE: vmagent and Single-node VictoriaMetrics: add -graphite.sanitizeMetricName command-line flag for sanitizing metrics ingested via Graphite protocol. See this issue.

• FEATURE: vmagent: yandexcloud_sd_configs: add support for obtaining IAM token in GCE format additionally to the deprecated Amazon EC2 IMDSv1 format. See this issue.

• FEATURE: vmalert: make -replay.timeTo optional in replay mode. When omitted, the current timestamp will be used. See this issue.

• FEATURE: vmauth: reduce CPU usage when proxying data ingestion requests.

• FEATURE: vmauth: allow disabling request body caching with -maxRequestBodySizeToRetry=0. See this issue. Thanks to @shichanglin5 for the pull request.

• FEATURE: vmauth: allow overriding Host header with backend host before sending the request to the configured backend. See these docs and this issue.

• FEATURE: VictoriaMetrics cluster: do not retry RPC calls to vmstorage nodes if complexity limits were exceeded.

• FEATURE: vmbackup and vmrestore: add support for Azure Managed Identity and default credentials lookup. See these docs and this issue for the details. Thanks to @justinrush for the pull request.

• FEATURE: vmbackup and vmrestore: allow overriding Azure storage domain when performing backups via AZURE_STORAGE_DOMAIN environment variable. See these docs and this issue. Thanks to @justinrush for the pull request.

• FEATURE: vmui: show compacted result in the JSON tab for query results. See this issue.

• FEATURE: dashboards: add Grafana dashboard and alerting rules for vmauth dashboard. See this issue for details.

• FEATURE: vmagent dashboard: stream aggregation section: add graphs based on newly exposed streaming aggregation metrics.

• BUGFIX: MetricsQL: properly calculate histogram_quantile over Prometheus buckets with inconsistent values. See this comment and this pull request. Updates this issue.

• BUGFIX: vmagent: fix panic when using multiple topics with the same name when ingesting metrics from Kafka. See this issue for the details.

• BUGFIX: vmalert: fix incorrect redirection in WebUI of vmalert. See this issue and this pull request.

• BUGFIX: vmgateway: properly apply read and write based rate limits. See this issue for details.

• BUGFIX: vmbackupmanager: fix vm_backup_last_run_failed metric not being properly initialized during startup. Previously, it could imply an error even if the backup have been completed successfully. See this issue for the details.

• BUGFIX: vmui: fix input cursor position reset in modal settings. See this pull request.

• BUGFIX: docker-compose: fix incorrect link to vmui from VictoriaMetrics plugin in Grafana.

This release also includes changes from v1.102.0-rc1 and v1.102.0-rc2 releases.

See all the changes at the CHANGELOG.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

• vmagent
• vmalert
• [vmalert-tool](https://docs.vict...

v1.97.6

Released at 2024-07-17

v1.97.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise.
All these fixes are also included in the latest community release.
The v1.97.x line will be supported for at least 12 months since v1.97.0 release

• SECURITY: upgrade Go builder from Go1.22.4 to Go1.22.5. See the list of issues addressed in Go1.22.5.

• SECURITY: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1. See alpine 3.20.1 release notes.

• BUGFIX: vmagent: fix panic when using multiple topics with the same name when ingesting metrics from Kafka. See this issue for the details.

• BUGFIX: all VictoriaMetrics components: properly calculate process_resident_memory_bytes metric for OS with non-default value of memory page size. See this issue for details.

• BUGFIX: vmalert: fix path for system links printed on default vmalert's UI page when -http.pathPrefix is set.

• BUGFIX: vmbackup: properly configure authentication with S3 when -configFilePath cmd-line flag is specified.

• BUGFIX: vmalert enterprise: properly configure authentication with S3 when -s3.configFilePath cmd-line flag is specified for reading rule configs.

• BUGFIX: vmalert: properly specify oauth2 ClientSecret when configuring authentication for notifier.url. See this issue for details. Thanks to @yincongcyincong for the pull request.

• BUGFIX: vmalert: fix incorrect redirection in WebUI of vmalert. See this issue and this pull request.

• BUGFIX: Single-node VictoriaMetrics and vmstorage in VictoriaMetrics cluster: add validation for the max value specified for -retentionPeriod. See this issue for details.

• BUGFIX: vmui: copy row button in Table view produces unexpected result. See this issue and pull request.

• BUGFIX: vmalert-tool: prevent hanging when processing groups without rules. See this issue.

• BUGFIX: vmui: fix input cursor position reset in modal settings. See this pull request.

• BUGFIX: MetricsQL: properly calculate histogram_quantile over Prometheus buckets with inconsistent values. See this comment and this pull request. Updates this issue.

v1.93.16

Released at 2024-07-17

v1.93.x is a line of LTS releases. It contains important up-to-date bugfixes.
The v1.93.x line will be supported for at least 12 months since v1.93.0 release

• SECURITY: upgrade Go builder from Go1.22.4 to Go1.22.5. See the list of issues addressed in Go1.22.5.

• SECURITY: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1. See alpine 3.20.1 release notes.

• BUGFIX: vmbackup: properly configure authentication with S3 when -configFilePath cmd-line flag is specified.

• BUGFIX: vmalert: fix path for system links printed on default vmalert's UI page when -http.pathPrefix is set.

• BUGFIX: vmalert: fix incorrect redirection in WebUI of vmalert. See this issue and this pull request.

• BUGFIX: vmalert enterprise: properly configure authentication with S3 when -s3.configFilePath cmd-line flag is specified for reading rule configs.

• BUGFIX: vmalert: properly specify oauth2 ClientSecret when configuring authentication for notifier.url. See this issue for details. Thanks to @yincongcyincong for the pull request.

• BUGFIX: vmui: copy row button in Table view produces unexpected result. See this issue and pull request.

• BUGFIX: MetricsQL: properly calculate histogram_quantile over Prometheus buckets with inconsistent values. See this comment and this pull request. Updates this issue.

v0.28.0-victorialogs

Released at 2024-07-10

• FEATURE: web UI: show a spinner on top of bar chart until user's request is finished. See this issue.
• FEATURE: web UI: use compact representation of JSON lines at JSON tab if only a single log field is queried. See this feature request.
• FEATURE: web UI: properly show the number of matching logs on the selected time range at bar chart for queries with arbitrary pipes, including stats pipe and top pipe.

v0.27.1-victorialogs

Released at 2024-07-05

• BUGFIX: properly JSON-encode strings with special chars in HTTP querying API responses. This fixes the error decode response: invalid character 'x' in string escape code error in VictoriaLogs datasource for Grafana. See this issue. The issue has been introduced in the release v0.9.0.

v0.27.0-victorialogs

Released at 2024-07-02

• FEATURE: add -syslog.useLocalTimestamp.tcp and -syslog.useLocalTimestamp.udp command-line flags, which could be used for using the local timestamp as _time field for the logs ingested via the corresponding -syslog.listenAddr.tcp / -syslog.listenAddr.udp. By default the timestap from the syslog message is used as _time field. See these docs.

• BUGFIX: make slowly ingested logs visible for search as soon as they are ingested into VictoriaLogs. Previously slowly ingested logs could remain invisible for search for long time.

v0.26.1-victorialogs

Released at 2024-07-01

• BUGFIX: return the proper surrounding logs for stream_context pipe when additional pipes are put after the stream_context pipe. This has been broken in v0.26.0.

v0.26.0-victorialogs

Released at 2024-07-01

• FEATURE: add ability to return log position (aka rank) after sorting logs with sort pipe. This can be done by adding rank as <fieldName> to the end of | sort ... pipe. For example, _time:5m | sort by (_time) rank as position instructs storing position of every sorted log line into position field name.
• FEATURE: add delimiter log with --- message between log chunks returned by stream_context pipe. This should simplify investigation of the returned logs.
• FEATURE: reduce memory usage when big number of context logs are requested from stream_context pipe.

v0.25.0-victorialogs

Released at 2024-06-28

• FEATURE: add ability to select surrounding logs in front and after the selected logs via stream_context pipe. This functionality may be useful for investigating stacktraces panics or some correlated log messages.

• FEATURE: add ability to return top N "fields" groups from /select/logsql/hits HTTP endpoint, by specifying fields_limit=N query arg. This query arg is going to be used in this feature request.

• BUGFIX: fix runtime error: index out of range [0] with length 0 panic when empty lines are ingested via Syslog format by Cisco controllers. See this issue.

v0.24.0-victorialogs

Released at 2024-06-27

• FEATURE: add /select/logsql/tail HTTP endpoint, which can be used for live tailing of LogsQL query results. See these docs for details.

• FEATURE: add /select/logsql/stream_ids HTTP endpoint, which can be used for returning _stream_id values with the number of hits for the given LogsQL query. See these docs for details.

• FEATURE: add -retention.maxDiskSpaceUsageBytes command-line flag, which allows limiting disk space usage for VictoriaLogs data by automatic dropping the oldest per-day partitions if the storage disk space usage becomes bigger than the -retention.maxDiskSpaceUsageBytes. See these docs.

• BUGFIX: properly take into account query timeout specified via -search.maxQueryDuration command-line flag and/or via timeout query arg. Previously these timeouts could be ingored during query execution.

• BUGFIX: web UI: fix the update of the relative time range when Execute Query is clicked. See this issue.