bump up 0.137.0 #40
Merged
bump up 0.137.0 #40
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…#42736) Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/redis/go-redis/v9](https://redirect.github.com/redis/go-redis) | `v9.12.1` -> `v9.14.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>redis/go-redis (github.com/redis/go-redis/v9)</summary> ### [`v9.14.0`](https://redirect.github.com/redis/go-redis/releases/tag/v9.14.0): 9.14.0 [Compare Source](https://redirect.github.com/redis/go-redis/compare/v9.13.0...v9.14.0) #### Highlights - Added batch process method to the pipeline ([#&open-telemetry#8203;3510](https://redirect.github.com/redis/go-redis/pull/3510)) ### Changes #### 🚀 New Features - Added batch process method to the pipeline ([#&open-telemetry#8203;3510](https://redirect.github.com/redis/go-redis/pull/3510)) #### 🐛 Bug Fixes - fix: SetErr on Cmd if the command cannot be queued correctly in multi/exec ([#&open-telemetry#8203;3509](https://redirect.github.com/redis/go-redis/pull/3509)) #### 🧰 Maintenance - Updates release drafter config to exclude dependabot ([#&open-telemetry#8203;3511](https://redirect.github.com/redis/go-redis/pull/3511)) - chore(deps): bump actions/setup-go from 5 to 6 ([#&open-telemetry#8203;3504](https://redirect.github.com/redis/go-redis/pull/3504)) #### Contributors We'd like to thank all the contributors who worked on this release! [@&open-telemetry#8203;elena-kolevska](https://redirect.github.com/elena-kolevksa), [@&open-telemetry#8203;htemelski-redis](https://redirect.github.com/htemelski-redis) and [@&open-telemetry#8203;ndyakov](https://redirect.github.com/ndyakov) ### [`v9.13.0`](https://redirect.github.com/redis/go-redis/releases/tag/v9.13.0): 9.13.0 [Compare Source](https://redirect.github.com/redis/go-redis/compare/v9.12.1...v9.13.0) ##### Highlights - Pipeliner expose queued commands ([#&open-telemetry#8203;3496](https://redirect.github.com/redis/go-redis/pull/3496)) - Ensure that JSON.GET returns Nil response ([#&open-telemetry#8203;3470](https://redirect.github.com/redis/go-redis/pull/3470)) - Fixes on Read and Write buffer sizes and UniversalOptions ##### Changes - Pipeliner expose queued commands ([#&open-telemetry#8203;3496](https://redirect.github.com/redis/go-redis/pull/3496)) - fix(test): fix a timing issue in pubsub test ([#&open-telemetry#8203;3498](https://redirect.github.com/redis/go-redis/pull/3498)) - Allow users to enable read-write splitting in failover mode. ([#&open-telemetry#8203;3482](https://redirect.github.com/redis/go-redis/pull/3482)) - Set the read/write buffer size of the sentinel client to 4KiB ([#&open-telemetry#8203;3476](https://redirect.github.com/redis/go-redis/pull/3476)) ##### 🚀 New Features - fix(otel): register wait metrics ([#&open-telemetry#8203;3499](https://redirect.github.com/redis/go-redis/pull/3499)) - Support subscriptions against cluster slave nodes ([#&open-telemetry#8203;3480](https://redirect.github.com/redis/go-redis/pull/3480)) - Add wait metrics to otel ([#&open-telemetry#8203;3493](https://redirect.github.com/redis/go-redis/pull/3493)) - Clean failing timeout implementation ([#&open-telemetry#8203;3472](https://redirect.github.com/redis/go-redis/pull/3472)) ##### 🐛 Bug Fixes - Do not assume that all non-IP hosts are loopbacks ([#&open-telemetry#8203;3085](https://redirect.github.com/redis/go-redis/pull/3085)) - Ensure that JSON.GET returns Nil response ([#&open-telemetry#8203;3470](https://redirect.github.com/redis/go-redis/pull/3470)) ##### 🧰 Maintenance - fix(otel): register wait metrics ([#&open-telemetry#8203;3499](https://redirect.github.com/redis/go-redis/pull/3499)) - fix(make test): Add default env in makefile ([#&open-telemetry#8203;3491](https://redirect.github.com/redis/go-redis/pull/3491)) - Update the introduction to running tests in README.md ([#&open-telemetry#8203;3495](https://redirect.github.com/redis/go-redis/pull/3495)) - test: Add comprehensive edge case tests for IncrByFloat command ([#&open-telemetry#8203;3477](https://redirect.github.com/redis/go-redis/pull/3477)) - Set the default read/write buffer size of Redis connection to 32KiB ([#&open-telemetry#8203;3483](https://redirect.github.com/redis/go-redis/pull/3483)) - Bumps test image to 8.2.1-pre ([#&open-telemetry#8203;3478](https://redirect.github.com/redis/go-redis/pull/3478)) - fix UniversalOptions miss ReadBufferSize and WriteBufferSize options ([#&open-telemetry#8203;3485](https://redirect.github.com/redis/go-redis/pull/3485)) - chore(deps): bump actions/checkout from 4 to 5 ([#&open-telemetry#8203;3484](https://redirect.github.com/redis/go-redis/pull/3484)) - Removes dry run for stale issues policy ([#&open-telemetry#8203;3471](https://redirect.github.com/redis/go-redis/pull/3471)) - Update otel metrics URL ([#&open-telemetry#8203;3474](https://redirect.github.com/redis/go-redis/pull/3474)) ##### Contributors We'd like to thank all the contributors who worked on this release! [@&open-telemetry#8203;LINKIWI](https://redirect.github.com/LINKIWI), [@&open-telemetry#8203;cxljs](https://redirect.github.com/cxljs), [@&open-telemetry#8203;cybersmeashish](https://redirect.github.com/cybersmeashish), [@&open-telemetry#8203;elena-kolevska](https://redirect.github.com/elena-kolevska), [@&open-telemetry#8203;htemelski-redis](https://redirect.github.com/htemelski-redis), [@&open-telemetry#8203;mwhooker](https://redirect.github.com/mwhooker), [@&open-telemetry#8203;ndyakov](https://redirect.github.com/ndyakov), [@&open-telemetry#8203;ofekshenawa](https://redirect.github.com/ofekshenawa), [@&open-telemetry#8203;suever](https://redirect.github.com/suever) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjk3LjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: otelbot <[email protected]>
… Azure Blob exporter (open-telemetry#42674) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description When `template_enabled` is `true`, you can use Go templates in `metrics_format`, `logs_format`, and `traces_format` to create dynamic blob names based on telemetry data. The root object for the template is the telemetry data itself (`pmetric.Metrics`, `plog.Logs`, or `ptrace.Traces`). <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42643 <!--Describe what testing was performed and which tests were added.--> #### Testing 1. added test in `exporter_test.go`. 2. validated using real blob account. ```yaml blob_name_format: metrics_format: 2006/01/02/metrics_{{ (getResourceMetricAttr . 0 "service.name") }}_15_04.json logs_format: 2006/01/02/logs_{{ getScopeLogAttr . 0 0 "scope.name" }}_15_04.json traces_format: 2006/01/02/traces_{{ (getSpan . 0 0 0).Name }}_15_04.json template_enabled: true ``` <img width="632" height="365" alt="image" src="https://github.com/user-attachments/assets/37f4fbcb-4b64-49c2-bff1-bcf6c0451578" /> <!--Describe the documentation added.--> #### Documentation Updated in `README.md` <!--Please delete paragraphs that you did not use before submitting.-->
…-telemetry#42708) Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/ClickHouse/clickhouse-go/v2](https://redirect.github.com/ClickHouse/clickhouse-go) | `v2.40.1` -> `v2.40.3` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>ClickHouse/clickhouse-go (github.com/ClickHouse/clickhouse-go/v2)</summary> ### [`v2.40.3`](https://redirect.github.com/ClickHouse/clickhouse-go/blob/HEAD/CHANGELOG.md#v2403-2025-09-13----Release-notes-generated-using-configuration-in-githubreleaseyml-at-main---) [Compare Source](https://redirect.github.com/ClickHouse/clickhouse-go/compare/v2.40.2...v2.40.3) #### What's Changed ##### Other Changes 🛠 - bug: deserializing into nullable field by [@&open-telemetry#8203;rbroggi](https://redirect.github.com/rbroggi) in [#&open-telemetry#8203;1649](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1649) - Fixes for [#&open-telemetry#8203;1649](https://redirect.github.com/ClickHouse/clickhouse-go/issues/1649) by [@&open-telemetry#8203;SpencerTorres](https://redirect.github.com/SpencerTorres) in [#&open-telemetry#8203;1654](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1654) #### New Contributors - [@&open-telemetry#8203;rbroggi](https://redirect.github.com/rbroggi) made their first contribution in [#&open-telemetry#8203;1649](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1649) **Full Changelog**: <ClickHouse/clickhouse-go@v2.40.2...v2.40.3> ### [`v2.40.2`](https://redirect.github.com/ClickHouse/clickhouse-go/blob/HEAD/CHANGELOG.md#v2402-2025-09-13----Release-notes-generated-using-configuration-in-githubreleaseyml-at-main---) [Compare Source](https://redirect.github.com/ClickHouse/clickhouse-go/compare/v2.40.1...v2.40.2) #### What's Changed ##### Other Changes 🛠 - Bump golang.org/x/net from 0.42.0 to 0.43.0 by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1634](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1634) - Bump github.com/ClickHouse/ch-go from 0.67.0 to 0.68.0 by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1639](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1639) - Bump github.com/stretchr/testify from 1.10.0 to 1.11.1 by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1641](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1641) - Bump go.opentelemetry.io/otel/trace from 1.37.0 to 1.38.0 by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1642](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1642) - Bump github.com/docker/docker from 28.3.3+incompatible to 28.4.0+incompatible by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1646](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1646) - Bump golang.org/x/net from 0.43.0 to 0.44.0 by [@&open-telemetry#8203;dependabot](https://redirect.github.com/dependabot)\[bot] in [#&open-telemetry#8203;1647](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1647) - chore: migrate to maintained YAML library by [@&open-telemetry#8203;joschi](https://redirect.github.com/joschi) in [#&open-telemetry#8203;1651](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1651) - skip random tests on Go 1.25 by [@&open-telemetry#8203;SpencerTorres](https://redirect.github.com/SpencerTorres) in [#&open-telemetry#8203;1652](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1652) - bug: headers map can be nil by [@&open-telemetry#8203;r0bobo](https://redirect.github.com/r0bobo) in [#&open-telemetry#8203;1650](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1650) #### New Contributors - [@&open-telemetry#8203;joschi](https://redirect.github.com/joschi) made their first contribution in [#&open-telemetry#8203;1651](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1651) - [@&open-telemetry#8203;r0bobo](https://redirect.github.com/r0bobo) made their first contribution in [#&open-telemetry#8203;1650](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1650) **Full Changelog**: <ClickHouse/clickhouse-go@v2.40.1...v2.40.2> </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjk3LjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: otelbot <[email protected]> Co-authored-by: Yang Song <[email protected]>
…d/common to v1.1.28 (open-telemetry#42743) Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common](https://redirect.github.com/tencentcloud/tencentcloud-sdk-go) | `v1.1.27` -> `v1.1.28` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>tencentcloud/tencentcloud-sdk-go (github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common)</summary> ### [`v1.1.28`](https://redirect.github.com/tencentcloud/tencentcloud-sdk-go/compare/v1.1.27...v1.1.28) [Compare Source](https://redirect.github.com/tencentcloud/tencentcloud-sdk-go/compare/v1.1.27...v1.1.28) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjk3LjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: otelbot <[email protected]>
…ributes (open-telemetry#42683) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Since the following [PR](scaleway/scaleway-sdk-go#2714) has been merged and released, we can now expose host image metadata on the Scaleway provider. I kept both `host.image.id` and `host.image.name` as enabled by default since the provider was not yet included in any release. <!--Describe what testing was performed and which tests were added.--> #### Testing I tested directly in a VM, and also updated the tests to ensure these values are exposed properly when enabled. ```sh 2025-09-15T13:33:27.366Z info [email protected]/service.go:205 Starting otelcontribcol... {"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "Version": "0.135.0-dev", "NumCPU": 1} 2025-09-15T13:33:27.367Z info extensions/extensions.go:41 Starting extensions... {"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}} 2025-09-15T13:33:27.368Z info internal/resourcedetection.go:137 began detecting resource information{"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "resourcedetection", "otelcol.component.kind": "processor", "otelcol.pipeline.id": "metrics", "otelcol.signal": "metrics"} 2025-09-15T13:33:27.512Z info internal/resourcedetection.go:188 detected resource information {"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "resourcedetection", "otelcol.component.kind": "processor", "otelcol.pipeline.id": "metrics", "otelcol.signal": "metrics", "resource": {"cloud.account.id":"10542306-0c75-4265-9c2c-1fbfe4ea0bf0","cloud.availability_zone":"fr-par-1","cloud.platform":"scaleway_cloud_compute","cloud.provider":"scaleway_cloud","cloud.region":"fr-par","host.id":"132c8bcc-739d-4ed9-9b53-c5b27197a19b","host.image.id":"90e47fab-efa3-46d8-9607-f327a0ea65bb","host.image.name":"Ubuntu 24.04 Noble Numbat","host.name":"scw-goofy-borg","host.type":"STARDUST1-S"}} 2025-09-15T13:33:27.514Z info [email protected]/service.go:228 Everything is ready. Begin running and processing data. {"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}} 2025-09-15T13:33:28.515Z info Metrics {"resource": {"service.instance.id": "eb986521-bd97-4ab8-a739-b7a6ca95836f", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "debug", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "resource metrics": 3, "metrics": 5, "data points": 17} 2025-09-15T13:33:28.518Z info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 Resource attributes: -> cloud.account.id: Str(10542306-0c75-4265-9c2c-1fbfe4ea0bf0) -> cloud.availability_zone: Str(fr-par-1) -> cloud.provider: Str(scaleway_cloud) -> cloud.platform: Str(scaleway_cloud_compute) -> cloud.region: Str(fr-par) -> host.id: Str(132c8bcc-739d-4ed9-9b53-c5b27197a19b) -> host.image.id: Str(90e47fab-efa3-46d8-9607-f327a0ea65bb) -> host.image.name: Str(Ubuntu 24.04 Noble Numbat) -> host.name: Str(scw-goofy-borg) -> host.type: Str(STARDUST1-S) ``` Signed-off-by: Paulo Dias <[email protected]>
This pull request updates the example configuration in the `receiver/netflowreceiver/README.md` file to fix the YAML formatting for the NetFlow receiver. The change ensures that the configuration examples use the correct structure for each receiver type. Documentation and configuration improvements: * Corrected the YAML structure by removing unnecessary list indicators (`-`) before the `scheme` key for each receiver type in the example configuration in `receiver/netflowreceiver/README.md`.
… attribute to spanmetrics metrics (open-telemetry#41865) #### Description <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40400 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>
…etry#41802) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description * This enables recovery from a panic when the bbolt db is corrupted and renames the file when a panic occurs. * This changes the `recreate` behavior to not rename the file upon every start of the collector. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Resolves open-telemetry#36840 Resolves open-telemetry#35899 <!--Describe what testing was performed and which tests were added.--> #### Testing 1. Start collector with file extension configured. This should create the file with some content within it. 2. Stop the collector. 3. Manually edit or "break" the bbolt db file by adding characters in random places, forcefully causing a panic 4. Start the collector 5. See logs: ```json {"level":"info","ts":"2025-07-31T23:26:34.218-0400","msg":"Setting up own telemetry...","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"}} {"level":"info","ts":"2025-07-31T23:26:34.242-0400","msg":"Starting otelcontribcol...","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"Version":"0.131.0-dev","NumCPU":6} {"level":"info","ts":"2025-07-31T23:26:34.242-0400","msg":"Starting extensions...","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"}} {"level":"info","ts":"2025-07-31T23:26:34.242-0400","msg":"Extension is starting...","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"file_storage/persistent_queue_storage","otelcol.component.kind":"extension"} {"level":"info","ts":"2025-07-31T23:26:34.242-0400","msg":"Extension started.","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"file_storage/persistent_queue_storage","otelcol.component.kind":"extension"} #### This line #### {"level":"warn","ts":"2025-07-31T23:26:34.242-0400","msg":"Database corruption detected, recreating database file","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"file_storage/persistent_queue_storage","otelcol.component.kind":"extension","file":"/data/otelcol/persistent_queue_storage/exporter_otlphttp_general_logs","panic":"assertion failed: Page expected to be: 96, but self identifies as 4909050520039286100"} {"level":"info","ts":"2025-07-31T23:26:34.243-0400","msg":"Corrupted database file renamed","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"file_storage/persistent_queue_storage","otelcol.component.kind":"extension","original":"/data/otelcol/persistent_queue_storage/exporter_otlphttp_general_logs","backup":"/data/otelcol/persistent_queue_storage/exporter_otlphttp_general_logs.2025-08-27T13:26:07.479.backup"} #### through this line #### {"level":"info","ts":"2025-07-31T23:26:34.244-0400","msg":"New queue metadata key not found, attempting to load legacy format.","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"otlphttp/general","otelcol.component.kind":"exporter","otelcol.signal":"logs"} {"level":"info","ts":"2025-07-31T23:26:34.244-0400","msg":"Initializing new persistent queue","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"otlphttp/general","otelcol.component.kind":"exporter","otelcol.signal":"logs"} {"level":"info","ts":"2025-07-31T23:26:34.244-0400","msg":"Successfully migrated to consolidated metadata format","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"},"otelcol.component.id":"otlphttp/general","otelcol.component.kind":"exporter","otelcol.signal":"logs"} {"level":"info","ts":"2025-07-31T23:26:34.255-0400","msg":"Everything is ready. Begin running and processing data.","resource":{"service.instance.id":"d830aeff-7993-49f7-9817-a0c96af3498d","service.name":"otelcontribcol","service.version":"0.131.0-dev"}} ``` <!--Describe the documentation added.--> #### Documentation Updated the existing documentation with behavioral changes for `recreate` option. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Antoine Toulme <[email protected]>
…y#42692) #### Description Add the following examples to the documentation: - Minimal configuration - Cursor tracking - Reading from the beginning <!--Describe the documentation added.--> #### Documentation This PR improves the documented examples --------- Co-authored-by: Andrzej Stencel <[email protected]>
…n-telemetry#42539) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Document the metrics produced by the `allocatable_types_to_report` setting in the k8scluster receiver. - Add an explicit table mapping allocatable types to metric names in README. - Clarify that `storage` is not part of Kubernetes Node Allocatable and remove it from the listed types. - https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable - Add a reference to Kubernetes Node Allocatable docs for clarity. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42311 <!--Describe what testing was performed and which tests were added.--> #### Testing Deployed `opentelemetry-collector-contrib` v0.133.0 via the official Helm chart(`mode=deployment`, `presets.clusterMetrics=true`) and enabled allocatable metrics in the `k8s_cluster` receiver as follows: ```yaml config: receivers: k8s_cluster: auth_type: serviceAccount collection_interval: 30s allocatable_types_to_report: - cpu - memory - ephemeral-storage - storage - pods exporters: prometheus: endpoint: "0.0.0.0:8889" ``` With this configuration, the following metrics were observed on /metrics: ``` # HELP k8s_node_allocatable_cpu Amount of cpu allocatable on the node # TYPE k8s_node_allocatable_cpu gauge k8s_node_allocatable_cpu{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver",otel_scope_schema_url="",otel_scope_version="0.133.0"} 1.93 # HELP k8s_node_allocatable_ephemeral_storage_bytes Amount of ephemeral-storage allocatable on the node # TYPE k8s_node_allocatable_ephemeral_storage_bytes gauge k8s_node_allocatable_ephemeral_storage_bytes{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver",otel_scope_schema_url="",otel_scope_version="0.133.0"} 7.6224326324e+10 # HELP k8s_node_allocatable_memory_bytes Amount of memory allocatable on the node # TYPE k8s_node_allocatable_memory_bytes gauge k8s_node_allocatable_memory_bytes{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver",otel_scope_schema_url="",otel_scope_version="0.133.0"} 5.54446848e+08 # HELP k8s_node_allocatable_pods Amount of pods allocatable on the node # TYPE k8s_node_allocatable_pods gauge k8s_node_allocatable_pods{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver",otel_scope_schema_url="",otel_scope_version="0.133.0"} 4 ``` <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: jaehanbyun <[email protected]> Co-authored-by: Christos Markou <[email protected]>
…42737) Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more [here](https://redirect.github.com/renovatebot/renovate/discussions/37842). This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/relvacode/iso8601](https://redirect.github.com/relvacode/iso8601) | `v1.6.0` -> `v1.7.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>relvacode/iso8601 (github.com/relvacode/iso8601)</summary> ### [`v1.7.0`](https://redirect.github.com/relvacode/iso8601/releases/tag/v1.7.0) [Compare Source](https://redirect.github.com/relvacode/iso8601/compare/v1.6.0...v1.7.0) ##### What's Changed - Support whitespace between date and time component by [@&open-telemetry#8203;relvacode](https://redirect.github.com/relvacode) in [#&open-telemetry#8203;29](https://redirect.github.com/relvacode/iso8601/pull/29) - Check for remaining data with Zulu zone by [@&open-telemetry#8203;relvacode](https://redirect.github.com/relvacode) in [#&open-telemetry#8203;31](https://redirect.github.com/relvacode/iso8601/pull/31) **Full Changelog**: <relvacode/iso8601@v1.6.0...v1.7.0> </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjk3LjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: otelbot <[email protected]>
…pen-telemetry#42581) #### Description Enables usage of OpenTelemetry's TLS configuration structure for clickhouse-go driver. Example: ```yaml exporters: clickhouse: endpoint: tcp://127.0.0.1:9000 tls: insecure: false insecure_skip_verify: false ca_file: CAroot.crt cert_file: client.crt key_file: client.key ``` #### Link to tracking issue Fixes open-telemetry#22805, open-telemetry#41116 #### Testing Added integration test that uses locally generated test certificates to test certificate authentication with ClickHouse. Certificates can be regenerated with `./testdata/certs/gen-certs.sh`. Also updated ClickHouse image versions to latest stable/LTS. #### Documentation Updated README with `tls` config description and example.
…en-telemetry#42616) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR fixes a typo in the search artifact size metrics, which is part of the existing search dispatch collection. This typo has been causing errors with parsing empty string values. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#42615
) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42514 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: Jared Tan <[email protected]> Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Alex Boten <[email protected]>
The Contributor Experience group created a survey to help understand challenges and feedback from new contributors. We have this survey running for a few months on opentelemetry.io and the JS repo, with helpful feedback, so now adding to more repos. Example of message: open-telemetry/opentelemetry-js#5884 (comment) --------- Co-authored-by: Antoine Toulme <[email protected]>
…#42660) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds a new optional parameter `s3_base_prefix` to the `awss3exporter` which is used as the root path for all files uploaded. This new parameter is helpful when using the `resource_attrs_to_s3/s3_prefix` override ability but you still want a root path to be used for all file uploads. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42661 <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit tests and ran the otel collector locally using a config file that specifies an `awss3` exporter with the new `s3_base_prefix` parameter <!--Describe the documentation added.--> #### Documentation Updated the readme and added new configuration examples <!--Please delete paragraphs that you did not use before submitting.-->
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Updates the countconnector metric timestamps to use earliest timestamp from batch as start timestamp and latest as timestamp, instead of using timestamp from metric creation time <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40573 <!--Describe what testing was performed and which tests were added.--> #### Testing Updates TracesToMetric tests to include checks for timestamp values
…ctive feature gate (open-telemetry#42727) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description After the merge of open-telemetry#41042 we need to completely remove the `receiver.kubeletstats.enableCPUUsageMetrics` feature gate and cleanup the component accordingly. The feature gate has been [in place until v0.131.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/41042/files#diff-3d568b694da81fd8cca718ee598c1fa14d20176a73af0f8d009388f5a6c2e11dR33) hence now it can be removed entirely. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#41178 Supersedes open-telemetry#41880. <!--Describe what testing was performed and which tests were added.--> #### Testing Updated <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Co-authored-by: mugund10 <[email protected]> Signed-off-by: ChrsMark <[email protected]> Co-authored-by: mugund10 <[email protected]>
…n-telemetry#42753) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Seems like github.com/tdakkota/asciicheck is no longer available, but still imported [(golangci/golangci-lint)](https://github.com/golangci/golangci-lint/blob/v2.4.0/go.mod#L115) in the latest release. This is temporary until a new golangci-lint release will use the updated asciicheck repo. Some more context [here](golangci/golangci-lint#6018).
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Two codeowners in the allowlist have recently become OpenTelemetry community members and no longer need to be in the allowlist.
…y#42774) #### Description This commit updates configuration and filtering options in the stanza documentation of the journald input to match the journald receiver documentation.
…etry#42776) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description [As requested](open-telemetry#42741 (comment)), the Kong test for Prometheus should use a past scrape of kong data as the input, rather than spinning up a kong docker container and connecting to it.
… in Sarama calls (open-telemetry#41363) … <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This change implements client reset functionality to address recoverable errors in Sarama calls, such as connection resets and EOF errors. When a recoverable error is encountered, the client is reset, enabling the scraper to reconnect and resume metric collection seamlessly. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue none <!--Describe what testing was performed and which tests were added.--> #### Testing Existing tests were modified accordingly. <!--Describe the documentation added.--> #### Documentation none <!--Please delete paragraphs that you did not use before submitting.-->
#### Description Add --allow-export-failures flag to telemetrygen to continue running when export operations fail (instead of terminating) <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42135
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Same as open-telemetry#42635 in different tests. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Updates open-telemetry#42639 --------- Co-authored-by: Yang Song <[email protected]>
This PR updates the opentelemetry-collector modules to open-telemetry/opentelemetry-collector@ba0b327 --------- Signed-off-by: otelbot <[email protected]> Co-authored-by: otelbot <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
…#42789) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> Hotfix to make sure contributors can merge PRs :) #### Link to tracking issue Updates open-telemetry#42639
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> Scoped tests are too slow for certain components (e.g. Prometheus components) after open-telemetry#42498. I still think running the tests more than once is a good idea to prevent flakes, but maybe twice is a better balance between catching flakes and not taking ages to merge each PR. #### Link to tracking issue Follows open-telemetry#42498
…b.uid (open-telemetry#42641) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds support to expose `k8s.cronjob.uid` as resource metadata when a `Job` is owned by a `CronJob`. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42557 <!--Describe what testing was performed and which tests were added.--> #### Testing Local tested with `telemetrygen` and is working as expected. ``` [pod/k8sevents-receiver-opentelemetry-collector-6fd9966559-brlb6/opentelemetry-collector] {"level":"debug","ts":"2025-09-11T16:29:11.588Z","caller":"[email protected]/processor.go:159","msg":"getting the pod","resource":{"service.instance.id":"9631e38b-aec3-439f-8178-d96fc8368e1e","service.name":"otelcontribcol","service.version":"0.135.0-dev"},"otelcol.component.id":"k8sattributes","otelcol.component.kind":"processor","otelcol.pipeline.id":"traces","otelcol.signal":"traces","pod":{"Name":"otel-log-cronjob-29293469-lw97x","Address":"10.244.0.70","PodUID":"7960681c-5a24-4287-8bea-e2cf506500ee","Attributes":{"k8s.cronjob.name":"otel-log-cronjob","k8s.cronjob.uid":"082b1c42-e393-46bc-9d51-b20a3700d1ab","k8s.job.name":"otel-log-cronjob-29293469","k8s.job.uid":"fbd853b8-7f63-44d8-ace1-8b48c89e3041"},"StartTime":"2025-09-11T16:29:00Z","Ignore":false,"Namespace":"default","NodeName":"","DeploymentUID":"","StatefulSetUID":"","DaemonSetUID":"","JobUID":"fbd853b8-7f63-44d8-ace1-8b48c89e3041","HostNetwork":false,"Containers":{"ByID":null,"ByName":null},"DeletedAt":"0001-01-01T00:00:00Z"}} [pod/k8sevents-receiver-opentelemetry-collector-6fd9966559-brlb6/opentelemetry-collector] {"level":"info","ts":"2025-09-11T16:29:11.588Z","msg":"Traces","resource":{"service.instance.id":"9631e38b-aec3-439f-8178-d96fc8368e1e","service.name":"otelcontribcol","service.version":"0.135.0-dev"},"otelcol.component.id":"debug","otelcol.component.kind":"exporter","otelcol.signal":"traces","resource spans":1,"spans":2} [pod/k8sevents-receiver-opentelemetry-collector-6fd9966559-brlb6/opentelemetry-collector] {"level":"info","ts":"2025-09-11T16:29:11.588Z","msg":"ResourceSpans #0\nResource SchemaURL: https://opentelemetry.io/schemas/1.4.0\nResource attributes:\n -> k8s.container.name: Str(telemetrygen)\n -> service.name: Str(telemetrygen)\n -> k8s.pod.ip: Str(10.244.0.70)\n -> k8s.cronjob.name: Str(otel-log-cronjob)\n -> k8s.cronjob.uid: Str(082b1c42-e393-46bc-9d51-b20a3700d1ab)\n -> k8s.job.uid: Str(fbd853b8-7f63-44d8-ace1-8b48c89e3041)\n -> k8s.job.name: Str(otel-log-cronjob-29293469)\nScopeSpans #0\nScopeSpans SchemaURL: \nInstrumentationScope telemetrygen \nSpan #0\n Trace ID : 3c7381c14a37814676b00a7d961cb219\n Parent ID : 4f8780d5148a9c1c\n ID : 17e9da9533dc93ca\n Name : okey-dokey-0\n Kind : Server\n Start time : 2025-09-11 16:29:09.583785469 +0000 UTC\n End time : 2025-09-11 16:29:09.583908469 +0000 UTC\n Status code : Unset\n Status message : \nAttributes:\n -> net.peer.ip: Str(1.2.3.4)\n -> peer.service: Str(telemetrygen-client)\nSpan #1\n Trace ID : 3c7381c14a37814676b00a7d961cb219\n Parent ID : \n ID : 4f8780d5148a9c1c\n Name : lets-go\n Kind : Client\n Start time : 2025-09-11 16:29:09.583785469 +0000 UTC\n End time : 2025-09-11 16:29:09.583908469 +0000 UTC\n Status code : Unset\n Status message : \nAttributes:\n -> net.peer.ip: Str(1.2.3.4)\n -> peer.service: Str(telemetrygen-server)\n","resource":{"service.instance.id":"9631e38b-aec3-439f-8178-d96fc8368e1e","service.name":"otelcontribcol","service.version":"0.135.0-dev"},"otelcol.component.id":"debug","otelcol.component.kind":"exporter","otelcol.signal":"traces"} ``` Added also the tests to guarantee the proper functionality. --------- Signed-off-by: Paulo Dias <[email protected]>
This is a redo of open-telemetry#41849 with a fix, use quotes around the value '0' so it is not assimilated to false. --------- Co-authored-by: Paulo Janotti <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Allow the Tail Sampling Processor to use extensions that implement an interface simply containing NewEvaluator. To use an extension all that needs to be done is specify the extension's type/name such as my_extension or my_extension/my_name in the type field of the policy configuration. When configuration is loaded or updated NewEvaluator will be called. Extensions can be configured in two places. First, in the extensions section like all other extensions. This is useful for configuration such as if an extension needs to connect to an external service. In addition, configuration can be defined in the policy config under a key matching the type of the extension for anything related to one instance, following the pattern for all other policy types. This is useful when reusing the same extension e.g. different params for different services. For example: ```yaml type: custom_policy custom_policy: foo: bar ``` What this ends up with is that extensions look exactly like all other policy types with no need for users to know about some sort of extension container. I have tested this out with an extension in a custom build and it is working well, I am sure we will iterate on the interfaces a bit as we write more. Specifically a way to stop the extension when policies are updated may be necessary to clean up any background processes. @yvrhdn is working on an extension we plan to add to contrib as well. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Part of open-telemetry#31582
…n-telemetry#43113) Followon from open-telemetry#43050 #### Description Connects up PermissiveLabelSanitization feature gate. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue First part of open-telemetry#43077 <!--Describe what testing was performed and which tests were added.--> #### Testing New unit tests <!--Describe the documentation added.--> #### Documentation explanatory comments added to new options in code <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Owen Williams <[email protected]>
…#42802) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds support for resource detection in Upcloud. I'm proposing to be a code owner for this detector 🙌 Semantic Conventions PR: open-telemetry/semantic-conventions#2789 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42801 <!--Describe what testing was performed and which tests were added.--> #### Testing Tests added and also tested on an Upcloud instance, as we can see the output below. ```sh 2025-09-21T21:37:02.682Z info [email protected]/service.go:205 Starting otelcontribcol... {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "Version": "0.135.0-dev", "NumCPU": 1} 2025-09-21T21:37:02.682Z info extensions/extensions.go:41 Starting extensions... {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}} 2025-09-21T21:37:02.683Z info internal/resourcedetection.go:137 began detecting resource information {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "resourcedetection", "otelcol.component.kind": "processor", "otelcol.pipeline.id": "metrics", "otelcol.signal": "metrics"} 2025-09-21T21:37:02.684Z info internal/resourcedetection.go:188 detected resource information {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "resourcedetection", "otelcol.component.kind": "processor", "otelcol.pipeline.id": "metrics", "otelcol.signal": "metrics", "resource": {"cloud.provider":"upcloud","cloud.region":"es-mad1","host.id":"00133099-f1fd-4ed2-b1c7-d027eb43a8f5","host.name":"ubuntu-1cpu-1gb-es-mad1"}} 2025-09-21T21:37:02.684Z info [email protected]/service.go:228 Everything is ready. Begin running and processing data. {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}} 2025-09-21T21:37:03.685Z info Metrics {"resource": {"service.instance.id": "208133c3-f741-4f28-bdbd-ecafbddcf0ef", "service.name": "otelcontribcol", "service.version": "0.135.0-dev"}, "otelcol.component.id": "debug", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "resource metrics": 3, "metrics": 5, "data points": 17} 2025-09-21T21:37:03.685Z info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 Resource attributes: -> cloud.provider: Str(upcloud) -> cloud.region: Str(es-mad1) -> host.id: Str(00133099-f1fd-4ed2-b1c7-d027eb43a8f5) -> host.name: Str(ubuntu-1cpu-1gb-es-mad1) ``` <!--Describe the documentation added.--> #### Documentation Updated the README.md with this new detector. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]>
open-telemetry#42760) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description As we discussed open-telemetry#42103 (comment), I decided to exclude all resource attributes in spanmetrics. Note: fix a typo in `useSecondAsDefaultMetricsUnit` feature gate ReferenceURL <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42103 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fix the exporter/googlecloudstorageexporter/go.mod and exporter/googlecloudstorageexporter/go.sum to match the versions required.
… under a feature gate (open-telemetry#43019) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds franz-go support to the kafkametricsreceiver, behind a feature gate (`receiver.kafkametricsreceiver.UseFranzGo`). <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#41480 <!--Describe what testing was performed and which tests were added.--> #### Testing Tested locally and added tests for trying to cover all the current Sarama ones. <!--Describe the documentation added.--> #### Documentation Updated README.md with reference about opt-in using franz-go library. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]>
…etry#43132) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR fixes the `ntp.host` resource attribute was not being emitted even though it was enabled by default. I'm also proposing being an additional code owner for this component. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43129 <!--Describe what testing was performed and which tests were added.--> #### Testing I added new tests for `receiver.go`. Also tested it locally with the same configuration shared on the issue. ```sh 2025-10-05T00:16:24.452+0100 info [email protected]/service.go:222 Starting otelcontribcol... {"resource": {"service.instance.id": "9202fda2-095d-4055-8412-dc4de4b8308d", "service.name": "otelcontribcol", "service.version": "0.136.0-dev"}, "Version": "0.136.0-dev", "NumCPU": 12} 2025-10-05T00:16:24.452+0100 info extensions/extensions.go:41 Starting extensions... {"resource": {"service.instance.id": "9202fda2-095d-4055-8412-dc4de4b8308d", "service.name": "otelcontribcol", "service.version": "0.136.0-dev"}} 2025-10-05T00:16:24.452+0100 info [email protected]/service.go:245 Everything is ready. Begin running and processing data. {"resource": {"service.instance.id": "9202fda2-095d-4055-8412-dc4de4b8308d", "service.name": "otelcontribcol", "service.version": "0.136.0-dev"}} 2025-10-05T00:16:25.658+0100 info Metrics {"resource": {"service.instance.id": "9202fda2-095d-4055-8412-dc4de4b8308d", "service.name": "otelcontribcol", "service.version": "0.136.0-dev"}, "otelcol.component.id": "debug", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "resource metrics": 1, "metrics": 1, "data points": 1} 2025-10-05T00:16:25.659+0100 info ResourceMetrics #0 Resource SchemaURL: Resource attributes: -> ntp.host: Str(time.nist.gov:123) ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope github.com/open-telemetry/opentelemetry-collector-contrib/receiver/ntpreceiver 0.136.0-dev Metric #0 Descriptor: -> Name: ntp.offset -> Description: Time difference between local and NTP server clocks -> Unit: ns -> DataType: Gauge NumberDataPoints #0 StartTimestamp: 2025-10-04 23:16:24.452351 +0000 UTC Timestamp: 2025-10-04 23:16:25.647124 +0000 UTC Value: 91327175 {"resource": {"service.instance.id": "9202fda2-095d-4055-8412-dc4de4b8308d", "service.name": "otelcontribcol", "service.version": "0.136.0-dev"}, "otelcol.component.id": "debug", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics"} ``` --------- Signed-off-by: Paulo Dias <[email protected]>
…etry#42953) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes ~ <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
…#42633) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Set `namespace="remote"` for producer spans so that X-ray will infer a downstream service node. Changed consumer spans to be segments so that they can correlate to their own node while being downstream from the producer. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40995 <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit tests for producer span and updated unit tests for consumer spans. <!--Please delete paragraphs that you did not use before submitting.-->
…cts (open-telemetry#43140) Relates to open-telemetry#43134 - this is addressing unkeyed literal initialization for public structs across components, to help upgrade checkapi.
…en-telemetry#43105) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds support for a new setting named `max_partition_fetch_size` to be used with `kgo.FetchMaxPartitionBytes` franz-go option. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43097 <!--Describe what testing was performed and which tests were added.--> #### Testing Updated tests to ensure the new config is applied and works as expected. <!--Describe the documentation added.--> #### Documentation Documentation updated with the new setting, and referencing will only work while using `franz-go` as Sarama doesn't have support for it. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]> Co-authored-by: Vihas Makwana <[email protected]>
…n-telemetry#43115) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fix for memory leak when using `ObfuscateSQLStringWithOptions()` in the obfuscate library Similar fix done in [SQL Server receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/42303/files ) and [OracleDB Receiver](open-telemetry#43096) <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43076 --------- Signed-off-by: Paulo Dias <[email protected]> Co-authored-by: Christos Markou <[email protected]>
…-telemetry#42783) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> Stops doing validation of characters in API key. Validation of secrets is challenging. Furthermore, any possible changes on the API key format would mean users would have to upgrade their clients; being more flexible and leaving validation for runtime helps avoid unnecessary upgrades. #### Link to tracking issue Fixes open-telemetry#42677
…y#42984) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes ~ <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
…pen-telemetry#43146) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description `TestLRUSetLifeTime` is a flaky test that we have taken a couple of stabs to fix in the past however we haven't been successful. I have tried reproducing the error in my local but failed. Looking into the code for go-freelru I discovered that the library uses wall clock (and not monotonic clock) for expiring items which might be the root cause of the flakiness (elastic/go-freelru#1). In an attempt to fix this, I have migrated to `assert.InEpsilon` and tightened the bounds for `AssertEventually` to about 1% delta. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42538 (edit: added by @mx-psi) Fixes open-telemetry#42670 Fixes open-telemetry#42413 <!--Describe what testing was performed and which tests were added.--> #### Testing N/A <!--Describe the documentation added.--> #### Documentation N/A <!--Please delete paragraphs that you did not use before submitting.-->
…#42973) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes ~ <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
…#42946) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes ~ <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
This PR updates the opentelemetry-collector modules to open-telemetry/opentelemetry-collector@d00f059 --------- Signed-off-by: otelbot <[email protected]> Co-authored-by: otelbot <[email protected]>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description unexport JSONEncoder
…ry#42945) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes ~ <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
As indicated by @schmikei, the plan is to hold off on upgrading this dependency. Closes open-telemetry#41040 Signed-off-by: alex boten <[email protected]>
This adds OtelArrow sender and receiver to the testbed and adds the protocol as a test case to TestMetric10kDPS. No changelog is necessary since there is no user facing changes or API changes. The test shows OtelArrow receiver fails to shutdown on SIGTERM signal. I had to replace a fatal error in TestCase.indicateError by a regular log message to avoid failing the entire suite when shutdown timeout for OtelArrow case. Results running locally: ``` Test |Result|Duration|CPU Avg%|CPU Max%|CPU Limit|RAM Avg MiB|RAM Max MiB|RAM Limit MiB|Sent Items|Received Items| ----------------------------------------|------|-------:|-------:|-------:|--------:|----------:|----------:|------------:|---------:|-------------:| Metric10kDPS/Carbon |PASS | 16s| 172.4| 179.9| 0.0| 59| 84| 0| 1050700| 1050700| Metric10kDPS/OTLP |PASS | 15s| 17.6| 18.1| 0.0| 62| 88| 0| 1050700| 1050700| Metric10kDPS/OTLP-HTTP |PASS | 16s| 20.9| 22.0| 0.0| 57| 81| 0| 1050700| 1050700| Metric10kDPS/SignalFx |PASS | 16s| 35.3| 36.7| 0.0| 61| 86| 0| 1050700| 1050700| Metric10kDPS/STEF |PASS | 17s| 12.1| 13.8| 0.0| 72| 115| 0| 1050700| 1050700| Metric10kDPS/OtelArrow |PASS | 25s| 22.9| 23.8| 0.0| 123| 183| 0| 1051400| 1051400|signal: killed Total duration: 104s ```
…42875) > [!NOTE] > Mend has cancelled [the proposed renaming](https://redirect.github.com/renovatebot/renovate/discussions/37842) of the Renovate GitHub app being renamed to `mend[bot]`. > > This notice will be removed on 2025-10-07. <hr> This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/google/go-github/v74](https://redirect.github.com/google/go-github) | `v74.0.0` -> `v75.0.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. :warning: MAJOR VERSION UPDATE :warning: - please manually update this package --- ### Release Notes <details> <summary>google/go-github (github.com/google/go-github/v74)</summary> ### [`v75.0.0`](https://redirect.github.com/google/go-github/releases/tag/v75.0.0) [Compare Source](https://redirect.github.com/google/go-github/compare/v74.0.0...v75.0.0) This release contains the following breaking API changes: - refactor!: Change GitService methods to pass required params by-value instead of by-ref ([#&open-telemetry#8203;3654](https://redirect.github.com/google/go-github/issues/3654)) BREAKING CHANGE: `GitService` methods now pass required params by-value instead of by-ref. ...and the following additional changes: - Bump go-github from v73 to v74 in /scrape ([#&open-telemetry#8203;3639](https://redirect.github.com/google/go-github/issues/3639)) - Add the metadata field to create DependencyGraphSnapshot ([#&open-telemetry#8203;3640](https://redirect.github.com/google/go-github/issues/3640)) - Bump golangci-lint to 2.3.0 ([#&open-telemetry#8203;3641](https://redirect.github.com/google/go-github/issues/3641)) - Add additional settings fields to org API ([#&open-telemetry#8203;3642](https://redirect.github.com/google/go-github/issues/3642)) - docs: Extend the description of ref parameters ([#&open-telemetry#8203;3643](https://redirect.github.com/google/go-github/issues/3643)) - fix: Add validation for nil inputs in various services ([#&open-telemetry#8203;3636](https://redirect.github.com/google/go-github/issues/3636)) - Add location info to SecretScanningAlert ([#&open-telemetry#8203;3645](https://redirect.github.com/google/go-github/issues/3645)) - docs: Update links to use the latest version of GitHub documentation ([#&open-telemetry#8203;3648](https://redirect.github.com/google/go-github/issues/3648)) - Add FieldValue field to ProjectV2ItemChange event. ([#&open-telemetry#8203;3650](https://redirect.github.com/google/go-github/issues/3650)) - Add Metadata field to DependencyGraph\* structs ([#&open-telemetry#8203;3653](https://redirect.github.com/google/go-github/issues/3653)) - refactor: Fix gocritic.paramTypeCombine lint issues ([#&open-telemetry#8203;3655](https://redirect.github.com/google/go-github/issues/3655)) - chore: Show correct path when example has lint errors ([#&open-telemetry#8203;3656](https://redirect.github.com/google/go-github/issues/3656)) - Add Social Accounts API ([#&open-telemetry#8203;3647](https://redirect.github.com/google/go-github/issues/3647)) - feat: Implement List Repository Activities endpoint ([#&open-telemetry#8203;3651](https://redirect.github.com/google/go-github/issues/3651)) - docs: Use secure URLs in string literals ([#&open-telemetry#8203;3657](https://redirect.github.com/google/go-github/issues/3657)) - feat: Update openapi ([#&open-telemetry#8203;3662](https://redirect.github.com/google/go-github/issues/3662)) - feat: Add artifact and log retention period API support ([#&open-telemetry#8203;3664](https://redirect.github.com/google/go-github/issues/3664)) - Document upcoming changes to events payload ([#&open-telemetry#8203;3667](https://redirect.github.com/google/go-github/issues/3667)) - build(deps): Bump the actions group with 2 updates ([#&open-telemetry#8203;3670](https://redirect.github.com/google/go-github/issues/3670)) - build(deps): Bump golang.org/x/net from 0.42.0 to 0.43.0 in /scrape ([#&open-telemetry#8203;3669](https://redirect.github.com/google/go-github/issues/3669)) - fix: Replace 'organizations' with 'orgs' in API endpoints ([#&open-telemetry#8203;3673](https://redirect.github.com/google/go-github/issues/3673)) - Update AUTHORS ([#&open-telemetry#8203;3674](https://redirect.github.com/google/go-github/issues/3674)) - feat: Add secret scanning push protection pattern configurations API ([#&open-telemetry#8203;3672](https://redirect.github.com/google/go-github/issues/3672)) - feat: Add self-hosted runner permission API support ([#&open-telemetry#8203;3675](https://redirect.github.com/google/go-github/issues/3675)) - chore: Do not force Go 1.22.0 as toolchain version ([#&open-telemetry#8203;3678](https://redirect.github.com/google/go-github/issues/3678)) - feat: Add GitHub Classroom GetAssignment API endpoint ([#&open-telemetry#8203;3685](https://redirect.github.com/google/go-github/issues/3685)) - chore: Add new lint rule to make sure exported names documented ([#&open-telemetry#8203;3682](https://redirect.github.com/google/go-github/issues/3682)) - chore: Enable gocritic.deprecatedComment check ([#&open-telemetry#8203;3688](https://redirect.github.com/google/go-github/issues/3688)) - chore: Format code with gofumpt ([#&open-telemetry#8203;3689](https://redirect.github.com/google/go-github/issues/3689)) - feat: Add private repo workflows permission API support ([#&open-telemetry#8203;3679](https://redirect.github.com/google/go-github/issues/3679)) - chore: Replace reflect.DeepEqual with cmp.Equal in tests ([#&open-telemetry#8203;3691](https://redirect.github.com/google/go-github/issues/3691)) - docs: Update CONTRIBUTING.md to clarify documentation requirements for exported types ([#&open-telemetry#8203;3693](https://redirect.github.com/google/go-github/issues/3693)) - build(deps): Bump github.com/getkin/kin-openapi from 0.132.0 to 0.133.0 in /tools ([#&open-telemetry#8203;3698](https://redirect.github.com/google/go-github/issues/3698)) - build(deps): Bump actions/setup-go from 5.5.0 to 6.0.0 in the actions group ([#&open-telemetry#8203;3709](https://redirect.github.com/google/go-github/issues/3709)) - build(deps): Bump codecov/codecov-action from 5.4.3 to 5.5.1 ([#&open-telemetry#8203;3711](https://redirect.github.com/google/go-github/issues/3711)) - build(deps): Bump golang.org/x/net from 0.43.0 to 0.44.0 in /scrape ([#&open-telemetry#8203;3716](https://redirect.github.com/google/go-github/issues/3716)) - Add exempt as bypass mode to ruleset bypass actors ([#&open-telemetry#8203;3719](https://redirect.github.com/google/go-github/issues/3719)) - Bump Go toolchain to 1.24 ([#&open-telemetry#8203;3721](https://redirect.github.com/google/go-github/issues/3721)) - Bump golang.org/x/sync from 0.16.0 to 0.17.0 in /tools ([#&open-telemetry#8203;3722](https://redirect.github.com/google/go-github/issues/3722)) - Bump version of go-github to v75.0.0 ([#&open-telemetry#8203;3723](https://redirect.github.com/google/go-github/issues/3723)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45Ny4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjEzMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmN5LW1ham9yLXVwZGF0ZSJdfQ==--> --------- Signed-off-by: alex boten <[email protected]> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Alex Boten <[email protected]>
…telemetry#43152) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description There's been some confusion around required permissions for full usage of the SQL Server receiver, so this PR adds a section clarifying what's required. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40937
The following commands were run to prepare this release: - make chlog-update VERSION=v0.137.0 - sed -i.bak s/0[.]136[.]0/0.137.0/g versions.yaml - make multimod-prerelease - make multimod-sync --------- Signed-off-by: otelbot <[email protected]> Co-authored-by: otelbot <[email protected]>
Signed-off-by: Jared Tan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
72 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Link to tracking issue
Fixes
Testing
Documentation