chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.151.0 (#65)
This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [go.opentelemetry.io/collector/processor/processortest](https://github.com/open-telemetry/opentelemetry-collector) | `v0.150.0` → `v0.151.0` |  |  | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)</summary> ### [`v0.151.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1570v01510) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.150.0...v0.151.0) ##### 🛑 Breaking changes 🛑 - `cmd/builder`: In the generated Collector source, the `replace` statements in the Go module will now use relative paths by default. ([#​15097](https://github.com/open-telemetry/opentelemetry-collector/issues/15097)) We expect that this will not break existing use-cases where the generated collector is only used in an interim manner for builds. It enables the possibility of tracking the generated Collector code as a longer living artifact, allowing it to be run on any machine (whereas absolute paths will be different depending on the machine the Collector source is generated on.) We have added `dist::use_absolute_replace_paths` to go back to the absolute path behaviour in the case where there is an unforeseen use-case that requires absolute paths. - `pkg/confighttp`: Stabilize framedSnappy feature gate. ([#​15096](https://github.com/open-telemetry/opentelemetry-collector/issues/15096)) ##### 💡 Enhancements 💡 - `all`: Add declarative schema support for service telemetry resource configuration. ([#​14411](https://github.com/open-telemetry/opentelemetry-collector/issues/14411)) The `service::telemetry::resource` configuration now accepts the declarative schema with explicit name/value pairs: ```yaml service: telemetry: resource: schema_url: https://opentelemetry.io/schemas/1.38.0 attributes: - name: service.name value: my-collector - name: host.name value: collector-host ``` The legacy inline attribute map format is still supported for backward compatibility: ```yaml service: telemetry: resource: service.name: my-collector host.name: collector-host ``` Note: `resource.detectors` is accepted for forward compatibility but is not yet applied by the collector. - `exporter/otlp_grpc`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp exporter. ([#​14998](https://github.com/open-telemetry/opentelemetry-collector/issues/14998)) - `exporter/otlp_http`: Added the `server.address` and `url.path` attributes to metrics generated by the otlp\_http exporter. ([#​14998](https://github.com/open-telemetry/opentelemetry-collector/issues/14998)) - `pkg/config/configgrpc`: Add `UserAgent` field to `ClientConfig` to allow overriding the default gRPC user-agent string. ([#​14686](https://github.com/open-telemetry/opentelemetry-collector/issues/14686)) The otlp gRPC exporter was unconditionally setting the User-Agent via grpc.WithUserAgent() at dial time, which takes precedence over per-call metadata, causing any user-configured User-Agent to be silently discarded. A dedicated `UserAgent` field has been added to `ClientConfig` which, when set, is used in the dial option directly instead of the default BuildInfo-derived string. - `pkg/config/configgrpc`: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution ([#​14990](https://github.com/open-telemetry/opentelemetry-collector/issues/14990)) After the migration to grpc.NewClient, some gRPC client components such as the OTLP exporter experienced connection issues in dual-stack DNS environments. This can now be fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field. - `pkg/config/confignet`: Add support for Windows Named Pipe (npipe) transport ([#​15085](https://github.com/open-telemetry/opentelemetry-collector/issues/15085)) - `pkg/service`: Emit a warning when using the old v0.2.0 declarative config format ([#​15088](https://github.com/open-telemetry/opentelemetry-collector/issues/15088)) ##### 🧰 Bug fixes 🧰 - `pkg/otelcol`: Print components exactly once in the `otelcol components` command ([#​14682](https://github.com/open-telemetry/opentelemetry-collector/issues/14682)) This resolves an issue where aliased components were skipped. - `pkg/otelcol`: Synchronize Collector Run and Shutdown lifecycles so that Shutdown blocks until Run completes all cleanup. ([#​4947](https://github.com/open-telemetry/opentelemetry-collector/issues/4947)) Shutdown now blocks until Run finishes cleanup, matching http.Server semantics. If Shutdown is called before Run, the next Run call returns nil after cleaning up the config provider. - `pkg/pdata`: Use spec-compliant string representation for NaN, Infinity, and -Infinity in Value.AsString(). ([#​14487](https://github.com/open-telemetry/opentelemetry-collector/issues/14487)) - `pkg/pprofile`: Fix data corruption of resource and scope attributes after marshal-unmarshal-merge round-trip. ([#​15084](https://github.com/open-telemetry/opentelemetry-collector/issues/15084)) - `pkg/service`: Non-string resource attributes in telemetry configuration now return an error instead of panicking ([#​15171](https://github.com/open-telemetry/opentelemetry-collector/issues/15171)) - `pkg/xscraperhelper`: fix the merge of profiles in the profiling scraper helpers ([#​14790](https://github.com/open-telemetry/opentelemetry-collector/issues/14790)) - `receiver/otlp`: Fix profiles receiver reporting its samples as spans ([#​15089](https://github.com/open-telemetry/opentelemetry-collector/issues/15089)) <!-- previous-version --> </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:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My41LjQiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=--> Reviewed-on: https://gitea.t000-n.de/t.behrendt/tracebasedlogsampler/pulls/65 Reviewed-by: t.behrendt <t.behrendt@noreply.localhost> Co-authored-by: Renovate Bot <renovate@t00n.de> Co-committed-by: Renovate Bot <renovate@t00n.de>
This commit was merged in pull request #65.
This commit is contained in:
@@ -4,7 +4,7 @@ go 1.25.0
|
||||
|
||||
require (
|
||||
github.com/stretchr/testify v1.11.1
|
||||
go.uber.org/zap v1.27.1
|
||||
go.uber.org/zap v1.28.0
|
||||
)
|
||||
|
||||
require (
|
||||
@@ -28,15 +28,15 @@ require (
|
||||
github.com/pmezard/go-difflib v1.0.0 // indirect
|
||||
github.com/stretchr/objx v0.5.2 // indirect
|
||||
go.opentelemetry.io/auto/sdk v1.2.1 // indirect
|
||||
go.opentelemetry.io/collector/component/componentstatus v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/consumer/xconsumer v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/featuregate v1.56.0 // indirect
|
||||
go.opentelemetry.io/collector/internal/componentalias v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/component/componentstatus v0.151.0 // indirect
|
||||
go.opentelemetry.io/collector/consumer/xconsumer v0.151.0 // indirect
|
||||
go.opentelemetry.io/collector/featuregate v1.57.0 // indirect
|
||||
go.opentelemetry.io/collector/internal/componentalias v0.151.0 // indirect
|
||||
go.opentelemetry.io/collector/internal/telemetry v0.129.0 // indirect
|
||||
go.opentelemetry.io/collector/pdata/pprofile v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/pdata/testdata v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/pipeline v1.56.0 // indirect
|
||||
go.opentelemetry.io/collector/processor/xprocessor v0.150.0 // indirect
|
||||
go.opentelemetry.io/collector/pdata/pprofile v0.151.0 // indirect
|
||||
go.opentelemetry.io/collector/pdata/testdata v0.151.0 // indirect
|
||||
go.opentelemetry.io/collector/pipeline v1.57.0 // indirect
|
||||
go.opentelemetry.io/collector/processor/xprocessor v0.151.0 // indirect
|
||||
go.opentelemetry.io/contrib/bridges/otelzap v0.11.0 // indirect
|
||||
go.opentelemetry.io/otel v1.43.0 // indirect
|
||||
go.opentelemetry.io/otel/log v0.12.2 // indirect
|
||||
@@ -56,13 +56,13 @@ require (
|
||||
)
|
||||
|
||||
require (
|
||||
go.opentelemetry.io/collector/component v1.56.0
|
||||
go.opentelemetry.io/collector/component/componenttest v0.150.0
|
||||
go.opentelemetry.io/collector/component v1.57.0
|
||||
go.opentelemetry.io/collector/component/componenttest v0.151.0
|
||||
go.opentelemetry.io/collector/confmap v1.56.0
|
||||
go.opentelemetry.io/collector/consumer v1.56.0
|
||||
go.opentelemetry.io/collector/consumer/consumertest v0.150.0
|
||||
go.opentelemetry.io/collector/pdata v1.56.0
|
||||
go.opentelemetry.io/collector/processor v1.56.0
|
||||
go.opentelemetry.io/collector/processor/processortest v0.150.0
|
||||
go.opentelemetry.io/collector/consumer v1.57.0
|
||||
go.opentelemetry.io/collector/consumer/consumertest v0.151.0
|
||||
go.opentelemetry.io/collector/pdata v1.57.0
|
||||
go.opentelemetry.io/collector/processor v1.57.0
|
||||
go.opentelemetry.io/collector/processor/processortest v0.151.0
|
||||
go.uber.org/multierr v1.11.0 // indirect
|
||||
)
|
||||
|
||||
Reference in New Issue
Block a user