[pdata] Update values returned by all String methods of enum types #6250
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dmitryax
changed the title
dmitryax
force-pushed
the
update-other-names
branch
4 times, most recently
from
2d9ad3c to
d60e6ef
Compare
dmitryax
force-pushed
the
update-other-names
branch
from
d60e6ef to
3079b88
Compare
Codecov ReportBase: 91.86% // Head: 91.93% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #6250 +/- ##
==========================================
+ Coverage 91.86% 91.93% +0.06%
==========================================
Files 237 237
Lines 13620 13694 +74
==========================================
+ Hits 12512 12589 +77
+ Misses 879 876 -3
Partials 229 229
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
dmitryax
force-pushed
the
update-other-names
branch
from
3079b88 to
aa32267
Compare
Update values returned by all String methods of enum types to a consistent short form representing the enum identifier
dmitryax
force-pushed
the
update-other-names
branch
from
aa32267 to
e950650
Compare
|
@bogdandrutu this is ready for review |
dmitryax
added a commit
to dmitryax/opentelemetry-collector-contrib
that referenced
this pull request
Nov 2, 2022
[SpanKind|StatusCode].String() will be changed to return different string values. This change replaces existing method calls with contrib internal functions to avoid breaking changes when open-telemetry/opentelemetry-collector#6250 is merged
bogdandrutu
approved these changes
Nov 4, 2022
|
@bogdandrutu curious why this repo started creating merge commits recently? |
mx-psi
pushed a commit
to open-telemetry/opentelemetry-collector-contrib
that referenced
this pull request
Aug 28, 2024
#34799) **Description:** Trace `SpanKind` and `StatusCode` are exporting [old enum values](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/04b3b9898b242c0b3b707bc043c025eb9f6f73ba/internal/coreinternal/traceutil/traceutil.go#L13-L47). This change will make these fields consistent with the specification. I have marked this as a breaking change since it may affect queries that filter by these strings. There should be no change to exporter deployments, only to the read queries. See above/below links for more information as well as a sample of the old vs new values. Example: `STATUS_CODE_ERROR` -> `Error` **Link to tracking Issue:** - open-telemetry/opentelemetry-collector#6250 - open-telemetry/opentelemetry-collector#6251 **Testing:** - Updated integration tests
codeboten
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Sep 10, 2024
…ib/cmd/telemetrygen to v0.109.0 (#35126) 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.108.0` -> `v0.109.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.109.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01090) [Compare Source](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.108.0...v0.109.0) ##### 🛑 Breaking changes 🛑 - `clickhouseexporter`: Upgrade trace SpanKind and StatusCode string values ([#​34799](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34799)) This change updates the output of the trace SpanKind and StatusCode fields to be consistent with the specification's enum values. While this change will not break any deployments, it may affect queries dependent on the old enum names. For more details on old->new values, see this related PR: [https://github.com/open-telemetry/opentelemetry-collector/pull/6250](https://redirect.github.com/open-telemetry/opentelemetry-collector/pull/6250)6250 - `spanmetricsconnector`: Improve consistency between metrics generated by spanmetricsconnector. Added traces.span.metrics as default namespace ([#​33227](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33227), [#​32818](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32818)) Default namespace for the generated metrics is traces.span.metrics now. | The deprecated metrics are: calls, duration and events. | The feature flag connector.spanmetrics.legacyLatencyMetricNames was added to revert the behavior. - `servicegraphconnector`: Fix histogram metrics miss unit ([#​34511](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34511)) All metrics will remove the suffix `_seconds`. It will not introduce breaking change if users use | `prometheusexporter` or `prometheusremotewriteexporter` to exporter metrics in pipeline. | In some cases, like using `clickhouseexporter`(save data in native OTLP format), it will be a breaking change. | Users can use `transformprocessor` to add back this suffix. - `gitproviderreceiver`: The Git Provider Receiver has been renamed to GitHub Receiver. ([#​34731](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34731)) This rename was to better match the OpenTelemetry semantic convention changes in v1.27.0 and allows for Traces and Log signals to be added to this component. Traces as mentioned in issue [#​27460](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27460) will be added in a future release to this component. - `ottl`: Remove tracing from OTTL due to performance concerns ([#​34910](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34910)) - `vcenterreceiver`: Updated units on several metrics to be more in line with documented semantics. ([#​34946](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34946)) The following are the metrics with their respective unit changes: - vcenter.datacenter.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.effective ({MHz} -> MHz) - vcenter.cluster.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.cluster.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.host.network.packet.error.rate ({errors/sec} -> {errors/s}) - vcenter.host.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.host.network.packet.drop.rate ({packets/sec} -> {packets/s}) - vcenter.host.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.host.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.resource_pool.cpu.usage ({MHz} -> MHz) - vcenter.vm.network.throughput (By/sec -> By/s) - vcenter.vm.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.vm.vsan.operations ({operations/sec} -> {operations/s}) ##### 🚩 Deprecations 🚩 - `instanaexporter`: Marking instanaexporter module as deprecated ([#​34994](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34994)) ##### 💡 Enhancements 💡 - `pkg/ottl`: Added Decode() converter function ([#​32493](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32493)) - `testbed`: Add test case scenarios to handle large files to existing testbed. ([#​34288](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34288)) - `filestorage`: Add directory validation for compaction on-rebound ([#​35114](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35114)) - `windowseventlogreceiver`: Avoid rendering the whole event to obtain the provider name ([#​34755](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34755)) - `datadogreceiver`: add support for sketch metrics in Datadog receiver ([#​18278](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/18278)) - `datadogconnector`: Optimize Datadog connector when there are many peer tags and `connector.datadogconnector.NativeIngest` is enabled ([#​34945](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34945)) `connector.datadogconnector.NativeIngest` is currently enabled by default - `splunkhecexporter`: Drop empty log events ([#​34871](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34871)) Log records with no body are dropped by Splunk on reception as they contain no log message, albeit they may have attributes. This PR removes those logs from consideration to be exported. This is in tune with the behavior of splunkhecreceiver, which refuses HEC events with no event ([#​19769](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/19769)) - `elasticsearchexporter`: Add exponential histogram support ([#​34813](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34813)) - `elasticsearchexporter`: Add span event support to traces OTel mapping mode ([#​34831](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34831)) Span events are now supported in OTel mapping mode. They will be routed to `logs-${data_stream.dataset}-${data_stream.namespace}` if `traces_dynamic_index::enabled` is `true`. - `transformprocessor`: Support aggregating metrics based on their attribute values and substituting the values with a new value. ([#​16224](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/16224)) - `kafkareceiver`: Adds tunable fetch sizes to Kafka Receiver ([#​22741](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/22741), [#​34431](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34431)) Adds the ability to tune the minumum, default and maximum fetch sizes for the Kafka Receiver - `solarwindsapmsettingsextension`: Added logic for refresh function ([#​27668](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27668)) - `githubreceiver`: Promote GitHub receiver metrics to alpha status. ([#​34960](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34960)) - `googlecloudmonitoringreceiver`: Enhancing the Google Cloud monitoring receiver to establish a client connection, scrape GCP Cloud Metrics, and transform them into an OpenTelemetry compatible format for pipeline processing. ([#​33762](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33762)) - Implements client connection to Google Cloud Monitoring API. - Scrapes timeseries data based on configured metrics. - Converts the data into OpenTelemetry format for use in the pipeline. - `processor/interval`: Support for gauge and summary metrics. ([#​34803](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34803)) Only the last value of a gauge or summary metric is reported in the interval processor, instead of all values. - `kafkareceiver`: Add support for encoding extensions in the Kafka receiver. ([#​33888](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33888)) This change adds support for encoding extensions in the Kafka receiver. Loading extensions takes precedence over the internally supported encodings. - `datadogexporter`: Add support for setting a custom log source from resource attribute `datadog.log.source` ([#​35051](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35051)) - `opampextension`: Adds the ability to configure the polling interval for the HTTP client. ([#​34749](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34749)) - `otelarrowexporter`: Add gRPC timeout propagation. ([#​34733](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34733)) - `pkg/ottl`: Add `Sort` function to sort array to ascending order or descending order ([#​34200](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34200)) - `exporter/prometheusexpoter`: Support for Prometheus Created Timestamps. ([#​32521](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32521)) - `redactionprocessor`: Add support for logs and metrics ([#​34479](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34479)) - `exceptionsconnector,servicegraphconnector,spanmetricsconnector`: Extract the `getDimensionValue` function as a common function. ([#​34627](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34627)) - `sqlqueryreceiver`: Support populating log attributes from sql query ([#​24459](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/24459)) - `opampsupervisor`: Add new config parameter `agent.health_check_port` to allow configuring the port used by the agent healthcheck extension. ([#​34643](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34643)) ##### 🧰 Bug fixes 🧰 - `apachereceiver`: Fix panic on invalid endpoint configuration ([#​34992](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34992)) - `deltatocumulative`: drop bad samples ([#​34979](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34979)) removes bad (rejected) samples from output. previously identified and metric-tracked those as such, but didn't actually drop them. - `elasticsearchexporter`: Fix dynamic mapping for double values storing integers ([#​34680](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34680)) - `elasticsearchexporter`: Stringify attribute array values in metrics OTel mode ([#​35004](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35004)) Elasticsearch TSDB does not support array dimensions. Workaround it by stringifying attribute array values in OTel mapping mode for metrics. - `fileconsumer`: Fix bug where max_concurrent_files could not be set to 1. ([#​35080](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35080)) - `servicegraphconnector`: Fix incorrectly reversed latency settings for the server and client ([#​34933](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34933)) - `hostmetricsreceiver`: In filesystem scraper, do not prefix partitions when using the environment variable HOST_PROC_MOUNTINFO ([#​35043](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35043)) - `splunkhecreceiver`: Fix memory leak when the receiver is used for both metrics and logs at the same time ([#​34886](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34886)) - `geoipprocessor`: Avoid using internal empty attribute.Set pointer ([#​34882](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34882)) - `pkg/stanza`: Synchronize shutdown in stanza adapter ([#​31074](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/31074)) Stanza-based receivers should now flush all data before shutting down - `sqlserverreceiver`: Fix bug where metrics were being emitted with the wrong database name resource attribute ([#​35036](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35036)) - `signalfxexporter`: Fix memory leak by re-organizing the exporter's functionality lifecycle ([#​32781](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32781)) - `otlpjsonconnector`: Handle OTLPJSON unmarshal error ([#​34782](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34782)) - `mysqlreceiver`: mysql client raise error when the TABLE_ROWS column is NULL, convert NULL to int64 ([#​34195](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34195)) - `pkg/stanza`: An operator configured with silent errors shouldn't log errors while processing log entries. ([#​35008](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35008)) - `datadogexporter`: Use correct hostname for logs when using Datadog Agent logs pipeline with a gateway deployment. ([#​35058](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35058)) </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 this update 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:eyJjcmVhdGVkSW5WZXIiOiIzOC41OS4yIiwidXBkYXRlZEluVmVyIjoiMzguNTkuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIiwicmVub3ZhdGVib3QiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
mx-psi
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Sep 11, 2024
…ib/internal/common to v0.109.0 (#35127) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/internal/common](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/internal/common)</summary> ### [`v0.109.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01090) [Compare Source](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.108.0...v0.109.0) ##### 🛑 Breaking changes 🛑 - `clickhouseexporter`: Upgrade trace SpanKind and StatusCode string values ([#​34799](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34799)) This change updates the output of the trace SpanKind and StatusCode fields to be consistent with the specification's enum values. While this change will not break any deployments, it may affect queries dependent on the old enum names. For more details on old->new values, see this related PR: [https://github.com/open-telemetry/opentelemetry-collector/pull/6250](https://redirect.github.com/open-telemetry/opentelemetry-collector/pull/6250)6250 - `spanmetricsconnector`: Improve consistency between metrics generated by spanmetricsconnector. Added traces.span.metrics as default namespace ([#​33227](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33227), [#​32818](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32818)) Default namespace for the generated metrics is traces.span.metrics now. | The deprecated metrics are: calls, duration and events. | The feature flag connector.spanmetrics.legacyLatencyMetricNames was added to revert the behavior. - `servicegraphconnector`: Fix histogram metrics miss unit ([#​34511](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34511)) All metrics will remove the suffix `_seconds`. It will not introduce breaking change if users use | `prometheusexporter` or `prometheusremotewriteexporter` to exporter metrics in pipeline. | In some cases, like using `clickhouseexporter`(save data in native OTLP format), it will be a breaking change. | Users can use `transformprocessor` to add back this suffix. - `gitproviderreceiver`: The Git Provider Receiver has been renamed to GitHub Receiver. ([#​34731](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34731)) This rename was to better match the OpenTelemetry semantic convention changes in v1.27.0 and allows for Traces and Log signals to be added to this component. Traces as mentioned in issue [#​27460](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27460) will be added in a future release to this component. - `ottl`: Remove tracing from OTTL due to performance concerns ([#​34910](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34910)) - `vcenterreceiver`: Updated units on several metrics to be more in line with documented semantics. ([#​34946](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34946)) The following are the metrics with their respective unit changes: - vcenter.datacenter.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.effective ({MHz} -> MHz) - vcenter.cluster.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.cluster.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.host.network.packet.error.rate ({errors/sec} -> {errors/s}) - vcenter.host.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.host.network.packet.drop.rate ({packets/sec} -> {packets/s}) - vcenter.host.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.host.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.resource_pool.cpu.usage ({MHz} -> MHz) - vcenter.vm.network.throughput (By/sec -> By/s) - vcenter.vm.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.vm.vsan.operations ({operations/sec} -> {operations/s}) ##### 🚩 Deprecations 🚩 - `instanaexporter`: Marking instanaexporter module as deprecated ([#​34994](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34994)) ##### 💡 Enhancements 💡 - `pkg/ottl`: Added Decode() converter function ([#​32493](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32493)) - `testbed`: Add test case scenarios to handle large files to existing testbed. ([#​34288](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34288)) - `filestorage`: Add directory validation for compaction on-rebound ([#​35114](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35114)) - `windowseventlogreceiver`: Avoid rendering the whole event to obtain the provider name ([#​34755](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34755)) - `datadogreceiver`: add support for sketch metrics in Datadog receiver ([#​18278](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/18278)) - `datadogconnector`: Optimize Datadog connector when there are many peer tags and `connector.datadogconnector.NativeIngest` is enabled ([#​34945](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34945)) `connector.datadogconnector.NativeIngest` is currently enabled by default - `splunkhecexporter`: Drop empty log events ([#​34871](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34871)) Log records with no body are dropped by Splunk on reception as they contain no log message, albeit they may have attributes. This PR removes those logs from consideration to be exported. This is in tune with the behavior of splunkhecreceiver, which refuses HEC events with no event ([#​19769](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/19769)) - `elasticsearchexporter`: Add exponential histogram support ([#​34813](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34813)) - `elasticsearchexporter`: Add span event support to traces OTel mapping mode ([#​34831](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34831)) Span events are now supported in OTel mapping mode. They will be routed to `logs-${data_stream.dataset}-${data_stream.namespace}` if `traces_dynamic_index::enabled` is `true`. - `transformprocessor`: Support aggregating metrics based on their attribute values and substituting the values with a new value. ([#​16224](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/16224)) - `kafkareceiver`: Adds tunable fetch sizes to Kafka Receiver ([#​22741](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/22741), [#​34431](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34431)) Adds the ability to tune the minumum, default and maximum fetch sizes for the Kafka Receiver - `solarwindsapmsettingsextension`: Added logic for refresh function ([#​27668](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27668)) - `githubreceiver`: Promote GitHub receiver metrics to alpha status. ([#​34960](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34960)) - `googlecloudmonitoringreceiver`: Enhancing the Google Cloud monitoring receiver to establish a client connection, scrape GCP Cloud Metrics, and transform them into an OpenTelemetry compatible format for pipeline processing. ([#​33762](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33762)) - Implements client connection to Google Cloud Monitoring API. - Scrapes timeseries data based on configured metrics. - Converts the data into OpenTelemetry format for use in the pipeline. - `processor/interval`: Support for gauge and summary metrics. ([#​34803](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34803)) Only the last value of a gauge or summary metric is reported in the interval processor, instead of all values. - `kafkareceiver`: Add support for encoding extensions in the Kafka receiver. ([#​33888](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33888)) This change adds support for encoding extensions in the Kafka receiver. Loading extensions takes precedence over the internally supported encodings. - `datadogexporter`: Add support for setting a custom log source from resource attribute `datadog.log.source` ([#​35051](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35051)) - `opampextension`: Adds the ability to configure the polling interval for the HTTP client. ([#​34749](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34749)) - `otelarrowexporter`: Add gRPC timeout propagation. ([#​34733](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34733)) - `pkg/ottl`: Add `Sort` function to sort array to ascending order or descending order ([#​34200](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34200)) - `exporter/prometheusexpoter`: Support for Prometheus Created Timestamps. ([#​32521](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32521)) - `redactionprocessor`: Add support for logs and metrics ([#​34479](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34479)) - `exceptionsconnector,servicegraphconnector,spanmetricsconnector`: Extract the `getDimensionValue` function as a common function. ([#​34627](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34627)) - `sqlqueryreceiver`: Support populating log attributes from sql query ([#​24459](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/24459)) - `opampsupervisor`: Add new config parameter `agent.health_check_port` to allow configuring the port used by the agent healthcheck extension. ([#​34643](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34643)) ##### 🧰 Bug fixes 🧰 - `apachereceiver`: Fix panic on invalid endpoint configuration ([#​34992](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34992)) - `deltatocumulative`: drop bad samples ([#​34979](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34979)) removes bad (rejected) samples from output. previously identified and metric-tracked those as such, but didn't actually drop them. - `elasticsearchexporter`: Fix dynamic mapping for double values storing integers ([#​34680](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34680)) - `elasticsearchexporter`: Stringify attribute array values in metrics OTel mode ([#​35004](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35004)) Elasticsearch TSDB does not support array dimensions. Workaround it by stringifying attribute array values in OTel mapping mode for metrics. - `fileconsumer`: Fix bug where max_concurrent_files could not be set to 1. ([#​35080](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35080)) - `servicegraphconnector`: Fix incorrectly reversed latency settings for the server and client ([#​34933](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34933)) - `hostmetricsreceiver`: In filesystem scraper, do not prefix partitions when using the environment variable HOST_PROC_MOUNTINFO ([#​35043](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35043)) - `splunkhecreceiver`: Fix memory leak when the receiver is used for both metrics and logs at the same time ([#​34886](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34886)) - `geoipprocessor`: Avoid using internal empty attribute.Set pointer ([#​34882](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34882)) - `pkg/stanza`: Synchronize shutdown in stanza adapter ([#​31074](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/31074)) Stanza-based receivers should now flush all data before shutting down - `sqlserverreceiver`: Fix bug where metrics were being emitted with the wrong database name resource attribute ([#​35036](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35036)) - `signalfxexporter`: Fix memory leak by re-organizing the exporter's functionality lifecycle ([#​32781](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32781)) - `otlpjsonconnector`: Handle OTLPJSON unmarshal error ([#​34782](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34782)) - `mysqlreceiver`: mysql client raise error when the TABLE_ROWS column is NULL, convert NULL to int64 ([#​34195](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34195)) - `pkg/stanza`: An operator configured with silent errors shouldn't log errors while processing log entries. ([#​35008](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35008)) - `datadogexporter`: Use correct hostname for logs when using Datadog Agent logs pipeline with a gateway deployment. ([#​35058](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35058)) </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 this update 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:eyJjcmVhdGVkSW5WZXIiOiIzOC41OS4yIiwidXBkYXRlZEluVmVyIjoiMzguNTkuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIiwicmVub3ZhdGVib3QiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this pull request
Sep 12, 2024
open-telemetry#34799) **Description:** Trace `SpanKind` and `StatusCode` are exporting [old enum values](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/04b3b9898b242c0b3b707bc043c025eb9f6f73ba/internal/coreinternal/traceutil/traceutil.go#L13-L47). This change will make these fields consistent with the specification. I have marked this as a breaking change since it may affect queries that filter by these strings. There should be no change to exporter deployments, only to the read queries. See above/below links for more information as well as a sample of the old vs new values. Example: `STATUS_CODE_ERROR` -> `Error` **Link to tracking Issue:** - open-telemetry/opentelemetry-collector#6250 - open-telemetry/opentelemetry-collector#6251 **Testing:** - Updated integration tests
yurishkuro
referenced
this pull request
in jaegertracing/jaeger
Sep 22, 2024
) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/exporter/prometheusexporter](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/extension/healthcheckv2extension](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/extension/storage](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/pkg/translator/jaeger](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/processor/tailsamplingprocessor](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/receiver/jaegerreceiver](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/receiver/kafkareceiver](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/receiver/zipkinreceiver](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib) | `v0.108.0` -> `v0.109.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/) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter)</summary> ### [`v0.109.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01090) [Compare Source](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.108.0...v0.109.0) ##### 🛑 Breaking changes 🛑 - `clickhouseexporter`: Upgrade trace SpanKind and StatusCode string values ([#​34799](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34799)) This change updates the output of the trace SpanKind and StatusCode fields to be consistent with the specification's enum values. While this change will not break any deployments, it may affect queries dependent on the old enum names. For more details on old->new values, see this related PR: [https://github.com/open-telemetry/opentelemetry-collector/pull/6250](https://redirect.github.com/open-telemetry/opentelemetry-collector/pull/6250)6250 - `spanmetricsconnector`: Improve consistency between metrics generated by spanmetricsconnector. Added traces.span.metrics as default namespace ([#​33227](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33227), [#​32818](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32818)) Default namespace for the generated metrics is traces.span.metrics now. | The deprecated metrics are: calls, duration and events. | The feature flag connector.spanmetrics.legacyLatencyMetricNames was added to revert the behavior. - `servicegraphconnector`: Fix histogram metrics miss unit ([#​34511](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34511)) All metrics will remove the suffix `_seconds`. It will not introduce breaking change if users use | `prometheusexporter` or `prometheusremotewriteexporter` to exporter metrics in pipeline. | In some cases, like using `clickhouseexporter`(save data in native OTLP format), it will be a breaking change. | Users can use `transformprocessor` to add back this suffix. - `gitproviderreceiver`: The Git Provider Receiver has been renamed to GitHub Receiver. ([#​34731](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34731)) This rename was to better match the OpenTelemetry semantic convention changes in v1.27.0 and allows for Traces and Log signals to be added to this component. Traces as mentioned in issue [#​27460](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27460) will be added in a future release to this component. - `ottl`: Remove tracing from OTTL due to performance concerns ([#​34910](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34910)) - `vcenterreceiver`: Updated units on several metrics to be more in line with documented semantics. ([#​34946](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34946)) The following are the metrics with their respective unit changes: - vcenter.datacenter.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.limit ({MHz} -> MHz) - vcenter.cluster.cpu.effective ({MHz} -> MHz) - vcenter.cluster.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.cluster.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.host.network.packet.error.rate ({errors/sec} -> {errors/s}) - vcenter.host.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.host.network.packet.drop.rate ({packets/sec} -> {packets/s}) - vcenter.host.vsan.operations ({operations/sec} -> {operations/s}) - vcenter.host.vsan.congestions ({congestions/sec} -> {congestions/s}) - vcenter.resource_pool.cpu.usage ({MHz} -> MHz) - vcenter.vm.network.throughput (By/sec -> By/s) - vcenter.vm.network.packet.rate ({packets/sec} -> {packets/s}) - vcenter.vm.vsan.operations ({operations/sec} -> {operations/s}) ##### 🚩 Deprecations 🚩 - `instanaexporter`: Marking instanaexporter module as deprecated ([#​34994](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34994)) ##### 💡 Enhancements 💡 - `pkg/ottl`: Added Decode() converter function ([#​32493](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32493)) - `testbed`: Add test case scenarios to handle large files to existing testbed. ([#​34288](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34288)) - `filestorage`: Add directory validation for compaction on-rebound ([#​35114](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35114)) - `windowseventlogreceiver`: Avoid rendering the whole event to obtain the provider name ([#​34755](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34755)) - `datadogreceiver`: add support for sketch metrics in Datadog receiver ([#​18278](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/18278)) - `datadogconnector`: Optimize Datadog connector when there are many peer tags and `connector.datadogconnector.NativeIngest` is enabled ([#​34945](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34945)) `connector.datadogconnector.NativeIngest` is currently enabled by default - `splunkhecexporter`: Drop empty log events ([#​34871](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34871)) Log records with no body are dropped by Splunk on reception as they contain no log message, albeit they may have attributes. This PR removes those logs from consideration to be exported. This is in tune with the behavior of splunkhecreceiver, which refuses HEC events with no event ([#​19769](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/19769)) - `elasticsearchexporter`: Add exponential histogram support ([#​34813](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34813)) - `elasticsearchexporter`: Add span event support to traces OTel mapping mode ([#​34831](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34831)) Span events are now supported in OTel mapping mode. They will be routed to `logs-${data_stream.dataset}-${data_stream.namespace}` if `traces_dynamic_index::enabled` is `true`. - `transformprocessor`: Support aggregating metrics based on their attribute values and substituting the values with a new value. ([#​16224](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/16224)) - `kafkareceiver`: Adds tunable fetch sizes to Kafka Receiver ([#​22741](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/22741), [#​34431](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34431)) Adds the ability to tune the minumum, default and maximum fetch sizes for the Kafka Receiver - `solarwindsapmsettingsextension`: Added logic for refresh function ([#​27668](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/27668)) - `githubreceiver`: Promote GitHub receiver metrics to alpha status. ([#​34960](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34960)) - `googlecloudmonitoringreceiver`: Enhancing the Google Cloud monitoring receiver to establish a client connection, scrape GCP Cloud Metrics, and transform them into an OpenTelemetry compatible format for pipeline processing. ([#​33762](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33762)) - Implements client connection to Google Cloud Monitoring API. - Scrapes timeseries data based on configured metrics. - Converts the data into OpenTelemetry format for use in the pipeline. - `processor/interval`: Support for gauge and summary metrics. ([#​34803](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34803)) Only the last value of a gauge or summary metric is reported in the interval processor, instead of all values. - `kafkareceiver`: Add support for encoding extensions in the Kafka receiver. ([#​33888](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/33888)) This change adds support for encoding extensions in the Kafka receiver. Loading extensions takes precedence over the internally supported encodings. - `datadogexporter`: Add support for setting a custom log source from resource attribute `datadog.log.source` ([#​35051](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35051)) - `opampextension`: Adds the ability to configure the polling interval for the HTTP client. ([#​34749](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34749)) - `otelarrowexporter`: Add gRPC timeout propagation. ([#​34733](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34733)) - `pkg/ottl`: Add `Sort` function to sort array to ascending order or descending order ([#​34200](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34200)) - `exporter/prometheusexpoter`: Support for Prometheus Created Timestamps. ([#​32521](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32521)) - `redactionprocessor`: Add support for logs and metrics ([#​34479](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34479)) - `exceptionsconnector,servicegraphconnector,spanmetricsconnector`: Extract the `getDimensionValue` function as a common function. ([#​34627](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34627)) - `sqlqueryreceiver`: Support populating log attributes from sql query ([#​24459](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/24459)) - `opampsupervisor`: Add new config parameter `agent.health_check_port` to allow configuring the port used by the agent healthcheck extension. ([#​34643](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34643)) ##### 🧰 Bug fixes 🧰 - `apachereceiver`: Fix panic on invalid endpoint configuration ([#​34992](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34992)) - `deltatocumulative`: drop bad samples ([#​34979](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34979)) removes bad (rejected) samples from output. previously identified and metric-tracked those as such, but didn't actually drop them. - `elasticsearchexporter`: Fix dynamic mapping for double values storing integers ([#​34680](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34680)) - `elasticsearchexporter`: Stringify attribute array values in metrics OTel mode ([#​35004](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35004)) Elasticsearch TSDB does not support array dimensions. Workaround it by stringifying attribute array values in OTel mapping mode for metrics. - `fileconsumer`: Fix bug where max_concurrent_files could not be set to 1. ([#​35080](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35080)) - `servicegraphconnector`: Fix incorrectly reversed latency settings for the server and client ([#​34933](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34933)) - `hostmetricsreceiver`: In filesystem scraper, do not prefix partitions when using the environment variable HOST_PROC_MOUNTINFO ([#​35043](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35043)) - `splunkhecreceiver`: Fix memory leak when the receiver is used for both metrics and logs at the same time ([#​34886](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34886)) - `geoipprocessor`: Avoid using internal empty attribute.Set pointer ([#​34882](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34882)) - `pkg/stanza`: Synchronize shutdown in stanza adapter ([#​31074](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/31074)) Stanza-based receivers should now flush all data before shutting down - `sqlserverreceiver`: Fix bug where metrics were being emitted with the wrong database name resource attribute ([#​35036](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35036)) - `signalfxexporter`: Fix memory leak by re-organizing the exporter's functionality lifecycle ([#​32781](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/32781)) - `otlpjsonconnector`: Handle OTLPJSON unmarshal error ([#​34782](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34782)) - `mysqlreceiver`: mysql client raise error when the TABLE_ROWS column is NULL, convert NULL to int64 ([#​34195](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/34195)) - `pkg/stanza`: An operator configured with silent errors shouldn't log errors while processing log entries. ([#​35008](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35008)) - `datadogexporter`: Use correct hostname for logs when using Datadog Agent logs pipeline with a gateway deployment. ([#​35058](https://redirect.github.com/open-telemetry/opentelemetry-collector-contrib/issues/35058)) </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 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/jaegertracing/jaeger). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC41OS4yIiwidXBkYXRlZEluVmVyIjoiMzguODAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiY2hhbmdlbG9nOmRlcGVuZGVuY2llcyJdfQ==--> Signed-off-by: Mend Renovate <bot@renovateapp.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update values returned by all String methods of enum types to a consistent short form representing the enum identifier.
The following methods don't rely on proto enum constant names anymore and return values consistent with other pdata enums:
plog.SeverityNumber.String() now returns:
ptrace.SpanKind.String() now returns:
ptrace.StatusCode.String() now returns:
This change represents the approach A described in #6251