-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[CHORE] enable tracing for our crates #2993
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
@@ -39,7 +39,8 @@ pub(crate) fn init_otel_tracing(service_name: &String, otel_endpoint: &String) { | |||
.with_filter(tracing_subscriber::filter::LevelFilter::INFO); | |||
// global filter layer. Don't filter anything at global layer for this crate. And disable |
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.
nit: change the comment here as it is not in sync with the code below
2d5e187
to
27c9f5c
Compare
27c9f5c
to
af30d87
Compare
let global_layer = EnvFilter::new( | ||
"error,".to_string() | ||
+ &vec![ | ||
"chroma", |
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.
everytime we add a crate, will we have to add it here?
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.
If we want it to be something other than error, yes. There's no real good way to select by crate and then not have to select by crate.
Description of changes
worker
crate. Enable it for all our crates at trace level and info level for non-chroma crates.Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?