Skip to content
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

Switch from env_logger crate to tracing for more in-depth observability info #96

Open
emanguy opened this issue Aug 26, 2024 · 5 comments
Assignees

Comments

@emanguy
Copy link
Collaborator

emanguy commented Aug 26, 2024

We're currently using env_logger for basic logging in the backend, but to really help us troubleshoot stuff in production we should migrate to the tracing crate. This has essentially the same API for basic logging, but it also enables us to use tracing spans and export trace data to external services such as Google Cloud Trace or AWS Distro. Doing this will help us troubleshoot problems in the backend and help identify performance issues.

@emanguy emanguy converted this from a draft issue Aug 26, 2024
@emanguy emanguy self-assigned this Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

4 participants
@emanguy and others