-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Setup OpenTelemetry exporters when initializing prefect #15946
Conversation
CodSpeed Performance ReportMerging #15946 will not alter performanceComparing Summary
|
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.
Great tests! I'm thinking we need to move some of the imports conditionally into functions?
Yeah, I'm working on something like that, having a |
Co-authored-by: Chris Guidry <chris.g@prefect.io>
9c10a12
to
2674b32
Compare
if server_type != ServerType.CLOUD: | ||
return None, None, None | ||
|
||
assert settings.api.key |
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.
If you need an API key for this to work, can we raise a friendly error when the API key is missing?
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.
Yeah, I have a ticket to come through and make this a more friendly thing in general: https://linear.app/prefect/issue/CLOUD-675/make-telemetry-failures-more-friendly
Co-authored-by: Alexander Streed <desertaxle@users.noreply.github.com>
This PR adds OpenTelemetry support to Prefect Cloud by setting up exporters for traces, metrics, and logs during initialization when enabled.
Key changes: