-
Notifications
You must be signed in to change notification settings - Fork 13
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
How to view a trace for a script or test that does not include Django? #86
Comments
@zyd14 this is a great point – at the moment the best way to view a non-django/non-web trace is probably via the Kolo VSCode extension: https://docs.kolo.app/en/latest/howto/vscode.html We've thought about the non-webserver use case a tiny bit in the past and have two ideas for the future:
Don't want to promise anything on when either of these will be available, but we'll likely have the second one ready before the first :) |
@wilhelmklopp Thanks for the quick response! I was able to use the VSCode extension working for now. Appreciate the insight into future possibilities. A followup question - is it possible to run kolo programmatically? I'd assume so since you have the middleware setup for Django. My specific use case is that I would like to get traces from another python tool (Dagster) which is run from the command-line like Thanks again for the cool library! I'll be keeping my eye on it for sure! |
Does dagster provide a |
Hi there,
This library looks awesome, but I'd like to apply it to some non-webserver use-cases (primarily data pipelines, but probably some web servers in the future as well). Is there a way to visualize a trace generated for a script or test that doesn't include Django? The docs here describe how to enable tracing of a script or test, but do not describe how you might be able to then visualize the trace. Any guidance would be greatly appreciated, the library looks like it could help solve a lot of observability issues.
The text was updated successfully, but these errors were encountered: