-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[WIP][collector] Switch to OTEL's http/grpc server #6277
[WIP][collector] Switch to OTEL's http/grpc server #6277
Conversation
Signed-off-by: chahatsagarmain <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6277 +/- ##
==========================================
- Coverage 96.17% 96.05% -0.12%
==========================================
Files 357 357
Lines 20553 20473 -80
==========================================
- Hits 19766 19666 -100
- Misses 601 617 +16
- Partials 186 190 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
@yurishkuro how do i handle tenancy for GRPC after utilzing configgrpc ? |
Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
@yurishkuro the endpoint is being set correctly in test OTLP HTTP Endpoint: :0 OTLP GRPC Endpoint: :0 but the its throwing an error could not start OTLP receiver: could not start the OTLP receiver: listen: unknown network
|
Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few more comments
GRPC configgrpc.ServerConfig | ||
HTTP confighttp.ServerConfig | ||
}{ | ||
Enabled: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we setting Enabled
to true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's part of the main config and is exposed as a CLI flag today (on by default but can be disabled by the user). So I assume it does need to be set to true manually here if we're not initalizing this struct by other means.
Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: chahat sagar <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
…/jaeger into collector-tlscfg Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
Signed-off-by: chahatsagarmain <[email protected]>
// CORS allows CORS requests , sets the values for Allowed Headers and Allowed Origins. | ||
CORS corscfg.Options | ||
// KeepAlive configures allow Keep-Alive for Zipkin HTTP server | ||
confighttp.ServerConfig | ||
KeepAlive bool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is unused probably since migrating to Zipkin receiver.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! In the future let's try to go with smaller PRs. |
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test