-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
otlpreceiver
is not throwing a valid gRPC
Status
for successful scenarios or authentication-related errors
#7646
Labels
bug
Something isn't working
Comments
shalithakaru
changed the title
May 9, 2023
otlpreceiver
OTLP receiver is not throwing a valid grpc-status
for authentication-related errors or in successful scenariootlpreceiver
is not throwing a valid grpc-status
for authentication-related errors or in successful scenario
shalithakaru
changed the title
May 9, 2023
otlpreceiver
is not throwing a valid grpc-status
for authentication-related errors or in successful scenariootlpreceiver
is not throwing a valid grpc-status
for successful scenarios or authentication-related errors.
shalithakaru
changed the title
May 9, 2023
otlpreceiver
is not throwing a valid grpc-status
for successful scenarios or authentication-related errors.otlpreceiver
is not throwing a valid gRPC
Status
for successful scenarios or authentication-related errors
jpkrohling
added a commit
to jpkrohling/opentelemetry-collector
that referenced
this issue
Jul 19, 2024
Fixes open-telemetry#7646 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
This was referenced Jul 19, 2024
mx-psi
pushed a commit
that referenced
this issue
Jul 24, 2024
Fixes #7646 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
OTLP receiver is not throwing a valid
gRPC
Status
for successful scenarios or authentication-related errors.Steps to reproduce
(Please note you need this extension to enable authentication with the receiver)
OTLP/HTTP is 4318
OTLP/gRPC is 4317
What did you expect to see?
gRPC Status:16
for unauthenticated requests andgRPC Status:0
for successful authentication.What did you see instead?
HTTP will throw proper status codes like
401(Unauthorized)
for errors and200
for successful authentication.But with gRPC, it will throw
gRPC Status:2
for errors and nothing for successful authentication.What version did you use?
Version: v0.76.1
What config did you use?
Config: N/A
Environment
N/A
Additional context
Temporary fix for error scenarios
to
Suggestion: I think it's better if we can fix interceptors in
configgrpc
similar toconfighttp
interceptorI was not able to find a any solution for the successful scenario
The text was updated successfully, but these errors were encountered: