-
Notifications
You must be signed in to change notification settings - Fork 710
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
Is it possible to save traces locally? #164
Comments
Yup. Something like this should work:
and register it as an additional processor:
|
Made a SDK in GO, you could check it out. Allows you to run everything locally. |
Added a pull request #192 for the missing TracingProcessor export. That was necessary for me to make the above example work for me. Also a little improvement to not throw an error for the missing output dir in case you did not add one like me:
|
# Summary This adds the missing TracingProcessor export to __init__.py. # Behavior When trying to add a custom tracing processor, the TracingProcessor importing fails with not found error when trying the example usage proposed in issue #164 Specifically this line throws the error: `add_trace_processor(MyTracingProcessor("output"))` # Expected Behavior Inspecting the init file, simply the import/export was missing. Adding these made the example code work for me # Test plan Local dev of example code in #164 # Issue number #164 # Checks None
Describe the feature
Would like to save traces locally for debugging, especially when using custom models. Is it possible to save traces to file(s) locally?
The text was updated successfully, but these errors were encountered: