forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit 9e035d5
fix(deps): update all opentelemetry collector contrib packages to v0.119.0 (open-telemetry#37666)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib)
| `v0.118.0` -> `v0.119.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
|
[github.com/open-telemetry/opentelemetry-collector-contrib/internal/common](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib)
| `v0.118.0` -> `v0.119.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.
---
### Release Notes
<details>
<summary>open-telemetry/opentelemetry-collector-contrib
(github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen)</summary>
###
[`v0.119.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01190)
[Compare
Source](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.118.0...v0.119.0)
##### 🛑 Breaking changes 🛑
- `receiver/cloudfoundry`: Promote
`cloudfoundry.resourceAttributes.allow` feature gate to beta
([#&open-telemetry#8203;34824](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34824))
The `cloudfoundry.resourceAttributes.allow` feature gate is now enabled
by default.
- `datadogexporter`: Remove stable feature gate
`exporter.datadog.hostname.preview`
([#&open-telemetry#8203;37561](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37561))
- `exporter/prometheusremotewrite`: Change
`exporter.prometheusremotewriteexporter.deprecateCreatedMetric` feature
gate from Beta to Stable version.
([#&open-telemetry#8203;35003](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35003))
The `export_created_metric` configuration parameter is now permanently
deprecated.
- `elasticsearchexporter`: Consistently store the structured body of
logs and events in `body.structured` in `otel` mode
([#&open-telemetry#8203;37387](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37387))
- `solacereceiver`: Update validation step to allow only one auth
method.
([#&open-telemetry#8203;36386](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36386))
##### 🚩 Deprecations 🚩
- `signalfxreceiver`: `access_token_passthrough` is deprecated
([#&open-telemetry#8203;37575](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37575))
- "`access_token_passthrough` is deprecated."
- "Please enable include_metadata in the receiver and add the following
config to the batch processor:"
```yaml
batch:
metadata_keys: [X-Sf-Token]
```
##### 🚀 New components 🚀
- `envoyalsreceiver`: Add a new receiver for the Envoy ALS (Access Log
Service).
([#&open-telemetry#8203;36464](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36464))
- `metricstarttimeprocessor`: Add the initial skeleton for the
metricsstarttimeprocessor
([#&open-telemetry#8203;37186](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37186))
The component is still in development and is not ready for use.
- `exporter/sematext`: Add a new component for exporting metrics and
logs to Sematext
([#&open-telemetry#8203;36465](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36465))
##### 💡 Enhancements 💡
- `awss3exporter`: Add support for S3 Storgeclass
([#&open-telemetry#8203;35173](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35173))
- `processor/transformprocessor`: Add support for flat configuration
style.
([#&open-telemetry#8203;29017](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/29017))
The flat configuration style allows users to configure statements by
providing a list of statements instead of a
structured configuration map. The statement's context is expressed by
adding the context's name prefix to path names,
which are used to infer and to select the appropriate context for the
statement.
- `httpcheckreceiver`: Added support for specifying multiple endpoints
in the `httpcheckreceiver` using the `endpoints` field. Users can now
monitor multiple URLs with a single configuration block, improving
flexibility and reducing redundancy.
([#&open-telemetry#8203;37121](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37121))
- `signaltometricsconnector`: Move signal to metrics connector to alpha
stability
([#&open-telemetry#8203;35930](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35930))
- `exporter/clickhouse`: Adding missing examples of DDL created by the
clickhouse exporter
([#&open-telemetry#8203;35903](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35903))
- `opampsupervisor`: add support for headers configuration for reporting
own telemetry
([#&open-telemetry#8203;37353](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37353))
- `opampsupervisor`: report own metrics via OTLP instead of prometheus
receiver
([#&open-telemetry#8203;37346](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37346))
- `resourcedetectionprocessor`: Expose additional configuration
parameters for the AWS metadata client used by the EC2 detector
([#&open-telemetry#8203;35936](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35936))
In some cases, you might need to change the behavior of the AWS metadata
client from the [standard
retryer](https://docs.aws.amazon.com/sdk-for-go/v2/developer-guide/configure-retries-timeouts.html)
By default, the client retries 3 times with a max backoff delay of 20s.
We offer a limited set of options to override those defaults
specifically, such that you can set the client to retry 10 times, for up
to 5 minutes, for example:
```yaml
processors:
resourcedetection/ec2:
detectors: ["ec2"]
ec2:
max_attempts: 10
max_backoff: 5m
```
- `cumulativetodeltaprocessor`: Add metric type filter for
cumulativetodelta processor
([#&open-telemetry#8203;33673](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33673))
- `datadogconnector`: Support obfuscating sql queries in APM stats
([#&open-telemetry#8203;37457](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37457))
Ensure that feature flags "enable_receive_resource_spans_v2" and
"enable_operation_and_resource_name_logic_v2"
are also enabled on both Datadog Exporter and Datadog Connector so that
span attributes are properly
mapped to span type and span resource in Datadog APM; otherwise spans
and apm stats may not be
obfuscated and attributes on stats payloads may not match traces.
See
https://docs.datadoghq.com/opentelemetry/schema_semantics/semantic_mapping/?tab=datadogexporter#mapping-opentelemetry-database-system-type-to-datadog-span-type
NOTE: Long/complex SQL queries may cause a performance impact on APM
Stats calculation in Datadog Connector.
Consider implementing sampling in your pipeline prior to sending traces
to Datadog Connector if you experience this.
- `resourcedetectionprocessor`: Add `fail_on_missing_metadata` option on
EC2 detector
([#&open-telemetry#8203;35936](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35936))
If the EC2 metadata endpoint is unavailable, the EC2 detector by default
ignores the error.
By setting `fail_on_missing_metadata` to true on the detector, the user
will now trigger an error explicitly,
which will stop the collector from starting.
- `elasticsearchexporter`: Group data points into a single document even
if they are from different but equal resources
([#&open-telemetry#8203;37509](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37509))
This may prevent document rejections in case the same batch contains
different resources or scopes that have the same set of attributes
- `elasticsearchexporter`: Add config `logs_dynamic_id` to dynamically
set the document ID of log records using log record attribute
`elasticsearch.document_id`
([#&open-telemetry#8203;36882](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36882))
- `elasticsearchexporter`: Declare MutatesData: false
([#&open-telemetry#8203;37234](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37234))
When multiple exporters are used, the collector doesn't need to clone
the incoming data anymore
- `resourcedetectionprocessor`: The `gcp` resource detector will now
detect resource attributes identifying a GCE instance's managed instance
group.
([#&open-telemetry#8203;36142](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36142))
- `jaegerreceiver`: Log the endpoints of different servers started by
jaegerreceiver
([#&open-telemetry#8203;36961](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36961))
This change logs the endpoints of different servers started by
jaegerreceiver. It simplifies debugging by ensuring log messages match
configuration settings.
- `githubgen`: Switch over all usages of githubgen to the new tool
location, since the old tool was deprecated
([#&open-telemetry#8203;37412](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37412),
[#&open-telemetry#8203;37294](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37294))
- `hostmetrics/process`: Added support for tracking process.uptime
([#&open-telemetry#8203;36667](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36667))
- `netflowreceiver`: Adds the implementation of the netflow receiver
([#&open-telemetry#8203;32732](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32732))
The receiver now supports receiving NetFlow v5, NetFow v9, IPFIX, and
sFlow v5 logs.
- `googlecloudpubsubreceiver`: Added support for encoding extensions.
([#&open-telemetry#8203;37109](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37109))
- `processor/transformprocessor`: Replace parser collection
implementations with `ottl.ParserCollection` and add initial support for
expressing statement's context via path names.
([#&open-telemetry#8203;29017](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/29017))
- `prometheusreceiver`: Add
`receiver.prometheusreceiver.UseCollectorStartTimeFallback` featuregate
for the start time metric adjuster to use the collector start time as an
approximation of process start time as a fallback.
([#&open-telemetry#8203;36364](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36364))
- `tailsamplingprocessor`: Reworked the consume traces, sampling
decision, and policy loading paths to improve performance and
readability
([#&open-telemetry#8203;37560](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37560))
##### 🧰 Bug fixes 🧰
- `deltatocumulativeprocessor`: In order to cap number of histogram
buckets take the min of desired scale across negative and positive
buckets instead of the max
([#&open-telemetry#8203;37416](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37416))
- `filelogreceiver`: Fix issue where flushed tokens could be truncated.
([#&open-telemetry#8203;35042](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35042))
- `connector/routing`: Fix config validation with context other than
`resource`
([#&open-telemetry#8203;37410](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37410))
- `k8sattributesprocessor`: Wait for the other informers to complete
their initial sync before starting the pod informers
([#&open-telemetry#8203;37056](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37056))
- `metricsgenerationprocessor`: Generated metric name may not match
metric being scaled
([#&open-telemetry#8203;37474](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37474))
- `otlpjsonfilereceiver`: Include file attributes and append it to the
log record
([#&open-telemetry#8203;36641](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/36641))
- `routingconnector`: The connector splits the original payload so that
it may be emitted in parts to each route.
([#&open-telemetry#8203;37390](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37390))
- `pkg/stanza`: Fix default source identifier in recombine operator
([#&open-telemetry#8203;37210](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37210))
Its defualt value is now aligned with the semantic conventions:
`attributes["log.file.path"]`
- `tailsamplingprocessor`: Fixed sampling decision metrics
`otelcol_processor_tail_sampling_sampling_trace_dropped_too_early` and
`otelcol_processor_tail_sampling_sampling_policy_evaluation_error_total`,
these were sometimes overcounted.
([#&open-telemetry#8203;37212](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37212))
As a result of this change non-zero values of
`otelcol_processor_tail_sampling_sampling_trace_dropped_too_early`
and
`otelcol_processor_tail_sampling_sampling_policy_evaluation_error_total`
metrics will be lower.
Before this fix, errors got counted several times depending on the
amount of traces being processed
that tick and where in the batch the error happened.
Zero values are unaffected.
- `signalfxexporter`: Warn on dropping metric data points when they have
more than allowed dimension count
([#&open-telemetry#8203;37484](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/37484))
The SignalFx exporter drops metric data points if they have more than 36
dimensions.
Currently, the exporter logs at debug level when this occurs.
With this change, the exporter will log at the warning level.
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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 these
updates again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNDUuMCIsInVwZGF0ZWRJblZlciI6IjM5LjE0NS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Alex Boten <[email protected]>1 parent f6a94f9 commit 9e035d5Copy full SHA for 9e035d5
File tree
Expand file treeCollapse file tree
1 file changed
+2
-2
lines changedFilter options
- cmd/telemetrygen/internal/e2etest
Expand file treeCollapse file tree
1 file changed
+2
-2
lines changedcmd/telemetrygen/internal/e2etest/go.mod
Copy file name to clipboardExpand all lines: cmd/telemetrygen/internal/e2etest/go.mod+2-2Lines changed: 2 additions & 2 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
3 | 3 |
| |
4 | 4 |
| |
5 | 5 |
| |
6 |
| - | |
7 |
| - | |
| 6 | + | |
| 7 | + | |
8 | 8 |
| |
9 | 9 |
| |
10 | 10 |
| |
|
0 commit comments