-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[CLN] Use GRPC for chroma-load OTEL #4427
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
Conversation
Also, remove sampling. Will leverage refinery for this instead.
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
.with_config(trace_config) | ||
.build(); | ||
let tracer = tracer_provider.tracer(service_name.clone()); | ||
// TODO(MrCroxx): Should we the tracer provider as global? | ||
// global::set_tracer_provider(tracer_provider); | ||
|
||
// Prepare meter. |
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.
Refinery doesn't support metrics and Honeycomb doesn't support tonic. This was setup the way it is to get metrics into honeycomb. Metrics, not traces.
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.
We can use otel-collector as the same endpoint for both metrics and traces. This simplifies our config and setup complexity (from chroma service standpoint, at least)
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.
Talked offline. Will send to otel-collector, not refinery. This might work.
## Description of changes Remove sampling. Will leverage refinery for this instead. ## Test plan These changes are untested. However, it is now using (mostly) the same setup code as the other chroma services (which are working). So, we can test in staging after this is merged.
Description of changes
Remove sampling. Will leverage refinery for this instead.
Test plan
These changes are untested. However, it is now using (mostly) the same setup code as the other chroma services (which are working). So, we can test in staging after this is merged.