This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [google.golang.org/grpc](https://redirect.github.com/grpc/grpc-go) |
`v1.70.0` -> `v1.71.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.71.0`](https://redirect.github.com/grpc/grpc-go/releases/tag/v1.71.0):
Release 1.71.0
[Compare
Source](https://redirect.github.com/grpc/grpc-go/compare/v1.70.0...v1.71.0)
### API Changes
- balancer: Custom LB policies that record metrics must use the new
`MetricsRecorder` method on `Balancer.ClientConn` instead of the removed
`Balancer.BuildOptions.MetricsRecorder` field to obtain a metrics
recorder.
([#​8027](https://redirect.github.com/grpc/grpc-go/issues/8027))
- balancer: `balancer.ClientConn` implementations must now embed a
delegate implementation. This allows grpc-go to add new methods to the
interface and remain backward compatible.
([#​8026](https://redirect.github.com/grpc/grpc-go/issues/8026))
- balancer/endpointsharding: The constructor accepts the child
balancer's builder and a struct with optional configuration.
([#​8052](https://redirect.github.com/grpc/grpc-go/issues/8052))
### New Features
- xds: Add support for dualstack via the
[additional_addresses](df394a41c8/api/envoy/config/endpoint/v3/endpoint_components.proto (L91-L96)
)
field in the Endpoint resource. To disable this feature, set the
environment variable `GRPC_EXPERIMENTAL_XDS_DUALSTACK_ENDPOINTS=false`.
([#​8134](https://redirect.github.com/grpc/grpc-go/issues/8134))
- stats/opentelemetry: Add experimental support for OpenTelemetry
tracing.
([#​7852](https://redirect.github.com/grpc/grpc-go/issues/7852))
- xds/internal/xdsclient: Add counter metrics for valid and invalid
resource updates.
([#​8038](https://redirect.github.com/grpc/grpc-go/issues/8038))
- balancer/leastrequest, roundrobin: Add dualstack support.
([#​7969](https://redirect.github.com/grpc/grpc-go/issues/7969),
[#​7966](https://redirect.github.com/grpc/grpc-go/issues/7966))
- balancer/endpointsharding: Balancers created with the new
`DisableAutoReconnect` option will not attempt to call `ExitIdle`
automatically on their children when the children report idle.
([#​8052](https://redirect.github.com/grpc/grpc-go/issues/8052))
### Bug Fixes
- client: Fix support for proxies when using `grpc.NewClient` so the
target is resolved by the proxy as expected.
([#​7881](https://redirect.github.com/grpc/grpc-go/issues/7881))
- Added `WithLocalDNSResolution()` dial option to explicitly force
target resolution on the client instead.
([#​7881](https://redirect.github.com/grpc/grpc-go/issues/7881))
- weightedtarget: Return erroring picker when no targets are configured.
([#​8070](https://redirect.github.com/grpc/grpc-go/issues/8070))
- xds: Fail RPCs with `UNAVAILABLE` when the EDS resource is missing or
contains no endpoints
([#​8070](https://redirect.github.com/grpc/grpc-go/issues/8070))
- xdsclient: Fix a bug where connectivity failures were reported to
resource watchers before trying all listed servers.
([#​8075](https://redirect.github.com/grpc/grpc-go/issues/8075))
- grpc: Fix the number of bytes reported in the error message when
encoded messages are larger than 4GB.
([#​8033](https://redirect.github.com/grpc/grpc-go/issues/8033))
- rls: Fix a bug where RLS channel updates could be lost during startup.
([#​8055](https://redirect.github.com/grpc/grpc-go/issues/8055))
- xds: Fixed a bug preventing tests from creating multiple servers or
channels with different bootstrap configs.
([#​8050](https://redirect.github.com/grpc/grpc-go/issues/8050))
- grpc: Fix message length checks when compression is enabled and
`maxReceiveMessageSize` is `MaxInt`
([#​7918](https://redirect.github.com/grpc/grpc-go/issues/7918))
- Special Thanks:
[@​vinothkumarr227](https://redirect.github.com/vinothkumarr227)
### Documentation
- client: Improve documentation of `grpc.NewClient` and
`ClientConn.CanonicalTarget` by providing examples.
([#​8078](https://redirect.github.com/grpc/grpc-go/issues/8078))
- examples/features/dualstack: New example demonstrating usage of
endpoints and dualstack functionality.
([#​8098](https://redirect.github.com/grpc/grpc-go/issues/8098))
</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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xODUuNCIsInVwZGF0ZWRJblZlciI6IjM5LjE4NS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: dmathieu <42@dmathieu.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.24 | amd64 |
Ubuntu | 1.23 | amd64 |
Ubuntu | 1.22 | amd64 |
Ubuntu | 1.24 | 386 |
Ubuntu | 1.23 | 386 |
Ubuntu | 1.22 | 386 |
Ubuntu | 1.24 | arm64 |
Ubuntu | 1.23 | arm64 |
Ubuntu | 1.22 | arm64 |
macOS 13 | 1.24 | amd64 |
macOS 13 | 1.23 | amd64 |
macOS 13 | 1.22 | amd64 |
macOS | 1.24 | arm64 |
macOS | 1.23 | arm64 |
macOS | 1.22 | arm64 |
Windows | 1.24 | amd64 |
Windows | 1.23 | amd64 |
Windows | 1.22 | amd64 |
Windows | 1.24 | 386 |
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.