[pkg/otlp/attributes] Add Kubernetes DD tags to keep #334
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
songy23
reviewed
May 22, 2024
| @@ -95,39 +95,77 @@ var ( | |||
|
|
|||
| // Kubernetes out of the box Datadog tags | |||
| // https://docs.datadoghq.com/containers/kubernetes/tag/?tab=containerizedagent#out-of-the-box-tags | |||
| // https://github.com/DataDog/datadog-agent/blob/d33d042d6786e8b85f72bb627fbf06ad8a658031/comp/core/tagger/taggerimpl/collectors/workloadmeta_extract.go | |||
There was a problem hiding this comment.
Can we expose those constants and use them here? Am concerned about the tags diverge moving forward
There was a problem hiding this comment.
That might be difficult because comp/core/tagger isn't a module. We could ask container platform if it's possible to create a separate module for storing these constants
There was a problem hiding this comment.
OK, probably worth leaving an issue or ticket to track it. Would be good to keep those constants in a single source of truth
songy23
approved these changes
May 22, 2024
| @@ -95,39 +95,77 @@ var ( | |||
|
|
|||
| // Kubernetes out of the box Datadog tags | |||
| // https://docs.datadoghq.com/containers/kubernetes/tag/?tab=containerizedagent#out-of-the-box-tags | |||
| // https://github.com/DataDog/datadog-agent/blob/d33d042d6786e8b85f72bb627fbf06ad8a658031/comp/core/tagger/taggerimpl/collectors/workloadmeta_extract.go | |||
There was a problem hiding this comment.
OK, probably worth leaving an issue or ticket to track it. Would be good to keep those constants in a single source of truth
Merged
yurishkuro
referenced
this pull request
in jaegertracing/jaeger
Jul 2, 2024
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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/kafkaexporter](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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/connector/spanmetricsconnector)</summary> ### [`v0.104.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01040) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.103.0...v0.104.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: removed compress_encoding ([#​33604](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33604)) - `exporter/clickhouse`: Change behavior of how default database is read from the config ([#​33693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33693)) Changed the default `database` to `default`. The final database will prioritize `endpoint`, unless `database` is set to a value not equal to `default`. If neither are specified then it defaults to the `default` database. Possible breaking change if someone has the DSN configured in combination with `database` config option. - `exporter/clickhouse`: Add `async_insert` config option to enable inserting asynchronously by default. ([#​33614](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33614)) Adds `async_insert` config option to enable inserting asynchronously by default. To preserve the previous behavior, set `async_insert` to `false` in your config. When enabled, the exporter will insert asynchronously, which can improve performance for high-throughput deployments. The `async_insert` option can be set to `true` or `false` to enable or disable async inserts, respectively. The default value is `true`. Keep in mind this setting is added since the exporter now sets it to default. Async insert and its related settings can still be defined in `endpoint` and `connection_params`, which take priority over the new config option. - `clickhouseexporter`: Add `AggregationTemporality` column to histogram and exponential histogram tables. Rename `AggTemp` column to `AggregationTemporality` in sum table. ([#​33424](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33424)) It's a breaking change. users who upgrade to the latest version need to alter the Clickhouse table: ```sql ALTER TABLE otel_metrics_exponential_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_sum RENAME COLUMN AggTemp TO AggregationTemporality; ``` - `exporter/clickhouse`: Remove deprecated `ttl_days` config option, use `ttl` instead. ([#​33648](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33648)) - `vcenterreceiver`: Drops support for vCenter 6.7 ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `all`: Promote `component.UseLocalHostAsDefaultHost` feature gate to beta. This changes default endpoints from 0.0.0.0 to localhost ([#​30702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30702)) This change affects the following components: - extension/awsproxy - extension/health_check - extension/health_checkv2 - extension/jaegerremotesampling - internal/aws/proxy - processor/remotetap - receiver/awsfirehose - receiver/awsxray - receiver/influxdb - receiver/jaeger - receiver/loki - receiver/opencensus - receiver/sapm - receiver/signalfx - receiver/skywalking - receiver/splunk_hec - receiver/zipkin - receiver/zookeeper - `receiver/mongodb`: Graduate receiver.mongodb.removeDatabaseAttr feature gate to stable ([#​24972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24972)) ##### 🚩 Deprecations 🚩 - `exporter/elasticsearch`: Deprecate the "dedot" configuration. ([#​33772](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33772)) dedot has been deprecated, and will always be enabled in ECS mode and disabled for other modes in future - `exporter/elasticsearch`: Deprecate the "dedup" configuration. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) dedup has been deprecated, and will always be enabled in future. ##### 🚀 New components 🚀 - `otelarrow`: OTel-Arrow exporter and receiver are marked alpha, added to otelcontribcol ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `exporter/elasticsearch`: Add initial support for metrics ([#​33513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33513)) - `elasticsearchexporter`: Add translation for k8s.deployment.name resource attribute ([#​33622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33622)) - `k8sattributesprocessor`: Add support for exposing `k8s.pod.ip` as a resource attribute ([#​32960](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32960)) - `geoipprocessor`: Add MaxMind geoip provider for GeoIP2-City and GeoLite2-City databases. ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `vcenterreceiver`: Adds vCenter CPU readiness metric for VMs. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `awsemfexporter`: AWS EMF Exporter to add AppSignals metadata flag into the user-agent ([#​32998](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32998)) - `receiver/mongodb`: Ensure support of 6.0 and 7.0 MongoDB versions with integration tests ([#​32716](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32716)) - `sumologicexporter`: added timeout validation ([#​33151](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33151)) - `clickhouseexporter`: Updated the default logs table to a more optimized schema ([#​33611](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33611)) Simplified data types, improved partitioning and time range queries. - `datadogconnector`: Add a feature gate `connector.datadogconnector.NativeIngest` that enables datadog connector to use the new native OTel API in APM stats computation. ([#​33297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33297)) The feature gate `connector.datadogconnector.NativeIngest` is disabled by default. - `datadogexporter`: Adds Kubernetes DD tags to keep when mapping resource attributes ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/334](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/334)/334 for details. - `exporter/elasticsearch`: Add data stream routing ([#​33794](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33794), [#​33756](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33756)) `data_stream.dataset` and `data_stream.namespace` in attributes will be respected when config `*_dynamic_index.enabled` is true. - `exporter/elasticsearch`: Encode metrics resource attributes in ECS mapping mode ([#​33823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33823)) - `elasticsearchexporter`: Preserve `host.name` resource attribute in ECS mode ([#​33670](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33670)) - `servicegraphprocessor`: Added a new configuration option `enable_virtual_node_label` to allow users to identify which node is the virtual node in each edge of the service graph. ([#​31889](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31889)) - `pkg/stanza`: Switch JSON parser used by json_parser to github.com/goccy/go-json ([#​33784](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33784)) - `k8sobserver`: Add support for k8s.ingress endpoint. ([#​32971](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32971)) - `statsdreceiver`: Optimize statsdreceiver to reduce object allocations ([#​33683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33683)) - `routingprocessor`: Use mdatagen to define the component's telemetry ([#​33526](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33526)) - `loadbalancerexporter`: Refactors how the load balancing exporter splits metrics ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) All splitting is *behaviorally*, the same. However, the `resource` routingID now uses the `internal/exp/metrics/identity` package to generate the load balancing key, instead of bespoke code. This means that when upgrading to this version your routes for specific metric groupings could change. However, this will be stable and all future metrics will follow the new routing - `receiver/mongodbreceiver`: Add `server.address` and `server.port` resource attributes to MongoDB receiver. ([#​32810](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32810), [#​32350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32350)) The new resource attributes are added to the MongoDB receiver to distinguish metrics coming from different MongoDB instances. - `server.address`: The address of the MongoDB host, enabled by default. - `server.port`: The port of the MongoDB host, disabled by default. - `observerextension`: Expose host and port in endpoint's environment ([#​33571](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33571)) - `rabbitmqexporter`: Promote rabbitmqexporter to alpha. ([#​33331](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33331)) - `pkg/ottl`: Add a `schema_url` field to access the SchemaURL in resources and scopes on all signals ([#​30229](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30229)) - `solacereceiver`: Renamed some SemConv fields to support latest semantic conventions for messaging spans (version `1.25.0`) ([#​33499](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33499)) - `sqlserverreceiver`: Enable more perf counter metrics when directly connecting to SQL Server ([#​33420](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33420)) This enables the following metrics by default on non Windows-based systems: `sqlserver.batch.request.rate` `sqlserver.batch.sql_compilation.rate` `sqlserver.batch.sql_recompilation.rate` `sqlserver.page.buffer_cache.hit_ratio` `sqlserver.user.connection.count` - `extension/googleclientauth`: Add Google-signed ID token support ([#​33185](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33185)) Update github.com/GoogleCloudPlatform/opentelemetry-operations-go/extension/googleclientauth to v0.48.0. With this update, extension/googleclientauth now supports Google-signed ID token as auth header. - `vcenterreceiver`: Adds vCenter CPU capacity and network drop rate metrics to hosts. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) ##### 🧰 Bug fixes 🧰 - `resourcedetectionprocessor`: Fetch CPU info only if related attributes are enabled ([#​33774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33774)) - `datasetexporter`: Upgrade dataset-go to v0.19.0 and fix found issues ([#​33498](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33498), [#​32533](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32533), [#​33675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33675)) Upgrade `dataset-go` library from v0.18.0 to v0.19.0. Enable skipped integration test and adjust the test so it is passing again. Do not validate configuration, let the framework run the validation. - `datasetexporter`: Upgrade dataset-go to v0.20.0 ([#​33812](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33812)) Upgrade `dataset-go` library from v0.19.0 to v0.20.0. Make number of outgoing connections configurable. - `datadogexporter`: Fix panics on invalid sized trace & span IDs ([#​33566](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33566)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/340](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/340)/340 for details. - `datadogexporter`: Ignore metric datapoints with `no recorded value` flag ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) This flag is not supported by Datadog, so we just ignore these datapoints. [https://github.com/DataDog/opentelemetry-mapping-go/pull/330](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/330)/330 for details. - `tailsamplingprocessor`: Fix precedence of inverted match in and policy ([#​33671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33671)) Previously if the decision from a policy evaluation was `NotSampled` or `InvertNotSampled` it would return a `NotSampled` decision regardless, effectively downgrading the result. This was breaking the documented behaviour that inverted decisions should take precedence over all others. - `otelarrowreceiver`: Ensure consume operations are not canceled at stream EOF. ([#​33570](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33570)) - `vcenterreceiver`: Fixes errors in some of the client calls for environments containing multiple datacenters. ([#​33734](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33734)) </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 has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/jaegertracing/jaeger). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJjaGFuZ2Vsb2c6ZGVwZW5kZW5jaWVzIl19--> Signed-off-by: Mend Renovate <bot@renovateapp.com>
mx-psi
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Jul 2, 2024
…ib/internal/common to v0.104.0 (#33851) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/internal/common](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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.104.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01040) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.103.0...v0.104.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: removed compress_encoding ([#​33604](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33604)) - `exporter/clickhouse`: Change behavior of how default database is read from the config ([#​33693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33693)) Changed the default `database` to `default`. The final database will prioritize `endpoint`, unless `database` is set to a value not equal to `default`. If neither are specified then it defaults to the `default` database. Possible breaking change if someone has the DSN configured in combination with `database` config option. - `exporter/clickhouse`: Add `async_insert` config option to enable inserting asynchronously by default. ([#​33614](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33614)) Adds `async_insert` config option to enable inserting asynchronously by default. To preserve the previous behavior, set `async_insert` to `false` in your config. When enabled, the exporter will insert asynchronously, which can improve performance for high-throughput deployments. The `async_insert` option can be set to `true` or `false` to enable or disable async inserts, respectively. The default value is `true`. Keep in mind this setting is added since the exporter now sets it to default. Async insert and its related settings can still be defined in `endpoint` and `connection_params`, which take priority over the new config option. - `clickhouseexporter`: Add `AggregationTemporality` column to histogram and exponential histogram tables. Rename `AggTemp` column to `AggregationTemporality` in sum table. ([#​33424](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33424)) It's a breaking change. users who upgrade to the latest version need to alter the Clickhouse table: ```sql ALTER TABLE otel_metrics_exponential_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_sum RENAME COLUMN AggTemp TO AggregationTemporality; ``` - `exporter/clickhouse`: Remove deprecated `ttl_days` config option, use `ttl` instead. ([#​33648](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33648)) - `vcenterreceiver`: Drops support for vCenter 6.7 ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `all`: Promote `component.UseLocalHostAsDefaultHost` feature gate to beta. This changes default endpoints from 0.0.0.0 to localhost ([#​30702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30702)) This change affects the following components: - extension/awsproxy - extension/health_check - extension/health_checkv2 - extension/jaegerremotesampling - internal/aws/proxy - processor/remotetap - receiver/awsfirehose - receiver/awsxray - receiver/influxdb - receiver/jaeger - receiver/loki - receiver/opencensus - receiver/sapm - receiver/signalfx - receiver/skywalking - receiver/splunk_hec - receiver/zipkin - receiver/zookeeper - `receiver/mongodb`: Graduate receiver.mongodb.removeDatabaseAttr feature gate to stable ([#​24972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24972)) ##### 🚩 Deprecations 🚩 - `exporter/elasticsearch`: Deprecate the "dedot" configuration. ([#​33772](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33772)) dedot has been deprecated, and will always be enabled in ECS mode and disabled for other modes in future - `exporter/elasticsearch`: Deprecate the "dedup" configuration. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) dedup has been deprecated, and will always be enabled in future. ##### 🚀 New components 🚀 - `otelarrow`: OTel-Arrow exporter and receiver are marked alpha, added to otelcontribcol ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `exporter/elasticsearch`: Add initial support for metrics ([#​33513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33513)) - `elasticsearchexporter`: Add translation for k8s.deployment.name resource attribute ([#​33622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33622)) - `k8sattributesprocessor`: Add support for exposing `k8s.pod.ip` as a resource attribute ([#​32960](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32960)) - `geoipprocessor`: Add MaxMind geoip provider for GeoIP2-City and GeoLite2-City databases. ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `vcenterreceiver`: Adds vCenter CPU readiness metric for VMs. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `awsemfexporter`: AWS EMF Exporter to add AppSignals metadata flag into the user-agent ([#​32998](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32998)) - `receiver/mongodb`: Ensure support of 6.0 and 7.0 MongoDB versions with integration tests ([#​32716](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32716)) - `sumologicexporter`: added timeout validation ([#​33151](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33151)) - `clickhouseexporter`: Updated the default logs table to a more optimized schema ([#​33611](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33611)) Simplified data types, improved partitioning and time range queries. - `datadogconnector`: Add a feature gate `connector.datadogconnector.NativeIngest` that enables datadog connector to use the new native OTel API in APM stats computation. ([#​33297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33297)) The feature gate `connector.datadogconnector.NativeIngest` is disabled by default. - `datadogexporter`: Adds Kubernetes DD tags to keep when mapping resource attributes ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/334](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/334)/334 for details. - `exporter/elasticsearch`: Add data stream routing ([#​33794](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33794), [#​33756](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33756)) `data_stream.dataset` and `data_stream.namespace` in attributes will be respected when config `*_dynamic_index.enabled` is true. - `exporter/elasticsearch`: Encode metrics resource attributes in ECS mapping mode ([#​33823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33823)) - `elasticsearchexporter`: Preserve `host.name` resource attribute in ECS mode ([#​33670](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33670)) - `servicegraphprocessor`: Added a new configuration option `enable_virtual_node_label` to allow users to identify which node is the virtual node in each edge of the service graph. ([#​31889](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31889)) - `pkg/stanza`: Switch JSON parser used by json_parser to github.com/goccy/go-json ([#​33784](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33784)) - `k8sobserver`: Add support for k8s.ingress endpoint. ([#​32971](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32971)) - `statsdreceiver`: Optimize statsdreceiver to reduce object allocations ([#​33683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33683)) - `routingprocessor`: Use mdatagen to define the component's telemetry ([#​33526](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33526)) - `loadbalancerexporter`: Refactors how the load balancing exporter splits metrics ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) All splitting is *behaviorally*, the same. However, the `resource` routingID now uses the `internal/exp/metrics/identity` package to generate the load balancing key, instead of bespoke code. This means that when upgrading to this version your routes for specific metric groupings could change. However, this will be stable and all future metrics will follow the new routing - `receiver/mongodbreceiver`: Add `server.address` and `server.port` resource attributes to MongoDB receiver. ([#​32810](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32810), [#​32350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32350)) The new resource attributes are added to the MongoDB receiver to distinguish metrics coming from different MongoDB instances. - `server.address`: The address of the MongoDB host, enabled by default. - `server.port`: The port of the MongoDB host, disabled by default. - `observerextension`: Expose host and port in endpoint's environment ([#​33571](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33571)) - `rabbitmqexporter`: Promote rabbitmqexporter to alpha. ([#​33331](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33331)) - `pkg/ottl`: Add a `schema_url` field to access the SchemaURL in resources and scopes on all signals ([#​30229](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30229)) - `solacereceiver`: Renamed some SemConv fields to support latest semantic conventions for messaging spans (version `1.25.0`) ([#​33499](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33499)) - `sqlserverreceiver`: Enable more perf counter metrics when directly connecting to SQL Server ([#​33420](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33420)) This enables the following metrics by default on non Windows-based systems: `sqlserver.batch.request.rate` `sqlserver.batch.sql_compilation.rate` `sqlserver.batch.sql_recompilation.rate` `sqlserver.page.buffer_cache.hit_ratio` `sqlserver.user.connection.count` - `extension/googleclientauth`: Add Google-signed ID token support ([#​33185](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33185)) Update github.com/GoogleCloudPlatform/opentelemetry-operations-go/extension/googleclientauth to v0.48.0. With this update, extension/googleclientauth now supports Google-signed ID token as auth header. - `vcenterreceiver`: Adds vCenter CPU capacity and network drop rate metrics to hosts. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) ##### 🧰 Bug fixes 🧰 - `resourcedetectionprocessor`: Fetch CPU info only if related attributes are enabled ([#​33774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33774)) - `datasetexporter`: Upgrade dataset-go to v0.19.0 and fix found issues ([#​33498](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33498), [#​32533](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32533), [#​33675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33675)) Upgrade `dataset-go` library from v0.18.0 to v0.19.0. Enable skipped integration test and adjust the test so it is passing again. Do not validate configuration, let the framework run the validation. - `datasetexporter`: Upgrade dataset-go to v0.20.0 ([#​33812](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33812)) Upgrade `dataset-go` library from v0.19.0 to v0.20.0. Make number of outgoing connections configurable. - `datadogexporter`: Fix panics on invalid sized trace & span IDs ([#​33566](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33566)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/340](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/340)/340 for details. - `datadogexporter`: Ignore metric datapoints with `no recorded value` flag ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) This flag is not supported by Datadog, so we just ignore these datapoints. [https://github.com/DataDog/opentelemetry-mapping-go/pull/330](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/330)/330 for details. - `tailsamplingprocessor`: Fix precedence of inverted match in and policy ([#​33671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33671)) Previously if the decision from a policy evaluation was `NotSampled` or `InvertNotSampled` it would return a `NotSampled` decision regardless, effectively downgrading the result. This was breaking the documented behaviour that inverted decisions should take precedence over all others. - `otelarrowreceiver`: Ensure consume operations are not canceled at stream EOF. ([#​33570](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33570)) - `vcenterreceiver`: Fixes errors in some of the client calls for environments containing multiple datacenters. ([#​33734](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33734)) </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 has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
mx-psi
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Jul 2, 2024
…ib/cmd/telemetrygen to v0.104.0 (#33849) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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.104.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01040) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.103.0...v0.104.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: removed compress_encoding ([#​33604](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33604)) - `exporter/clickhouse`: Change behavior of how default database is read from the config ([#​33693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33693)) Changed the default `database` to `default`. The final database will prioritize `endpoint`, unless `database` is set to a value not equal to `default`. If neither are specified then it defaults to the `default` database. Possible breaking change if someone has the DSN configured in combination with `database` config option. - `exporter/clickhouse`: Add `async_insert` config option to enable inserting asynchronously by default. ([#​33614](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33614)) Adds `async_insert` config option to enable inserting asynchronously by default. To preserve the previous behavior, set `async_insert` to `false` in your config. When enabled, the exporter will insert asynchronously, which can improve performance for high-throughput deployments. The `async_insert` option can be set to `true` or `false` to enable or disable async inserts, respectively. The default value is `true`. Keep in mind this setting is added since the exporter now sets it to default. Async insert and its related settings can still be defined in `endpoint` and `connection_params`, which take priority over the new config option. - `clickhouseexporter`: Add `AggregationTemporality` column to histogram and exponential histogram tables. Rename `AggTemp` column to `AggregationTemporality` in sum table. ([#​33424](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33424)) It's a breaking change. users who upgrade to the latest version need to alter the Clickhouse table: ```sql ALTER TABLE otel_metrics_exponential_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_sum RENAME COLUMN AggTemp TO AggregationTemporality; ``` - `exporter/clickhouse`: Remove deprecated `ttl_days` config option, use `ttl` instead. ([#​33648](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33648)) - `vcenterreceiver`: Drops support for vCenter 6.7 ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `all`: Promote `component.UseLocalHostAsDefaultHost` feature gate to beta. This changes default endpoints from 0.0.0.0 to localhost ([#​30702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30702)) This change affects the following components: - extension/awsproxy - extension/health_check - extension/health_checkv2 - extension/jaegerremotesampling - internal/aws/proxy - processor/remotetap - receiver/awsfirehose - receiver/awsxray - receiver/influxdb - receiver/jaeger - receiver/loki - receiver/opencensus - receiver/sapm - receiver/signalfx - receiver/skywalking - receiver/splunk_hec - receiver/zipkin - receiver/zookeeper - `receiver/mongodb`: Graduate receiver.mongodb.removeDatabaseAttr feature gate to stable ([#​24972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24972)) ##### 🚩 Deprecations 🚩 - `exporter/elasticsearch`: Deprecate the "dedot" configuration. ([#​33772](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33772)) dedot has been deprecated, and will always be enabled in ECS mode and disabled for other modes in future - `exporter/elasticsearch`: Deprecate the "dedup" configuration. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) dedup has been deprecated, and will always be enabled in future. ##### 🚀 New components 🚀 - `otelarrow`: OTel-Arrow exporter and receiver are marked alpha, added to otelcontribcol ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `exporter/elasticsearch`: Add initial support for metrics ([#​33513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33513)) - `elasticsearchexporter`: Add translation for k8s.deployment.name resource attribute ([#​33622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33622)) - `k8sattributesprocessor`: Add support for exposing `k8s.pod.ip` as a resource attribute ([#​32960](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32960)) - `geoipprocessor`: Add MaxMind geoip provider for GeoIP2-City and GeoLite2-City databases. ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `vcenterreceiver`: Adds vCenter CPU readiness metric for VMs. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `awsemfexporter`: AWS EMF Exporter to add AppSignals metadata flag into the user-agent ([#​32998](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32998)) - `receiver/mongodb`: Ensure support of 6.0 and 7.0 MongoDB versions with integration tests ([#​32716](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32716)) - `sumologicexporter`: added timeout validation ([#​33151](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33151)) - `clickhouseexporter`: Updated the default logs table to a more optimized schema ([#​33611](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33611)) Simplified data types, improved partitioning and time range queries. - `datadogconnector`: Add a feature gate `connector.datadogconnector.NativeIngest` that enables datadog connector to use the new native OTel API in APM stats computation. ([#​33297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33297)) The feature gate `connector.datadogconnector.NativeIngest` is disabled by default. - `datadogexporter`: Adds Kubernetes DD tags to keep when mapping resource attributes ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/334](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/334)/334 for details. - `exporter/elasticsearch`: Add data stream routing ([#​33794](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33794), [#​33756](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33756)) `data_stream.dataset` and `data_stream.namespace` in attributes will be respected when config `*_dynamic_index.enabled` is true. - `exporter/elasticsearch`: Encode metrics resource attributes in ECS mapping mode ([#​33823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33823)) - `elasticsearchexporter`: Preserve `host.name` resource attribute in ECS mode ([#​33670](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33670)) - `servicegraphprocessor`: Added a new configuration option `enable_virtual_node_label` to allow users to identify which node is the virtual node in each edge of the service graph. ([#​31889](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31889)) - `pkg/stanza`: Switch JSON parser used by json_parser to github.com/goccy/go-json ([#​33784](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33784)) - `k8sobserver`: Add support for k8s.ingress endpoint. ([#​32971](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32971)) - `statsdreceiver`: Optimize statsdreceiver to reduce object allocations ([#​33683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33683)) - `routingprocessor`: Use mdatagen to define the component's telemetry ([#​33526](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33526)) - `loadbalancerexporter`: Refactors how the load balancing exporter splits metrics ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) All splitting is *behaviorally*, the same. However, the `resource` routingID now uses the `internal/exp/metrics/identity` package to generate the load balancing key, instead of bespoke code. This means that when upgrading to this version your routes for specific metric groupings could change. However, this will be stable and all future metrics will follow the new routing - `receiver/mongodbreceiver`: Add `server.address` and `server.port` resource attributes to MongoDB receiver. ([#​32810](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32810), [#​32350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32350)) The new resource attributes are added to the MongoDB receiver to distinguish metrics coming from different MongoDB instances. - `server.address`: The address of the MongoDB host, enabled by default. - `server.port`: The port of the MongoDB host, disabled by default. - `observerextension`: Expose host and port in endpoint's environment ([#​33571](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33571)) - `rabbitmqexporter`: Promote rabbitmqexporter to alpha. ([#​33331](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33331)) - `pkg/ottl`: Add a `schema_url` field to access the SchemaURL in resources and scopes on all signals ([#​30229](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30229)) - `solacereceiver`: Renamed some SemConv fields to support latest semantic conventions for messaging spans (version `1.25.0`) ([#​33499](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33499)) - `sqlserverreceiver`: Enable more perf counter metrics when directly connecting to SQL Server ([#​33420](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33420)) This enables the following metrics by default on non Windows-based systems: `sqlserver.batch.request.rate` `sqlserver.batch.sql_compilation.rate` `sqlserver.batch.sql_recompilation.rate` `sqlserver.page.buffer_cache.hit_ratio` `sqlserver.user.connection.count` - `extension/googleclientauth`: Add Google-signed ID token support ([#​33185](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33185)) Update github.com/GoogleCloudPlatform/opentelemetry-operations-go/extension/googleclientauth to v0.48.0. With this update, extension/googleclientauth now supports Google-signed ID token as auth header. - `vcenterreceiver`: Adds vCenter CPU capacity and network drop rate metrics to hosts. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) ##### 🧰 Bug fixes 🧰 - `resourcedetectionprocessor`: Fetch CPU info only if related attributes are enabled ([#​33774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33774)) - `datasetexporter`: Upgrade dataset-go to v0.19.0 and fix found issues ([#​33498](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33498), [#​32533](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32533), [#​33675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33675)) Upgrade `dataset-go` library from v0.18.0 to v0.19.0. Enable skipped integration test and adjust the test so it is passing again. Do not validate configuration, let the framework run the validation. - `datasetexporter`: Upgrade dataset-go to v0.20.0 ([#​33812](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33812)) Upgrade `dataset-go` library from v0.19.0 to v0.20.0. Make number of outgoing connections configurable. - `datadogexporter`: Fix panics on invalid sized trace & span IDs ([#​33566](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33566)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/340](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/340)/340 for details. - `datadogexporter`: Ignore metric datapoints with `no recorded value` flag ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) This flag is not supported by Datadog, so we just ignore these datapoints. [https://github.com/DataDog/opentelemetry-mapping-go/pull/330](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/330)/330 for details. - `tailsamplingprocessor`: Fix precedence of inverted match in and policy ([#​33671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33671)) Previously if the decision from a policy evaluation was `NotSampled` or `InvertNotSampled` it would return a `NotSampled` decision regardless, effectively downgrading the result. This was breaking the documented behaviour that inverted decisions should take precedence over all others. - `otelarrowreceiver`: Ensure consume operations are not canceled at stream EOF. ([#​33570](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33570)) - `vcenterreceiver`: Fixes errors in some of the client calls for environments containing multiple datacenters. ([#​33734](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33734)) </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 has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
codeboten
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Jul 9, 2024
…ib/internal/filter to v0.104.0 (#33968) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/internal/filter](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.103.0` -> `v0.104.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/filter)</summary> ### [`v0.104.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01040) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.103.0...v0.104.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: removed compress_encoding ([#​33604](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33604)) - `exporter/clickhouse`: Change behavior of how default database is read from the config ([#​33693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33693)) Changed the default `database` to `default`. The final database will prioritize `endpoint`, unless `database` is set to a value not equal to `default`. If neither are specified then it defaults to the `default` database. Possible breaking change if someone has the DSN configured in combination with `database` config option. - `exporter/clickhouse`: Add `async_insert` config option to enable inserting asynchronously by default. ([#​33614](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33614)) Adds `async_insert` config option to enable inserting asynchronously by default. To preserve the previous behavior, set `async_insert` to `false` in your config. When enabled, the exporter will insert asynchronously, which can improve performance for high-throughput deployments. The `async_insert` option can be set to `true` or `false` to enable or disable async inserts, respectively. The default value is `true`. Keep in mind this setting is added since the exporter now sets it to default. Async insert and its related settings can still be defined in `endpoint` and `connection_params`, which take priority over the new config option. - `clickhouseexporter`: Add `AggregationTemporality` column to histogram and exponential histogram tables. Rename `AggTemp` column to `AggregationTemporality` in sum table. ([#​33424](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33424)) It's a breaking change. users who upgrade to the latest version need to alter the Clickhouse table: ```sql ALTER TABLE otel_metrics_exponential_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_sum RENAME COLUMN AggTemp TO AggregationTemporality; ``` - `exporter/clickhouse`: Remove deprecated `ttl_days` config option, use `ttl` instead. ([#​33648](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33648)) - `vcenterreceiver`: Drops support for vCenter 6.7 ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `all`: Promote `component.UseLocalHostAsDefaultHost` feature gate to beta. This changes default endpoints from 0.0.0.0 to localhost ([#​30702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30702)) This change affects the following components: - extension/awsproxy - extension/health_check - extension/health_checkv2 - extension/jaegerremotesampling - internal/aws/proxy - processor/remotetap - receiver/awsfirehose - receiver/awsxray - receiver/influxdb - receiver/jaeger - receiver/loki - receiver/opencensus - receiver/sapm - receiver/signalfx - receiver/skywalking - receiver/splunk_hec - receiver/zipkin - receiver/zookeeper - `receiver/mongodb`: Graduate receiver.mongodb.removeDatabaseAttr feature gate to stable ([#​24972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24972)) ##### 🚩 Deprecations 🚩 - `exporter/elasticsearch`: Deprecate the "dedot" configuration. ([#​33772](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33772)) dedot has been deprecated, and will always be enabled in ECS mode and disabled for other modes in future - `exporter/elasticsearch`: Deprecate the "dedup" configuration. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) dedup has been deprecated, and will always be enabled in future. ##### 🚀 New components 🚀 - `otelarrow`: OTel-Arrow exporter and receiver are marked alpha, added to otelcontribcol ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `exporter/elasticsearch`: Add initial support for metrics ([#​33513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33513)) - `elasticsearchexporter`: Add translation for k8s.deployment.name resource attribute ([#​33622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33622)) - `k8sattributesprocessor`: Add support for exposing `k8s.pod.ip` as a resource attribute ([#​32960](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32960)) - `geoipprocessor`: Add MaxMind geoip provider for GeoIP2-City and GeoLite2-City databases. ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `vcenterreceiver`: Adds vCenter CPU readiness metric for VMs. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `awsemfexporter`: AWS EMF Exporter to add AppSignals metadata flag into the user-agent ([#​32998](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32998)) - `receiver/mongodb`: Ensure support of 6.0 and 7.0 MongoDB versions with integration tests ([#​32716](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32716)) - `sumologicexporter`: added timeout validation ([#​33151](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33151)) - `clickhouseexporter`: Updated the default logs table to a more optimized schema ([#​33611](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33611)) Simplified data types, improved partitioning and time range queries. - `datadogconnector`: Add a feature gate `connector.datadogconnector.NativeIngest` that enables datadog connector to use the new native OTel API in APM stats computation. ([#​33297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33297)) The feature gate `connector.datadogconnector.NativeIngest` is disabled by default. - `datadogexporter`: Adds Kubernetes DD tags to keep when mapping resource attributes ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/334](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/334)/334 for details. - `exporter/elasticsearch`: Add data stream routing ([#​33794](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33794), [#​33756](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33756)) `data_stream.dataset` and `data_stream.namespace` in attributes will be respected when config `*_dynamic_index.enabled` is true. - `exporter/elasticsearch`: Encode metrics resource attributes in ECS mapping mode ([#​33823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33823)) - `elasticsearchexporter`: Preserve `host.name` resource attribute in ECS mode ([#​33670](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33670)) - `servicegraphprocessor`: Added a new configuration option `enable_virtual_node_label` to allow users to identify which node is the virtual node in each edge of the service graph. ([#​31889](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31889)) - `pkg/stanza`: Switch JSON parser used by json_parser to github.com/goccy/go-json ([#​33784](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33784)) - `k8sobserver`: Add support for k8s.ingress endpoint. ([#​32971](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32971)) - `statsdreceiver`: Optimize statsdreceiver to reduce object allocations ([#​33683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33683)) - `routingprocessor`: Use mdatagen to define the component's telemetry ([#​33526](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33526)) - `loadbalancerexporter`: Refactors how the load balancing exporter splits metrics ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) All splitting is *behaviorally*, the same. However, the `resource` routingID now uses the `internal/exp/metrics/identity` package to generate the load balancing key, instead of bespoke code. This means that when upgrading to this version your routes for specific metric groupings could change. However, this will be stable and all future metrics will follow the new routing - `receiver/mongodbreceiver`: Add `server.address` and `server.port` resource attributes to MongoDB receiver. ([#​32810](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32810), [#​32350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32350)) The new resource attributes are added to the MongoDB receiver to distinguish metrics coming from different MongoDB instances. - `server.address`: The address of the MongoDB host, enabled by default. - `server.port`: The port of the MongoDB host, disabled by default. - `observerextension`: Expose host and port in endpoint's environment ([#​33571](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33571)) - `rabbitmqexporter`: Promote rabbitmqexporter to alpha. ([#​33331](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33331)) - `pkg/ottl`: Add a `schema_url` field to access the SchemaURL in resources and scopes on all signals ([#​30229](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30229)) - `solacereceiver`: Renamed some SemConv fields to support latest semantic conventions for messaging spans (version `1.25.0`) ([#​33499](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33499)) - `sqlserverreceiver`: Enable more perf counter metrics when directly connecting to SQL Server ([#​33420](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33420)) This enables the following metrics by default on non Windows-based systems: `sqlserver.batch.request.rate` `sqlserver.batch.sql_compilation.rate` `sqlserver.batch.sql_recompilation.rate` `sqlserver.page.buffer_cache.hit_ratio` `sqlserver.user.connection.count` - `extension/googleclientauth`: Add Google-signed ID token support ([#​33185](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33185)) Update github.com/GoogleCloudPlatform/opentelemetry-operations-go/extension/googleclientauth to v0.48.0. With this update, extension/googleclientauth now supports Google-signed ID token as auth header. - `vcenterreceiver`: Adds vCenter CPU capacity and network drop rate metrics to hosts. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) ##### 🧰 Bug fixes 🧰 - `resourcedetectionprocessor`: Fetch CPU info only if related attributes are enabled ([#​33774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33774)) - `datasetexporter`: Upgrade dataset-go to v0.19.0 and fix found issues ([#​33498](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33498), [#​32533](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32533), [#​33675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33675)) Upgrade `dataset-go` library from v0.18.0 to v0.19.0. Enable skipped integration test and adjust the test so it is passing again. Do not validate configuration, let the framework run the validation. - `datasetexporter`: Upgrade dataset-go to v0.20.0 ([#​33812](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33812)) Upgrade `dataset-go` library from v0.19.0 to v0.20.0. Make number of outgoing connections configurable. - `datadogexporter`: Fix panics on invalid sized trace & span IDs ([#​33566](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33566)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/340](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/340)/340 for details. - `datadogexporter`: Ignore metric datapoints with `no recorded value` flag ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) This flag is not supported by Datadog, so we just ignore these datapoints. [https://github.com/DataDog/opentelemetry-mapping-go/pull/330](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/330)/330 for details. - `tailsamplingprocessor`: Fix precedence of inverted match in and policy ([#​33671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33671)) Previously if the decision from a policy evaluation was `NotSampled` or `InvertNotSampled` it would return a `NotSampled` decision regardless, effectively downgrading the result. This was breaking the documented behaviour that inverted decisions should take precedence over all others. - `otelarrowreceiver`: Ensure consume operations are not canceled at stream EOF. ([#​33570](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33570)) - `vcenterreceiver`: Fixes errors in some of the client calls for environments containing multiple datacenters. ([#​33734](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33734)) </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 has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
mx-psi
referenced
this pull request
in open-telemetry/opentelemetry-collector-contrib
Jul 23, 2024
](https://renovatebot.com){kind=link}
…ib/pkg/experimentalmetricmetadata to v0.105.0 (#34215) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/pkg/experimentalmetricmetadata](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.0.0-00010101000000-000000000000` -> `v0.105.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/pkg/experimentalmetricmetadata)</summary> ### [`v0.105.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01050) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.104.0...v0.105.0) ##### 🛑 Breaking changes 🛑 - `skywalkingexporter`: Remove unmaintained component ([#​23796](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/23796)) - `elasticsearchexporter`: Make "dedup" option no-op, always de-duplicate. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) Elasticsearch does not permit duplicate keys in JSON objects, so there is no value in being able to configure deduplication. - `elasticsearchexporter`: Remove defunct "file" and "fields" configuration settings. ([#​33803](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33803)) This is a breaking change only because removing the attributes would prevent collector startup if those attributes are specified, but otherwise there is no functional change. These configuration attributes have never done anything. - `stanza`: errors from Operator.Process are returned instead of silently ignored. ([#​33783](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33783)) This public function is affected: https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.104.0/operator/helper#WriterOperator.Write - `vcenterreceiver`: Enables various vCenter metrics that were disabled by default until v0.105 ([#​34022](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34022)) The following metrics will be enabled by default "vcenter.host.network.packet.drop.rate", "vcenter.vm.cpu.readiness", "vcenter.host.cpu.capacity", and "vcenter.host.cpu.reserved". ##### 🚩 Deprecations 🚩 - `lokiexporter`: Deprecate component ([#​33916](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33916)) ##### 🚀 New components 🚀 - `sumconnector`: creates a wireframe and initial pr to develop from ([#​32669](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32669)) - `extensions/observer/cfgardenobserver`: Add a new observer that discovers containers through the Garden API ([#​33618](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33618)) ##### 💡 Enhancements 💡 - `pkg/ottl`: Added Hex() converter function ([#​31929](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31929)) - `pkg/ottl`: Add IsRootSpan() converter function. ([#​32918](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32918)) Converter `IsRootSpan()` returns `true` if the span in the corresponding context is root, that means its `parent_span_id` equals to hexadecimal representation of zero. In all other scenarios function returns `false`. - `vcenterreceiver`: Adds additional vCenter resource pool metrics and a memory_usage_type attribute for vcenter.resource_pool.memory.usage metric to use. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) Added "vcenter.resource_pool.memory.swapped", "vcenter.resource_pool.memory.ballooned", and "vcenter.resource_pool.memory.granted" metrics. Also added an additional attribute, "memory_usage_type" for "vcenter.resource_pool.memory.usage" metric, which is currently under a feature gate. - `kubeletstatsreceiver`: Add `k8s.pod.memory.node.utilization` and `k8s.container.memory.node.utilization` metrics ([#​33591](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33591)) - `vcenterreceiver`: Adds vCenter metrics at the datacenter level. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) Introduces various datacenter metrics which work by aggregating stats from datastores, clusters, hosts, and VM's. - `processor/resource, processor/attributes`: Add an option to extract value from a client address by specifying `client.address` value in the `from_context` field. ([#​34051](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34051)) - `awss3receiver`: Add support for retrieving logs and metrics to the AWS S3 Receiver. ([#​30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750)) - `receiver/azuremonitorreceiver`: Add support for Managed Identity and Default Credential auth ([#​31268](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31268), [#​33584](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33584)) - `azuremonitorreceiver`: Add `maximum_number_of_records_per_resource` config parameter in order to overwrite default ([#​32165](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32165)) - `clickhouseexporter`: Upgrading stability for logs to beta ([#​33615](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33615)) The logs exporter has been proven to be stable for large scale production deployments. Configuration options specific to logs are unlikely to change. - `cloudfoundryreceiver`: Add support to receive CloudFoundry Logs ([#​32671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32671)) - `datadogreceiver`: Add support for metrics in Datadog receiver ([#​18278](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/18278)) - `datadogexporter`: Add a feature gate `exporter.datadogexporter.TraceExportUseCustomHTTPClient` that allows a custom HTTP client to be used in trace export ([#​34025](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34025)) This is an experimental feature. By default the feature gate is disabled and trace export uses a default HTTP client. - `elasticsearchexporter`: Introduce experimental `telemetry.log_request_body` and `telemetry.log_response_body` config ([#​33854](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33854)) - `cmd/opampsupervisor`: Adds support for forwarding custom messages to/from the agent ([#​33575](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33575)) - `geoipprocessor`: Add providers configuration and maxmind provider factory ([#​33269](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33269)) - `healthcheckv2extension`: Add partial gRPC service implementation to healthcheckv2. ([#​26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661)) - `healthcheckv2extension`: Add support for streaming Watch RPC to healthcheckv2 gRPC service. ([#​26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661)) - `healthcheckv2extension`: Add HTTP service to healthcheckv2 ([#​26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661)) - `splunkhecexporter`: Increase the performance of JSON marshaling ([#​34011](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34011)) - `pkg/stanza`: Add `parse_ints` config in json parser to support parsing int or float properly ([#​33696](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33696)) - `loadbalancingexporter`: Adds a new streamID routingKey, which will route based on the datapoint ID. See updated README for details ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) - `awsxrayexporter`: Allow multiple log group names/arns to be set in environmental variables ([#​33795](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33795)) - `dockerobserver`: Add hint to error when using float for `api_version` field ([#​34043](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34043)) - `dockerstatsreceiver`: Add hint to error when using float for `api_version` field ([#​34043](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34043)) - `pkg/ottl`: Emit traces for statement sequence executions to troubleshoot OTTL statements/conditions ([#​33433](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33433)) - `pkg/stanza`: Bump 'logs.jsonParserArray' and 'logs.assignKeys' feature gates to beta. ([#​33948](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33948)) This enables the feature gates by default to allow use of the `json_array_parser` and `assign_keys` operations. - `receiver/filelog`: Add filelog.container.removeOriginalTimeField feature-flag for removing original time field ([#​33946](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33946)) - `statsdreceiver`: Allow configuring summary percentiles ([#​33701](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33701)) - `pkg/stanza`: Switch to faster json parser lib for container operator ([#​33929](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33929)) - `telemetrygen`: telemetrygen `--rate` flag changed from Int64 to Float64 ([#​33984](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33984)) - `extension/opamp`: Rely on the Collector APIs to do config redaction ([#​34078](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34078)) Previously all config fields had to be redacted, now `configopaque.String` is used to determine which fields should be redacted. As a result, fields that are not sensitive are no longer redacted. - `azuremonitorreceiver`: Upgrade stability to alpha ([#​33689](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33689)) - `windowsperfcountersreceiver`: `windowsperfcountersreceiver` now appends an index number to additional instance names that share a name. An example of this is when scraping ` rocess(*)` counters with multiple running instances of the same executable. ([#​32319](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32319)) **NOTES** - This change can expose cardinality issues where the counters were previously collapsed under the non-indexed instance name. - The change mimics Windows Performance Monitor behavior: The first instance name remains unchanged, additional instances are suffixed with `#<N>` where `N=1` and is increased for each duplicate. - e.g. Given 3 powershell instances, this will return `powershell`, `powershell#1` and `powershell#2`. ##### 🧰 Bug fixes 🧰 - `servicegraphconnector`: Fix failed label does not work leads to servicegraph metrics error ([#​32018](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32018)) - `apachesparkreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33906](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33906)) - `azureblobreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33902](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33902)) - `countconnector`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33903](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33903)) - `deltatorateprocessor`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33904](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33904)) - `httpcheckreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33897](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33897)) - `metricsgenerationprocessor`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33905](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33905)) - `podmanreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33899](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33899)) - `purefareceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33901](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33901)) - `purefbreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33900](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33900)) - `zookeeperreceiver`: Updating the stability to reflect that the component is shipped as part of contrib. ([#​33898](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33898)) - `probabilisticsamplerprocessor`: Fix bug where log sampling was being reported by the counter `otelcol_processor_probabilistic_sampler_count_traces_sampled` ([#​33874](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33874)) - `cmd/telemetrygen`: Fix `make docker-telemetrygen` command. ([#​33989](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33989)) - `processor/groupbyattrsprocessor`: Fix dropping of metadata fields when processing metrics. ([#​33419](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33419)) - `testbed`: Fixes incorrect count for sent data items in load generator. ([#​34057](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34057)) - `prometheusreceiver`: Fix hash computation to include non exported fields like regex in scrape configuration for TargetAllocator ([#​29313](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29313)) - `datadogexporter`: Exit when API key validation fails and `api::fail_on_invalid_key` is set to `true`. ([#​33935](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33935)) - `kafkametricsreceiver`: Fix issue with incorrect consumer offset ([#​33309](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33309)) - `sqlserverreceiver`: Enable default metrics to properly trigger SQL Server scrape ([#​34065](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/34065)) - `syslogreceiver`: Allow to define `max_octets` for octet counting RFC5424 syslog parser ([#​33182](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33182)) - `windowsperfcountersreceiver`: Metric definitions with no matching performance counter are no longer included as metrics with zero datapoints in the scrape output. ([#​4972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/4972)) ### [`v0.104.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01040) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.103.0...v0.104.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: removed compress_encoding ([#​33604](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33604)) - `exporter/clickhouse`: Change behavior of how default database is read from the config ([#​33693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33693)) Changed the default `database` to `default`. The final database will prioritize `endpoint`, unless `database` is set to a value not equal to `default`. If neither are specified then it defaults to the `default` database. Possible breaking change if someone has the DSN configured in combination with `database` config option. - `exporter/clickhouse`: Add `async_insert` config option to enable inserting asynchronously by default. ([#​33614](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33614)) Adds `async_insert` config option to enable inserting asynchronously by default. To preserve the previous behavior, set `async_insert` to `false` in your config. When enabled, the exporter will insert asynchronously, which can improve performance for high-throughput deployments. The `async_insert` option can be set to `true` or `false` to enable or disable async inserts, respectively. The default value is `true`. Keep in mind this setting is added since the exporter now sets it to default. Async insert and its related settings can still be defined in `endpoint` and `connection_params`, which take priority over the new config option. - `clickhouseexporter`: Add `AggregationTemporality` column to histogram and exponential histogram tables. Rename `AggTemp` column to `AggregationTemporality` in sum table. ([#​33424](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33424)) It's a breaking change. users who upgrade to the latest version need to alter the Clickhouse table: ```sql ALTER TABLE otel_metrics_exponential_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_histogram ADD COLUMN AggregationTemporality Int32 CODEC(ZSTD(1)); ALTER TABLE otel_metrics_sum RENAME COLUMN AggTemp TO AggregationTemporality; ``` - `exporter/clickhouse`: Remove deprecated `ttl_days` config option, use `ttl` instead. ([#​33648](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33648)) - `vcenterreceiver`: Drops support for vCenter 6.7 ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `all`: Promote `component.UseLocalHostAsDefaultHost` feature gate to beta. This changes default endpoints from 0.0.0.0 to localhost ([#​30702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30702)) This change affects the following components: - extension/awsproxy - extension/health_check - extension/health_checkv2 - extension/jaegerremotesampling - internal/aws/proxy - processor/remotetap - receiver/awsfirehose - receiver/awsxray - receiver/influxdb - receiver/jaeger - receiver/loki - receiver/opencensus - receiver/sapm - receiver/signalfx - receiver/skywalking - receiver/splunk_hec - receiver/zipkin - receiver/zookeeper - `receiver/mongodb`: Graduate receiver.mongodb.removeDatabaseAttr feature gate to stable ([#​24972](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24972)) ##### 🚩 Deprecations 🚩 - `exporter/elasticsearch`: Deprecate the "dedot" configuration. ([#​33772](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33772)) dedot has been deprecated, and will always be enabled in ECS mode and disabled for other modes in future - `exporter/elasticsearch`: Deprecate the "dedup" configuration. ([#​33773](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33773)) dedup has been deprecated, and will always be enabled in future. ##### 🚀 New components 🚀 - `otelarrow`: OTel-Arrow exporter and receiver are marked alpha, added to otelcontribcol ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `exporter/elasticsearch`: Add initial support for metrics ([#​33513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33513)) - `elasticsearchexporter`: Add translation for k8s.deployment.name resource attribute ([#​33622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33622)) - `k8sattributesprocessor`: Add support for exposing `k8s.pod.ip` as a resource attribute ([#​32960](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32960)) - `geoipprocessor`: Add MaxMind geoip provider for GeoIP2-City and GeoLite2-City databases. ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `vcenterreceiver`: Adds vCenter CPU readiness metric for VMs. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) - `awsemfexporter`: AWS EMF Exporter to add AppSignals metadata flag into the user-agent ([#​32998](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32998)) - `receiver/mongodb`: Ensure support of 6.0 and 7.0 MongoDB versions with integration tests ([#​32716](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32716)) - `sumologicexporter`: added timeout validation ([#​33151](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33151)) - `clickhouseexporter`: Updated the default logs table to a more optimized schema ([#​33611](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33611)) Simplified data types, improved partitioning and time range queries. - `datadogconnector`: Add a feature gate `connector.datadogconnector.NativeIngest` that enables datadog connector to use the new native OTel API in APM stats computation. ([#​33297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33297)) The feature gate `connector.datadogconnector.NativeIngest` is disabled by default. - `datadogexporter`: Adds Kubernetes DD tags to keep when mapping resource attributes ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/334](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/334)/334 for details. - `exporter/elasticsearch`: Add data stream routing ([#​33794](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33794), [#​33756](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33756)) `data_stream.dataset` and `data_stream.namespace` in attributes will be respected when config `*_dynamic_index.enabled` is true. - `exporter/elasticsearch`: Encode metrics resource attributes in ECS mapping mode ([#​33823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33823)) - `elasticsearchexporter`: Preserve `host.name` resource attribute in ECS mode ([#​33670](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33670)) - `servicegraphprocessor`: Added a new configuration option `enable_virtual_node_label` to allow users to identify which node is the virtual node in each edge of the service graph. ([#​31889](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31889)) - `pkg/stanza`: Switch JSON parser used by json_parser to github.com/goccy/go-json ([#​33784](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33784)) - `k8sobserver`: Add support for k8s.ingress endpoint. ([#​32971](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32971)) - `statsdreceiver`: Optimize statsdreceiver to reduce object allocations ([#​33683](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33683)) - `routingprocessor`: Use mdatagen to define the component's telemetry ([#​33526](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33526)) - `loadbalancerexporter`: Refactors how the load balancing exporter splits metrics ([#​32513](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32513)) All splitting is *behaviorally*, the same. However, the `resource` routingID now uses the `internal/exp/metrics/identity` package to generate the load balancing key, instead of bespoke code. This means that when upgrading to this version your routes for specific metric groupings could change. However, this will be stable and all future metrics will follow the new routing - `receiver/mongodbreceiver`: Add `server.address` and `server.port` resource attributes to MongoDB receiver. ([#​32810](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32810), [#​32350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32350)) The new resource attributes are added to the MongoDB receiver to distinguish metrics coming from different MongoDB instances. - `server.address`: The address of the MongoDB host, enabled by default. - `server.port`: The port of the MongoDB host, disabled by default. - `observerextension`: Expose host and port in endpoint's environment ([#​33571](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33571)) - `rabbitmqexporter`: Promote rabbitmqexporter to alpha. ([#​33331](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33331)) - `pkg/ottl`: Add a `schema_url` field to access the SchemaURL in resources and scopes on all signals ([#​30229](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30229)) - `solacereceiver`: Renamed some SemConv fields to support latest semantic conventions for messaging spans (version `1.25.0`) ([#​33499](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33499)) - `sqlserverreceiver`: Enable more perf counter metrics when directly connecting to SQL Server ([#​33420](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33420)) This enables the following metrics by default on non Windows-based systems: `sqlserver.batch.request.rate` `sqlserver.batch.sql_compilation.rate` `sqlserver.batch.sql_recompilation.rate` `sqlserver.page.buffer_cache.hit_ratio` `sqlserver.user.connection.count` - `extension/googleclientauth`: Add Google-signed ID token support ([#​33185](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33185)) Update github.com/GoogleCloudPlatform/opentelemetry-operations-go/extension/googleclientauth to v0.48.0. With this update, extension/googleclientauth now supports Google-signed ID token as auth header. - `vcenterreceiver`: Adds vCenter CPU capacity and network drop rate metrics to hosts. ([#​33607](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33607)) ##### 🧰 Bug fixes 🧰 - `resourcedetectionprocessor`: Fetch CPU info only if related attributes are enabled ([#​33774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33774)) - `datasetexporter`: Upgrade dataset-go to v0.19.0 and fix found issues ([#​33498](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33498), [#​32533](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32533), [#​33675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33675)) Upgrade `dataset-go` library from v0.18.0 to v0.19.0. Enable skipped integration test and adjust the test so it is passing again. Do not validate configuration, let the framework run the validation. - `datasetexporter`: Upgrade dataset-go to v0.20.0 ([#​33812](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33812)) Upgrade `dataset-go` library from v0.19.0 to v0.20.0. Make number of outgoing connections configurable. - `datadogexporter`: Fix panics on invalid sized trace & span IDs ([#​33566](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33566)) [https://github.com/DataDog/opentelemetry-mapping-go/pull/340](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/340)/340 for details. - `datadogexporter`: Ignore metric datapoints with `no recorded value` flag ([#​33728](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33728)) This flag is not supported by Datadog, so we just ignore these datapoints. [https://github.com/DataDog/opentelemetry-mapping-go/pull/330](https://togithub.com/DataDog/opentelemetry-mapping-go/pull/330)/330 for details. - `tailsamplingprocessor`: Fix precedence of inverted match in and policy ([#​33671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33671)) Previously if the decision from a policy evaluation was `NotSampled` or `InvertNotSampled` it would return a `NotSampled` decision regardless, effectively downgrading the result. This was breaking the documented behaviour that inverted decisions should take precedence over all others. - `otelarrowreceiver`: Ensure consume operations are not canceled at stream EOF. ([#​33570](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33570)) - `vcenterreceiver`: Fixes errors in some of the client calls for environments containing multiple datacenters. ([#​33734](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33734)) ### [`v0.103.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01030) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.102.0...v0.103.0) ##### 🛑 Breaking changes 🛑 - `cmd/opampsupervisor,extension/opamp`: Upgrade the opamp-go library to v0.15.0 ([#​33416](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33416)) With this change, UUIDv7 is recommended for the OpAMP extension's instance_uid field instead of ULID. ULIDs will continue to work, but may be displayed as UUIDs. The supervisor's persistent state (${storage_dir}/persistent_state.yaml) will need to be cleared to generate a new UUIDv7 instead of a ULID. This change may be incompatible with management servers using v0.14.0 of opamp-go. - `mongodbreceiver`: Now only supports `TCP` connections ([#​32199](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32199)) This fixes a bug where hosts had to explicitly set `tcp` as the transport type. The `transport` option has been removed. - `cmd/configschema`: Removes the deprecated `configschema` command. This command will no longer be released or supported. ([#​33384](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33384)) - `sqlserverreceiver`: sqlserver.database.io.read_latency has been renamed to sqlserver.database.latency with a `direction` attribute. ([#​29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865)) ##### 🚩 Deprecations 🚩 - `healthcheckextension`: Remove incorrect logic behind `check_collector_pipeline` config ([#​33469](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33469)) This logic incorrectly set the pipeline to OK after waiting for enough callbacks from the opencensus library to be called. As this was broken, I'm removing it to remove the dependency on opencensus as well. Improvements will be available via healthcheckv2 extension. - `googlecloudspannerreceiver`: Mark the component as unmaintained. If we don't find new maintainers, it will be deprecated and removed. ([#​32651](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32651)) ##### 💡 Enhancements 💡 - `filelogreceiver`: If include_file_record_number is true, it will add the file record number as the attribute `log.file.record_number` ([#​33530](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33530)) - `kubeletstats`: Add k8s.pod.cpu.node.utilization metric ([#​33390](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33390)) - `awss3exporter`: endpoint should contain the S3 bucket ([#​32774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32774)) - `awss3receiver`: Add support for encoding extensions to be used in the AWS S3 Receiver. ([#​30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750)) - `gitproviderreceiver`: Adds branch commit and line based metrics ([#​22028](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/22028)) Adds the following branch based metrics. - git.repository.branch.time - git.repository.branch.commit.aheadby.count - git.repository.branch.commit.behindby.count - git.repository.branch.line.deletion.count - git.repository.branch.line.addition.count - `statsdreceiver`: update statsd receiver to use mdatagen ([#​33524](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33524)) - `coralogixexporter`: Allow setting application name from `cx.application.name` and `cx.subsystem.name` resource attributes ([#​33217](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33217)) - `metricstransformprocessor`: Adds the 'count' aggregation type to the Metrics Transform Processor. ([#​24978](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24978)) - `elasticsearchexporter`: Add support for confighttp options, notably "auth". ([#​33367](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33367)) Add support for confighttp and related configuration settings, such as "auth". This change also means that the Elasticsearch URL may be specified as "endpoint", like the otlphttp exporter. - `elasticsearchexporter`: Check that endpoints are valid URLs during config validation. ([#​33350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33350)) Check that endpoints are valid URLs during config validation so that an invalid endpoint causes a fatal error during startup, rather than leading to a persistent runtime error. - `opampsupervisor`: Add config validation for the supervisor config ([#​32843](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32843)) - `statsdreceiver`: Added received/accepted/refused metrics ([#​24278](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24278)) - `filelogreceiver`: Add support for gzip compressed log files ([#​2328](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/2328)) - `confmap/provider/secretsmanagerprovider`: Add support for JSON formatted secrets in secretsmanagerprovider confmap ([#​32143](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32143)) The `secretsmanagerprovider` confmap will now allow to get secret by a json key if the secret value is json. To specify key separate key from secret name/arn by `#` e.g. `mySecret#mySecretKey`. - `geoipprocessor`: Add initial processing based on source.address resource attribute ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) - `healthcheckv2extension`: Add shared aggregation logic for status events. ([#​26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661)) - `tailsamplingprocessor`: Simple LRU Decision Cache for "keep" decisions ([#​31583](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31583)) - `processor/tailsampling`: Migrates internal telemetry to OpenTelemetry SDK via mdatagen ([#​31581](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31581)) The metric names and their properties, such as bucket boundaries for histograms, were kept like before, to keep backwards compatibility. - `kafka`: Added `disable_fast_negotiation` configuration option for Kafka Kerberos authentication, allowing the disabling of PA-FX-FAST negotiation. ([#​26345](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26345)) - `pkg/ottl`: Added `keep_matching_keys` function to allow dropping all keys from a map that don't match the pattern. ([#​32989](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32989)) - `OTel-Arrow`: Update to OTel-Arrow v0.24.0 ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) - `pkg/ottl`: Add debug logs to help troubleshoot OTTL statements/conditions ([#​33274](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33274)) - `pkg/ottl`: Introducing `append` function for appending items into an existing array ([#​32141](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32141)) - `pkg/ottl`: Introducing `Uri` converter parsing URI string into SemConv ([#​32433](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32433)) - `probabilisticsamplerprocessor`: Add Proportional and Equalizing sampling modes ([#​31918](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31918)) Both the existing hash_seed mode and the two new modes use OTEP 235 semantic conventions to encode sampling probability. - `prometheusreceiver`: Resource attributes produced by the prometheus receiver now include stable semantic conventions for `server` and `url`. ([#​32814](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32814)) To migrate from the legacy net.host.name, net.host.port, and http.scheme resource attributes, | migrate to server.address, server.port, and url.scheme, and then | set the receiver.prometheus.removeLegacyResourceAttributes feature gate. - `datadogexporter`: The Datadog Exporter now supports the `proxy_url` parameter to configure an HTTP proxy to use when sending telemetry to Datadog. ([#​33316](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33316)) - `spanmetrics`: Produce delta temporality span metrics with StartTimeUnixNano and TimeUnixNano values representing an uninterrupted series ([#​31671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31671), [#​30688](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30688)) This allows producing delta span metrics instead of the more memory-intensive cumulative metrics, specifically when a downstream component can convert the delta metrics to cumulative. - `sqlserverreceiver`: Add support for more Database IO metrics ([#​29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865)) The following metrics have been added: - sqlserver.database.latency - sqlserver.database.io - sqlserver.database.operations - `cmd/opampsupervisor`: Receive and report effective config to the OpAMP server ([#​30622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30622)) - `processor/transform`: Add `transform.flatten.logs` featuregate to give each log record a distinct resource and scope. ([#​32080](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32080)) This option is useful when applying transformations which alter the resource or scope. e.g. `set(resource.attributes["to"], attributes["from"])`, which may otherwise result in unexpected behavior. Using this option typically incurs a performance penalty as the processor must compute many hashes and create copies of resource and scope information for every log record. - `receiver/windowsperfcounters`: Counter configuration now supports recreating the underlying performance query at scrape time. ([#​32798](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32798)) ##### 🧰 Bug fixes 🧰 - `filelogreceiver`: Container parser should add k8s metadata as resource attributes and not as log record attributes ([#​33341](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33341)) - `deltatocumulative`: properly drop samples when at limit ([#​33285](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33285)) fixes a segfault in the limiting behavior, where streams exceeding the limit still had their samples processed. due to not being tracked, this led to a nil-pointer deref - `postgresqlreceiver`: Fix bug where `postgresql.rows` always returning 0 for `state="dead"` ([#​33489](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33489)) - `prometheusreceiver`: Fall back to scrape config job/instance labels for aggregated metrics without instance/job labels ([#​32555](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32555)) - `elasticsearchexporter`: Duplicate Key in JSON ([#​33454](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33454)) - `logzioexporter`: Fix issue where log attributes were not correctly exported ([#​33231](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33231)) - `exporter/datadog`: Prevents collector shut down when Datadog logs pipeline fails to validate API key ([#​33195](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33195)) ### [`v0.102.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01020) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.101.0...v0.102.0) ##### 🛑 Breaking changes 🛑 - `k8sattributesprocessor`: Move `k8sattr.rfc3339` feature gate to stable. ([#​33304](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33304)) - `extension/opamp`: Redact all values in the effective config ([#​33267](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33267)) All values will be treated as if they are a `configopaque.String` type. This will be changed once the Collector APIs are updated to unmarshal the config while only redacting actual `configopaque.String`-typed values. The exception to redaction is the `service::pipelines` section, which is useful for debugging and does not contain any `configopaque.String` values. - `extension/filestorage`: Replace path-unsafe characters in component names ([#​3148](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/3148)) The feature gate `extension.filestorage.replaceUnsafeCharacters` is now removed. - `vcenterreceiver`: vcenterreceiver replaces deprecated packet metrics by removing them and enabling by default the newer ones. ([#​32929](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32929), [#​32835](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32835)) Removes the following metrics: `vcenter.host.network.packet.errors`, `vcenter.host.network.packet.count`, and `vcenter.vm.network.packet.count`. Also enables by default the following metrics: `vcenter.host.network.packet.error.rate`, `vcenter.host.network.packet.rate`, and `vcenter.vm.network.packet.rate`. ##### 🚀 New components 🚀 - `geoipprocessor`: introduce the GeoIP processor ([#​32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663)) ##### 💡 Enhancements 💡 - `pkg/ottl`: Add the `Day` Converter to extract the int Day component from a time.Time ([#​33106](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33106)) - `pkg/ottl`: Adds `Month` converter to extract the int Month component from a time.Time ([#​33106](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33106)) - `cmd/telemetrygen`: Add support for adding spanID and traceID as exemplars to datapoints generated by telemetrygen ([#​33320](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33320)) - `cmd/telemetrygen`: Add support for specifying trace ID and span ID in telemetrygen for logs ([#​33234](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33234)) - `pkg/ottl`: Adds a `Year` converter for extracting the int year component from a time.Time ([#​33106](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33106)) - `filelogreceiver`: Log when files are rotated/moved/truncated ([#​33237](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33237)) - `stanza`: Add monitoring metrics for open and harvested files in fileconsumer ([#​31256](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31256)) - `awss3receiver`: Uses obsreport to report metrics for the AWS S3 Receiver. ([#​30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750)) - `awsxrayexporter`: AWS X-Ray exporter to make local root spans a segment for internal/service spans and subsegment + segment for client/producer/consumer spans. ([#​33000](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33000)) - `prometheusreceiver`: Allow to configure http client used by target allocator generated scrape targets ([#​18054](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/18054)) - `clickhouseexporter`: Add `create_schema` option to ClickHouse exporter ([#​32282](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32282)) The new create_schema option allows disabling default DDL to let the user manage their own schema. - `pkg/stanza`: Expose recombine max log size option in the container parser configuration ([#​33186](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33186)) - `sumologicexporter`: add support for tracing ([#​32315](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32315)) - `exceptionsconnector`: Add support for exemplars in exceptionsconnector ([#​24409](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24409)) - `processor/resourcedetectionprocessor`: Add support for Azure tags in ResourceDetectionProcessor. ([#​32953](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32953)) - `solarwindsapmsettingsextension`: Added the first part of concrete implementation of solarwindsapmsettingsextension ([#​27668](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/27668)) - `kubeletstatsreceiver`: Add k8s.container.cpu.node.utilization metric ([#​27885](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/27885)) - `pkg/ottl`: Adds a `Minute` converter for extracting the int minute component from a time.Time ([#​33106](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33106)) ##### 🧰 Bug fixes 🧰 - `podmanreceiver`: add scraper's shutdown method ([#​29994](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29994)) - `awsxrayexporter`: Fix the DB subsegment(client span) name with JDBC conn string starts with "jdbc:" ([#​33225](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33225)) - `exp/metrics`: fixes staleness.Evict such that it only ever evicts actually stale metrics ([#​33265](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33265)) - `receiver/mysql`: Remove the order by clause for the column that does not exist ([#​33271](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33271)) - `influxdb(exporter|receiver)`: remove Metric flags field to/from InfluxDB conversion ([#​29896](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29896)) - `kafkareceiver`: Fix bug that was blocking shutdown ([#​30789](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30789)) - `exporter/datadog`: Fixes a potential race condition when the traces exporter and metrics exporter are both shutting down. ([#​33291](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33291)) ### [`v0.101.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01010) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.100.0...v0.101.0) ##### 🛑 Breaking changes 🛑 - `sumologicexporter`: change logs behavior ([#​31479](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31479)) - set OTLP as default format - add support for OTLP format - do not support metadata attributes - do not support source headers - `sumologicexporter`: change metrics behavior ([#​31479](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31479)) - remove suppport for carbon2 and graphite - add support for otlp format - do not support metadata attributes - do not support source headers - set otlp as default metrics format - `sumologicexporter`: remove deprecated configuration options ([#​32315](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32315)) migration has been described in the following document https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.100.0/exporter/sumologicexporter#migration-to-new-architecture - `remotetapprocessor`: Make the `limit` configuration work properly. ([#​32385](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32385)) The `limit` configuration was ignored previously, but now it works according to the configuration and documentation. Nothing is required of users. See the remotetapprocessor's `README.md` for details. - `groupbytraceprocessor`: Fix groupbytrace metrics contain duplicate prefix ([#​32698](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32698)) - `vcenterreceiver`: Removes `vcenter.cluster.name` attribute from `vcenter.datastore` metrics ([#​32674](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32674)) If there were multiple Clusters, Datastore metrics were being repeated under Resources differentiated with a `vcenter.cluster.name` resource attribute. In the same vein, if there were standalone Hosts, in addition to clusters the metrics would be repeated under a Resource without the `vcenter.cluster.name` attribute. Now there will only be a single set of metrics for one Datastore (as there should be, as Datastores don't belong to Clusters). - `resourcedetectionprocessor`: Move `processor.resourcedetection.hostCPUModelAndFamilyAsString` feature gate to stable. ([#​29025](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29025)) - `filelog, journald, tcp, udp, syslog, windowseventlog receivers`: The internal logger has been changed from zap.SugaredLogger to zap.Logger. ([#​32177](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32177)) This should not have any meaningful impact on most users but the logging format for some logs may have changed. - `awsxrayexporter`: change x-ray exporter's translator to make "." split annotation pass as-is ([#​32694](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32694), [#​31732](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31732)) This change make below change to beta stage for feature gate 'exporter.xray.allowDot'，this change will let the change mention below enable by default | In the past, X-Ray doesn’t support “.”. So we have a translator in x-ray export to translates it to “\_” before sending traces to X-Ray Service. | To match otel naming style, x-ray service team decide to change their service to support both "." type and "" type of naming. In this case the translator that translate "." to "" is no-longer needed. This PR change the way this translator work | X-Ray PMs agree on rolling out this change by using feature-gate ##### 🚀 New components 🚀 - `awss3receiver`: Initial implementation of the AWS S3 receiver. ([#​30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750)) - `receiver/mysql`: Adds INFORMATION_SCHEMA TABLES metrics ([#​32693](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32693)) This adds table size metrics using the INFORMATION_SCHEMA TABLES table: https://dev.mysql.com/doc/refman/8.3/en/information-schema-tables-table.html. Specifically, we are adding the columns: `TABLE_ROWS`, `AVG_ROW_LENGTH`, `DATA_LENGTH`, `INDEX_LENGTH`. - `exporter/otelarrow`: Implementation copied from opentelemetry/otel-arrow repository [@​v0](https://togithub.com/v0).23.0. ([#​26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) ##### 💡 Enhancements 💡 - `filelogreceirules are not very usefuver`: Add container operator parser ([#​31959](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31959)) - `jsonlogencodingextension`: Move jsonlogencodingextension to alpha ([#​32697](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32697)) - `exceptionsconnector`: Make span name a default dimension for ouput metrics and log records. ([#​32162](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32162)) - `azureblobreceiver`: Support service principal authentication for Blob storage ([#​32705](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32705)) - `deltatocumulativeprocessor`: exponential histogram accumulation ([#​31340](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31340)) accumulates exponential histogram datapoints by adding respective bucket counts. also handles downscaling, changing zero-counts, offset adaptions and optional fields - `sumologicexporter`: add sticky session support ([#​32315](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32315)) - `elasticsearchexporter`: Replace go-elasticsearch BulkIndexer with go-docappender ([#​32378](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32378)) Replace go-elasticsearch BulkIndexer with go-docappender bulk indexer, in preparation for future reliability fixes. As a result of this change, there are minor behavioral differences: - flush timeout is now enforced on client side - oversize payload special handling is now removed - go-docappender uses bulk request filterPath which means bulk response is smaller, less JSON parsing and lower CPU usage - document level retry debug logging is removed as retries are done transparently - `elasticsearchexporter`: Converts more SemConv fields in OTel events to ECS fields in Elasticsearch documents when `mapping.mode: ecs` is specified. ([#​31694](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31694)) - `extension/storage/filestorage`: New flag cleanup_on_start for the compaction section (default=false). ([#​32863](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32863)) It will remove all temporary files in the compaction directory (those which start with `tempdb`), temp files will be left if a previous run of the process is killed while compacting. - `opampsupervisor`: Allows the supervisor to persist its instance ID between restarts. ([#​21073](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/21073)) - `opampsupervisor`: Adds the ability to configure the agent description ([#​32824](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32824)) - `vcenterreceiver`: Refactors how and when client makes calls in order to provide for faster collection times. ([#​31837](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31837)) - `resourcedetectionprocessor`: Support GCP Bare Metal Solution in resource detection processor. ([#​32985](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32985)) - `sp </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://www.mend.io/free-developer-tools/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MzguMCIsInVwZGF0ZWRJblZlciI6IjM3LjQzOC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.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.
What does this PR do?
Adds Kubernetes DD tags to keep in TagsFromAttributes from https://docs.datadoghq.com/containers/kubernetes/tag/?tab=containerizedagent#out-of-the-box-tags
Motivation