Enable GRPC logs for telemetry process in telemetry docker #20889
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
qiluo-msft
approved these changes
Nov 22, 2024
ganglyu
approved these changes
Nov 22, 2024
|
@zbud-msft Is this change required for 202405? Please add ADO number if it's required. |
|
@bingwang-ms Can we backport to 202405? I have added ADO number |
VladimirKuk
pushed a commit
to Marvell-switching/sonic-buildimage
that referenced
this pull request
Jan 21, 2025
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.
Why I did it
Work item tracking
How I did it
Added GRPC_GO_LOG flag to enable grpc logging for telemetry process in telemetry docker. Follow up of #20798.
How to verify it
Tested by adding these flags to telemetry.sh inside telemetry docker and sending request from client
Nov 21 23:27:53.652438 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:27:53 grpc: Server.Serve failed to complete security handshake from "X:39702": remote error: tls: bad certificate
Nov 21 23:27:54.834302 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:27:54 grpc: Server.Serve failed to complete security handshake from "X:39706": remote error: tls: bad certificate
Nov 21 23:27:56.806615 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:27:56 grpc: Server.Serve failed to complete security handshake from "X:48010": remote error: tls: bad certificate
Nov 21 23:27:59.296430 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:27:59 grpc: Server.Serve failed to complete security handshake from "X:48026": remote error: tls: bad certificate
Nov 21 23:28:04.104834 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:28:04 grpc: Server.Serve failed to complete security handshake from "X:48036": remote error: tls: bad certificate
Nov 21 23:28:10.553530 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:28:10 grpc: Server.Serve failed to complete security handshake from "X:55256": remote error: tls: bad certificate
Nov 21 23:28:21.792336 Z INFO telemetry#supervisord: telemetry WARNING: 2024/11/21 23:28:21 grpc: Server.Serve failed to complete security handshake from "X:33336": remote error: tls: bad certificate
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)