chore(deps): update dependency grafana/alloy to v1.5.1 #41

Merged
GregoryDosh merged 1 commit from renovate/grafana-alloy-1.x into main 2024-12-04 14:17:57 +00:00

This PR contains the following updates:

Package Update Change
grafana/alloy patch 1.5.0 -> 1.5.1

Release Notes

grafana/alloy (grafana/alloy)

v1.5.1

Compare Source

Enhancements
  • Logs from underlying clustering library memberlist are now surfaced with correct level (@​thampiotr)

  • Allow setting informer_sync_timeout in prometheus.operator.* components. (@​captncraig)

  • For sharding targets during clustering, loki.source.podlogs now only takes into account some labels. (@​ptodev)

Bugfixes
  • Fixed an issue in the pyroscope.write component to prevent TLS connection churn to Pyroscope when the pyroscope.receive_http clients don't request keepalive (@​madaraszg-tulip)

  • Fixed an issue in the pyroscope.write component with multiple endpoints not working correctly for forwarding profiles from pyroscope.receive_http (@​madaraszg-tulip)

  • Fixed a few race conditions that could lead to a deadlock when using import statements, which could lead to a memory leak on /metrics endpoint of an Alloy instance. (@​thampiotr)

  • Fix a race condition where the ui service was dependent on starting after the remotecfg service, which is not guaranteed. (@​dehaansa & @​erikbaranowski)

  • Fixed an issue in the otelcol.exporter.prometheus component that would set series value incorrectly for stale metrics (@​YusifAghalar)

  • loki.source.podlogs: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent.
    The bug only happened when no selector or namespace_selector blocks were specified in the Alloy configuration. (@​ptodev)

  • Fixed an issue in the pyroscope.write component to allow slashes in application names in the same way it is done in the Pyroscope push API (@​marcsanmi)

  • Fixed a crash when updating the configuration of remote.http. (@​kinolaev)

  • Fixed an issue in the otelcol.processor.attribute component where the actions delete and hash could not be used with the pattern argument. (@​wildum)

  • Fixed an issue in the prometheus.exporter.postgres component that would leak goroutines when the target was not reachable (@​dehaansa)


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.


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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [grafana/alloy](https://github.com/grafana/alloy) | patch | `1.5.0` -> `1.5.1` | --- ### Release Notes <details> <summary>grafana/alloy (grafana/alloy)</summary> ### [`v1.5.1`](https://github.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v151) [Compare Source](https://github.com/grafana/alloy/compare/v1.5.0...v1.5.1) ##### Enhancements - Logs from underlying clustering library `memberlist` are now surfaced with correct level ([@&#8203;thampiotr](https://github.com/thampiotr)) - Allow setting `informer_sync_timeout` in prometheus.operator.\* components. ([@&#8203;captncraig](https://github.com/captncraig)) - For sharding targets during clustering, `loki.source.podlogs` now only takes into account some labels. ([@&#8203;ptodev](https://github.com/ptodev)) ##### Bugfixes - Fixed an issue in the `pyroscope.write` component to prevent TLS connection churn to Pyroscope when the `pyroscope.receive_http` clients don't request keepalive ([@&#8203;madaraszg-tulip](https://github.com/madaraszg-tulip)) - Fixed an issue in the `pyroscope.write` component with multiple endpoints not working correctly for forwarding profiles from `pyroscope.receive_http` ([@&#8203;madaraszg-tulip](https://github.com/madaraszg-tulip)) - Fixed a few race conditions that could lead to a deadlock when using `import` statements, which could lead to a memory leak on `/metrics` endpoint of an Alloy instance. ([@&#8203;thampiotr](https://github.com/thampiotr)) - Fix a race condition where the ui service was dependent on starting after the remotecfg service, which is not guaranteed. ([@&#8203;dehaansa](https://github.com/dehaansa) & [@&#8203;erikbaranowski](https://github.com/erikbaranowski)) - Fixed an issue in the `otelcol.exporter.prometheus` component that would set series value incorrectly for stale metrics ([@&#8203;YusifAghalar](https://github.com/YusifAghalar)) - `loki.source.podlogs`: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent. The bug only happened when no `selector` or `namespace_selector` blocks were specified in the Alloy configuration. ([@&#8203;ptodev](https://github.com/ptodev)) - Fixed an issue in the `pyroscope.write` component to allow slashes in application names in the same way it is done in the Pyroscope push API ([@&#8203;marcsanmi](https://github.com/marcsanmi)) - Fixed a crash when updating the configuration of `remote.http`. ([@&#8203;kinolaev](https://github.com/kinolaev)) - Fixed an issue in the `otelcol.processor.attribute` component where the actions `delete` and `hash` could not be used with the `pattern` argument. ([@&#8203;wildum](https://github.com/wildum)) - Fixed an issue in the `prometheus.exporter.postgres` component that would leak goroutines when the target was not reachable ([@&#8203;dehaansa](https://github.com/dehaansa)) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xOS4xIiwidXBkYXRlZEluVmVyIjoiMzkuMTkuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
GregoryDosh deleted branch renovate/grafana-alloy-1.x 2024-12-04 14:17:57 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
homelab/ansible-collection!41
No description provided.