chore(deps): update docker.io/victoriametrics/victoria-logs docker tag to v1.45.0 #367
davide
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/docker.io-victoriametrics-victoria-logs-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.44.0→v1.45.0Release Notes
VictoriaMetrics/VictoriaMetrics (docker.io/victoriametrics/victoria-logs)
v1.45.0Compare Source
Changes since v1.44.0
FEATURE: allow setting
-retentionPeriodsmaller than one month. I.e.-retentionPeriod=3d,-retentionPeriod=2w, etc. is supported now. See #173FEATURE: optimize more cases according to https://utcc.utoronto.ca/~cks/space/blog/sysadmin/PrometheusLabelNonOptimization . Now the following cases are optimized too:
rollup_func(foo{filters}[d]) op bar->rollup_func(foo{filters}[d]) op bar{filters}transform_func(foo{filters}) op bar->transform_func(foo{filters}) op bar{filters}num_or_scalar op foo{filters} op bar->num_or_scalar op foo{filters} op bar{filters}FEATURE: improve time series search for queries with multiple label filters. I.e.
foo{label1="value", label2=~"regexp"}. See #781FEATURE: vmagent: add
stream parsemode. This mode allows reducing memory usage when individual scrape targets expose tens of millions of metrics. For example, during scraping Prometheus in federation mode. See-promscrape.streamParsecommand-line option andstream_parse: trueconfig option forscrape_configsection in-promscrape.config. See #825 and troubleshooting docs for vmagent.FEATURE: vmalert: add
-dryRuncommand-line option for validating the provided config files without the need to startvmalertservice.FEATURE: accept optional third argument of string type at
topk_*andbottomk_*functions. This is label name for additional time series to return with the sum of time series outside top/bottom K. See MetricsQL docs for more details.FEATURE: vmagent: expose
/api/v1/targetspage according to the corresponding Prometheus API. See #643BUGFIX: vmagent: properly handle OpenStack endpoint ending with
v3.0such ashttps://ostack.example.com:5000/v3.0in the same way as Prometheus does. See #728 (comment)BUGFIX: drop trailing data points for time series with a single raw sample. See #748
BUGFIX: do not drop trailing data points for instant queries to
/api/v1/query. See #845BUGFIX: vmbackup: fix panic when
-originisn't specified. See #856BUGFIX: vmalert: skip automatically added labels on alerts restore. Label
alertgroupwas introduced in this issue and automatically added to generated time series. By mistake, this new label wasn't correctly purged on restore event and affected alert's ID uniqueness. See #870BUGFIX: vmagent: fix panic at scrape error body formating. See #864
BUGFIX: vmagent: add leading missing slash to metrics path like Prometheus does. See #835
BUGFIX: vmagent: drop packet if remote storage returns 4xx status code. This make the behaviour consistent with Prometheus.
See #873
BUGFIX: vmagent: properly handle 301 redirects. See #869
How to run VictoriaMetrics
Unpack the
victoria-metrics-*.tar.gzarchive and read these docs.vmutils-*.tag.gzarchive contains the following tools:The corresponding docker images are available here.
Cluster version is available here.
vmctl releases are available here.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.