Merge upstream v0.96.0 #13660
Merged
Merge upstream v0.96.0 #13660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…telemetry#31057) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/aws/aws-sdk-go](https://togithub.com/aws/aws-sdk-go) | `v1.50.7` -> `v1.50.14` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>aws/aws-sdk-go (github.com/aws/aws-sdk-go)</summary> ### [`v1.50.14`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v15014-2024-02-08) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.13...v1.50.14) \=== ##### Service Client Updates - `service/codepipeline`: Updates service API and documentation - Add ability to execute pipelines with new parallel & queued execution modes and add support for triggers with filtering on branches and file paths. - `service/quicksight`: Updates service API and documentation - General Interactions for Visuals; Waterfall Chart Color Configuration; Documentation Update - `service/workspaces`: Updates service API and documentation - This release introduces User-Decoupling feature. This feature allows Workspaces Core customers to provision workspaces without providing users. CreateWorkspaces and DescribeWorkspaces APIs will now take a new optional parameter "WorkspaceName". ### [`v1.50.13`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v15013-2024-02-07) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.12...v1.50.13) \=== ##### Service Client Updates - `service/datasync`: Updates service API and documentation - `service/models.lex.v2`: Updates service API, documentation, and paginators - `service/redshift`: Updates service API, documentation, and paginators - LisRecommendations API to fetch Amazon Redshift Advisor recommendations. ### [`v1.50.12`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v15012-2024-02-06) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.11...v1.50.12) \=== ##### Service Client Updates - `service/appsync`: Updates service API and documentation - `service/ecs`: Updates service documentation - This release is a documentation only update to address customer issues. - `service/es`: Updates service API and documentation - This release adds clear visibility to the customers on the changes that they make on the domain. - `service/logs`: Updates service API and documentation - This release adds a new field, logGroupArn, to the response of the logs:DescribeLogGroups action. - `service/opensearch`: Updates service API and documentation - `service/wafv2`: Updates service API and documentation ### [`v1.50.11`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v15011-2024-02-05) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.10...v1.50.11) \=== ##### Service Client Updates - `service/glue`: Updates service API and documentation - Introduce Catalog Encryption Role within Glue Data Catalog Settings. Introduce SASL/PLAIN as an authentication method for Glue Kafka connections - `service/workspaces`: Updates service documentation - Added definitions of various WorkSpace states ### [`v1.50.10`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v15010-2024-02-02) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.9...v1.50.10) \=== ##### Service Client Updates - `service/dynamodb`: Updates service API, documentation, waiters, paginators, and examples - Any number of users can execute up to 50 concurrent restores (any type of restore) in a given account. - `service/sagemaker`: Updates service API and documentation - Amazon SageMaker Canvas adds GenerativeAiSettings support for CanvasAppSettings. ### [`v1.50.9`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v1509-2024-02-01) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.8...v1.50.9) \=== ##### Service Client Updates - `service/cognito-idp`: Updates service API and documentation - `service/ivs`: Updates service API, documentation, and paginators - `service/managedblockchain-query`: Updates service API and documentation - `service/mediaconvert`: Updates service API and documentation - This release includes support for broadcast-mixed audio description tracks. ### [`v1.50.8`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v1508-2024-01-31) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.50.7...v1.50.8) \=== ##### Service Client Updates - `service/cloudformation`: Updates service API, documentation, paginators, and examples - CloudFormation IaC generator allows you to scan existing resources in your account and select resources to generate a template for a new or existing CloudFormation stack. - `service/elasticloadbalancingv2`: Updates service API and documentation - `service/glue`: Updates service API and documentation - Update page size limits for GetJobRuns and GetTriggers APIs. - `service/ssm`: Updates service API and documentation - This release adds an optional Duration parameter to StateManager Associations. This allows customers to specify how long an apply-only-on-cron association execution should run. Once the specified Duration is out all the ongoing cancellable commands or automations are cancelled. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNzMuMCIsInVwZGF0ZWRJblZlciI6IjM3LjE3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
… to v1.9.2 (open-telemetry#31080) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/Azure/azure-sdk-for-go/sdk/azcore](https://togithub.com/Azure/azure-sdk-for-go) | `v1.9.1` -> `v1.9.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNzMuMCIsInVwZGF0ZWRJblZlciI6IjM3LjE3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
…lemetry#31061) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/knadh/koanf/v2](https://togithub.com/knadh/koanf) | `v2.0.2` -> `v2.1.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>knadh/koanf (github.com/knadh/koanf/v2)</summary> ### [`v2.1.0`](https://togithub.com/knadh/koanf/releases/tag/v2.1.0) [Compare Source](https://togithub.com/knadh/koanf/compare/v2.0.2...v2.1.0) ### Important [https://github.com/mitchellh/mapstructure/issues/349#issuecomment-1860372162](https://togithub.com/mitchellh/mapstructure/issues/349#issuecomment-1860372162) is discontinued and koanf has switched to using the fork `github.com/go-viper/mapstructure/v2`. If you are referencing the mapstructure lib in your code (custom DecoderConfig), you have to switch the paths to the above forked version of koanf. `github.com/mitchellh/mapstructure` => `github.com/go-viper/mapstructure/v2` #### What's Changed - fix: retract v2.0.2 by [@​rhnvrm](https://togithub.com/rhnvrm) in [https://github.com/knadh/koanf/pull/270](https://togithub.com/knadh/koanf/pull/270) **Full Changelog**: knadh/koanf@v2.0.2...v2.1.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 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4xNzMuMCIsInVwZGF0ZWRJblZlciI6IjM3LjE3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Yang Song <songy23@users.noreply.github.com>
…ry#30803) **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.--> This enables the `goleak` check on all tests in this package, to ensure the exporter isn't leaking goroutines. The only updates here are tests, as some were missing necessary `shutdown` calls. I also updated some variable naming to match types, such as `le` for a logs exporter instead of `me`. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All tests are passing, including added `goleak` check. --------- Co-authored-by: Alex Boten <aboten@lightstep.com>
…pen-telemetry#31164) **Description:** Add [`--no-print-directory`](https://www.gnu.org/software/make/manual/html_node/_002dw-Option.html) to Makefile invocations. The information is already there since the `make -C` invocation is printed, and it makes the output much longer. Before: ``` Running target 'test' in module 'extension/encoding' as part of group 'extension' make -C extension/encoding test make[2]: Entering directory '/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/encoding' # Actual test output goes here # ... make[2]: Leaving directory '/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/encoding' Running target 'test' in module 'extension/encoding/jaegerencodingextension' as part of group 'extension' # ... ``` After: ``` Running target 'test' in module 'extension/encoding' as part of group 'extension' make --no-print-directory -C extension/encoding test # Actual test output goes here # ... Running target 'test' in module 'extension/encoding/jaegerencodingextension' as part of group 'extension' # ... ```
…emetrygen to merge group (open-telemetry#31162) **Description:** Adds CI jobs that have required jobs to merge group. Needed for the merge queue requested on open-telemetry/community/issues/1936 **Link to tracking Issue:** open-telemetry#30880
…lemetry#30813) **Description:** <Describe what has changed.> The `addToGroupedMetric` previously took the logger as well as the config as arguments. However, the logger is already available as a field in the config so it is redundant to pass it separately. This commit removes the logger argument. **Testing:** The affected unit tests were updated
…metrics (open-telemetry#31161) **Description:** <Describe what has changed.> * Adds a new WriteMetricsOption type, which can be specified when calling WriteMetrics * Adds a WriteMetricsOption for skipping the timestamp normalization step. **Link to tracking Issue:** Closes open-telemetry#30919 **Testing:** <Describe what testing was performed and which tests were added.> * Unit test added for new functionality
…en-telemetry#31153) **Description:** * re-order how we start and stop the different goroutines in the logstransform processor The idea is, we start the goroutines from the consumer end up to the producer end, then shut them down in reverse order. This is similar to how stanza itself starts and stops it's operators, for instance (starts in reverse topological order, stops in topological order). **Link to tracking Issue:** Closes open-telemetry#31139 **Testing:** Added a unit test. This unit test regularly fails on the code on main (panics), but works consistently on this branch (I've run it 100 times to makes sure). ```sh go test -timeout 10m -count=100 -v -run '^TestProcessorShutdownWithSlowOperator$' github.com/open-telemetry/opentelemetry-collector-contrib/processor/logstransformprocessor ```
**Description:** This PR adds a more detailed example on how to use `multiline` setting on `filelog` receiver. From my search I wasn't able to find any examples around so I think it would be nice to have something for users that are willing to quickly get on-boarded on log collection. **Link to tracking Issue:** <Issue number if applicable> - **Testing:** <Describe what testing was performed and which tests were added.> - **Documentation:** <Describe the documentation added.> . Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
This creates dedicated modules for `filestorage` and `dbstorage` extensions. It leaves the `storage` module in place to contain the `storage/storagetest` package.
…ks in builder (open-telemetry#31172) See open-telemetry/opentelemetry-collector#9526 for context - we are removing the possibility that the next consumer passed in is nil in the pipelines builders.
…pen-telemetry#31150) **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.--> The [logicmonitor dependency](https://github.com/logicmonitor/lm-data-sdk-go) that handles exporting data relies on the context being cancelled to shutdown its running goroutines ([traces reference](https://github.com/logicmonitor/lm-data-sdk-go/blob/93e0505a0dce33bfd874c67bdf85e3845126cc3d/pkg/ratelimiter/traces.go#L113), [logs reference](https://github.com/logicmonitor/lm-data-sdk-go/blob/93e0505a0dce33bfd874c67bdf85e3845126cc3d/pkg/ratelimiter/logs.go#L70)). The exporter has now been updated to properly cancel the passed context to fix leaking goroutines on shutdown. This change also enables `goleak` to check for leaking goroutines in the logicmonitor exporter package. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing tests are passing, as well as added `goleak` check.
This will allow us to run all the "checks" locally. It's not fast, but it at least saves me from waiting for CI to tell me i messed up :D Signed-off-by: Alex Boten <aboten@lightstep.com>
This PR contains a few minor code cleanups and test speed optimizations.
…etry#31117) See open-telemetry#31115 Our existing definition and process for code ownership are quite good but this PR suggests a few minor tweaks. - Add triaging as a code owner responsibility. Since this is arguably the easiest thing a code owner can do, we should highlight that it is helpful work. - Move "The existing Code Owners are actively looking for more help" to the top of the list of reasons why additional code owners may be needed, since this is most often the case. - Add a note about code ownership not needing to be a full time job. The goal is not to lower the bar in terms of quality, but to encourage lower bandwidth contributors not to self-select out.
…ction (open-telemetry#31185) **Description:** Fsync was added to filestorage, but during compaction the database is re-opened which doesn't carry over the fsync configuration but always sets it to false(!) **Link to tracking Issue:** open-telemetry#20266 **Testing:** - **Documentation:** -
…metry#31168) **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.--> `Instumentation` -> `Instrumentation`. Also had to remove a dead link.
…emetry#31155) **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.--> This enables `goleak` checks on the `jaegarremotesampling` extension, to help ensure no goroutines are leaking. This is a test only change, a couple close/stop calls were missing. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing tests are passing, as well as added goleak check.
After discussion with @lquerel, he mentioned the component is no longer maintained at F5. Marking it as deprecated. --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
Fixes open-telemetry#31105 --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
…etry#31152) The opencensus receiver opens a few servers on `Start`, each of which use the context's cancel to signal shutdown. Without cancelling the context, the goroutines were being leaked. This change properly cancels the context and shutdowns the receiver's servers. This also enables `goleak` checks on the opencensus receiver and exporter. I realize the exporter is not technically related here, but its tests were what alerted me to the leak in the receiver. The `TestSendTraces` and `TestSendMetrics` tests in the exporter were starting opencensus receivers and exporters, and failing on leaks. The change here is test-only for the exporter, and a bug fix for the receiver. open-telemetry#30438 All existing tests are passing, as well as added `goleak` checks.
…ry#31148) Relates to open-telemetry#27849 Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>
Closes open-telemetry#20850 Closes open-telemetry#20851 Also enhances the `emittest` package, though it remains internal.
…y#31154) **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.--> This adds `goleak` checks on the `bearertokenauthextension` extension to help ensure no goroutines are being leaked. This is a test only change. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing tests are passing as well as added `goleak` check.
… traces consume (open-telemetry#30915) **Description:** According to open-telemetry#30141 (review) PR adds benchmarks for functions: - `mergeTraces` - `mergeMetrics` - `consumeTraces` - `consumeMetrics`
….0 (open-telemetry#31455) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/prometheus/client_golang](https://togithub.com/prometheus/client_golang) | `v1.18.0` -> `v1.19.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>prometheus/client_golang (github.com/prometheus/client_golang)</summary> ### [`v1.19.0`](https://togithub.com/prometheus/client_golang/releases/tag/v1.19.0) [Compare Source](https://togithub.com/prometheus/client_golang/compare/v1.18.0...v1.19.0) #### What's Changed The module `prometheus/common v0.48.0` introduced a bug when used together with client_golang. If your project uses client_golang and you want to use `prometheus/common v0.48.0` or higher, please update client_golang to v1.19.0. - \[CHANGE] Minimum required go version is now 1.20 (we also test client_golang against new 1.22 version). [#​1445](https://togithub.com/prometheus/client_golang/issues/1445) [#​1449](https://togithub.com/prometheus/client_golang/issues/1449) - \[FEATURE] collectors: Add version collector. [#​1422](https://togithub.com/prometheus/client_golang/issues/1422) [#​1427](https://togithub.com/prometheus/client_golang/issues/1427) #### New Contributors - [@​michurin](https://togithub.com/michurin) made their first contribution in [https://github.com/prometheus/client_golang/pull/1423](https://togithub.com/prometheus/client_golang/pull/1423) - [@​kavu](https://togithub.com/kavu) made their first contribution in [https://github.com/prometheus/client_golang/pull/1445](https://togithub.com/prometheus/client_golang/pull/1445) - [@​ywwg](https://togithub.com/ywwg) made their first contribution in [https://github.com/prometheus/client_golang/pull/1448](https://togithub.com/prometheus/client_golang/pull/1448) **Full Changelog**: prometheus/client_golang@v1.18.0...v1.19.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 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:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMTIuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIxMi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
…etry#30516) Relates to open-telemetry#27849 --------- Co-authored-by: Antoine Toulme <antoine@lunar-ocean.com>
…elemetry#30540) Relates to open-telemetry#27849 --------- Co-authored-by: Antoine Toulme <antoine@lunar-ocean.com>
…-telemetry#31347) [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [go.mongodb.org/mongo-driver](https://togithub.com/mongodb/mongo-go-driver) | `v1.13.1` -> `v1.14.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>mongodb/mongo-go-driver (go.mongodb.org/mongo-driver)</summary> ### [`v1.14.0`](https://togithub.com/mongodb/mongo-go-driver/releases/tag/v1.14.0): MongoDB Go Driver 1.14.0 [Compare Source](https://togithub.com/mongodb/mongo-go-driver/compare/v1.13.2...v1.14.0) The MongoDB Go Driver Team is pleased to release version 1.14.0 of the official Go driver. #### Release Notes This release bumps the minimum Go version from 1.13 to 1.18. It also brings several additional changes and improvements. ##### Notable Changes - In case of a heartbeat timeout, in-progress operations are preemptively canceled. - Support connecting with a "mongodb+srv://" URI that contains capital letters in the SRV hostname. *** For a full list of tickets included in this release, please see the links below: - [Improvements](https://jira.mongodb.org/issues/?jql=project%3Dgodriver%20and%20type%3Dimprovement%20and%20status%20%3D%20Closed%20and%20fixVersion%3D1.14.0) - [Tasks](https://jira.mongodb.org/issues/?jql=project%3Dgodriver%20and%20type%3D%22task%22%20and%20status%20%3D%20Closed%20and%20fixVersion%3D1.14.0) **Full Changelog**: [v1.13.2...1.14.0](https://togithub.com/mongodb/mongo-go-driver/compare/v1.13.2...v1.14.0) Documentation for the Go driver can be found on [pkg.go.dev](https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo?tab=doc) and the [MongoDB documentation site](https://docs.mongodb.com/ecosystem/drivers/go/). BSON library documentation is also available on [pkg.go.dev](https://pkg.go.dev/go.mongodb.org/mongo-driver/bson?tab=doc). Questions and inquiries can be asked on the [MongoDB Developer Community](https://community.mongodb.com/). Bugs can be reported in the [Go Driver project in the MongoDB JIRA](https://jira.mongodb.org/secure/CreateIssue!default.jspa?pid=14289) where a list of [current issues](https://jira.mongodb.org/browse/GODRIVER) can be found. Your feedback on the Go driver is greatly appreciated! ### [`v1.13.2`](https://togithub.com/mongodb/mongo-go-driver/releases/tag/v1.13.2): MongoDB Go Driver 1.13.2 [Compare Source](https://togithub.com/mongodb/mongo-go-driver/compare/v1.13.1...v1.13.2) The MongoDB Go Driver Team is pleased to release version 1.13.2 of the official Go driver. #### Release Notes This release restores the behavior that an empty map or slice is decoded as nil, and fixes a bug of connecting via UNIX sockets like `mongodb://%2Ftmp%2Fmongodb-27017.sock`. This release also stops propagating passwords in error messages. *** For a full list of tickets included in this release, please see the links below: - [Improvements](https://jira.mongodb.org/issues/?jql=project%3Dgodriver%20and%20type%3Dimprovement%20and%20status%20%3D%20Closed%20and%20fixVersion%3D1.13.2) - [Bugs](https://jira.mongodb.org/issues/?jql=project%3DGODRIVER%20and%20type%3DBug%20and%20status%3Dclosed%20and%20fixVersion%3D1.13.2) - [Tasks](https://jira.mongodb.org/issues/?jql=project%3Dgodriver%20and%20type%3D%22task%22%20and%20status%20%3D%20Closed%20and%20fixVersion%3D1.13.2) **Full Changelog**: [v1.13.1...1.13.2](https://togithub.com/mongodb/mongo-go-driver/compare/v1.13.1...v1.13.2) Documentation for the Go driver can be found on [pkg.go.dev](https://pkg.go.dev/go.mongodb.org/mongo-driver/mongo?tab=doc) and the [MongoDB documentation site](https://docs.mongodb.com/ecosystem/drivers/go/). BSON library documentation is also available on [pkg.go.dev](https://pkg.go.dev/go.mongodb.org/mongo-driver/bson?tab=doc). Questions and inquiries can be asked on the [MongoDB Developer Community](https://community.mongodb.com/). Bugs can be reported in the [Go Driver project in the MongoDB JIRA](https://jira.mongodb.org/secure/CreateIssue!default.jspa?pid=14289) where a list of [current issues](https://jira.mongodb.org/browse/GODRIVER) can be found. Your feedback on the Go driver is greatly appreciated! </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMDAuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIyMC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com>
Update test cases to ignore the order of resource/scope metrics since the returned histograms-only pmetrics can have different ordering for resource and scope metrics Fixes open-telemetry#31493
…31151) **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.--> This enables `goleak` checks in the Logz.io exporter to help ensure no goroutines are being leaked. This is a test only change as the only thing necessary was to add a missing close call on a server in a test. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing tests are passing, as well as added `goleak` check.
**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.--> `goleak` was detecting leaking goroutines in tests, this attempts to resolve. I found what appeared to be a couple races but can't reproduce locally so I'll run CI a few times to ensure this works as expected. Changes in PR: 1. Add correlation client Shutdown function that blocks on the waitgroup. This is the main fix of this PR that should fix the leaking goroutines. 2. Re-organize the shutdown process of the apm client correlation test suite to properly synchronize the shutting down process. 3. Fix typo 4. Add goleak checks to exporter/signalfx/internal/correlation` and `exporter/signalfx/internal/apm/correlations` **Link to tracking Issue:** <Issue number if applicable> Resolves open-telemetry#30864 open-telemetry#30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing and added tests should be passing. Since this has only failed in CI I'm going to try to run it a few times before marking as ready for review.
Updates all datadog dependencies to the psuedo version from the [otel/backport](https://github.com/DataDog/datadog-agent/tree/otel/backport) branch. Removes [blocking channel changes](DataDog/datadog-agent#23085) and associated changelog.
…31530) It'll allow us to apply comparisons to the stability levels
…on string (open-telemetry#31523) This PR introduces the ability to configure the Azure Monitor Exporter connection string through the `APPLICATIONINSIGHTS_CONNECTION_STRING` environment variable. Updated tests & readme.
Unclear why these ended up here, removing them. Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
**Description:** Add generated tests for chrony receiver; move initialization of the chrony client to the start function **Link to tracking Issue:** Relates to open-telemetry#27849
Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
**Description:** This adds Grafana Agent as a distribution to some new components after the Grafana Agent v0.40 release. https://github.com/grafana/agent/blob/v0.40.0/CHANGELOG.md **Documentation:** Adding links to grafana agent in the alphabetically-sorted list.
…try#31532) The tests can be disabled with `skip_lifecycle` and `skip_shutdown` metadata.yaml options. But it's strongly encouraged to avoid skipping them. This PR doesn't have any functional changes. Only tests changes
…ry#30887)" (open-telemetry#31541) This reverts commit 494bdb8. The change introduced a flaky test, making the build unstable. Reverting for now. Examples: - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8135561006/job/22233883822 - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8131615657/job/22221154096 - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8118428574/job/22192725196
…emetry#31528) **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 `source:{datadogexporter|datadogconnector}` tag to trace agent telemetry metrics. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
**Description:** Needed for open-telemetry/opentelemetry-collector/pull/9472
**Description:** This is in preparation for the v0.96.0 release - [chore] multimod update stable modules - [chore] multimod update beta modules - make update-otel - make genotelcontribcol; make genoteltestbedcol --------- Signed-off-by: Pablo Baeyens <pablo.baeyens@datadoghq.com>
…sage due to panic during shutdown (open-telemetry#31550) Fixes open-telemetry#31476
**Description:** <Describe what has changed.> Reuse of connections created per database (configured or discovered) vs current behavior to create & close connection per database on each scrape. **Link to tracking Issue:** open-telemetry#30831 **Testing:** Updated unit & integration tests. Also, ran locally multiple scenario: - no feature gate specified (default): current behavior maintained, connections created/closed on each database per scrape - feature gate connection pool enabled, no connection pool config specified (default): reduction of the number of connections created/closed - feature gate connection pool enabled, connection pool config tweaked: connections created on first scrape & closed when configured lifetime reached or collector shutdown **Documentation:** - change log - readme for the feature gate & related optional configurations linked to this feature **Note** Checking internally for getting the CLA signed
**Description:** Update core to v0.96.0 **Link to tracking Issue:** open-telemetry/opentelemetry-collector/issues/9681 --------- Signed-off-by: Pablo Baeyens <pablo.baeyens@datadoghq.com>
…emetry#31539) To unblock the build on Windows.
The following commands were run to prepare this release: - make chlog-update VERSION=v0.96.0 - sed -i.bak s/0.95.0/0.96.0/g versions.yaml - make multimod-prerelease - make multimod-sync --------- Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> Co-authored-by: Evan Bradley <11745660+evan-bradley@users.noreply.github.com>
](https://renovatebot.com){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge upstream v0.96.0