-
Notifications
You must be signed in to change notification settings - Fork 8
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
DataDog support for Worker and Scheduler #1712
base: develop
Are you sure you want to change the base?
Conversation
➡️ Preview environment created: Click Me! |
❌ E2E tests failed |
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.
@aweiland I have a few cosmetic suggestions, but I tested and it looks like this works 👍
logger.setLevel(logging.INFO) | ||
logger.addHandler(logging.StreamHandler()) | ||
logger.info("Enabling Datadog") | ||
# import ddtrace.auto # noqa |
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.
# import ddtrace.auto # noqa |
# network={"client": {"ip": real_host, "port": client_port}}, | ||
# duration=process_time, | ||
# ) | ||
# response.headers["X-Process-Time"] = str(process_time / 10 ** 9) |
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.
Should we be putting this back in?
# response.headers["X-Process-Time"] = str(process_time / 10 ** 9) | |
response.headers["X-Process-Time"] = str(process_time / 10 ** 9) |
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.
I debated whether it's worth sending back to the client or not. We have this information in Datadog so it didn't seem useful to me.
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.
In that case, we can remove the comment
Co-authored-by: Kenroy Gobourne <[email protected]>
Co-authored-by: Kenroy Gobourne <[email protected]>
Co-authored-by: Kenroy Gobourne <[email protected]>
Co-authored-by: Kenroy Gobourne <[email protected]>
…logger-backend-refactor into broker-structlog
📝 Description
🔗 Jira Ticket M2-8041
Changes include:
🪤 Peer Testing
✏️ Notes