8d9e11d19e
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [google.golang.org/grpc](https://redirect.github.com/grpc/grpc-go) | `v1.68.1` -> `v1.69.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>grpc/grpc-go (google.golang.org/grpc)</summary> ### [`v1.69.0`](https://redirect.github.com/grpc/grpc-go/releases/tag/v1.69.0): Release 1.69.0 [Compare Source](https://redirect.github.com/grpc/grpc-go/compare/v1.68.1...v1.69.0) ### Known Issues - The recently added `grpc.NewClient` function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. A fix is expected to be a part of grpc-go v1.70. ([#​7556](https://redirect.github.com/grpc/grpc-go/issues/7556)) ### New Features - stats/opentelemetry: Introduce new APIs to enable OpenTelemetry instrumentation for metrics on servers and clients ([#​7874](https://redirect.github.com/grpc/grpc-go/issues/7874)) - xdsclient: add support to fallback to lower priority servers when higher priority ones are down ([#​7701](https://redirect.github.com/grpc/grpc-go/issues/7701)) - dns: Add support for link local IPv6 addresses ([#​7889](https://redirect.github.com/grpc/grpc-go/issues/7889)) - The new experimental `pickfirst` LB policy (disabled by default) supports Happy Eyeballs, interleaving IPv4 and IPv6 address as described in [RFC-8305 section 4](https://www.rfc-editor.org/rfc/rfc8305#section-4), to attempt connections to multiple backends concurrently. The experimental `pickfirst` policy can be enabled by setting the environment variable `GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST` to `true`. ([#​7725](https://redirect.github.com/grpc/grpc-go/issues/7725), [#​7742](https://redirect.github.com/grpc/grpc-go/issues/7742)) - balancer/pickfirst: Emit metrics from the `pick_first` load balancing policy ([#​7839](https://redirect.github.com/grpc/grpc-go/issues/7839)) - grpc: export `MethodHandler`, which is the type of an already-exported field in `MethodDesc` ([#​7796](https://redirect.github.com/grpc/grpc-go/issues/7796)) - Special Thanks: [@​mohdjishin](https://redirect.github.com/mohdjishin) ### Bug Fixes - credentials/google: set scope for application default credentials ([#​7887](https://redirect.github.com/grpc/grpc-go/issues/7887)) - Special Thanks: [@​halvards](https://redirect.github.com/halvards) - xds: fix edge-case issues where some clients or servers would not initialize correctly or would not receive errors when resources are invalid or unavailable if another channel or server with the same target was already in use . ([#​7851](https://redirect.github.com/grpc/grpc-go/issues/7851), [#​7853](https://redirect.github.com/grpc/grpc-go/issues/7853)) - examples: fix the debugging example, which was broken by a recent change ([#​7833](https://redirect.github.com/grpc/grpc-go/issues/7833)) ### Behavior Changes - client: update retry attempt backoff to apply jitter per updates to [gRFC A6](https://redirect.github.com/grpc/proposal/blob/master/A6-client-retries.md). ([#​7869](https://redirect.github.com/grpc/grpc-go/issues/7869)) - Special Thanks: [@​isgj](https://redirect.github.com/isgj) - balancer/weightedroundrobin: use the `pick_first` LB policy to manage connections ([#​7826](https://redirect.github.com/grpc/grpc-go/issues/7826)) ### API Changes - balancer: An internal method is added to the `balancer.SubConn` interface to force implementors to embed a delegate implementation. This requirement is present in the interface documentation, but wasn't enforced earlier. ([#​7840](https://redirect.github.com/grpc/grpc-go/issues/7840)) ### Performance Improvements - mem: implement a `ReadAll()` method for more efficient `io.Reader` consumption ([#​7653](https://redirect.github.com/grpc/grpc-go/issues/7653)) - Special Thanks: [@​ash2k](https://redirect.github.com/ash2k) - mem: use slice capacity instead of length to determine whether to pool buffers or directly allocate them ([#​7702](https://redirect.github.com/grpc/grpc-go/issues/7702)) - Special Thanks: [@​PapaCharlie](https://redirect.github.com/PapaCharlie) ### Documentation - examples/csm_observability: Add xDS Credentials and switch server to be xDS enabled ([#​7875](https://redirect.github.com/grpc/grpc-go/issues/7875)) </details> --- ### Configuration 📅 **Schedule**: 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 is behind base branch, 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:eyJjcmVhdGVkSW5WZXIiOiIzOS41OC4xIiwidXBkYXRlZEluVmVyIjoiMzkuNTguMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiU2tpcCBDaGFuZ2Vsb2ciLCJkZXBlbmRlbmNpZXMiXX0=--> 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 | Beta1 |
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.23 | amd64 |
| Ubuntu | 1.22 | amd64 |
| Ubuntu | 1.23 | 386 |
| Ubuntu | 1.22 | 386 |
| Linux | 1.23 | arm64 |
| Linux | 1.22 | arm64 |
| macOS 13 | 1.23 | amd64 |
| macOS 13 | 1.22 | amd64 |
| macOS | 1.23 | arm64 |
| macOS | 1.22 | arm64 |
| Windows | 1.23 | amd64 |
| Windows | 1.22 | amd64 |
| Windows | 1.23 | 386 |
| Windows | 1.22 | 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.