chore(deps): update dependency grafana/alloy to v1.4.1 #28

svc-renovate-bot · 2024-09-26T18:17:05Z

svc-renovate-bot commented

2024-09-26 18:17:05 +00:00

This PR contains the following updates:

Package	Update	Change
grafana/alloy	minor	`1.3.1` -> `1.4.1`

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

grafana/alloy (grafana/alloy)

`v1.4.1`

Compare Source

Bugfixes

Windows installer: Don't quote Alloy's binary path in the Windows Registry. (@jkroepke)

`v1.4.0`

Compare Source

Security fixes

Add quotes to windows service path to prevent path interception attack. CVE-2024-8975 (@mattdurham)

Breaking changes

Some debug metrics for otelcol components have changed. (@thampiotr)
For example, otelcol.exporter.otlp's exporter_sent_spans_ratio_total metric is now otelcol_exporter_sent_spans_total.
[otelcol.processor.transform] The functions convert_sum_to_gauge and convert_gauge_to_sum must now be used in the metric context rather than in the datapoint context.
https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34567 (@wildum)
Upgrade Beyla from 1.7.0 to 1.8.2. A complete list of changes can be found on the Beyla releases page: https://github.com/grafana/beyla/releases. (@wildum)
It contains a few breaking changes for the component beyla.ebpf:
- renamed metric process.cpu.state to cpu.mode
- renamed metric beyla_build_info to beyla_internal_build_info

Features

Added Datadog Exporter community component, enabling exporting of otel-formatted Metrics and traces to Datadog. (@polyrain)
(Experimental) Add an otelcol.processor.interval component to aggregate metrics and periodically
forward the latest values to the next component in the pipeline.
(Experimental) Add a loki.secretfilter component to redact secrets from collected logs.

Enhancements

Clustering peer resolution through --cluster.join-addresses flag has been
improved with more consistent behaviour, better error handling and added
support for A/AAAA DNS records. If necessary, users can temporarily opt out of
this new behaviour with the --cluster.use-discovery-v1, but this can only be
used as a temporary measure, since this flag will be disabled in future
releases. (@thampiotr)
Added a new panel to Cluster Overview dashboard to show the number of peers
seen by each instance in the cluster. This can help diagnose cluster split
brain issues. (@thampiotr)
Updated Snowflake exporter with performance improvements for larger environments.
Also added a new panel to track deleted tables to the Snowflake mixin. (@Caleb-Hurshman)
Add a otelcol.processor.groupbyattrs component to reassociate collected metrics that match specified attributes
from opentelemetry. (@kehindesalaam)
Update windows_exporter to v0.27.2. (@jkroepke)
The smb.enabled_list and smb_client.enabled_list doesn't have any effect anymore. All sub-collectors are enabled by default.
Live debugging of loki.process will now also print the timestamp of incoming and outgoing log lines.
This is helpful for debugging stage.timestamp. (@ptodev)
Add extra validation in beyla.ebpf to avoid panics when network feature is enabled. (@marctc)
A new parameter aws_sdk_version_v2 is added for the cloudwatch exporters configuration. It enables the use of aws sdk v2 which has shown to have significant performance benefits. (@kgeckhart, @andriikushch)
prometheus.exporter.cloudwatch can now collect metrics from custom namespaces via the custom_namespace block. (@ptodev)
Add the label alloy_cluster in the metric alloy_config_hash when the flag cluster.name is set to help differentiate between
configs from the same alloy cluster or different alloy clusters. (@wildum)

Bugfixes

Fix a bug where the scrape timeout for a Probe resource was not applied, overwriting the scrape interval instead. (@morremeyer, @stefanandres)
Fix a bug where custom components don't always get updated when the config is modified in an imported directory. (@ante012)
Fixed an issue which caused loss of context data in Faro exception. (@codecapitano)
Fixed an issue where providing multiple hostnames or IP addresses
via --cluster.join-addresses would only use the first provided value.
(@thampiotr)
Fixed an issue where providing <hostname>:<port>
in --cluster.join-addresses would only resolve with DNS to a single address,
instead of using all the available records. (@thampiotr)
Fixed an issue where clustering peers resolution via hostname in --cluster.join-addresses
resolves to duplicated IP addresses when using SRV records. (@thampiotr)
Fixed an issue where the connection_string for the loki.source.azure_event_hubs component
was displayed in the UI in plaintext. (@MorrisWitthein)
Fix a bug in discovery.* components where old targets would continue to be
exported to downstream components. This would only happen if the config
for discovery.* is reloaded in such a way that no new targets were
discovered. (@ptodev, @thampiotr)
Fixed bug in loki.process with sampling stage where all components use same drop_counter_reason. (@captncraig)
Fixed an issue (see https://github.com/grafana/alloy/issues/1599) where specifying both path and key in the remote.vault path
configuration could result in incorrect URLs. The path and key arguments have been separated to allow for clear and accurate
specification of Vault secrets. (@PatMis16)

Other

Renamed standard library functions. Old names are still valid but are marked deprecated. (@wildum)
Aliases for the namespaces are deprecated in the Cloudwatch exporter. For example: "s3" is not allowed, "AWS/S3" should be used. Usage of the aliases will generate warnings in the logs. Support for the aliases will be dropped in the upcoming releases. (@kgeckhart, @andriikushch)
Update OTel from v0.105.0 vo v0.108.0: (@wildum)
- [otelcol.receiver.vcenter] New VSAN metrics.
  https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33556
- [otelcol.receiver.kafka] Add session_timeout and heartbeat_interval attributes.
  https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33082
- [otelcol.processor.transform] Add aggregate_on_attributes function for metrics.
  https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33334
- [otelcol.receiver.vcenter] Enable metrics by default
  https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33607
Updated the docker base image to Ubuntu 24.04 (Noble Numbat). (@mattiasa )

`v1.3.4`

Compare Source

Bugfixes

Windows installer: Don't quote Alloy's binary path in the Windows Registry. (@jkroepke)

`v1.3.3`

Compare Source

This is release v1.3.3 of Grafana Alloy.

Upgrading

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

Notable changes:

Security fixes

Add quotes to windows service path to prevent path interception attack. CVE-2024-8975 (@mattdurham)

Installation

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

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) | minor | `1.3.1` -> `1.4.1` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>grafana/alloy (grafana/alloy)</summary> ### [`v1.4.1`](https://github.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v141) [Compare Source](https://github.com/grafana/alloy/compare/v1.4.0...v1.4.1) ##### Bugfixes - Windows installer: Don't quote Alloy's binary path in the Windows Registry. ([@jkroepke](https://github.com/jkroepke)) ### [`v1.4.0`](https://github.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v140) [Compare Source](https://github.com/grafana/alloy/compare/v1.3.4...v1.4.0) ##### Security fixes - Add quotes to windows service path to prevent path interception attack. [CVE-2024-8975](https://grafana.com/security/security-advisories/cve-2024-8975/) ([@mattdurham](https://github.com/mattdurham)) ##### Breaking changes - Some debug metrics for `otelcol` components have changed. ([@thampiotr](https://github.com/thampiotr)) For example, `otelcol.exporter.otlp`'s `exporter_sent_spans_ratio_total` metric is now `otelcol_exporter_sent_spans_total`. - \[otelcol.processor.transform] The functions `convert_sum_to_gauge` and `convert_gauge_to_sum` must now be used in the `metric` `context` rather than in the `datapoint` context. https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34567 ([@wildum](https://github.com/wildum)) - Upgrade Beyla from 1.7.0 to 1.8.2. A complete list of changes can be found on the Beyla releases page: https://github.com/grafana/beyla/releases. ([@wildum](https://github.com/wildum)) It contains a few breaking changes for the component `beyla.ebpf`: - renamed metric `process.cpu.state` to `cpu.mode` - renamed metric `beyla_build_info` to `beyla_internal_build_info` ##### Features - Added Datadog Exporter community component, enabling exporting of otel-formatted Metrics and traces to Datadog. ([@polyrain](https://github.com/polyrain)) - (*Experimental*) Add an `otelcol.processor.interval` component to aggregate metrics and periodically forward the latest values to the next component in the pipeline. - (*Experimental*) Add a `loki.secretfilter` component to redact secrets from collected logs. ##### Enhancements - Clustering peer resolution through `--cluster.join-addresses` flag has been improved with more consistent behaviour, better error handling and added support for A/AAAA DNS records. If necessary, users can temporarily opt out of this new behaviour with the `--cluster.use-discovery-v1`, but this can only be used as a temporary measure, since this flag will be disabled in future releases. ([@thampiotr](https://github.com/thampiotr)) - Added a new panel to Cluster Overview dashboard to show the number of peers seen by each instance in the cluster. This can help diagnose cluster split brain issues. ([@thampiotr](https://github.com/thampiotr)) - Updated Snowflake exporter with performance improvements for larger environments. Also added a new panel to track deleted tables to the Snowflake mixin. ([@Caleb-Hurshman](https://github.com/Caleb-Hurshman)) - Add a `otelcol.processor.groupbyattrs` component to reassociate collected metrics that match specified attributes from opentelemetry. ([@kehindesalaam](https://github.com/kehindesalaam)) - Update windows_exporter to v0.27.2. ([@jkroepke](https://github.com/jkroepke)) The `smb.enabled_list` and `smb_client.enabled_list` doesn't have any effect anymore. All sub-collectors are enabled by default. - Live debugging of `loki.process` will now also print the timestamp of incoming and outgoing log lines. This is helpful for debugging `stage.timestamp`. ([@ptodev](https://github.com/ptodev)) - Add extra validation in `beyla.ebpf` to avoid panics when network feature is enabled. ([@marctc](https://github.com/marctc)) - A new parameter `aws_sdk_version_v2` is added for the cloudwatch exporters configuration. It enables the use of aws sdk v2 which has shown to have significant performance benefits. ([@kgeckhart](https://github.com/kgeckhart), [@andriikushch](https://github.com/andriikushch)) - `prometheus.exporter.cloudwatch` can now collect metrics from custom namespaces via the `custom_namespace` block. ([@ptodev](https://github.com/ptodev)) - Add the label `alloy_cluster` in the metric `alloy_config_hash` when the flag `cluster.name` is set to help differentiate between configs from the same alloy cluster or different alloy clusters. ([@wildum](https://github.com/wildum)) ##### Bugfixes - Fix a bug where the scrape timeout for a Probe resource was not applied, overwriting the scrape interval instead. ([@morremeyer](https://github.com/morremeyer), [@stefanandres](https://github.com/stefanandres)) - Fix a bug where custom components don't always get updated when the config is modified in an imported directory. ([@ante012](https://github.com/ante012)) - Fixed an issue which caused loss of context data in Faro exception. ([@codecapitano](https://github.com/codecapitano)) - Fixed an issue where providing multiple hostnames or IP addresses via `--cluster.join-addresses` would only use the first provided value. ([@thampiotr](https://github.com/thampiotr)) - Fixed an issue where providing `<hostname>:<port>` in `--cluster.join-addresses` would only resolve with DNS to a single address, instead of using all the available records. ([@thampiotr](https://github.com/thampiotr)) - Fixed an issue where clustering peers resolution via hostname in `--cluster.join-addresses` resolves to duplicated IP addresses when using SRV records. ([@thampiotr](https://github.com/thampiotr)) - Fixed an issue where the `connection_string` for the `loki.source.azure_event_hubs` component was displayed in the UI in plaintext. ([@MorrisWitthein](https://github.com/MorrisWitthein)) - Fix a bug in `discovery.*` components where old `targets` would continue to be exported to downstream components. This would only happen if the config for `discovery.*` is reloaded in such a way that no new targets were discovered. ([@ptodev](https://github.com/ptodev), [@thampiotr](https://github.com/thampiotr)) - Fixed bug in `loki.process` with `sampling` stage where all components use same `drop_counter_reason`. ([@captncraig](https://github.com/captncraig)) - Fixed an issue (see https://github.com/grafana/alloy/issues/1599) where specifying both path and key in the remote.vault `path` configuration could result in incorrect URLs. The `path` and `key` arguments have been separated to allow for clear and accurate specification of Vault secrets. ([@PatMis16](https://github.com/PatMis16)) ##### Other - Renamed standard library functions. Old names are still valid but are marked deprecated. ([@wildum](https://github.com/wildum)) - Aliases for the namespaces are deprecated in the Cloudwatch exporter. For example: "s3" is not allowed, "AWS/S3" should be used. Usage of the aliases will generate warnings in the logs. Support for the aliases will be dropped in the upcoming releases. ([@kgeckhart](https://github.com/kgeckhart), [@andriikushch](https://github.com/andriikushch)) - Update OTel from v0.105.0 vo v0.108.0: ([@wildum](https://github.com/wildum)) - \[`otelcol.receiver.vcenter`] New VSAN metrics. https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33556 - \[`otelcol.receiver.kafka`] Add `session_timeout` and `heartbeat_interval` attributes. https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33082 - \[`otelcol.processor.transform`] Add `aggregate_on_attributes` function for metrics. https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33334 - \[`otelcol.receiver.vcenter`] Enable metrics by default https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33607 - Updated the docker base image to Ubuntu 24.04 (Noble Numbat). ([@mattiasa](https://github.com/mattiasa) ) ### [`v1.3.4`](https://github.com/grafana/alloy/blob/HEAD/CHANGELOG.md#v134) [Compare Source](https://github.com/grafana/alloy/compare/v1.3.3...v1.3.4) ##### Bugfixes - Windows installer: Don't quote Alloy's binary path in the Windows Registry. ([@jkroepke](https://github.com/jkroepke)) ### [`v1.3.3`](https://github.com/grafana/alloy/releases/tag/v1.3.3) [Compare Source](https://github.com/grafana/alloy/compare/v1.3.1...v1.3.3) This is release `v1.3.3` of Grafana Alloy. ##### Upgrading Read the [release notes] for specific instructions on upgrading from older versions: [release notes]: https://grafana.com/docs/alloy/v1.3/release-notes/ ##### Notable changes: ##### Security fixes - Add quotes to windows service path to prevent path interception attack. [CVE-2024-8975](https://grafana.com/security/security-advisories/cve-2024-8975/) ([@mattdurham](https://github.com/mattdurham)) ##### Installation Refer to our [installation guide] for how to install Grafana Alloy. [installation guide]: https://grafana.com/docs/alloy/v1.3/get-started/install/ </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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

svc-renovate-bot added the

dependencies

label

2024-09-26 18:17:05 +00:00

svc-renovate-bot added 1 commit

2024-09-26 18:17:05 +00:00

chore(deps): update dependency grafana/alloy to v1.4.1 899bf1f074

GregoryDosh added 1 commit

2024-09-29 23:41:07 +00:00

Merge branch 'main' into renovate/grafana-alloy-1.x 1f754cf71c

GregoryDosh merged commit b643995b17 into main

2024-09-29 23:41:12 +00:00