Update check changes target #4
Closed
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
The following commands were run to prepare this release: - make chlog-update VERSION=v0.76.0/v1.0.0-rc10 - make prepare-release GH=none PREVIOUS_VERSION=1.0.0-rc9 RELEASE_CANDIDATE=1.0.0-rc10 MODSET=stable - make prepare-release GH=none PREVIOUS_VERSION=0.75.0 RELEASE_CANDIDATE=0.76.0 MODSET=beta
…lemetry#7451) content-type header could contain optional parameters after the mime-type, do not reject requests in this case
Update k8s example to not use 0.0.0.0 on OTLP receiver endpoint
**Description:** Puts the grpc meter provider behind a feature flag for controlling high cardinality metrics. **Link to tracking Issue:** open-telemetry#7517
Updating required APIs along the way. --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
…etry#7574) When request signing-based authentication extensions are used it is necessary to ensure that the Auth RoundTripper is the innermost as changes to the request by other RoundTrippers (such as compression or headers) may invalidate the request signature. This change will ensure that the Auth RoundTripper is invoked after all others and is followed directly by the http.Transport. --------- Signed-off-by: Anthony J Mirabella <a9@aneurysm9.com>
Bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.41.0 to 0.41.1 Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.41.0 to 0.41.1 Bump go.opentelemetry.io/contrib/zpages from 0.40.0 to 0.41.1 in /extension/zpagesextension Bump go.opentelemetry.io/otel from 1.15.0 to 1.15.1 in /exporter Bump go.opentelemetry.io/otel from 1.15.0 to 1.15.1 in /processor/batchprocessor Bump go.opentelemetry.io/otel from 1.15.0 to 1.15.1 in /receiver Bump go.opentelemetry.io/otel/exporters/prometheus from 0.38.0 to 0.38.1 in /processor/batchprocessor Bump go.opentelemetry.io/otel/metric from 0.38.0 to 0.38.1 in /component Bump go.opentelemetry.io/otel/metric from 0.38.0 to 0.38.1 in /processor/batchprocessor Bump go.opentelemetry.io/otel/sdk from 1.15.0 to 1.15.1 Bump go.opentelemetry.io/otel/sdk from 1.15.0 to 1.15.1 in /exporter Bump go.opentelemetry.io/otel/sdk from 1.15.0 to 1.15.1 in /extension/zpagesextension Bump go.opentelemetry.io/otel/sdk from 1.15.0 to 1.15.1 in /processor/batchprocessor Bump go.opentelemetry.io/otel/sdk from 1.15.0 to 1.15.1 in /receiver Bump go.opentelemetry.io/otel/sdk/metric from 0.38.0 to 0.38.1 Bump go.opentelemetry.io/otel/sdk/metric from 0.38.0 to 0.38.1 in /processor/batchprocessor Bump go.opentelemetry.io/otel/trace from 1.15.0 to 1.15.1 Bump go.opentelemetry.io/otel/trace from 1.15.0 to 1.15.1 in /component Bump go.opentelemetry.io/otel/trace from 1.15.0 to 1.15.1 in /exporter Bump go.opentelemetry.io/otel/trace from 1.15.0 to 1.15.1 in /extension/zpagesextension
Cleaning up the license files, and updating `checklicense` to verify the contents of the license as per the `opentelemetry-go-build-tools` repo. --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
Fixes open-telemetry#6849 Signed-off-by: Alex Boten <aboten@lightstep.com>
) Reduce the default queue size to 1000. Combined with the defaults on batchprocessor, the current default of 5000 is too much and will lead to an OOMKill in most environments if actually filled. 1000 is probably too high still, but we don't want to make too drastic of a change here at once. See linked issue for specifics.
Finalizes the purpose of `toVersion`. `toVersion` will represent the version where the feature gate is completely removed. Setting a `stable` gate to `true` will result in a warning log. Setting a `stable` gate to `false` will result in an error. Closes open-telemetry#7621
…elemetry#7559) Update the release process to skip releasing the stable set of modules if there are no changes since the last version
…7531) Adds the ability for create settings to access instantiated resource attributes Link to tracking Issue: open-telemetry#6599
…n-telemetry#7640) Update release scripts to not include unreleased version in the release titles
The following commands were run to prepare this release: make chlog-update VERSION=v0.77.0 make prepare-release GH=none PREVIOUS_VERSION=0.76.1 RELEASE_CANDIDATE=0.77.0 MODSET=beta
This removes the remaining references to components living in the `component` module. Fixes open-telemetry#6578 --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
…ter (open-telemetry#7586) * Update Deprecated to work like Stable but false * Add changelog * Fix lint * Update README
Bump github.com/mostynb/go-grpc-compression from 1.1.17 to 1.1.18 Bump github.com/prometheus/client_golang from 1.15.0 to 1.15.1 Bump github.com/prometheus/client_golang from 1.15.0 to 1.15.1 in /processor/batchprocessor Bump github.com/prometheus/client_model from 0.3.0 to 0.4.0 Bump github.com/prometheus/client_model from 0.3.0 to 0.4.0 in /processor/batchprocessor Bump github.com/prometheus/common from 0.42.0 to 0.43.0 in /processor/batchprocessor Bump golang.org/x/sys from 0.7.0 to 0.8.0 in /cmd/otelcorecol Bump golang.org/x/sys from 0.7.0 to 0.8.0 in /exporter/loggingexporter Bump golang.org/x/tools from 0.8.0 to 0.9.1 in /internal/tools Bump golang.org/x/vuln from 0.0.0-20230411201117-aaaefcd264f6 to 0.1.0 in /internal/tools Bump gonum.org/v1/gonum from 0.12.0 to 0.13.0 Bump google.golang.org/grpc from 1.54.0 to 1.55.0 Bump google.golang.org/grpc from 1.54.0 to 1.55.0 in /exporter/otlpexporter Bump google.golang.org/grpc from 1.54.0 to 1.55.0 in /exporter/otlphttpexporter Bump google.golang.org/grpc from 1.54.0 to 1.55.0 in /pdata Bump google.golang.org/grpc from 1.54.0 to 1.55.0 in /receiver/otlpreceiver
…ls (open-telemetry#7674) Bumps [github.com/cloudflare/circl](https://github.com/cloudflare/circl) from 1.1.0 to 1.3.3. - [Release notes](https://github.com/cloudflare/circl/releases) - [Commits](cloudflare/circl@v1.1.0...v1.3.3) --- updated-dependencies: - dependency-name: github.com/cloudflare/circl dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…7678) This adds the feature-gate telemetry.useOtelWithExtendedConfigurationForInternalTelemetry to start adding support for additional exporters for the collector's internal telemetry. This is part of of open-telemetry#7644 --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
…pace on device (open-telemetry#7396) * add full storage test for persistent storage * improve no disk space handling in persistent storage * review fixes * review fixes
--------- Signed-off-by: Alex Boten <aboten@lightstep.com>
Bump github.com/shirou/gopsutil/v3 from 3.23.3 to 3.23.4 Bump go.opentelemetry.io/contrib/propagators/b3 from 1.15.0 to 1.16.1 Bump go.opentelemetry.io/otel/bridge/opencensus from 0.38.0 to 0.38.1 Bump golang.org/x/net from 0.9.0 to 0.10.0
* move featuregate to stable module-set * Update versions.yaml Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com> * changelog --------- Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
* [chore] use license shortform To remain consistent w/ contrib repo, see open-telemetry/opentelemetry-collector-contrib#22052 Signed-off-by: Alex Boten <aboten@lightstep.com> * make goporto Signed-off-by: Alex Boten <aboten@lightstep.com> --------- Signed-off-by: Alex Boten <aboten@lightstep.com>
If new module is added to a module set or moved from another module set, the release should be required.
dmitryax
added a commit
that referenced
this pull request
Aug 3, 2023
To resolve the govulncheck reports: ``` Vulnerability #1: GO-2023-1987 Large RSA keys can cause high CPU usage in crypto/tls More info: https://pkg.go.dev/vuln/GO-2023-1987 Standard library Found in: crypto/tls@go1.19.11 Fixed in: crypto/tls@go1.21rc4 Example traces found: Error: #1: service/internal/proctelemetry/config.go:299:27: proctelemetry.initOTLPgRPCExporter calls otlpmetricgrpc.New, which eventually calls tls.Conn.Handshake Error: #2: service/internal/proctelemetry/config.go:156:39: proctelemetry.InitPrometheusServer calls http.Server.ListenAndServe, which eventually calls tls.Conn.HandshakeContext Error: #3: service/service.go:251:36: service.buildResource calls uuid.NewRandom, which eventually calls tls.Conn.Read Error: #4: service/config.go:35:13: service.Config.Validate calls fmt.Printf, which eventually calls tls.Conn.Write Error: #5: service/telemetry/telemetry.go:32:28: telemetry.Telemetry.Shutdown calls trace.TracerProvider.Shutdown, which eventually calls tls.Dialer.DialContext ```
dmitryax
added a commit
that referenced
this pull request
Aug 7, 2023
To resolve the govulncheck reports: ``` Vulnerability #1: GO-2023-1987 Large RSA keys can cause high CPU usage in crypto/tls More info: https://pkg.go.dev/vuln/GO-2023-1987 Standard library Found in: crypto/tls@go1.19.11 Fixed in: crypto/tls@go1.21rc4 Example traces found: Error: #1: service/internal/proctelemetry/config.go:299:27: proctelemetry.initOTLPgRPCExporter calls otlpmetricgrpc.New, which eventually calls tls.Conn.Handshake Error: #2: service/internal/proctelemetry/config.go:156:39: proctelemetry.InitPrometheusServer calls http.Server.ListenAndServe, which eventually calls tls.Conn.HandshakeContext Error: #3: service/service.go:251:36: service.buildResource calls uuid.NewRandom, which eventually calls tls.Conn.Read Error: #4: service/config.go:35:13: service.Config.Validate calls fmt.Printf, which eventually calls tls.Conn.Write Error: #5: service/telemetry/telemetry.go:32:28: telemetry.Telemetry.Shutdown calls trace.TracerProvider.Shutdown, which eventually calls tls.Dialer.DialContext ``` https://github.com/open-telemetry/opentelemetry-collector/actions/runs/5753675727/job/15597394973?pr=8144
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.
No description provided.