Foadnh bump to v0 85 0 #8745
Merged
Foadnh bump to v0 85 0 #8745
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
…y#25105) Bump github.com/Azure/azure-event-hubs-go/v3 from 3.6.0 to 3.6.1 in /receiver/azureblobreceiver Bump github.com/Azure/azure-event-hubs-go/v3 from 3.6.0 to 3.6.1 in /receiver/azureeventhubreceiver Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.44.316 to 1.44.319 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go-v2 from 1.20.0 to 1.20.1 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/config from 1.18.32 to 1.18.33 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.31 to 1.13.32 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/service/sts from 1.21.1 to 1.21.2 in /extension/sigv4authextension Bump github.com/getsentry/sentry-go from 0.22.0 to 0.23.0 in /exporter/sentryexporter Bump github.com/hashicorp/consul/api from 1.23.0 to 1.24.0 in /internal/metadataproviders Bump github.com/hashicorp/consul/api from 1.23.0 to 1.24.0 in /processor/resourcedetectionprocessor Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /exporter/signalfxexporter Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /extension/observer/hostobserver Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /receiver/awscontainerinsightreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /receiver/hostmetricsreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /receiver/jmxreceiver Bump github.com/shirou/gopsutil/v3 from 3.23.6 to 3.23.7 in /testbed Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.715 to 1.0.717 in /exporter/tencentcloudlogserviceexporter Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /extension/observer/dockerobserver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /internal/coreinternal Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/aerospikereceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/apachereceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/dockerstatsreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/elasticsearchreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/flinkmetricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/jmxreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/kafkametricsreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/memcachedreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/mongodbreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/mysqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/nginxreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/postgresqlreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/redisreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/sqlqueryreceiver Bump github.com/testcontainers/testcontainers-go from 0.21.0 to 0.22.0 in /receiver/zookeeperreceiver Bump github.com/vmware/govmomi from 0.30.6 to 0.30.7 in /receiver/vcenterreceiver Bump go.mongodb.org/mongo-driver from 1.12.0 to 1.12.1 in /receiver/mongodbreceiver Bump golang.org/x/crypto from 0.11.0 to 0.12.0 in /receiver/podmanreceiver Bump golang.org/x/net from 0.12.0 to 0.14.0 in /exporter/azuremonitorexporter Bump golang.org/x/net from 0.12.0 to 0.14.0 in /internal/aws/awsutil Bump golang.org/x/oauth2 from 0.10.0 to 0.11.0 in /exporter/f5cloudexporter Bump golang.org/x/oauth2 from 0.10.0 to 0.11.0 in /extension/oauth2clientauthextension Bump golang.org/x/sys from 0.10.0 to 0.11.0 in /exporter/signalfxexporter Bump golang.org/x/sys from 0.10.0 to 0.11.0 in /pkg/stanza Bump golang.org/x/sys from 0.10.0 to 0.11.0 in /pkg/winperfcounters Bump golang.org/x/sys from 0.10.0 to 0.11.0 in /receiver/hostmetricsreceiver Bump golang.org/x/sys from 0.10.0 to 0.11.0 in /receiver/windowseventlogreceiver Bump golang.org/x/text from 0.11.0 to 0.12.0 in /cmd/configschema Bump golang.org/x/text from 0.11.0 to 0.12.0 in /cmd/mdatagen Bump golang.org/x/text from 0.11.0 to 0.12.0 in /internal/coreinternal Bump golang.org/x/text from 0.11.0 to 0.12.0 in /pkg/stanza Bump golang.org/x/text from 0.11.0 to 0.12.0 in /testbed Bump golang.org/x/tools from 0.11.1 to 0.12.0 in /internal/tools Bump sigs.k8s.io/controller-runtime from 0.15.0 to 0.15.1 in /exporter/loadbalancingexporter --------- Co-authored-by: Dmitrii Anoshin <[email protected]>
…y#25113) Bump github.com/hashicorp/golang-lru from 0.5.4 to 1.0.2 in /extension/observer/ecsobserver Bump github.com/hashicorp/golang-lru from 0.6.0 to 1.0.2 in /processor/spanmetricsprocessor Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.717 to 1.0.719 in /exporter/tencentcloudlogserviceexporter Bump google.golang.org/api from 0.134.0 to 0.136.0 in /receiver/googlecloudspannerreceiver
…figopaque.String` (open-telemetry#24778) clickhouse exporter also needs use `Config.Password`. --------- Co-authored-by: Dmitrii Anoshin <[email protected]>
open-telemetry#25120) **Description:** Add a new test 'testInvalidMethod' in receiver_test.go, and refactor code for readability.
…metric (open-telemetry#25123) Replaces open-telemetry#25115 --------- Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]> Co-authored-by: Ryan Fitzpatrick <[email protected]>
…-telemetry#25127) **Description:** [exporter/signalfx] Added few tests for histogram metrics on SFx exporter's converter piece **Link to tracking Issue:** open-telemetry#25067
…25140) **Description:** related open-telemetry#23266 Signed-off-by: Ziqi Zhao <[email protected]>
…5143) **Description:** There is flaky Windows test **Link to tracking Issue:** open-telemetry#25094 **Testing:** Before applying this change, it has failed in 1 test out of 60. So this should pass 200 tests without failure.
…o translateOTelToGroupedMetric (open-telemetry#24051) **Description:** The config option `retain_initial_value_of_delta_metric` does not seem to be used in `translateOTelToGroupedMetric`, which prevents the initial value of a basic counter from being published during a Lambda cold boot. Please see the minimum project required to replicate the issue [here](https://github.com/jameshi16/delta-initial-value-minimum-project). **Link to tracking Issue:** The main issue related to this PR can be found [here](aws-observability/aws-otel-lambda#634). It seems like I had a predecessor fixing this issue (see open-telemetry#17988), but his changes does not work for my use case. **Testing:** An additional test ensures that if `retain_initial_value_of_delta_metric` is set, it will be propagated to the `cWMetricMetadata`. **Documentation:** None
…lemetry#25151) To not update required jobs every time a new go version is released. Needed for open-telemetry#25116
…bute (open-telemetry#23668) **Description:** Add k8s.cluster.uid to attribute to k8sattributes processor and disable it by default for backward compatibility. Users can set it to `true` to populate cluster uid as part of resource attributes. **Link to tracking Issue:** open-telemetry#21974
This is primarily to align the version with what the Collector uses in `confmap`. It doesn't introduce any functional changes.
**Description:** related open-telemetry#23266 Signed-off-by: Ziqi Zhao <[email protected]>
…ry#25182) Bump github.com/openzipkin/zipkin-go from 0.4.1 to 0.4.2 in /receiver/pulsarreceiver
This pull request is for a newly created Datadog connector that replaces the need for the Datadog processor. This replacement is needed because the processor made use of a work-around that directly allowed the processor to export data. This is not something that adheres to the OpenTelemetry standard and thus the previous system should be deprecated and replaced by this new connector. Link to issue: open-telemetry#19740 --------- Co-authored-by: Yang Song <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
…ent concurrent write to buffer. (open-telemetry#25100) Change the TCP/UDP inputs so that they parse the encoding and get the `encoding.Encoding` during initialization, but wait to create the `helper.Encoding` instance in each goroutine. This prevents concurrent calls to `Decode` using the same instance. Co-authored-by: Dan Jaglowski <[email protected]>
…ClientSecret from files (open-telemetry#26310) **Description:** This PR implements the feature described in detail in the issue linked below. In a nutshell, it extends the `oauth2clientauth` extension to read ClientID and/or ClientSecret from files whenever a new token is needed for the OAuth flow. As a result, the extension can use updated credentials (when the old ones expire for example) without the need to restart the OTEL collector, as long as the file contents are in sync. **Link to tracking Issue:** open-telemetry#26117 **Testing:** Apart from the unit testing you can see in the PR, I've tested this feature in two real-life environments: 1. As a systemd service exporting `otlphttp` data 2. A Kubernetes microservice (deployed by an OpenTelemetryCollector CR) exporting `otlphttp` data In both cases, the collectors export the data to a service which sits behind an OIDC authentication proxy. Using the `oauth2clientauth` extension, the `otlphttp` exporter hits the authentication provider to issue tokens for the OIDC client and successfully authenticates to the service. In my cases, the ClientSecret gets rotated quite frequently and there is a stack making sure the ClientID and ClientSecret in the corresponding files are up-to-date. **Documentation:** I have extended the extension's README file. I'm open to more suggestions! cc @jpkrohling @pavankrish123
) Followup to open-telemetry#26517 The `MultiLineTokenizerTestCase` became unnecessary with changes in the previous PR but the diff caused by removing it was quite large. This PR just removes the struct.
Subset of open-telemetry#26241 This finally removes the `SplitterConfig` struct, which at this point is only a wrapper around `MultilineConfig`.
) Use the Timeout setting from ScraperHelper instead --------- Signed-off-by: Alex Boten <[email protected]>
See open-telemetry#25060 for original request. This adds the reassign linter, checking no package variables are reassigned.
Signed-off-by: Alex Boten <[email protected]>
See open-telemetry#25060 for original request. This adds the wastedassign linter with default configuration. It ensures no assignmnent is made to a variable and then not used.
To ensure that no tests fail with the latest merges in core
This updates core once again because of the missed deps. --------- Signed-off-by: Alex Boten <[email protected]>
**Description:** Set up the telemetrygen job to restart on failure **Link to tracking Issue:** Fixes open-telemetry#24223 **Testing:** See open-telemetry#26530 (comment) This investigation shows that the job fails to run sometimes. All other deployments have a policy to restart on failure.
…ry#26571) Bump google.golang.org/api from 0.138.0 to 0.139.0 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.57.0 to 1.58.0 in /receiver/googlecloudspannerreceiver
Linked issue open-telemetry#26304 Signed-off-by: Jared Tan <[email protected]>
) **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 optional k8s.kubelet.version, k8s.kubeproxy.version node resource attributes Doing some actual testing with kind with k8s_cluster receiver and prometheus exporters. ``` k8s_cluster: node_conditions_to_report: [Ready, MemoryPressure] allocatable_types_to_report: [cpu, memory] resource_attributes: k8s.kubelet.version: enabled: true k8s.kubeproxy.version: enabled: true ``` and prometheus exporter: ``` prometheus: resource_to_telemetry_conversion: enabled: true endpoint: 0.0.0.0:9090 ``` Example metric: ``` k8s_node_allocatable_cpu{k8s_kubelet_version="v1.25.3",k8s_kubeproxy_version="v1.25.3",k8s_node_name="kind-control-plane",k8s_node_uid="09b55a47-87cb-4790-8834-2341d683999d",opencensus_resourcetype="k8s"} 8 ``` **Link to tracking Issue:** open-telemetry#24835 **Testing:** <Describe what testing was performed and which tests were added.> - added unit tests - manua ltest with kind **Documentation:** <Describe the documentation added.> - generated
…es (open-telemetry#26516) **Description:** Remove support for deprecated Kubernetes API resources: - `batch/v1beta1` - `autoscaling/v2beta2` This also resolves the issue with double reporting metrics for hpa and cronjob in certain k8s versions. **Link to tracking Issue(s):** open-telemetry#23612 open-telemetry#26551 **Testing:** From source, built the custom image [coolboi567/otelcontribcol:0.83.1](https://hub.docker.com/layers/coolboi567/otelcontribcol/0.83.1/images/sha256-fe111e1dff87a26eb64217a8505b84679263c8d7b3ffa16656bba1c1865052d5?context=explore) and tested in kubernetes cluster `v1.25` as well as `v1.27`. In K8s `v1.25`, we no longer see the warnings in the logs about usage of deprecated APIs. **Documentation:** N/A --------- Signed-off-by: Prashant Shahi <[email protected]> Co-authored-by: Dmitrii Anoshin <[email protected]>
Subset of open-telemetry#26241 Follows open-telemetry#26540 - Rename `MultilineConfig` to `split.Config` - Remove `Multiline`, previously a struct representation that only wrapped a split func - Remove `NewMultilineConfig`, because `split.Config` is just two simple fields with "" defaults. - Condense references in tests - Substantially increate test coverage in `split` package.
…n-telemetry#26098) **Description:** Updates the receiver to properly handle 410 response code. The expectations for what clients should do when a 410 is received can be found here: https://kubernetes.io/docs/reference/using-api/api-concepts/#410-gone-responses. I originally implemented this feature directly in `startWatch`, rebuilding the watcher and res channel within the for loop, but I grew concerned about making sure everything stopped correctly. I took a look at the retry watcher's implementation and reused its concepts for this implementation. If it is overcomplicated we can go back to my original idea. **Link to tracking Issue:** <Issue number if applicable> Closes open-telemetry#24903 **Testing:** <Describe what testing was performed and which tests were added.> Tested locally. Unit tests proved to be extremely challenging since I couldn't figure out how to get the mock to produce a 410. We really need e2e tests (open-telemetry#18395). --------- Co-authored-by: Evan Bradley <[email protected]>
For some reason, `make update-otel` failed for me. Will make a note to add an issue Signed-off-by: Alex Boten <[email protected]>
…metry#26366) **Description:** CWL Logs exporter was using an alias for the exporter package to avoid a naming conflict. I renamed the internal struct to resolve the error and remove the need for the alias. I did not create a breaking changelog entry for this as no api surface was changed. **Link to tracking Issue:** open-telemetry#26304
…etry#26642) [](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | prom/prometheus | minor | `v2.46.0` -> `v2.47.0` | --- ### 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:eyJjcmVhdGVkSW5WZXIiOiIzNi44My4wIiwidXBkYXRlZEluVmVyIjoiMzYuODMuMCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
The following commands were run to prepare this release: - make chlog-update VERSION=v0.85.0 - sed -i.bak s/0.84.0/0.85.0/g versions.yaml - make multimod-prerelease - make multimod-sync
](https://renovatebot.com){kind=link}
phoebe-canva
approved these changes
Nov 6, 2023
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.
Bump version to
v0.85.0