Skip to content

chore(deps): update grafana/alloy docker tag to v1.19.2 - #350

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/grafana-alloy-1.x
Open

chore(deps): update grafana/alloy docker tag to v1.19.2#350
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/grafana-alloy-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
grafana/alloy minor v1.17.1v1.19.2

Release Notes

grafana/alloy (grafana/alloy)

v1.19.2

Compare Source

v1.19.1

Compare Source

v1.19.0

Compare Source

v1.18.1

Compare Source

Bug Fixes 🐛
Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Installation

Refer to our installation guide for how to install Grafana Alloy.

v1.18.0

Compare Source

⚠ BREAKING CHANGES
  • otelcol.receiver.otlp, otelcol.receiver.faro, otelcol.receiver.jaeger, otelcol.receiver.zipkin, otelcol.receiver.influxdb, otelcol.receiver.splunkhec, otelcol.receiver.datadog, and otelcol.extension.jaeger_remote_sampling now default to idle_timeout = "1m", read_header_timeout = "1m", and write_timeout = "30s" on their HTTP servers, matching upstream default. These were previously being defaulted to "0s". You can explicitly set them to "0s" to restore the previous behavior.
  • otelcol.receiver.kafka and otelcol.exporter.kafka: resolve_canonical_bootstrap_servers_only is now a no-op and deprecated. The upstream migration from migration from sarama to `franz-go dropped the behavior. The argument still parses but no longer resolves bootstrap server addresses.
  • otelcol.exporter.splunkhecbatcher block removed (upstream deletion in otel-contrib v0.151). Configs using it will fail to load. Migration: move the equivalent fields under sending_queue.batch (enabled → presence of the block; flush_timeout/sizer/min_size/max_size keep their names).
Features 🌟
Bug Fixes 🐛

Upgrading

Read the release notes for specific instructions on upgrading from older versions:

Installation

Refer to our installation guide for how to install Grafana Alloy.


Configuration

📅 Schedule: (UTC)

  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/grafana-alloy-1.x branch from bda48b8 to 7807280 Compare August 25, 2026 13:55
@renovate renovate Bot changed the title chore(deps): update grafana/alloy docker tag to v1.18.1 chore(deps): update grafana/alloy docker tag to v1.19.0 Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/grafana-alloy-1.x branch from 7807280 to 69a350a Compare August 25, 2026 22:44
@renovate renovate Bot changed the title chore(deps): update grafana/alloy docker tag to v1.19.0 chore(deps): update grafana/alloy docker tag to v1.19.1 Aug 25, 2026
@renovate
renovate Bot force-pushed the renovate/grafana-alloy-1.x branch from 69a350a to 73f429d Compare August 27, 2026 00:51
@renovate renovate Bot changed the title chore(deps): update grafana/alloy docker tag to v1.19.1 chore(deps): update grafana/alloy docker tag to v1.19.2 Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants