renovate[bot]
834ede370c
This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [google.golang.org/grpc](https://redirect.github.com/grpc/grpc-go) | `v1.84.0` → `v1.85.0` |  |  | | [google.golang.org/grpc](https://redirect.github.com/grpc/grpc-go) | `v1.83.2` → `v1.85.0` |  |  | --- ### Release Notes <details> <summary>grpc/grpc-go (google.golang.org/grpc)</summary> ### [`v1.85.0`](https://redirect.github.com/grpc/grpc-go/releases/tag/v1.85.0): Release 1.85.0 [Compare Source](https://redirect.github.com/grpc/grpc-go/compare/v1.84.0...v1.85.0) ### New Features - stats: Expose the effective client authority (sent on the wire as the HTTP/2 `:authority` header) in client `stats.OutHeader` events. ([#​9296](https://redirect.github.com/grpc/grpc-go/issues/9296)) - Special Thanks: [@​aryansk](https://redirect.github.com/aryansk) - metadata: Add `ValueFromOutgoingContext`, which reads a single metadata value from outgoing context without copying the entire outgoing metadata into a new map. ([#​9282](https://redirect.github.com/grpc/grpc-go/issues/9282)) - Special Thanks: [@​yuyangguo42](https://redirect.github.com/yuyangguo42) ### Bug Fixes - transport: Refine control buffer throttling to only count peer-induced control frames, raise the default `GRPC_GO_EXPERIMENTAL_CONTROL_BUFFER_THROTTLE_LIMIT` from 100 to 10,000, and close client connections if reads remain throttled for `10s`. ([#​9563](https://redirect.github.com/grpc/grpc-go/issues/9563)) - server: Ensure `Stop()` forcefully terminates the server while `GracefulStop()` is waiting for active handlers to complete. ([#​9394](https://redirect.github.com/grpc/grpc-go/issues/9394)) - Special Thanks: [@​stanhu](https://redirect.github.com/stanhu) - server: Unconditionally increment the highest-seen stream ID on when handling `HEADERS` frames to comply with [RFC 7540 §5.1.1](https://www.rfc-editor.org/rfc/rfc7540.html#section-5.1.1). Previously, truncated `HEADERS` frames left the connection in an inconsistent state and allowed stream IDs to be reused by clients without resulting in a protocol error. ([#​9414](https://redirect.github.com/grpc/grpc-go/issues/9414)) - server: Terminate streams immediately when a `HEADERS` frame includes the `EndStream` bit. Previously, this caused server handlers to hang when reading a message. ([#​9391](https://redirect.github.com/grpc/grpc-go/issues/9391)) - server: Reject requests missing both `:authority` and `Host` headers with HTTP 400 and status `Internal`. ([#​9365](https://redirect.github.com/grpc/grpc-go/issues/9365)) - xds: Fix a bug where route header matchers with non-lowercase names failed to match routes. ([#​9353](https://redirect.github.com/grpc/grpc-go/issues/9353)) - Special Thanks: [@​winklemad](https://redirect.github.com/winklemad) - client: Ensure retried RPCs use the correct `:authority` value specified by the LB policy instead of inheriting it from a previous attempt. ([#​9277](https://redirect.github.com/grpc/grpc-go/issues/9277)) - Special Thanks: [@​nvxbug](https://redirect.github.com/nvxbug) - transport: Fail streams with `io.ErrUnexpectedEOF` instead of `io.EOF` upon receiving truncated message headers or bodies after partial data has already been received. ([#​9204](https://redirect.github.com/grpc/grpc-go/issues/9204)) - Special Thanks: [@​buger](https://redirect.github.com/buger) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - 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 these updates 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-go). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE4NC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
OpenTelemetry-Go
OpenTelemetry-Go is the Go implementation of OpenTelemetry. It provides a set of APIs to directly measure performance and behavior of your software and send this data to observability platforms.
Project Status
| Signal | Status |
|---|---|
| Traces | Stable |
| Metrics | Stable |
| Logs | Stable |
Progress and status specific to this repository is tracked in our project boards and milestones.
Project versioning information and stability guarantees can be found in the versioning documentation.
Compatibility
OpenTelemetry-Go ensures compatibility with the current supported versions of the Go language:
Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.
For versions of Go that are no longer supported upstream, opentelemetry-go will stop ensuring compatibility with these versions in the following manner:
- A minor release of opentelemetry-go will be made to add support for the new supported release of Go.
- The following minor release of opentelemetry-go will remove compatibility testing for the oldest (now archived upstream) version of Go. This, and future, releases of opentelemetry-go may include features only supported by the currently supported versions of Go.
Currently, this project supports the following environments.
| OS | Go Version | Architecture |
|---|---|---|
| Ubuntu | 1.27 | amd64 |
| Ubuntu | 1.26 | amd64 |
| Ubuntu | 1.27 | 386 |
| Ubuntu | 1.26 | 386 |
| Ubuntu | 1.27 | arm64 |
| Ubuntu | 1.26 | arm64 |
| macOS | 1.27 | amd64 |
| macOS | 1.26 | amd64 |
| macOS | 1.27 | arm64 |
| macOS | 1.26 | arm64 |
| Windows | 1.27 | amd64 |
| Windows | 1.26 | amd64 |
| Windows | 1.27 | 386 |
| Windows | 1.26 | 386 |
While this project should work for other systems, no compatibility guarantees are made for those systems currently.
Getting Started
You can find a getting started guide on opentelemetry.io.
OpenTelemetry's goal is to provide a single set of APIs to capture distributed traces and metrics from your application and send them to an observability platform. This project allows you to do just that for applications written in Go. There are two steps to this process: instrument your application, and configure an exporter.
Instrumentation
To start capturing distributed traces and metric events from your application it first needs to be instrumented. The easiest way to do this is by using an instrumentation library for your code. Be sure to check out the officially supported instrumentation libraries.
If you need to extend the telemetry an instrumentation library provides or want to build your own instrumentation for your application directly you will need to use the Go otel package. The examples are a good way to see some practical uses of this process.
Export
Now that your application is instrumented to collect telemetry, it needs an export pipeline to send that telemetry to an observability platform.
All officially supported exporters for the OpenTelemetry project are contained in the exporters directory.
| Exporter | Logs | Metrics | Traces |
|---|---|---|---|
| OTLP | ✓ | ✓ | ✓ |
| Prometheus | ✓ | ||
| stdout | ✓ | ✓ | ✓ |
| Zipkin | ✓ |
Contributing
See the contributing documentation.