-
Notifications
You must be signed in to change notification settings - Fork 5
feat: add OpenTelemetry + X-Ray tracing #81
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
|
📚 Documentation preview will be available at: https://developmentseed.github.io/titiler-cmr/pr-previews/pr-81/ Status: ✅ Preview is ready! |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
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.
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.
This is really great! I'm super impressed by the Docker solution you put together here, since it also gets around one of the slowest parts of our lambda deployments.
Yeah, I need to clean up the logging configuration so that we get all of the logs in local deployments. My initial idea to move everything to handler.py basically eliminated local ogs. Thanks for the suggestion! |
I applied the same approach as we did in titiler-multidim (developmentseed/titiler-multidim#103) and it is looking good - the traces/spans are all available in X-Ray and the logging statements are correlated which will make it possible to track performance of specific datasets, features, query patterns.
Here is a preview of an X-Ray trace with the correlated logs at the bottom:
