|
1 | 1 | # Use this changelog template to create an entry for release notes. |
2 | 2 |
|
3 | 3 | # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' |
4 | | -change_type: enhancement |
| 4 | +change_type: bug_fix |
5 | 5 |
|
6 | 6 | # The name of the component, or a single word describing the area of concern, (e.g. receiver/otlp) |
7 | | -component: pkg/config/configgrpc |
| 7 | +component: pkg/otelcol |
8 | 8 |
|
9 | 9 | # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). |
10 | | -note: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution |
| 10 | +note: Stop emitting verbose gRPC transport messages at WARN during normal client disconnect. |
11 | 11 |
|
12 | 12 | # One or more tracking issues or pull requests related to the change |
13 | | -issues: [14990] |
| 13 | +issues: [5169] |
14 | 14 |
|
15 | 15 | # (Optional) One or more lines of additional information to render under the primary note. |
16 | 16 | # These lines will be padded with 2 spaces and then inserted directly into the document. |
17 | 17 | # Use pipe (|) for multiline entries. |
18 | 18 | subtext: | |
19 | | - After the migration to grpc.NewClient, some gRPC client components such as the OTLP |
20 | | - exporter experienced connection issues in dual-stack DNS environments. This can now be |
21 | | - fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field. |
| 19 | + grpc-go gates chatty per-RPC notices (e.g. "HandleStreams failed to read frame: |
| 20 | + connection reset by peer") behind `LoggerV2.V(2)`. zapgrpc.Logger.V conflates |
| 21 | + grpclog verbosity with zap severity, so V(2) returns true whenever WARN is |
| 22 | + enabled and these messages emit at WARN. Wrap the installed grpclog.LoggerV2 |
| 23 | + with a corrected V() that compares against a fixed verbosity threshold, |
| 24 | + matching grpclog's intended semantics. See uber-go/zap#1544. |
22 | 25 |
|
23 | 26 | # Optional: The change log or logs in which this entry should be included. |
24 | 27 | # e.g. '[user]' or '[user, api]' |
25 | 28 | # Include 'user' if the change is relevant to end users. |
26 | 29 | # Include 'api' if there is a change to a library API. |
27 | 30 | # Default: '[user]' |
28 | | -change_logs: [user, api] |
| 31 | +change_logs: [user] |
0 commit comments