-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/dockerstats] Optionally Include container.image.id
and container.command
resource attributes
#21092
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
As long as they are disabled by default, I think we're good here. I can assign the issue to you if you'd like. |
Sure, assign it to me. We'll work on a PR as soon as possible. Thanks! |
This looks reasonable to add @sigilioso, happy to review. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
#21185 and open-telemetry/semantic-conventions#39 are addressing this. |
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add `container.image.id` and `container.command_line` as optional resource attributes, disabled by default. **Link to tracking Issue:** <Issue number if applicable> Tracking issue #21092 **Testing:** <Describe what testing was performed and which tests were added.> Until this point, all resource attributes have been enabled by default, resulting in the coupling of the [test](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7bf5d66fae6c1c5360ec2875948f2c2adab6c44f/receiver/dockerstatsreceiver/receiver_test.go#L191) to the default configuration. In order to test the current implementation with the new resource attributes enabled & disabled, a minor refactoring was required in the `TestScrapeV2` test, allowing to pass different configurations for each test. Refer to the following commit 508dbee9aa9a22c1ca79f16bba5abeecceeb9c48 to check the refactor in the test. **Documentation:** <Describe the documentation added.> New resource attributes documentation was generated by `mdatagen`.
…ry#21185) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add `container.image.id` and `container.command_line` as optional resource attributes, disabled by default. **Link to tracking Issue:** <Issue number if applicable> Tracking issue open-telemetry#21092 **Testing:** <Describe what testing was performed and which tests were added.> Until this point, all resource attributes have been enabled by default, resulting in the coupling of the [test](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7bf5d66fae6c1c5360ec2875948f2c2adab6c44f/receiver/dockerstatsreceiver/receiver_test.go#L191) to the default configuration. In order to test the current implementation with the new resource attributes enabled & disabled, a minor refactoring was required in the `TestScrapeV2` test, allowing to pass different configurations for each test. Refer to the following commit 508dbee9aa9a22c1ca79f16bba5abeecceeb9c48 to check the refactor in the test. **Documentation:** <Describe the documentation added.> New resource attributes documentation was generated by `mdatagen`.
commit 2ae4bb7319f43c979735e96e1f782494e05e0cc7 Author: OpenTelemetry Bot <[email protected]> Date: Wed Jul 5 04:13:15 2023 -0700 [chore] Prepare release 0.81.0 (#23978) The following commands were run to prepare this release: - make chlog-update VERSION=v0.81.0 - sed -i.bak s/0.80.0/0.81.0/g versions.yaml - make multimod-prerelease - make multimod-sync --------- Co-authored-by: Pablo Baeyens <[email protected]> commit e9bdc636a01731bc1531f0b1a74859812e073eb4 Author: Pablo Baeyens <[email protected]> Date: Wed Jul 5 12:50:05 2023 +0200 Revert "[chore] Remove skip flaky test for hostmetricsreceiver" (#23982) Reverts open-telemetry/opentelemetry-collector-contrib#23874. The test is still flaky on Windows. commit f85dd5b4b59282932db14a1187ad3687083b4c5c Author: Pablo Baeyens <[email protected]> Date: Wed Jul 5 11:21:45 2023 +0200 Make sed replace statements more resilient (#23977) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> While working on open-telemetry/opentelemetry-collector/issues/8033, I got the following error ([full logs](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5461142477/jobs/9938863136)): ``` github.com/open-telemetry/opentelemetry-collector-contrib/cmd/otelcontribcol imports github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver imports github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver/internal/collection imports github.com/openshift/api/quota/v1: reading github.com/openshift/api/go.mod at revision v0.0.0-20.81.01171038-322a19404e37: unknown revision v0.0.0-20.81.01171038-322a19404e37 ``` This is because the script for preparing releases has the following sed statement: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/10e46605b7b9f775a3658f4e2ba59960ffe33847/cmd/otelcontribcol/builder-config.yaml#L416 which ends up replacing `018080` within the `openshift/api` pseudoversion by `0.81.0`. To work around this, we make the replace statements more specific. An alternative would be something like https://stackoverflow.com/a/2705678, but this approach is still broken if a dependency we are replacing has exactly the version we are updating from, so I think ultimately we need a different approach. **Testing:** I tested this on https://github.com/mx-psi/opentelemetry-collector-contrib/actions/runs/5462095129/jobs/9940974190; the job is able to run until the point of creating the PR, where it fails because the bot account does not have permission to create a PR. commit 10e46605b7b9f775a3658f4e2ba59960ffe33847 Author: John Law <[email protected]> Date: Wed Jul 5 08:21:22 2023 +1200 [ci] Specify 7 as arm version for arm build in CI (#23436) **Description:** Currently, we specify arm architecture in the cross build test without specifying the `GOARM` variable. This means the `GOARM` value falls back to the default and the default value depends on the platform that we are building on. We are building on `linux/amd64` machine in github action, so the `GOARM` defaults to `5`. [There are changes to default to GOARM=7 for all non-arm systems in the upcoming golang version](https://go-review.googlesource.com/c/go/+/470695) I'm looking to add an armv7 release, so without waiting for the newer golang version, I want to explicitly set the arm version in the CI to align with the release arm version. In this pull request, I expanded the configuration for arm build by adding a new block with the arm version under `include`. Then introduce the `GOARM` environment variable when calling `make otelcontribcol` **Testing:** Able to run `make GOOS=x GOARCH=y GOARM=z otelcontribcol` with the following configurations locally - [x] `GOOS=linux`, `GOARCH=arm`, `GOARM=7` - [x] `GOOS=linux`, `GOARCH=arm64`, `GOARM=` - [x] `GOOS=darwin`, `GOARCH=amd64`, `GOARM=` - [x] `GOOS=window`, `GOARCH=amd64`, `GOARM=` commit d51d3135984633d7d07fdb42f38ef122849e548a Author: Jonah Kowall <[email protected]> Date: Tue Jul 4 16:20:42 2023 -0400 Removing jkowall from codeowners for logzioexporter (#23845) Removing @jkowall from codeowners https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20768 Signed-off-by: Jonah Kowall <[email protected]> commit 9caec802b06e75bdb4a3f6b27409bfbefca543b8 Author: Daniel Jaglowski <[email protected]> Date: Tue Jul 4 16:19:47 2023 -0400 [chore] Minor cleanup of vcenter metric code (#23873) commit aa6560128d4cd9f7a540935a8b3e2a4c603e38c0 Author: David Ashpole <[email protected]> Date: Tue Jul 4 16:17:13 2023 -0400 Add dashpole back to auto-assignees (#23876) I'm back from leave! commit 65cc16d880571ef2224154253dbea885f5d8fac9 Author: David Ashpole <[email protected]> Date: Tue Jul 4 16:16:10 2023 -0400 Remove tbarker from codeowners (#23877) **Description:** Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23405 @tbarker25 doesn't work on OpenTelemetry for Google anymore. cc @punya commit d98c227f8d4c7072344a46ae1d2d64e33c2b8644 Author: OpenTelemetry Bot <[email protected]> Date: Tue Jul 4 11:23:18 2023 -0700 [chore] dependabot updates Tue Jul 4 17:49:08 UTC 2023 (#23954) Bump cloud.google.com/go/pubsub from 1.31.0 to 1.32.0 in /exporter/googlecloudpubsubexporter Bump cloud.google.com/go/pubsub from 1.31.0 to 1.32.0 in /receiver/googlecloudpubsubreceiver Bump github.com/DataDog/datadog-api-client-go/v2 from 2.13.0 to 2.14.0 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/attributes from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/logs from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/metrics from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/quantile from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/aliyun/aliyun-log-go-sdk from 0.1.49 to 0.1.50 in /exporter/alibabacloudlogserviceexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /internal/aws/cwlogs Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in /internal/tools Bump github.com/hashicorp/consul/api from 1.21.0 to 1.22.0 in /internal/metadataproviders Bump github.com/hashicorp/consul/api from 1.21.0 to 1.22.0 in /processor/resourcedetectionprocessor Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /exporter/fileexporter Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /exporter/sapmexporter Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /receiver/sapmreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /exporter/signalfxexporter Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /extension/observer/hostobserver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/awscontainerinsightreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/hostmetricsreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/jmxreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /testbed Bump github.com/sijms/go-ora/v2 from 2.7.6 to 2.7.8 in /receiver/sqlqueryreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.687 to 1.0.692 in /exporter/tencentcloudlogserviceexporter Bump github.com/vmware/govmomi from 0.30.4 to 0.30.5 in /receiver/vcenterreceiver Bump go.mongodb.org/atlas from 0.29.0 to 0.30.0 in /receiver/mongodbatlasreceiver Bump golang.org/x/vuln from 0.1.0 to 0.2.0 in /internal/tools Bump google.golang.org/api from 0.128.0 to 0.129.0 in /exporter/f5cloudexporter Bump google.golang.org/api from 0.128.0 to 0.129.0 in /exporter/googlecloudpubsubexporter Bump google.golang.org/api from 0.128.0 to 0.129.0 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/api from 0.128.0 to 0.129.0 in /receiver/googlecloudspannerreceiver commit dbcf37ae329f0aef6f664ed5c05a9ac85f54579a Author: Ziqi Zhao <[email protected]> Date: Wed Jul 5 01:30:16 2023 +0800 [chore] fix exhaustive lint for dynatrace exporter (#23951) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 5d1f251e7ba5b013dcc0d4c96b510024d3a6da92 Author: Andrzej Stencel <[email protected]> Date: Tue Jul 4 19:29:19 2023 +0200 [chore] [receiver/snmp] fix docs on default collection interval (#23945) The default connection interval is actually `10s` and not `1m`. commit 3cb495438d022cecbb4e3c93f96088a787e02d3e Author: Tomaz Muraus <[email protected]> Date: Tue Jul 4 14:40:48 2023 +0200 [chore] [exporter/datasetexporter] Update metadata (#23885) This pull request updates metadata for DataSet exporter. Metadata was out of date and didn't reflect that the exporter plugin is distributed as part of contrib. --- NOTE: Per request in a PR review (atoulme), this change was moved out of https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/23672 to a new and separate PR. commit 81320c41004bdd739b5c4e5dafcf20230087c68b Author: Pavol Loffay <[email protected]> Date: Mon Jul 3 12:15:09 2023 +0200 Json payload in Kafka exporter is not experimental (#23884) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** <Issue number if applicable> Resolves https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23871 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> Signed-off-by: Pavol Loffay <[email protected]> commit 8510b37b1c427cc4d117cc65fcfc412ab7756420 Author: Ziqi Zhao <[email protected]> Date: Mon Jul 3 17:17:59 2023 +0800 [chore] fix exhaustive lint for podmanreceiver (#23823) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 537ba472f09a3b346b8cca8c6bdfa5d441707e11 Author: ZenoCC-Peng <[email protected]> Date: Mon Jul 3 01:41:49 2023 -0700 [chore] Remove skip flaky test for hostmetricsreceiver (#23874) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Run 20 times the GitHub Action on my personal branch, there were no test failures. See the files: [Hostmetricsreceiver-FlakyTest-10030.xlsx](https://github.com/open-telemetry/opentelemetry-collector-contrib/files/11911111/Hostmetricsreceiver-FlakyTest-10030.xlsx). **Link to tracking Issue:** <Issue number if applicable>[10030](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/10030) **Testing:** hostmetricsreceiver/internal/scraper/loadscraper/load_scraper_test.go --------- Co-authored-by: Alex Boten <[email protected]> Co-authored-by: zeno-splunk <[email protected]> commit 4c817c69a2fe9cab7f1a9c357a84eff7a40b7fe7 Author: Laser <[email protected]> Date: Fri Jun 30 21:25:25 2023 +0300 [connector/spanmetricsconnector] Added disabling options (#23039) **Description:** <Describe what has changed.> Added disabling options for histogram metrics and option to exclude default labels from all metrics. In some cases users want to optionally disable part of metrics because they generate too much data or are not needed. We've tried to use transform as [it was suggested here](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20525) And this helps in part of getting less data. But we consumed too much memory because of high cardinality labels. So we decided to suggest this mr to escape metric creation at the very beginning. **Link to tracking Issue:** [GH-16344] **Testing:** Added tests to the repository **Documentation:** Readme file updated --------- Co-authored-by: Antoine Toulme <[email protected]> commit 3c9ddf9726c5ec6ca66a8486a875a54102c8a8a2 Author: Miguel Rodriguez <[email protected]> Date: Fri Jun 30 14:23:57 2023 -0400 [receiver/filelog] Add Support for only reading the current file (#23633) Adding a feature to filelog to allow reading of only the current file from a collection of files through sorting the file names and picking the newest one. commit 95f0a13dd9c6045d1ce2c250ca0701d52b5f43f3 Author: Antoine Toulme <[email protected]> Date: Fri Jun 30 10:02:02 2023 -0700 [receiver/k8s_cluster] Add back all other vendor-specific node conditions (#23854) **Description:** Add back all other vendor-specific node conditions, and report them even if missing, as well as all allocatable node metrics if present, to the list of Kubernetes node metrics available, which went missing during the pdata translation **Link to tracking Issue:** Fixes #23839 **Testing:** Unit tests. **Documentation:** Not quite. Maybe a doc entry is required here. I haven't looked yet where to place it. commit 46d03a09bb7b137c59a032f93133c6ef0c8c1bca Author: Tyler Helmuth <[email protected]> Date: Fri Jun 30 10:41:50 2023 -0600 [internal/filter] filtermetric to filterottl bridge (#23141) **Description:** This PR adds a bridge between `filtermetric.NewSkipExpr` and `filterottl.NewBoolExprForMetric` behind a feature gate. With the feature gate enabled, any component using `filtermetric.NewSkipExpr` will start using OTTL behind the scenes. In addition, the filterprocessor's implementation of `newSkipResExpr`, which is a skip expression for resources, is bridged to `filterottl.NewBoolExprForResource`. Since this implementation exists only for filtering metrics, the same feature gate is used for both. While investigating the existing `internal/filtermetric` uses with filterprocessor and attributesprocessor I found that: - The attributes processor does not support Expressions or Resource Attributes. The readme claims that it does, but the implementation does not support it (and there are no tests). This bridge DOES NOT rectify that. - The filterprocessor allows filtering by resource attributes, expressions, and metric name. Unlike it's implementation for filtering spans and logs, the filterprocessor handles filtering spans at the Resource level loop. This is the most performant solution, and how OTTL likes to think about the problem, but it results in a different pattern than filtering spans and logs. This bridge DOES NOT attempt to move the resource implementation into `internal/filtermetric`. **Link to tracking Issue:** Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/18643 Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/18642 Depends on: - [x] https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/23142 **Testing:** Added tests comparing the output of the existing config and the bridge. commit f1068be12dee7664a74fd42354c27b3803c52bc4 Author: Antoine Toulme <[email protected]> Date: Fri Jun 30 05:58:54 2023 -0700 [receiver/mongodb] fix missing version (#23860) **Description:** Fix missing version in mongodb creating panics during scrapes **Link to tracking Issue:** Fixes #23859 **Testing:** No tests, really. **Documentation:** N/A commit 5a2214b73450cb8e59d74f3858409a1accd020eb Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:57:20 2023 +0200 [receiver/mongodbatlas] Change the types of `Config.PrivateKey` and `Config.Alerts.Secret` to be `configopaque.String` (#23865) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 35a2adb91a780c4b8f7a33eb9ca4fcb4bf92f7f6 Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:55:00 2023 +0200 [receiver/mysql] Change the type of `Config.Password` to be `configopaque.String` (#23868) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 4b935647eb02f1ec6be923d06cea637ffe16646a Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:54:09 2023 +0200 [receiver/mongodb] Change the type of `Config.Password` to be `configopaque.String` (#23866) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 151ab61d175861a03300a61836c9fd55ae1d915f Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:53:13 2023 +0200 [receiver/elasticsearch] Change the type of `Config.Password` to be `configopaque.String` (#23862) **Description:** Split out from: #17353 **Link to tracking Issue:** commit a754d0e3cd53b63a4e0b577adc9be5368bd9e33c Author: Ziqi Zhao <[email protected]> Date: Fri Jun 30 16:40:59 2023 +0800 [chore] fix exhaustive lint for datadog exporter (#23838) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit efca12365053d560dadf5876b4cef12fb588f599 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 22:44:40 2023 -0700 [chore] set remoteobserverprocessor to alpha (#23858) Fixes #19633 commit 2fd6dbfeec7ba4f9625e5051d36f0bbdd8d8b5f0 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 21:04:09 2023 -0700 Rename websocketprocessor to remoteobserverprocessor (#23857) **Description:** Rename websocketprocessor to remoteobserverprocessor **Link to tracking Issue:** Fixes #23856 commit 21928994067957530840fa6ca9ee76fee79664e4 Author: Ziqi Zhao <[email protected]> Date: Fri Jun 30 09:17:01 2023 +0800 [chore] [exporter/clickhouse] fix exhaustive lint (#23853) related to #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit c61650dc25b294460120dc6e059dd6f2ac521774 Author: Daniel Jaglowski <[email protected]> Date: Thu Jun 29 18:41:22 2023 -0400 [chore] Remove flaky rabbitmq integration test (#23846) Resolves #22134 commit 1fe8fdf8063e95c36485a7fd3c39d0b0df00159a Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 13:32:20 2023 -0700 Add pod metrics (#23844) **Description:** Add explicitly `k8s.node.allocatable_pods` to the list of Kubernetes node metrics available, which went missing during the pdata translation **Link to tracking Issue:** commit 377f6664b658c450c5eda0f0e43462c4a81417b5 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 12:35:56 2023 -0700 [chore] [receiver/k8s_cluster] update the tests to cover all the existing k8s node metrics (#23841) commit 9a521ed97cea5b3a2f742a692a288621cbb728bf Author: Alex Boten <[email protected]> Date: Thu Jun 29 11:02:55 2023 -0700 [chore] make update-otel (#23837) Signed-off-by: Alex Boten <[email protected]> commit 3c934d6220da41d76276c7ec0c26e58db5ada8c6 Author: Irina <[email protected]> Date: Thu Jun 29 17:47:02 2023 +0100 [chore] translator/loki: remove deprecated code (#23827) **Description:** <Describe what has changed.> When did the massive cleaning of the deprecated code in loki translator, forgot to remove LogsToLoki method **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/15653 commit 0e12ba7b04474df7fe36886ffbd3fa994a1bcd92 Author: Adam Boguszewski <[email protected]> Date: Thu Jun 29 08:08:21 2023 -0700 [chore]: update status for carbon exporter and receiver (#23834) **Description:** These components have codeowner again, so their status has been changed to `beta` (as it was before changing to `unmaintained`) commit 850add36a712f25ae0883212c7615125d15bbeec Author: Ziqi Zhao <[email protected]> Date: Thu Jun 29 22:56:24 2023 +0800 fix exhaustive lint for receivercreater (#23831) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit ead6114904fd240a4d26a2ac0cf8437fdacd115a Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:39:55 2023 +0200 [receiver/aerospikereceiver] Change the type of `Config.Password` to be `configopaque.String` (#23828) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 56d662550fbbbb3356b64866f05c80bf9997d263 Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:30:22 2023 +0200 [receiver/bigip] Change the type of `Config.Password` to be `configopaque.String` (#23830) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 5550060f3df6cd585db21c014a7b2ed97799615b Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:29:56 2023 +0200 [receiver/couchdb] Change the type of `Config.Password` to be `configopaque.String` (#23833) **Description:** Split out from: #17353 **Link to tracking Issue:** commit c404e07bf35dd76aabe6a17f63a41850f782ce2b Author: Carson Cook <[email protected]> Date: Thu Jun 29 08:22:18 2023 -0400 elasticsearchexporter: use configured dedup and dedot values (#19420) **Description:** <Describe what has changed.> Fixes bug in elasticsearch exporter where `mapping.dedup` and `mapping.dedot` values aren't used, even though they are documented as having an effect. **Link to tracking Issue:** #19419 --------- Signed-off-by: Carson Cook <[email protected]> commit 3dfc0f9ceb7deaa02a135e2fde952abb4e2b0bb4 Author: AJ Saclayan <[email protected]> Date: Thu Jun 29 05:54:00 2023 -0500 [connector/spanmetrics] fix delta temporality metrics (#23799) **Description:** Today, when you configure a spanmetricsconnector to emit metrics with delta temporality, the `startTimestamp` is not updated when deltas are calculated. Ideally, each new metric generated should have a timestamp at which the metric does the span aggregation. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/7128 **Testing:** Built otelcolcontrib docker image with changes and ran locally with the following configuration: ```yaml receivers: otlp: protocols: grpc: http: cors: allowed_origins: ["*"] allowed_headers: ["*"] exporters: otlp/newrelic: endpoint: https://otlp.nr-data.net:4317 headers: api-key: ${NEW_RELIC_LICENSE_KEY} logging: connectors: spanmetrics: histogram: exponential: max_size: 160 dimensions_cache_size: 2000 aggregation_temporality: "AGGREGATION_TEMPORALITY_DELTA" metrics_flush_interval: 15s service: telemetry: logs: level: debug pipelines: traces: receivers: [otlp] exporters: [spanmetrics] metrics: receivers: [spanmetrics] exporters: [logging, otlp/newrelic] ``` and sent the following payload twice (a couple minutes apart): ```json { "resourceSpans": [ { "resource": { "attributes": [ { "key": "service.name", "value": { "stringValue": "my.service" } } ], "droppedAttributesCount": 0 }, "scopeSpans": [ { "scope": { "name": "test", "version": "1.0.0" }, "spans": [ { "traceId": "02cfc23b60d24d708f5b478177f2c51d", "spanId": "00f067aa0ba902b7", "traceState": "", "parentSpanId": "0123abc456def789", "name": "test_span_metrics_connector", "kind": "SPAN_KIND_INTERNAL", "startTimeUnixNano": {{timeUnixNano1SecAgo}}, "endTimeUnixNano": {{timeUnixNano}}, "attributes": [ ], "droppedAttributesCount": 0, "events": [], "droppedEventsCount": 0, "links": [], "droppedLinksCount": 0, "status": { } } ] } ] } ] } ``` Note in green there are two histograms, with the timestamps updated. The red was tested with the same configuration without the change. <img width="1024" alt="image" src="https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/55757302/386d3218-b1d3-49d9-a86b-0c3fd4b61bd6"> **Documentation:** <Describe the documentation added.> commit fbd85e02bd03a144a6b96d4b5fd6b6b4c6e1594c Author: PaoloGallina <[email protected]> Date: Wed Jun 28 22:20:43 2023 +0200 [admin] feat(ci/cd): add version validation to prepare-release (#23818) **Description:** Adding version validation to prepare-release I used the same regex already used in [set_release_tag.sh](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7e74bd350192456ded06ae80fb5586bec921f2e0/.github/workflows/scripts/set_release_tag.sh#L7), just without the v. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21490 commit 7e74bd350192456ded06ae80fb5586bec921f2e0 Author: Raphael Philipe Mendes da Silva <[email protected]> Date: Wed Jun 28 11:23:57 2023 -0700 [chore] Add warning to the awscontainerinsightsreceiver (#23817) **Description:** Add warning section to the awscontainerinsightsreceiver **Link to tracking Issue:** #19172 Signed-off-by: Raphael Silva <[email protected]> commit 0ab552c249007ece56d19a41778ccebc9fedc45f Author: Ziqi Zhao <[email protected]> Date: Thu Jun 29 00:59:17 2023 +0800 [chore] fix exhaustive lint for kubeletstatsreceiver (#23815) **Description:** <Describe what has changed.> related #23266 --------- Signed-off-by: Ziqi Zhao <[email protected]> commit 8772353e38e4a7feb2af272698ee039692b21efa Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 09:54:48 2023 -0700 [chore] enable exhaustive lint for mdatagen (#23806) commit 5adb2373c26d70559a1f0b23c6711ec98689d579 Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 09:53:58 2023 -0700 [chore] signalfxexporter exhaustive lint (#23802) commit f50151e31e5220d601f127d4632685d6b0ed16ee Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 08:53:20 2023 -0700 [chore] enable exhaustive lint for k8sclusterreceiver (#23803) commit 08202563ce02b03c389493bdb4b51de66dbb9e78 Author: Tyler Helmuth <[email protected]> Date: Wed Jun 28 09:10:22 2023 -0600 [processor/transform] Add new example (#23812) **Description:** Adds an example of how to set a new attribute from another telemetry path. commit f195900aa20617dca2370df638f4776a0ffc160e Author: Dominik Rosiek <[email protected]> Date: Wed Jun 28 16:21:45 2023 +0200 feat!(mysqlreceiver): set `mysql.locked_connects` as optional in order to remove it in next release (#23673) Set `mysql.locked_connects` as optional, as it is duplication of `mysql.connection.errors` metric Signed-off-by: Dominik Rosiek <[email protected]> commit 37a919c51095de6f5dbb5f8655eb712555f04aa4 Author: Mikołaj Świątek <[email protected]> Date: Wed Jun 28 14:23:49 2023 +0100 [receiver/windowseventlog] Fix buffer overflow when reading raw events (#23678) **Description:** Fixing a bug where an event larger than half the buffer capacity would cause a panic due to an overflow. The reason this happens is because raw events are render using the `evtRender` syscall, which returns the byte count, rather than the UTF16 character count, but we treat it as if it was the latter. **Link to tracking Issue:** #23677 **Testing:** Added some tests for previously untested parts of the code, and a test that triggers the problem in particular. I've also done a E2E test on a live system which previously triggered the problem, but doesn't after the fix. commit 207b866e03813cae04b0db85e376b3bb8d76470e Author: Ziqi Zhao <[email protected]> Date: Wed Jun 28 16:45:55 2023 +0800 fix exhaustive lint for awscontainerinsightreceiver (#23772) **Description:** Related issue #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 5d7b22d54585cd654eae00a41c63eaa89d76cc2c Author: Braydon Kains <[email protected]> Date: Tue Jun 27 19:24:40 2023 -0400 [receiver/hostmetrics] add process.handles metric (#22813) **Description:** <Describe what has changed.> Adds a new Windows-exclusive metric called process.handles, which represents the handle count of the given process. When enabled, the receiver will make a WMI Query at the beginning of each scrape to update the handle count for all processes on the system. If the metric is enabled on a platform other than Windows, an error will be produced when attempting to refresh handle counts. This matches the rough behaviour of the Linux exclusive `process.open_file_descriptors`. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> Ran the binary with the following configuration: ``` receivers: hostmetrics: collection_interval: 2s scrapers: cpu: {} disk: {} filesystem: {} load: {} memory: {} network: {} paging: {} process: mute_process_name_error: true metrics: process.handles: enabled: true processes: {} exporters: file: path: x.json service: pipelines: metrics: receivers: [hostmetrics] exporters: [file] ``` The following is an example result of a scrape with this configuration. https://gist.github.com/braydonk/c97996272574319e03111dc79076a1bd commit 2d23e4d9e0eb313da5d192e1066f444d19b8601f Author: Adam Boguszewski <[email protected]> Date: Tue Jun 27 13:58:00 2023 -0700 [chore][carbonreceiver][carbonexporter]: add aboguszewski-sumo as code owner (#23676) These components are lacking a codeowner, so I'd like to take this role. commit d200d2e50fa0e086ea91fbcb76764294040754cf Author: splunkertimn <[email protected]> Date: Tue Jun 27 16:01:07 2023 -0400 [receiver/syslog] fixed syslog octet frame parsing (#23645) Parse multiple syslog events from a single packet when octet framing is enabled. commit 7a1061d300e8fa990849bfcb2d4a2863ceebc44c Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 11:58:42 2023 -0700 [chore] fix pod and container metadata to include parent and units (#23795) **Description:** Add parent information to pod and container metadata. **Link to tracking Issue:** Fixes #23793 commit c4dd245e186208f4ecd093552920ae5612284de5 Author: Pranav Shankar <[email protected]> Date: Tue Jun 27 20:55:09 2023 +0200 [receiver/sqlquery] Add support of optional Start and Stop Timestamp (#19160) In this PR, support for Start and Stop Timestamp to be picked up from the metrics stored in the rows is added. This will allow SQL queries to be more expressive and allows users to define the period of aggregation which is not only dependent on the default system time set upon processing. **Link to tracking Issue:** --------- Co-authored-by: Juraci Paixão Kröhling <[email protected]> commit 1edf7c9c03cb04e2002696b966ca70f2996c2a38 Author: Goutham Veeramachaneni <[email protected]> Date: Tue Jun 27 19:28:23 2023 +0200 docs: Clarify what an association is in k8sattr. processor (#23661) It took me several readings of the docs to understand what is happening in the config. I tried to clarify what an association is and how they are specified. I've removed the line "All rules are going to be executed, and combination of result is going to be a pod metadata cache key." because it actually doesn't matter from a user perspective. It looks like an internal detail and is confusing in this section of the docs. Signed-off-by: Gotham <[email protected]> commit 1e60629434bcd1f8d04f1d1976f41b1ad7c67a52 Author: Mend Renovate <[email protected]> Date: Tue Jun 27 19:26:29 2023 +0200 chore(deps): update wandalen/wretry.action action to v1.3.0 (#23771) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [Wandalen/wretry.action](https://togithub.com/Wandalen/wretry.action) | action | minor | `v1.0.36` -> `v1.3.0` | --- <details> <summary>Wandalen/wretry.action (Wandalen/wretry.action)</summary> [`v1.3.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0) [`v1.2.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0) [`v1.0.42`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42) [`v1.0.41`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41) [`v1.0.40`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40) [`v1.0.39`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39) [`v1.0.38`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38) [`v1.0.37`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37) </details> --- 📅 **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:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> commit 6a35e5f9405d8b03c149dfec952dcac3b162662d Author: OpenTelemetry Bot <[email protected]> Date: Tue Jun 27 10:24:05 2023 -0700 [chore] dependabot updates Tue Jun 27 15:57:22 UTC 2023 (#23785) Bump Wandalen/wretry.action from 1.0.36 to 1.3.0 Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.15.0 to 1.15.2 in /exporter/datadogexporter Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.15.0 to 1.15.2 in /processor/resourcedetectionprocessor Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in /receiver/saphanareceiver Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in /receiver/sqlqueryreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awsxrayreceiver Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in /internal/tools Bump github.com/google/cadvisor from 0.47.1 to 0.47.2 in /receiver/awscontainerinsightreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.685 to 1.0.687 in /exporter/tencentcloudlogserviceexporter Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /extension/observer/dockerobserver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /internal/coreinternal Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/aerospikereceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/apachereceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/dockerstatsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/elasticsearchreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/flinkmetricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/jmxreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/kafkametricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/memcachedreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/mongodbreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/mysqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/nginxreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/postgresqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/rabbitmqreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/redisreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/riakreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/sqlqueryreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/zookeeperreceiver Bump go.mongodb.org/mongo-driver from 1.11.7 to 1.12.0 in /receiver/mongodbreceiver Bump go.opentelemetry.io/collector/cmd/builder from 0.79.0 to 0.80.0 in /internal/tools Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /cmd/telemetrygen Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /examples/demo/client Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /examples/demo/server Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/coralogixexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/googlecloudpubsubexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/jaegerexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/opencensusexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/skywalkingexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/asapauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/basicauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/bearertokenauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/headerssetterextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/jaegerremotesampling Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/oauth2clientauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/sigv4authextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /processor/routingprocessor Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /processor/spanmetricsprocessor Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/jaegerreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/opencensusreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/skywalkingreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/datadogexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/logzioexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/tencentcloudlogserviceexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /pkg/translator/opencensus Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/collectdreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/opencensusreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/prometheusreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/skywalkingreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/solacereceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/zipkinreceiver --------- Signed-off-by: Alex Boten <[email protected]> Co-authored-by: Alex Boten <[email protected]> commit 3d893e2727a4144488d09badb518c45b82422f2f Author: ZahidMirza95 <[email protected]> Date: Tue Jun 27 10:15:09 2023 -0700 [receiver/filelog] added example, additional info to configs and info on log rotation (#23609) Added example on how to use filelog receiver with log files. Also, added some details to the configuration descriptions and added anchor to some sections in the document. Additionally, added information on log rotation. - Added example on how to use filelog receiver with log files - Also, added some details to the configuration descriptions - Added information on log rotation - Added anchors to some sections commit 88ba4ed63e1bda1cbbb7ba42f6b5e1354d266791 Author: Mackenzie <[email protected]> Date: Tue Jun 27 18:54:10 2023 +0200 [cmd/mdatagen] Add validation to metadata.yaml (#23783) **Description:** This PR adds validation to mdatagen. It ensures that all required fields are present, and validates their content. The validation lies mostly in `validate.go` (and for tests `validate_test.go`), however validation that needs to be done via decoding lies in `loader.go` + `metricdata.go` (and for tests `loader_test.go`). **Link to tracking Issue:** commit 64ebfbce662f261b3afbf6bef7d5d6c7ee80de69 Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 09:43:04 2023 -0700 Switch k8s.pod and k8s.container metrics to use pdata. (#23441) Updates https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/4367 commit fa2e2255f7ec5b9f2f0d003b23515aa805df0053 Author: Daniel Jaglowski <[email protected]> Date: Tue Jun 27 12:31:18 2023 -0400 Revert "[pkg/stanza/fileconsumer] Fix issue where buffer size could cause incorrect fingerprint update" (#23781) Reverts open-telemetry/opentelemetry-collector-contrib#23183 Several rotation test failures have been observed since this was merged. ([example](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5391301380/jobs/9787962306?pr=23780#step:8:75)) I do not immediately see the problem so I think this needs to be reverted for now. commit 34b47334a19b50210cb14de9ae3326cc0d285261 Author: Daniel Jaglowski <[email protected]> Date: Tue Jun 27 12:19:15 2023 -0400 [chore] Add 'test' as prerequisite to default module-level make target (#23779) We've documented the intended approach to our default targets [here](https://github.com/open-telemetry/opentelemetry-collector/blob/5852d09fb7b519e18610b99fc5a9da8cddbbf790/CONTRIBUTING.md?plain=1#L589-L591). In `Makefile.Common`, the default target is `common`. This adds the `test` target as a prerequisite. commit dea886211de3abab9bb7ca9c2cae6b45947b7cf3 Author: Mend Renovate <[email protected]> Date: Tue Jun 27 17:17:16 2023 +0200 chore(deps): update docker-compose deps (#23770) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [otel/opentelemetry-collector-contrib](https://togithub.com/open-telemetry/opentelemetry-collector-releases) | minor | `0.79.0` -> `0.80.0` | | prom/prometheus | minor | `v2.44.0` -> `v2.45.0` | --- <details> <summary>open-telemetry/opentelemetry-collector-releases (otel/opentelemetry-collector-contrib)</summary> [`v0.80.0`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.80.0) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-releases/compare/v0.79.0...v0.80.0) - [`3fe11dc`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3fe11dc) Update versions to v0.80.0 ([#​362](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/362)) - [`f82587a`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/f82587a) Add warning about git tags ([#​359](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/359)) - [`3af8267`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3af8267) Bump github.com/goreleaser/nfpm/v2 from 2.29.0 to 2.30.1 ([#​358](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/358)) - [`cb3c890`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/cb3c890) Add all missing components to contrib distribution manifest ([#​356](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/356)) - [`60a7e46`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/60a7e46) Add missing components to contrib distribution ([#​354](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/354)) - [`73fd3ae`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/73fd3ae) Add haproxyreceiver to the contrib distribution ([#​355](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/355)) - [`98597be`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/98597be) \[chore] bump go version ([#​352](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/352)) </details> --- 📅 **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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> commit 7e3548fd92e255572b240b8aadf0aff2d63da99c Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 07:04:32 2023 -0700 [chore] make azureeventhubreceiver pass exhaustive linting (#23774) commit c247210d319a58665f1988e231a5c5fcfc9b8383 Author: Marc Sanmiquel <[email protected]> Date: Tue Jun 27 08:12:20 2023 +0200 [receiver/dockerstats] Add optional resource attributes (#21185) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add `container.image.id` and `container.command_line` as optional resource attributes, disabled by default. **Link to tracking Issue:** <Issue number if applicable> Tracking issue https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21092 **Testing:** <Describe what testing was performed and which tests were added.> Until this point, all resource attributes have been enabled by default, resulting in the coupling of the [test](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7bf5d66fae6c1c5360ec2875948f2c2adab6c44f/receiver/dockerstatsreceiver/receiver_test.go#L191) to the default configuration. In order to test the current implementation with the new resource attributes enabled & disabled, a minor refactoring was required in the `TestScrapeV2` test, allowing to pass different configurations for each test. Refer to the following commit 508dbee9aa9a22c1ca79f16bba5abeecceeb9c48 to check the refactor in the test. **Documentation:** <Describe the documentation added.> New resource attributes documentation was generated by `mdatagen`. commit c15794f8b3ad8bdf1bbf5abfba8486df4ad1b7c9 Author: Mackenzie <[email protected]> Date: Mon Jun 26 22:24:45 2023 +0200 [cmd/mdatagen] Add parent field to metadata.yaml file for subcomponents (#23636) This PR adds a `parent` field to the `metadata.yaml`. This is used in subcomponents, and the field contains the type of their parent component. --------- Co-authored-by: Dmitrii Anoshin <[email protected]> commit c2401dbbc240783005454f7b7046a303d495c5e1 Author: Mackenzie <[email protected]> Date: Mon Jun 26 20:04:16 2023 +0200 postgresqlreceiver: Add missing units in metadata.yaml (#23571) Metric unit is required, see: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/mdatagen/metadata-schema.yaml#L72-L73. This PR adds the unit to metrics where this is missing: - postgresql.bgwriter.maxwritten - postgresql.table.count commit 9fe4230817a192049f6c539f6c5d9ea31ce05f99 Author: Mike Dame <[email protected]> Date: Mon Jun 26 13:32:09 2023 -0400 [chore]: Update GCP dependencies (#23679) **Description:** Updates GCP libraries to v0.39.2 and 1.15.2 **Documentation:** updated readmes for new experimental WAL fields commit a7045cbee91a7d9fc6b16554ee4cf2ab2284a396 Author: Daniel Jaglowski <[email protected]> Date: Mon Jun 26 11:52:26 2023 -0400 [chore] Fix spark integration test by pinning version (#23675) Fixes #23670 The test appears to have begun failing when the [`latest`](https://hub.docker.com/layers/apache/spark/latest/images/sha256-a1dd2487a97fb5e35c5a5b409e830b501a92919029c62f9a559b13c4f5c50f63?context=explore) tag of for the image was updated. This PR just pins the version. commit bf00ae8213b55f2abf73a4df1c0a15dd1367c813 Author: Murphy Chen <[email protected]> Date: Mon Jun 26 23:52:09 2023 +0800 [exporter/clickhouse] Fix create database failure (#23666) resolve: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23664 commit 6f0fabb2ace265ebb18fb2f716567b4f7af1f335 Author: Murphy Chen <[email protected]> Date: Mon Jun 26 23:04:57 2023 +0800 [exporter/clickhouse] Add scope columns to log table (#23667) resolve: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/20280 commit fbe16e156cd90e11cbe5b70c59a83d94dc923cf4 Author: Daniel Jaglowski <[email protected]> Date: Mon Jun 26 09:24:56 2023 -0400 [pkg/stanza/fileconsumer] Fix issue where buffer size could cause incorrect fingerprint update (#23183) The logic for determining when to update a fingerprint previously failed to account for the case where the buffer size is smaller than the fingerprint. This allows the fingerprint to be truncated in some cases. This PR rewrites the logic to explicitly handle each expected case, with optimization for handling the most common cases first. commit 04327f5deaebd5f8abea3b313dd2f45ccef5bf7e Author: Olga <[email protected]> Date: Mon Jun 26 12:26:46 2023 +0200 [processor/resourcedetection] add resource_attributes to every detector in resource processor (#23253) **Description:** Adding resource_attributes option to every detector in resource detection processor <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** [21482](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21482) **Testing:** Unit test for `resource_attribute` config, adjusting current unit tests to the new implementation **Documentation:** Updated README.md --------- Co-authored-by: Dmitrii Anoshin <[email protected]> commit 1a096adbeb24abc94eb9da2ea0126cf646d44c9b Author: Dmitrii Anoshin <[email protected]> Date: Mon Jun 26 02:31:07 2023 -0700 [chore] [receiver/apachespark] Disable failing integration test (#23671) Temporarily disable the integration test to unblock the CI. Updates https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23670 commit da5df85e77bb717e87096c20663ddc8bbb5ebf8a Author: Juan Manuel "Kang" Pérez <[email protected]> Date: Sun Jun 25 07:12:50 2023 +0200 [receiver/dockerstatsreceiver] Add metrics that are only available on hosts that use cgroups v2 (#22706) **Description:** This PR updates the documentation of all the metrics that are available only on cgroups v1 or cgroups v2. It PR also adds two metrics that are only available when the host is using cgroups v2: * `container.memory.anon` * `container.memory.file` Both are documented here: https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files I enabled the metric `container.memory.file` by default (causing a breaking change) because it is a metric that was already scraped for cgroups v1, contained in the metric `container.memory.total_cache`. ```yaml container.memory.total_cache: enabled: true description: "Total amount of memory used by the processes of this cgroup (and descendants) that can be associated with a block on a block device. Also accounts for memory used by tmpfs (Only available with cgroups v1)." container.memory.file: enabled: true description: "Amount of memory used to cache filesystem data, including tmpfs and shared memory (Only available with cgroups v2)." ``` Let me know your thoughts about this breaking change. **Link to tracking Issue:** #21097 **Testing:** The refactor done during PR #21110 had mocks ready to test these new metrics. There is no need to add more tests. **Documentation:** To see which metrics are available in Docker: * v1: https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L86 * v2: https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L195 Kernel cgroup documentation: * v1: https://docs.kernel.org/admin-guide/cgroup-v1/memory.html * v2: https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files commit 8ba48f6c48a1523fb2b7ec034b8d4d5e44f9e642 Author: Bomin Rahmani <[email protected]> Date: Fri Jun 23 15:18:45 2023 -0400 [receiver/postgresql] Fix blocks read metric (#23657) **Description:** <Describe what has changed.> fixed an issue where postgresql receiver was emitting the same attribute value "toast_hit" twice under postgresql.blocks_read metric. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> commit 0c625d042498a9985c51cee6476d4c17cfa0570b Author: Bomin Rahmani <[email protected]> Date: Fri Jun 23 15:18:05 2023 -0400 [receiver/vcenter] Fix datastore disk usage metric (#23654) **Description:** Fixed a bug in which the Vcenter receiver was incorrectly emmiting the disk_state: used datapoint twice under the vcenter.datastore.disk.usage metric instead of a disk_state: used disk_state: available **Documentation:** <Describe the documentation added.> commit 403b0eff117df29d969cc18706d1c58b605db8e2 Author: bryan-aguilar <[email protected]> Date: Fri Jun 23 10:15:36 2023 -0700 [receiver/awsecscontainermetrics] Fix possible panics from unchecked de-references (#23644) Fixes possible panics from unchecked de-references in metrics helper in `awsecscontainermetrics` receiver. **Link to tracking Issue:** https://github.com/aws-observability/aws-otel-collector/issues/2110 **Testing:** Added unit tests for these de-references **Documentation:** n//a commit c40be10a6e75e5ea15916d1dfeec95bf4de7a32c Author: PaoloGallina <[email protected]> Date: Fri Jun 23 19:14:36 2023 +0200 feat(statsdReceiver): add name and version to scope (#23564) Following the same approach of https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20903 I am adding the scope whenever the metric is copied. We could also add the _scope_ at creation time, however, it would change the signature of several functions having already too many parameters. **Link to tracking Issue:** <Issue number if applicable> Fix https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23563 **Testing:** Added a test to cover the new use case commit b2a1d1f47e43843d3fc2078bcc1191d44973162e Author: Tomáš Žďára <[email protected]> Date: Fri Jun 23 19:12:48 2023 +0200 DSET-3468: update dataset-go to latest, send more details in user-agent (#23640) **Description:** updated dataset-go library, send more details in user-agent For more details see https://github.com/scalyr/dataset-go/releases/tag/v0.0.9 **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/20660 / DSET-3468 **Testing:** verified via unit tests and also e2e with DataSet environment **Documentation:** see https://github.com/scalyr/dataset-go/blob/fbaead7856a9c5669262564dfa4a13aa14a0775d/examples/readme/main.go#L81 commit 7c0fd3de2aa7cbf61d6360c6208079c761992512 Author: OpenTelemetry Bot <[email protected]> Date: Thu Jun 22 15:26:02 2023 -0700 Add JMX metrics gatherer version 1.27.0-alpha (#23435) Add JMX metrics gatherer version `1.27.0-alpha`. cc @open-telemetry/java-contrib-approvers commit 703be0d287915f34d1d8f23d48e1292e1c0d82bb Author: ZenoCC-Peng <[email protected]> Date: Thu Jun 22 13:43:15 2023 -0700 [receiver/kafkametrics] Fix metrics in kafkametricsreceiver (#4327) (#23632) Utilize mdatagen to modify certain metrics from gauge to non-monotonic sum, employing delta aggregation. Adjust the test files to align with the sum test type and update the expected.yaml file for integration testing purposes. Co-authored-by: zeno-splunk <[email protected]> commit 03b375ebef74eee1a25e9e82ea5815ef29f373d7 Author:…
commit 2ae4bb7319f43c979735e96e1f782494e05e0cc7 Author: OpenTelemetry Bot <[email protected]> Date: Wed Jul 5 04:13:15 2023 -0700 [chore] Prepare release 0.81.0 (#23978) The following commands were run to prepare this release: - make chlog-update VERSION=v0.81.0 - sed -i.bak s/0.80.0/0.81.0/g versions.yaml - make multimod-prerelease - make multimod-sync --------- Co-authored-by: Pablo Baeyens <[email protected]> commit e9bdc636a01731bc1531f0b1a74859812e073eb4 Author: Pablo Baeyens <[email protected]> Date: Wed Jul 5 12:50:05 2023 +0200 Revert "[chore] Remove skip flaky test for hostmetricsreceiver" (#23982) Reverts open-telemetry/opentelemetry-collector-contrib#23874. The test is still flaky on Windows. commit f85dd5b4b59282932db14a1187ad3687083b4c5c Author: Pablo Baeyens <[email protected]> Date: Wed Jul 5 11:21:45 2023 +0200 Make sed replace statements more resilient (#23977) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> While working on open-telemetry/opentelemetry-collector/issues/8033, I got the following error ([full logs](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5461142477/jobs/9938863136)): ``` github.com/open-telemetry/opentelemetry-collector-contrib/cmd/otelcontribcol imports github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver imports github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver/internal/collection imports github.com/openshift/api/quota/v1: reading github.com/openshift/api/go.mod at revision v0.0.0-20.81.01171038-322a19404e37: unknown revision v0.0.0-20.81.01171038-322a19404e37 ``` This is because the script for preparing releases has the following sed statement: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/10e46605b7b9f775a3658f4e2ba59960ffe33847/cmd/otelcontribcol/builder-config.yaml#L416 which ends up replacing `018080` within the `openshift/api` pseudoversion by `0.81.0`. To work around this, we make the replace statements more specific. An alternative would be something like https://stackoverflow.com/a/2705678, but this approach is still broken if a dependency we are replacing has exactly the version we are updating from, so I think ultimately we need a different approach. **Testing:** I tested this on https://github.com/mx-psi/opentelemetry-collector-contrib/actions/runs/5462095129/jobs/9940974190; the job is able to run until the point of creating the PR, where it fails because the bot account does not have permission to create a PR. commit 10e46605b7b9f775a3658f4e2ba59960ffe33847 Author: John Law <[email protected]> Date: Wed Jul 5 08:21:22 2023 +1200 [ci] Specify 7 as arm version for arm build in CI (#23436) **Description:** Currently, we specify arm architecture in the cross build test without specifying the `GOARM` variable. This means the `GOARM` value falls back to the default and the default value depends on the platform that we are building on. We are building on `linux/amd64` machine in github action, so the `GOARM` defaults to `5`. [There are changes to default to GOARM=7 for all non-arm systems in the upcoming golang version](https://go-review.googlesource.com/c/go/+/470695) I'm looking to add an armv7 release, so without waiting for the newer golang version, I want to explicitly set the arm version in the CI to align with the release arm version. In this pull request, I expanded the configuration for arm build by adding a new block with the arm version under `include`. Then introduce the `GOARM` environment variable when calling `make otelcontribcol` **Testing:** Able to run `make GOOS=x GOARCH=y GOARM=z otelcontribcol` with the following configurations locally - [x] `GOOS=linux`, `GOARCH=arm`, `GOARM=7` - [x] `GOOS=linux`, `GOARCH=arm64`, `GOARM=` - [x] `GOOS=darwin`, `GOARCH=amd64`, `GOARM=` - [x] `GOOS=window`, `GOARCH=amd64`, `GOARM=` commit d51d3135984633d7d07fdb42f38ef122849e548a Author: Jonah Kowall <[email protected]> Date: Tue Jul 4 16:20:42 2023 -0400 Removing jkowall from codeowners for logzioexporter (#23845) Removing @jkowall from codeowners https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20768 Signed-off-by: Jonah Kowall <[email protected]> commit 9caec802b06e75bdb4a3f6b27409bfbefca543b8 Author: Daniel Jaglowski <[email protected]> Date: Tue Jul 4 16:19:47 2023 -0400 [chore] Minor cleanup of vcenter metric code (#23873) commit aa6560128d4cd9f7a540935a8b3e2a4c603e38c0 Author: David Ashpole <[email protected]> Date: Tue Jul 4 16:17:13 2023 -0400 Add dashpole back to auto-assignees (#23876) I'm back from leave! commit 65cc16d880571ef2224154253dbea885f5d8fac9 Author: David Ashpole <[email protected]> Date: Tue Jul 4 16:16:10 2023 -0400 Remove tbarker from codeowners (#23877) **Description:** Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23405 @tbarker25 doesn't work on OpenTelemetry for Google anymore. cc @punya commit d98c227f8d4c7072344a46ae1d2d64e33c2b8644 Author: OpenTelemetry Bot <[email protected]> Date: Tue Jul 4 11:23:18 2023 -0700 [chore] dependabot updates Tue Jul 4 17:49:08 UTC 2023 (#23954) Bump cloud.google.com/go/pubsub from 1.31.0 to 1.32.0 in /exporter/googlecloudpubsubexporter Bump cloud.google.com/go/pubsub from 1.31.0 to 1.32.0 in /receiver/googlecloudpubsubreceiver Bump github.com/DataDog/datadog-api-client-go/v2 from 2.13.0 to 2.14.0 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/attributes from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/logs from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/otlp/metrics from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/DataDog/opentelemetry-mapping-go/pkg/quantile from 0.5.0 to 0.5.1 in /exporter/datadogexporter Bump github.com/aliyun/aliyun-log-go-sdk from 0.1.49 to 0.1.50 in /exporter/alibabacloudlogserviceexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.294 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.290 to 1.44.295 in /internal/aws/cwlogs Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in /internal/tools Bump github.com/hashicorp/consul/api from 1.21.0 to 1.22.0 in /internal/metadataproviders Bump github.com/hashicorp/consul/api from 1.21.0 to 1.22.0 in /processor/resourcedetectionprocessor Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /exporter/fileexporter Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /exporter/sapmexporter Bump github.com/klauspost/compress from 1.16.6 to 1.16.7 in /receiver/sapmreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /exporter/signalfxexporter Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /extension/observer/hostobserver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/awscontainerinsightreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/hostmetricsreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /receiver/jmxreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.5 to 3.23.6 in /testbed Bump github.com/sijms/go-ora/v2 from 2.7.6 to 2.7.8 in /receiver/sqlqueryreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.687 to 1.0.692 in /exporter/tencentcloudlogserviceexporter Bump github.com/vmware/govmomi from 0.30.4 to 0.30.5 in /receiver/vcenterreceiver Bump go.mongodb.org/atlas from 0.29.0 to 0.30.0 in /receiver/mongodbatlasreceiver Bump golang.org/x/vuln from 0.1.0 to 0.2.0 in /internal/tools Bump google.golang.org/api from 0.128.0 to 0.129.0 in /exporter/f5cloudexporter Bump google.golang.org/api from 0.128.0 to 0.129.0 in /exporter/googlecloudpubsubexporter Bump google.golang.org/api from 0.128.0 to 0.129.0 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/api from 0.128.0 to 0.129.0 in /receiver/googlecloudspannerreceiver commit dbcf37ae329f0aef6f664ed5c05a9ac85f54579a Author: Ziqi Zhao <[email protected]> Date: Wed Jul 5 01:30:16 2023 +0800 [chore] fix exhaustive lint for dynatrace exporter (#23951) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 5d1f251e7ba5b013dcc0d4c96b510024d3a6da92 Author: Andrzej Stencel <[email protected]> Date: Tue Jul 4 19:29:19 2023 +0200 [chore] [receiver/snmp] fix docs on default collection interval (#23945) The default connection interval is actually `10s` and not `1m`. commit 3cb495438d022cecbb4e3c93f96088a787e02d3e Author: Tomaz Muraus <[email protected]> Date: Tue Jul 4 14:40:48 2023 +0200 [chore] [exporter/datasetexporter] Update metadata (#23885) This pull request updates metadata for DataSet exporter. Metadata was out of date and didn't reflect that the exporter plugin is distributed as part of contrib. --- NOTE: Per request in a PR review (atoulme), this change was moved out of https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/23672 to a new and separate PR. commit 81320c41004bdd739b5c4e5dafcf20230087c68b Author: Pavol Loffay <[email protected]> Date: Mon Jul 3 12:15:09 2023 +0200 Json payload in Kafka exporter is not experimental (#23884) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** <Issue number if applicable> Resolves https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23871 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> Signed-off-by: Pavol Loffay <[email protected]> commit 8510b37b1c427cc4d117cc65fcfc412ab7756420 Author: Ziqi Zhao <[email protected]> Date: Mon Jul 3 17:17:59 2023 +0800 [chore] fix exhaustive lint for podmanreceiver (#23823) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 537ba472f09a3b346b8cca8c6bdfa5d441707e11 Author: ZenoCC-Peng <[email protected]> Date: Mon Jul 3 01:41:49 2023 -0700 [chore] Remove skip flaky test for hostmetricsreceiver (#23874) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Run 20 times the GitHub Action on my personal branch, there were no test failures. See the files: [Hostmetricsreceiver-FlakyTest-10030.xlsx](https://github.com/open-telemetry/opentelemetry-collector-contrib/files/11911111/Hostmetricsreceiver-FlakyTest-10030.xlsx). **Link to tracking Issue:** <Issue number if applicable>[10030](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/10030) **Testing:** hostmetricsreceiver/internal/scraper/loadscraper/load_scraper_test.go --------- Co-authored-by: Alex Boten <[email protected]> Co-authored-by: zeno-splunk <[email protected]> commit 4c817c69a2fe9cab7f1a9c357a84eff7a40b7fe7 Author: Laser <[email protected]> Date: Fri Jun 30 21:25:25 2023 +0300 [connector/spanmetricsconnector] Added disabling options (#23039) **Description:** <Describe what has changed.> Added disabling options for histogram metrics and option to exclude default labels from all metrics. In some cases users want to optionally disable part of metrics because they generate too much data or are not needed. We've tried to use transform as [it was suggested here](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20525) And this helps in part of getting less data. But we consumed too much memory because of high cardinality labels. So we decided to suggest this mr to escape metric creation at the very beginning. **Link to tracking Issue:** [GH-16344] **Testing:** Added tests to the repository **Documentation:** Readme file updated --------- Co-authored-by: Antoine Toulme <[email protected]> commit 3c9ddf9726c5ec6ca66a8486a875a54102c8a8a2 Author: Miguel Rodriguez <[email protected]> Date: Fri Jun 30 14:23:57 2023 -0400 [receiver/filelog] Add Support for only reading the current file (#23633) Adding a feature to filelog to allow reading of only the current file from a collection of files through sorting the file names and picking the newest one. commit 95f0a13dd9c6045d1ce2c250ca0701d52b5f43f3 Author: Antoine Toulme <[email protected]> Date: Fri Jun 30 10:02:02 2023 -0700 [receiver/k8s_cluster] Add back all other vendor-specific node conditions (#23854) **Description:** Add back all other vendor-specific node conditions, and report them even if missing, as well as all allocatable node metrics if present, to the list of Kubernetes node metrics available, which went missing during the pdata translation **Link to tracking Issue:** Fixes #23839 **Testing:** Unit tests. **Documentation:** Not quite. Maybe a doc entry is required here. I haven't looked yet where to place it. commit 46d03a09bb7b137c59a032f93133c6ef0c8c1bca Author: Tyler Helmuth <[email protected]> Date: Fri Jun 30 10:41:50 2023 -0600 [internal/filter] filtermetric to filterottl bridge (#23141) **Description:** This PR adds a bridge between `filtermetric.NewSkipExpr` and `filterottl.NewBoolExprForMetric` behind a feature gate. With the feature gate enabled, any component using `filtermetric.NewSkipExpr` will start using OTTL behind the scenes. In addition, the filterprocessor's implementation of `newSkipResExpr`, which is a skip expression for resources, is bridged to `filterottl.NewBoolExprForResource`. Since this implementation exists only for filtering metrics, the same feature gate is used for both. While investigating the existing `internal/filtermetric` uses with filterprocessor and attributesprocessor I found that: - The attributes processor does not support Expressions or Resource Attributes. The readme claims that it does, but the implementation does not support it (and there are no tests). This bridge DOES NOT rectify that. - The filterprocessor allows filtering by resource attributes, expressions, and metric name. Unlike it's implementation for filtering spans and logs, the filterprocessor handles filtering spans at the Resource level loop. This is the most performant solution, and how OTTL likes to think about the problem, but it results in a different pattern than filtering spans and logs. This bridge DOES NOT attempt to move the resource implementation into `internal/filtermetric`. **Link to tracking Issue:** Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/18643 Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/18642 Depends on: - [x] https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/23142 **Testing:** Added tests comparing the output of the existing config and the bridge. commit f1068be12dee7664a74fd42354c27b3803c52bc4 Author: Antoine Toulme <[email protected]> Date: Fri Jun 30 05:58:54 2023 -0700 [receiver/mongodb] fix missing version (#23860) **Description:** Fix missing version in mongodb creating panics during scrapes **Link to tracking Issue:** Fixes #23859 **Testing:** No tests, really. **Documentation:** N/A commit 5a2214b73450cb8e59d74f3858409a1accd020eb Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:57:20 2023 +0200 [receiver/mongodbatlas] Change the types of `Config.PrivateKey` and `Config.Alerts.Secret` to be `configopaque.String` (#23865) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 35a2adb91a780c4b8f7a33eb9ca4fcb4bf92f7f6 Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:55:00 2023 +0200 [receiver/mysql] Change the type of `Config.Password` to be `configopaque.String` (#23868) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 4b935647eb02f1ec6be923d06cea637ffe16646a Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:54:09 2023 +0200 [receiver/mongodb] Change the type of `Config.Password` to be `configopaque.String` (#23866) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 151ab61d175861a03300a61836c9fd55ae1d915f Author: Mackenzie <[email protected]> Date: Fri Jun 30 14:53:13 2023 +0200 [receiver/elasticsearch] Change the type of `Config.Password` to be `configopaque.String` (#23862) **Description:** Split out from: #17353 **Link to tracking Issue:** commit a754d0e3cd53b63a4e0b577adc9be5368bd9e33c Author: Ziqi Zhao <[email protected]> Date: Fri Jun 30 16:40:59 2023 +0800 [chore] fix exhaustive lint for datadog exporter (#23838) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit efca12365053d560dadf5876b4cef12fb588f599 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 22:44:40 2023 -0700 [chore] set remoteobserverprocessor to alpha (#23858) Fixes #19633 commit 2fd6dbfeec7ba4f9625e5051d36f0bbdd8d8b5f0 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 21:04:09 2023 -0700 Rename websocketprocessor to remoteobserverprocessor (#23857) **Description:** Rename websocketprocessor to remoteobserverprocessor **Link to tracking Issue:** Fixes #23856 commit 21928994067957530840fa6ca9ee76fee79664e4 Author: Ziqi Zhao <[email protected]> Date: Fri Jun 30 09:17:01 2023 +0800 [chore] [exporter/clickhouse] fix exhaustive lint (#23853) related to #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit c61650dc25b294460120dc6e059dd6f2ac521774 Author: Daniel Jaglowski <[email protected]> Date: Thu Jun 29 18:41:22 2023 -0400 [chore] Remove flaky rabbitmq integration test (#23846) Resolves #22134 commit 1fe8fdf8063e95c36485a7fd3c39d0b0df00159a Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 13:32:20 2023 -0700 Add pod metrics (#23844) **Description:** Add explicitly `k8s.node.allocatable_pods` to the list of Kubernetes node metrics available, which went missing during the pdata translation **Link to tracking Issue:** commit 377f6664b658c450c5eda0f0e43462c4a81417b5 Author: Antoine Toulme <[email protected]> Date: Thu Jun 29 12:35:56 2023 -0700 [chore] [receiver/k8s_cluster] update the tests to cover all the existing k8s node metrics (#23841) commit 9a521ed97cea5b3a2f742a692a288621cbb728bf Author: Alex Boten <[email protected]> Date: Thu Jun 29 11:02:55 2023 -0700 [chore] make update-otel (#23837) Signed-off-by: Alex Boten <[email protected]> commit 3c934d6220da41d76276c7ec0c26e58db5ada8c6 Author: Irina <[email protected]> Date: Thu Jun 29 17:47:02 2023 +0100 [chore] translator/loki: remove deprecated code (#23827) **Description:** <Describe what has changed.> When did the massive cleaning of the deprecated code in loki translator, forgot to remove LogsToLoki method **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/15653 commit 0e12ba7b04474df7fe36886ffbd3fa994a1bcd92 Author: Adam Boguszewski <[email protected]> Date: Thu Jun 29 08:08:21 2023 -0700 [chore]: update status for carbon exporter and receiver (#23834) **Description:** These components have codeowner again, so their status has been changed to `beta` (as it was before changing to `unmaintained`) commit 850add36a712f25ae0883212c7615125d15bbeec Author: Ziqi Zhao <[email protected]> Date: Thu Jun 29 22:56:24 2023 +0800 fix exhaustive lint for receivercreater (#23831) **Description:** related #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit ead6114904fd240a4d26a2ac0cf8437fdacd115a Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:39:55 2023 +0200 [receiver/aerospikereceiver] Change the type of `Config.Password` to be `configopaque.String` (#23828) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 56d662550fbbbb3356b64866f05c80bf9997d263 Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:30:22 2023 +0200 [receiver/bigip] Change the type of `Config.Password` to be `configopaque.String` (#23830) **Description:** Split out from: #17353 **Link to tracking Issue:** commit 5550060f3df6cd585db21c014a7b2ed97799615b Author: Mackenzie <[email protected]> Date: Thu Jun 29 15:29:56 2023 +0200 [receiver/couchdb] Change the type of `Config.Password` to be `configopaque.String` (#23833) **Description:** Split out from: #17353 **Link to tracking Issue:** commit c404e07bf35dd76aabe6a17f63a41850f782ce2b Author: Carson Cook <[email protected]> Date: Thu Jun 29 08:22:18 2023 -0400 elasticsearchexporter: use configured dedup and dedot values (#19420) **Description:** <Describe what has changed.> Fixes bug in elasticsearch exporter where `mapping.dedup` and `mapping.dedot` values aren't used, even though they are documented as having an effect. **Link to tracking Issue:** #19419 --------- Signed-off-by: Carson Cook <[email protected]> commit 3dfc0f9ceb7deaa02a135e2fde952abb4e2b0bb4 Author: AJ Saclayan <[email protected]> Date: Thu Jun 29 05:54:00 2023 -0500 [connector/spanmetrics] fix delta temporality metrics (#23799) **Description:** Today, when you configure a spanmetricsconnector to emit metrics with delta temporality, the `startTimestamp` is not updated when deltas are calculated. Ideally, each new metric generated should have a timestamp at which the metric does the span aggregation. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/7128 **Testing:** Built otelcolcontrib docker image with changes and ran locally with the following configuration: ```yaml receivers: otlp: protocols: grpc: http: cors: allowed_origins: ["*"] allowed_headers: ["*"] exporters: otlp/newrelic: endpoint: https://otlp.nr-data.net:4317 headers: api-key: ${NEW_RELIC_LICENSE_KEY} logging: connectors: spanmetrics: histogram: exponential: max_size: 160 dimensions_cache_size: 2000 aggregation_temporality: "AGGREGATION_TEMPORALITY_DELTA" metrics_flush_interval: 15s service: telemetry: logs: level: debug pipelines: traces: receivers: [otlp] exporters: [spanmetrics] metrics: receivers: [spanmetrics] exporters: [logging, otlp/newrelic] ``` and sent the following payload twice (a couple minutes apart): ```json { "resourceSpans": [ { "resource": { "attributes": [ { "key": "service.name", "value": { "stringValue": "my.service" } } ], "droppedAttributesCount": 0 }, "scopeSpans": [ { "scope": { "name": "test", "version": "1.0.0" }, "spans": [ { "traceId": "02cfc23b60d24d708f5b478177f2c51d", "spanId": "00f067aa0ba902b7", "traceState": "", "parentSpanId": "0123abc456def789", "name": "test_span_metrics_connector", "kind": "SPAN_KIND_INTERNAL", "startTimeUnixNano": {{timeUnixNano1SecAgo}}, "endTimeUnixNano": {{timeUnixNano}}, "attributes": [ ], "droppedAttributesCount": 0, "events": [], "droppedEventsCount": 0, "links": [], "droppedLinksCount": 0, "status": { } } ] } ] } ] } ``` Note in green there are two histograms, with the timestamps updated. The red was tested with the same configuration without the change. <img width="1024" alt="image" src="https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/55757302/386d3218-b1d3-49d9-a86b-0c3fd4b61bd6"> **Documentation:** <Describe the documentation added.> commit fbd85e02bd03a144a6b96d4b5fd6b6b4c6e1594c Author: PaoloGallina <[email protected]> Date: Wed Jun 28 22:20:43 2023 +0200 [admin] feat(ci/cd): add version validation to prepare-release (#23818) **Description:** Adding version validation to prepare-release I used the same regex already used in [set_release_tag.sh](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7e74bd350192456ded06ae80fb5586bec921f2e0/.github/workflows/scripts/set_release_tag.sh#L7), just without the v. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21490 commit 7e74bd350192456ded06ae80fb5586bec921f2e0 Author: Raphael Philipe Mendes da Silva <[email protected]> Date: Wed Jun 28 11:23:57 2023 -0700 [chore] Add warning to the awscontainerinsightsreceiver (#23817) **Description:** Add warning section to the awscontainerinsightsreceiver **Link to tracking Issue:** #19172 Signed-off-by: Raphael Silva <[email protected]> commit 0ab552c249007ece56d19a41778ccebc9fedc45f Author: Ziqi Zhao <[email protected]> Date: Thu Jun 29 00:59:17 2023 +0800 [chore] fix exhaustive lint for kubeletstatsreceiver (#23815) **Description:** <Describe what has changed.> related #23266 --------- Signed-off-by: Ziqi Zhao <[email protected]> commit 8772353e38e4a7feb2af272698ee039692b21efa Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 09:54:48 2023 -0700 [chore] enable exhaustive lint for mdatagen (#23806) commit 5adb2373c26d70559a1f0b23c6711ec98689d579 Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 09:53:58 2023 -0700 [chore] signalfxexporter exhaustive lint (#23802) commit f50151e31e5220d601f127d4632685d6b0ed16ee Author: Antoine Toulme <[email protected]> Date: Wed Jun 28 08:53:20 2023 -0700 [chore] enable exhaustive lint for k8sclusterreceiver (#23803) commit 08202563ce02b03c389493bdb4b51de66dbb9e78 Author: Tyler Helmuth <[email protected]> Date: Wed Jun 28 09:10:22 2023 -0600 [processor/transform] Add new example (#23812) **Description:** Adds an example of how to set a new attribute from another telemetry path. commit f195900aa20617dca2370df638f4776a0ffc160e Author: Dominik Rosiek <[email protected]> Date: Wed Jun 28 16:21:45 2023 +0200 feat!(mysqlreceiver): set `mysql.locked_connects` as optional in order to remove it in next release (#23673) Set `mysql.locked_connects` as optional, as it is duplication of `mysql.connection.errors` metric Signed-off-by: Dominik Rosiek <[email protected]> commit 37a919c51095de6f5dbb5f8655eb712555f04aa4 Author: Mikołaj Świątek <[email protected]> Date: Wed Jun 28 14:23:49 2023 +0100 [receiver/windowseventlog] Fix buffer overflow when reading raw events (#23678) **Description:** Fixing a bug where an event larger than half the buffer capacity would cause a panic due to an overflow. The reason this happens is because raw events are render using the `evtRender` syscall, which returns the byte count, rather than the UTF16 character count, but we treat it as if it was the latter. **Link to tracking Issue:** #23677 **Testing:** Added some tests for previously untested parts of the code, and a test that triggers the problem in particular. I've also done a E2E test on a live system which previously triggered the problem, but doesn't after the fix. commit 207b866e03813cae04b0db85e376b3bb8d76470e Author: Ziqi Zhao <[email protected]> Date: Wed Jun 28 16:45:55 2023 +0800 fix exhaustive lint for awscontainerinsightreceiver (#23772) **Description:** Related issue #23266 Signed-off-by: Ziqi Zhao <[email protected]> commit 5d7b22d54585cd654eae00a41c63eaa89d76cc2c Author: Braydon Kains <[email protected]> Date: Tue Jun 27 19:24:40 2023 -0400 [receiver/hostmetrics] add process.handles metric (#22813) **Description:** <Describe what has changed.> Adds a new Windows-exclusive metric called process.handles, which represents the handle count of the given process. When enabled, the receiver will make a WMI Query at the beginning of each scrape to update the handle count for all processes on the system. If the metric is enabled on a platform other than Windows, an error will be produced when attempting to refresh handle counts. This matches the rough behaviour of the Linux exclusive `process.open_file_descriptors`. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> Ran the binary with the following configuration: ``` receivers: hostmetrics: collection_interval: 2s scrapers: cpu: {} disk: {} filesystem: {} load: {} memory: {} network: {} paging: {} process: mute_process_name_error: true metrics: process.handles: enabled: true processes: {} exporters: file: path: x.json service: pipelines: metrics: receivers: [hostmetrics] exporters: [file] ``` The following is an example result of a scrape with this configuration. https://gist.github.com/braydonk/c97996272574319e03111dc79076a1bd commit 2d23e4d9e0eb313da5d192e1066f444d19b8601f Author: Adam Boguszewski <[email protected]> Date: Tue Jun 27 13:58:00 2023 -0700 [chore][carbonreceiver][carbonexporter]: add aboguszewski-sumo as code owner (#23676) These components are lacking a codeowner, so I'd like to take this role. commit d200d2e50fa0e086ea91fbcb76764294040754cf Author: splunkertimn <[email protected]> Date: Tue Jun 27 16:01:07 2023 -0400 [receiver/syslog] fixed syslog octet frame parsing (#23645) Parse multiple syslog events from a single packet when octet framing is enabled. commit 7a1061d300e8fa990849bfcb2d4a2863ceebc44c Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 11:58:42 2023 -0700 [chore] fix pod and container metadata to include parent and units (#23795) **Description:** Add parent information to pod and container metadata. **Link to tracking Issue:** Fixes #23793 commit c4dd245e186208f4ecd093552920ae5612284de5 Author: Pranav Shankar <[email protected]> Date: Tue Jun 27 20:55:09 2023 +0200 [receiver/sqlquery] Add support of optional Start and Stop Timestamp (#19160) In this PR, support for Start and Stop Timestamp to be picked up from the metrics stored in the rows is added. This will allow SQL queries to be more expressive and allows users to define the period of aggregation which is not only dependent on the default system time set upon processing. **Link to tracking Issue:** --------- Co-authored-by: Juraci Paixão Kröhling <[email protected]> commit 1edf7c9c03cb04e2002696b966ca70f2996c2a38 Author: Goutham Veeramachaneni <[email protected]> Date: Tue Jun 27 19:28:23 2023 +0200 docs: Clarify what an association is in k8sattr. processor (#23661) It took me several readings of the docs to understand what is happening in the config. I tried to clarify what an association is and how they are specified. I've removed the line "All rules are going to be executed, and combination of result is going to be a pod metadata cache key." because it actually doesn't matter from a user perspective. It looks like an internal detail and is confusing in this section of the docs. Signed-off-by: Gotham <[email protected]> commit 1e60629434bcd1f8d04f1d1976f41b1ad7c67a52 Author: Mend Renovate <[email protected]> Date: Tue Jun 27 19:26:29 2023 +0200 chore(deps): update wandalen/wretry.action action to v1.3.0 (#23771) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [Wandalen/wretry.action](https://togithub.com/Wandalen/wretry.action) | action | minor | `v1.0.36` -> `v1.3.0` | --- <details> <summary>Wandalen/wretry.action (Wandalen/wretry.action)</summary> [`v1.3.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0) [`v1.2.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0) [`v1.0.42`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42) [`v1.0.41`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41) [`v1.0.40`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40) [`v1.0.39`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39) [`v1.0.38`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38) [`v1.0.37`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37) [Compare Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37) </details> --- 📅 **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:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> commit 6a35e5f9405d8b03c149dfec952dcac3b162662d Author: OpenTelemetry Bot <[email protected]> Date: Tue Jun 27 10:24:05 2023 -0700 [chore] dependabot updates Tue Jun 27 15:57:22 UTC 2023 (#23785) Bump Wandalen/wretry.action from 1.0.36 to 1.3.0 Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.15.0 to 1.15.2 in /exporter/datadogexporter Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.15.0 to 1.15.2 in /processor/resourcedetectionprocessor Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in /receiver/saphanareceiver Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in /receiver/sqlqueryreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in /receiver/awsxrayreceiver Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in /internal/tools Bump github.com/google/cadvisor from 0.47.1 to 0.47.2 in /receiver/awscontainerinsightreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.685 to 1.0.687 in /exporter/tencentcloudlogserviceexporter Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /extension/observer/dockerobserver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /internal/coreinternal Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/aerospikereceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/apachereceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/dockerstatsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/elasticsearchreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/flinkmetricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/jmxreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/kafkametricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/memcachedreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/mongodbreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/mysqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/nginxreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/postgresqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/rabbitmqreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/redisreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/riakreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/sqlqueryreceiver Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0 in /receiver/zookeeperreceiver Bump go.mongodb.org/mongo-driver from 1.11.7 to 1.12.0 in /receiver/mongodbreceiver Bump go.opentelemetry.io/collector/cmd/builder from 0.79.0 to 0.80.0 in /internal/tools Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /cmd/telemetrygen Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /examples/demo/client Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /examples/demo/server Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/coralogixexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/googlecloudpubsubexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/jaegerexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/opencensusexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /exporter/skywalkingexporter Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/asapauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/basicauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/bearertokenauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/headerssetterextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/jaegerremotesampling Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/oauth2clientauthextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /extension/sigv4authextension Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /processor/routingprocessor Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /processor/spanmetricsprocessor Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/jaegerreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/opencensusreceiver Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /receiver/skywalkingreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/datadogexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/logzioexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /exporter/tencentcloudlogserviceexporter Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /pkg/translator/opencensus Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/collectdreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/opencensusreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/prometheusreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/skywalkingreceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/solacereceiver Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in /receiver/zipkinreceiver --------- Signed-off-by: Alex Boten <[email protected]> Co-authored-by: Alex Boten <[email protected]> commit 3d893e2727a4144488d09badb518c45b82422f2f Author: ZahidMirza95 <[email protected]> Date: Tue Jun 27 10:15:09 2023 -0700 [receiver/filelog] added example, additional info to configs and info on log rotation (#23609) Added example on how to use filelog receiver with log files. Also, added some details to the configuration descriptions and added anchor to some sections in the document. Additionally, added information on log rotation. - Added example on how to use filelog receiver with log files - Also, added some details to the configuration descriptions - Added information on log rotation - Added anchors to some sections commit 88ba4ed63e1bda1cbbb7ba42f6b5e1354d266791 Author: Mackenzie <[email protected]> Date: Tue Jun 27 18:54:10 2023 +0200 [cmd/mdatagen] Add validation to metadata.yaml (#23783) **Description:** This PR adds validation to mdatagen. It ensures that all required fields are present, and validates their content. The validation lies mostly in `validate.go` (and for tests `validate_test.go`), however validation that needs to be done via decoding lies in `loader.go` + `metricdata.go` (and for tests `loader_test.go`). **Link to tracking Issue:** commit 64ebfbce662f261b3afbf6bef7d5d6c7ee80de69 Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 09:43:04 2023 -0700 Switch k8s.pod and k8s.container metrics to use pdata. (#23441) Updates https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/4367 commit fa2e2255f7ec5b9f2f0d003b23515aa805df0053 Author: Daniel Jaglowski <[email protected]> Date: Tue Jun 27 12:31:18 2023 -0400 Revert "[pkg/stanza/fileconsumer] Fix issue where buffer size could cause incorrect fingerprint update" (#23781) Reverts open-telemetry/opentelemetry-collector-contrib#23183 Several rotation test failures have been observed since this was merged. ([example](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5391301380/jobs/9787962306?pr=23780#step:8:75)) I do not immediately see the problem so I think this needs to be reverted for now. commit 34b47334a19b50210cb14de9ae3326cc0d285261 Author: Daniel Jaglowski <[email protected]> Date: Tue Jun 27 12:19:15 2023 -0400 [chore] Add 'test' as prerequisite to default module-level make target (#23779) We've documented the intended approach to our default targets [here](https://github.com/open-telemetry/opentelemetry-collector/blob/5852d09fb7b519e18610b99fc5a9da8cddbbf790/CONTRIBUTING.md?plain=1#L589-L591). In `Makefile.Common`, the default target is `common`. This adds the `test` target as a prerequisite. commit dea886211de3abab9bb7ca9c2cae6b45947b7cf3 Author: Mend Renovate <[email protected]> Date: Tue Jun 27 17:17:16 2023 +0200 chore(deps): update docker-compose deps (#23770) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [otel/opentelemetry-collector-contrib](https://togithub.com/open-telemetry/opentelemetry-collector-releases) | minor | `0.79.0` -> `0.80.0` | | prom/prometheus | minor | `v2.44.0` -> `v2.45.0` | --- <details> <summary>open-telemetry/opentelemetry-collector-releases (otel/opentelemetry-collector-contrib)</summary> [`v0.80.0`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.80.0) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-releases/compare/v0.79.0...v0.80.0) - [`3fe11dc`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3fe11dc) Update versions to v0.80.0 ([#​362](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/362)) - [`f82587a`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/f82587a) Add warning about git tags ([#​359](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/359)) - [`3af8267`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3af8267) Bump github.com/goreleaser/nfpm/v2 from 2.29.0 to 2.30.1 ([#​358](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/358)) - [`cb3c890`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/cb3c890) Add all missing components to contrib distribution manifest ([#​356](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/356)) - [`60a7e46`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/60a7e46) Add missing components to contrib distribution ([#​354](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/354)) - [`73fd3ae`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/73fd3ae) Add haproxyreceiver to the contrib distribution ([#​355](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/355)) - [`98597be`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/98597be) \[chore] bump go version ([#​352](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/352)) </details> --- 📅 **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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> commit 7e3548fd92e255572b240b8aadf0aff2d63da99c Author: Antoine Toulme <[email protected]> Date: Tue Jun 27 07:04:32 2023 -0700 [chore] make azureeventhubreceiver pass exhaustive linting (#23774) commit c247210d319a58665f1988e231a5c5fcfc9b8383 Author: Marc Sanmiquel <[email protected]> Date: Tue Jun 27 08:12:20 2023 +0200 [receiver/dockerstats] Add optional resource attributes (#21185) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add `container.image.id` and `container.command_line` as optional resource attributes, disabled by default. **Link to tracking Issue:** <Issue number if applicable> Tracking issue https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21092 **Testing:** <Describe what testing was performed and which tests were added.> Until this point, all resource attributes have been enabled by default, resulting in the coupling of the [test](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7bf5d66fae6c1c5360ec2875948f2c2adab6c44f/receiver/dockerstatsreceiver/receiver_test.go#L191) to the default configuration. In order to test the current implementation with the new resource attributes enabled & disabled, a minor refactoring was required in the `TestScrapeV2` test, allowing to pass different configurations for each test. Refer to the following commit 508dbee9aa9a22c1ca79f16bba5abeecceeb9c48 to check the refactor in the test. **Documentation:** <Describe the documentation added.> New resource attributes documentation was generated by `mdatagen`. commit c15794f8b3ad8bdf1bbf5abfba8486df4ad1b7c9 Author: Mackenzie <[email protected]> Date: Mon Jun 26 22:24:45 2023 +0200 [cmd/mdatagen] Add parent field to metadata.yaml file for subcomponents (#23636) This PR adds a `parent` field to the `metadata.yaml`. This is used in subcomponents, and the field contains the type of their parent component. --------- Co-authored-by: Dmitrii Anoshin <[email protected]> commit c2401dbbc240783005454f7b7046a303d495c5e1 Author: Mackenzie <[email protected]> Date: Mon Jun 26 20:04:16 2023 +0200 postgresqlreceiver: Add missing units in metadata.yaml (#23571) Metric unit is required, see: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/mdatagen/metadata-schema.yaml#L72-L73. This PR adds the unit to metrics where this is missing: - postgresql.bgwriter.maxwritten - postgresql.table.count commit 9fe4230817a192049f6c539f6c5d9ea31ce05f99 Author: Mike Dame <[email protected]> Date: Mon Jun 26 13:32:09 2023 -0400 [chore]: Update GCP dependencies (#23679) **Description:** Updates GCP libraries to v0.39.2 and 1.15.2 **Documentation:** updated readmes for new experimental WAL fields commit a7045cbee91a7d9fc6b16554ee4cf2ab2284a396 Author: Daniel Jaglowski <[email protected]> Date: Mon Jun 26 11:52:26 2023 -0400 [chore] Fix spark integration test by pinning version (#23675) Fixes #23670 The test appears to have begun failing when the [`latest`](https://hub.docker.com/layers/apache/spark/latest/images/sha256-a1dd2487a97fb5e35c5a5b409e830b501a92919029c62f9a559b13c4f5c50f63?context=explore) tag of for the image was updated. This PR just pins the version. commit bf00ae8213b55f2abf73a4df1c0a15dd1367c813 Author: Murphy Chen <[email protected]> Date: Mon Jun 26 23:52:09 2023 +0800 [exporter/clickhouse] Fix create database failure (#23666) resolve: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23664 commit 6f0fabb2ace265ebb18fb2f716567b4f7af1f335 Author: Murphy Chen <[email protected]> Date: Mon Jun 26 23:04:57 2023 +0800 [exporter/clickhouse] Add scope columns to log table (#23667) resolve: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/20280 commit fbe16e156cd90e11cbe5b70c59a83d94dc923cf4 Author: Daniel Jaglowski <[email protected]> Date: Mon Jun 26 09:24:56 2023 -0400 [pkg/stanza/fileconsumer] Fix issue where buffer size could cause incorrect fingerprint update (#23183) The logic for determining when to update a fingerprint previously failed to account for the case where the buffer size is smaller than the fingerprint. This allows the fingerprint to be truncated in some cases. This PR rewrites the logic to explicitly handle each expected case, with optimization for handling the most common cases first. commit 04327f5deaebd5f8abea3b313dd2f45ccef5bf7e Author: Olga <[email protected]> Date: Mon Jun 26 12:26:46 2023 +0200 [processor/resourcedetection] add resource_attributes to every detector in resource processor (#23253) **Description:** Adding resource_attributes option to every detector in resource detection processor <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> **Link to tracking Issue:** [21482](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/21482) **Testing:** Unit test for `resource_attribute` config, adjusting current unit tests to the new implementation **Documentation:** Updated README.md --------- Co-authored-by: Dmitrii Anoshin <[email protected]> commit 1a096adbeb24abc94eb9da2ea0126cf646d44c9b Author: Dmitrii Anoshin <[email protected]> Date: Mon Jun 26 02:31:07 2023 -0700 [chore] [receiver/apachespark] Disable failing integration test (#23671) Temporarily disable the integration test to unblock the CI. Updates https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23670 commit da5df85e77bb717e87096c20663ddc8bbb5ebf8a Author: Juan Manuel "Kang" Pérez <[email protected]> Date: Sun Jun 25 07:12:50 2023 +0200 [receiver/dockerstatsreceiver] Add metrics that are only available on hosts that use cgroups v2 (#22706) **Description:** This PR updates the documentation of all the metrics that are available only on cgroups v1 or cgroups v2. It PR also adds two metrics that are only available when the host is using cgroups v2: * `container.memory.anon` * `container.memory.file` Both are documented here: https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files I enabled the metric `container.memory.file` by default (causing a breaking change) because it is a metric that was already scraped for cgroups v1, contained in the metric `container.memory.total_cache`. ```yaml container.memory.total_cache: enabled: true description: "Total amount of memory used by the processes of this cgroup (and descendants) that can be associated with a block on a block device. Also accounts for memory used by tmpfs (Only available with cgroups v1)." container.memory.file: enabled: true description: "Amount of memory used to cache filesystem data, including tmpfs and shared memory (Only available with cgroups v2)." ``` Let me know your thoughts about this breaking change. **Link to tracking Issue:** #21097 **Testing:** The refactor done during PR #21110 had mocks ready to test these new metrics. There is no need to add more tests. **Documentation:** To see which metrics are available in Docker: * v1: https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L86 * v2: https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L195 Kernel cgroup documentation: * v1: https://docs.kernel.org/admin-guide/cgroup-v1/memory.html * v2: https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files commit 8ba48f6c48a1523fb2b7ec034b8d4d5e44f9e642 Author: Bomin Rahmani <[email protected]> Date: Fri Jun 23 15:18:45 2023 -0400 [receiver/postgresql] Fix blocks read metric (#23657) **Description:** <Describe what has changed.> fixed an issue where postgresql receiver was emitting the same attribute value "toast_hit" twice under postgresql.blocks_read metric. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> commit 0c625d042498a9985c51cee6476d4c17cfa0570b Author: Bomin Rahmani <[email protected]> Date: Fri Jun 23 15:18:05 2023 -0400 [receiver/vcenter] Fix datastore disk usage metric (#23654) **Description:** Fixed a bug in which the Vcenter receiver was incorrectly emmiting the disk_state: used datapoint twice under the vcenter.datastore.disk.usage metric instead of a disk_state: used disk_state: available **Documentation:** <Describe the documentation added.> commit 403b0eff117df29d969cc18706d1c58b605db8e2 Author: bryan-aguilar <[email protected]> Date: Fri Jun 23 10:15:36 2023 -0700 [receiver/awsecscontainermetrics] Fix possible panics from unchecked de-references (#23644) Fixes possible panics from unchecked de-references in metrics helper in `awsecscontainermetrics` receiver. **Link to tracking Issue:** https://github.com/aws-observability/aws-otel-collector/issues/2110 **Testing:** Added unit tests for these de-references **Documentation:** n//a commit c40be10a6e75e5ea15916d1dfeec95bf4de7a32c Author: PaoloGallina <[email protected]> Date: Fri Jun 23 19:14:36 2023 +0200 feat(statsdReceiver): add name and version to scope (#23564) Following the same approach of https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/20903 I am adding the scope whenever the metric is copied. We could also add the _scope_ at creation time, however, it would change the signature of several functions having already too many parameters. **Link to tracking Issue:** <Issue number if applicable> Fix https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/23563 **Testing:** Added a test to cover the new use case commit b2a1d1f47e4384…
I'm closing this since the new attributes are already included. |
Component(s)
receiver/dockerstats
Is your feature request related to a problem? Please describe.
I would like to include two additional resource attributes:
container.image.id
andcontainer.command
as those can be handy while container images are being changed (during development).Describe the solution you'd like
I would like the receiver to support both resource attributes. Those could be disabled by default and enabled by configuration.
container.image.id
: would contain the valuecontainer.Image
from docker inspect API. During development is common to keep the image name. Eg:container-dev
while introducing changes. Therefore, the currently reportedcontainer.image
may not be enough.container.cmd
: would contain the value fromcontainer.Config.Cmd
(the command displayed when doingdocker ps
).Describe alternatives you've considered
No response
Additional context
This is part of a NewRelic initiative to adopt the dockerstats receiver as a source of instrumentation. We are ready to work on it if we agree on optionally including the new resource attributes.
The text was updated successfully, but these errors were encountered: