Skip to content

[ENH] Add load service to local dev tiltfile #4397

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

Merged
merged 1 commit into from
May 6, 2025

Conversation

jasonvigil
Copy link
Contributor

Description of changes

Make the trace exporter to export all INFO and above traces (not just ERROR).

Also, update load service tracing to use GRPC (to match our other services).

Test plan

Ran locally via tilt up. Verified traces appear under chroma-load service in jaeger.

Documentation Changes

n/a

Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

config.yaml: |
load_service:
service_name: "chroma-load"
otel_endpoint: "http://otel-collector.chroma:4317"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.chroma... It's always DNS 🙃

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

classic

.with_http()
.with_http_client(client)
let tracing_span_exporter = opentelemetry_otlp::SpanExporter::builder()
.with_tonic()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this was mis-configured to use HTTP instead of gRPC too? Is that what the with_tonic() also changes?

aside: I wish that this was somehow made our "default" Chroma setup so that it's consistent for all our rust code.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only chroma-load is not using our default otel setup. See tracing crate.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is because chroma-load was exporting to honeycomb directly. I'd love to see it unified.

Copy link
Contributor

@eculver eculver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to be careful with "log spew" given that the tracer is now set to INFO level -- I haven't audited the callsites, but it may be a thing we set dynamically.

@jasonvigil jasonvigil force-pushed the jason/add-load-service-to-tiltfile branch from abe253e to 978c418 Compare May 5, 2025 17:34
Make the trace exporter to export all INFO and above traces (not just ERROR).
@jasonvigil jasonvigil force-pushed the jason/add-load-service-to-tiltfile branch from 978c418 to 339db10 Compare May 6, 2025 02:05
@jasonvigil jasonvigil merged commit ec1f94c into main May 6, 2025
70 checks passed
@jasonvigil jasonvigil deleted the jason/add-load-service-to-tiltfile branch May 7, 2025 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants