37 KiB
sort | weight | title | menu | aliases | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
100 | 100 | CHANGELOG |
|
|
CHANGELOG
The following tip
changes can be tested by building VictoriaMetrics components from the latest commits according to the following docs:
- How to build single-node VictoriaMetrics
- How to build cluster version of VictoriaMetrics
- How to build vmagent
- How to build vmalert
- How to build vmauth
- How to build vmctl
Metrics of the latest version of VictoriaMetrics cluster are available for viewing at our sandbox. The sandbox cluster installation is running under the constant load generated by prometheus-benchmark and used for testing latest releases.
tip
-
SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See the list of issues addressed in Go1.21.6.
-
FEATURE: vmagent: add support for Service Discovery of the Hetzner Cloud and Hetzner Robot API targets. this feature request.
-
FEATURE: graphite: add support for negative index in
groupByNode
andaliasByNode
functions. Thanks to @rbizos for the pull request. -
FEATURE: vmagent: add support for DataDog v2 data ingestion protocol. See these docs and this feature request.
-
FEATURE: vmagent: expose ability to set OAuth2 endpoint parameters per each
-remoteWrite.url
via the command-line flag-remoteWrite.oauth2.endpointParams
. See these docs. Thanks to @mhill-holoplot for the pull request. -
FEATURE: vmalert: expose ability to set OAuth2 endpoint parameters via the following command-line flags:
-datasource.oauth2.endpointParams
for-datasource.url
-notifier.oauth2.endpointParams
for-notifier.url
-remoteRead.oauth2.endpointParams
for-remoteRead.url
-remoteWrite.oauth2.endpointParams
for-remoteWrite.url
-
FEATURE: vmauth: add ability to proxy incoming requests to different backends based on the requested host via
src_hosts
option aturl_map
. See these docs. -
FEATURE: vmctl: rename cmd-line flag
vm-native-disable-retries
tovm-native-disable-per-metric-migration
to better reflect its meaning. -
FEATURE: all VictoriaMetrics components: add ability to specify arbitrary HTTP headers to send with every request to
-pushmetrics.url
. Seepush metrics
docs. -
FEATURE: all VictoriaMetrics components: add
-metrics.exposeMetadata
command-line flag, which allows displayingTYPE
andHELP
metadata at/metrics
page exposed at-httpListenAddr
. This may be needed when the/metrics
page is scraped by collector, which requires theTYPE
andHELP
metadata such as Google Cloud Managed Prometheus. -
FEATURE: dashboards/cluster: add panels for detailed visualization of traffic usage between vmstorage, vminsert, vmselect components and their clients. New panels are available in the rows dedicated to specific components.
-
FEATURE: dashboards/cluster: update "Slow Queries" panel to show percentage of the slow queries to the total number of read queries served by vmselect. The percentage value should make it more clear for users whether there is a service degradation.
-
FEATURE: dashboards/single: change dashboard title from
VictoriaMetrics
toVictoriaMetrics - single-node
. The new title should provide better understanding of this dashboard purpose. -
FEATURE vmctl: add
-vm-native-src-insecure-skip-verify
and-vm-native-dst-insecure-skip-verify
command-line flags for native protocol. It can be used for skipping TLS certificate verification when connecting to the source or destination addresses. -
FEATURE: Alerting rules for VictoriaMetrics: add
job
label toDiskRunsOutOfSpace
alerting rule, so it is easier to understand to which installation the triggered instance belongs. -
BUGFIX: VictoriaMetrics cluster: properly return full results when
-search.skipSlowReplicas
command-line flag is passed tovmselect
and when vmstorage groups are in use. Previously partial results could be returned in this case. -
BUGFIX:
vminsert
: properly accept samples via OpenTelemetry data ingestion protocol when these samples have no resource attributes. Previously such samples were silently skipped. -
BUGFIX:
vmstorage
: added missing-inmemoryDataFlushInterval
command-line flag, which was missing in VictoriaMetrics cluster after implementing this feature in v1.85.0. -
BUGFIX:
vmstorage
: properly expirestorage/prefetchedMetricIDs
cache. Previously this cache was never expired, so it could grow big under high churn rate. This could result in increasing CPU load over time. -
BUGFIX: vmalert: check
-external.url
schema when starting vmalert, must behttp
orhttps
. Before, alertmanager could reject alert notifications if-external.url
contained no or wrong schema. -
BUGFIX: vmalert: automatically add
exported_
prefix for original evaluation result label if it's conflicted with external or reserved one, previously it was overridden. See this issue. -
BUGFIX: MetricsQL: consistently sort results for
q1 or q2
query, so they do not change colors with each refresh in Grafana. See this issue. -
BUGFIX: MetricsQL: properly return results from bottomk and
bottomk_*()
functions when some of these results contain NaN values. See this issue. Thanks to @xiaozongyang for the fix. -
BUGFIX: MetricsQL: properly handle queries, which wrap rollup functions with multiple arguments without explicitly specified lookbehind window in square brackets into aggregate functions. For example,
sum(quantile_over_time(0.5, process_resident_memory_bytes))
was resulting toexpecting at least 2 args to ...; got 1 args
error. Thanks to @atykhyy for the pull request. -
BUGFIX: vmctl: retry on import errors in
vm-native
mode. Before, retries happened only on writes into a network connection between source and destination. But errors returned by server after all the data was transmitted were logged, but not retried. -
BUGFIX: vmagent: properly assume role with AWS IRSA authorization. Previously role chaining was not supported. See this issue for details.
-
BUGFIX: vmagent: exit if there is config syntax error in
scrape_config_files
when-promscrape.config.strictParse=true
. See this issue. -
BUGFIX: vmui: fix a link for the statistic inaccuracy explanation in the cardinality explorer tool. See this issue.
-
BUGFIX: all: fix potential panic during components shutdown when metrics push is configured. See this issue. Thanks to @zhdd99 for the pull request.
v1.96.0
See changes here
v1.95.1
See changes here
v1.95.0
See changes here
v1.94.0
See changes here
v1.93.10
Released at 2024-01-17
v1.93.x is a line of LTS releases (e.g. long-time support). 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.21.5 to Go1.21.6. See the list of issues addressed in Go1.21.6.
-
BUGFIX:
vminsert
: properly accept samples via OpenTelemetry data ingestion protocol when these samples have no resource attributes. Previously such samples were silently skipped. -
BUGFIX:
vmstorage
: added missing-inmemoryDataFlushInterval
command-line flag, which was missing in VictoriaMetrics cluster after implementing this feature in v1.85.0. -
BUGFIX:
vmstorage
: properly expirestorage/prefetchedMetricIDs
cache. Previously this cache was never expired, so it could grow big under high churn rate. This could result in increasing CPU load over time. -
BUGFIX: vmalert: check
-external.url
schema when starting vmalert, must behttp
orhttps
. Before, alertmanager could reject alert notifications if-external.url
contained no or wrong schema. -
BUGFIX: MetricsQL: properly return results from bottomk and
bottomk_*()
functions when some of these results contain NaN values. See this issue. Thanks to @xiaozongyang for the fix. -
BUGFIX: MetricsQL: properly handle queries, which wrap rollup functions with multiple arguments without explicitly specified lookbehind window in square brackets into aggregate functions. For example,
sum(quantile_over_time(0.5, process_resident_memory_bytes))
was resulting toexpecting at least 2 args to ...; got 1 args
error. Thanks to @atykhyy for the pull request. -
BUGFIX: vmagent: properly assume role with AWS IRSA authorization. Previously role chaining was not supported. See this issue for details.
-
BUGFIX: all: fix potential panic during components shutdown when metrics push is configured. See this issue. Thanks to @zhdd99 for the pull request.
-
BUGFIX: vmctl: check for Error field in response from influx client during migration. Before, only network errors were checked. Thanks to @wozz for the pull request.
-
BUGFIX: vmctl: retry on import errors in
vm-native
mode. Before, retries happened only on writes into a network connection between source and destination. But errors returned by server after all the data was transmitted were logged, but not retried.
v1.93.9
See changes here
v1.93.8
See changes here
v1.93.7
See changes here
v1.93.6
See changes here
v1.93.5
See changes here
v1.93.4
See changes here
v1.93.3
See changes here
v1.93.2
See changes here
v1.93.1
See changes here
v1.93.0
See changes here
v1.92.1
See changes here
v1.92.0
See changes here
v1.91.3
See changes here
v1.91.2
See changes here
v1.91.1
See changes here
v1.91.0
See changes here
v1.90.0
See changes here
v1.89.1
See changes here
v1.89.0
See changes here
v1.88.1
See changes here
v1.88.0
See changes here
v1.87.13
Released at 2024-01-17
v1.87.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes. The v1.87.x line will be supported for at least 12 months since v1.87.0 release
-
SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See the list of issues addressed in Go1.21.6.
-
BUGFIX:
vmstorage
: added missing-inmemoryDataFlushInterval
command-line flag, which was missing in VictoriaMetrics cluster after implementing this feature in v1.85.0. -
BUGFIX: MetricsQL: properly handle queries, which wrap rollup functions with multiple arguments without explicitly specified lookbehind window in square brackets into aggregate functions. For example,
sum(quantile_over_time(0.5, process_resident_memory_bytes))
was resulting toexpecting at least 2 args to ...; got 1 args
error. Thanks to @atykhyy for the pull request. -
BUGFIX:
vmstorage
: properly expirestorage/prefetchedMetricIDs
cache. Previously this cache was never expired, so it could grow big under high churn rate. This could result in increasing CPU load over time. -
BUGFIX: MetricsQL: properly return results from bottomk and
bottomk_...
functions when some of these results contain NaN values. See this issue. Thanks to @xiaozongyang for the fix. -
BUGFIX: all: fix potential panic during components shutdown when metrics push is configured. See this issue. Thanks to @zhdd99 for the pull request.
v1.87.12
See changes here
v1.87.11
See changes here
v1.87.10
See changes here
v1.87.9
See changes here
v1.87.8
See changes here
v1.87.7
See changes here
v1.87.6
See changes here
v1.87.5
See changes here
v1.87.4
See changes here
v1.87.3
See changes here
v1.87.2
See changes here
v1.87.1
See changes here
v1.87.0
See changes here
v1.86.2
See changes here
v1.86.1
See changes here
v1.86.0
See changes here
v1.85.3
See changes here
v1.85.2
See changes here
v1.85.1
See changes here
v1.85.0
See changes here
v1.84.0
See changes here
v1.83.1
See changes here
v1.83.0
See changes here
v1.82.1
See changes here
v1.82.0
See changes here
v1.81.2
See changes here
v1.81.1
See changes here
v1.81.0
See changes here
v1.80.0
See changes here
v1.79.14
See changes here
v1.79.13
See changes here
v1.79.12
See changes here
v1.79.11
See changes here
v1.79.10
See changes here
v1.79.9
See changes here
v1.79.8
See changes here
v1.79.7
See changes here
v1.79.6
See changes here
v1.79.5
See changes here
v1.79.4
See changes here
v1.79.3
See changes here
v1.79.2
See changes here
v1.79.1
See changes here
v1.79.0
See changes here
v1.78.1
See changes here
v1.78.0
See changes here
v1.77.2
See changes here
v1.77.1
See changes here
v1.77.0
See changes here
v1.76.1
See changes here
v1.76.0
See changes here
v1.75.1
See changes here
v1.75.0
See changes here
v1.74.0
See changes here
v1.73.1
See changes here
v1.73.0
See changes here
v1.72.0
See changes here
v1.71.0
See changes here
v1.70.0
See changes here
v1.69.0
See changes here
v1.68.0
See changes here
v1.67.0
See changes here
v1.66.2
See changes here
v1.66.1
See changes here
v1.66.0
See changes here
v1.65.0
See changes here
v1.64.1
See changes here
v1.64.0
See changes here
v1.63.0
See changes here
v1.62.0
See changes here
v1.61.1
See changes here
v1.61.0
See changes here
v1.60.0
See changes here
v1.59.0
See changes here
v1.58.0
See changes here
v1.57.1
See changes here
v1.57.0
See changes here
v1.56.0
See changes here
v1.55.1
See changes here
v1.55.0
See changes here
v1.54.1
See changes here
v1.54.0
See changes here
v1.53.1
See changes here
v1.53.0
See changes here
v1.52.0
See changes here
v1.51.0
See changes here
v1.50.2
See changes here
v1.50.1
See changes here
v1.50.0
See changes here
v1.49.0
See changes here
v1.48.0
See changes here
v1.47.0
See changes here
v1.46.0
See changes here
v1.45.0
See changes here
v1.44.0
See changes here
v1.43.0
See changes here
v1.42.0
See changes here
Previous releases
See releases page.