-
Notifications
You must be signed in to change notification settings - Fork 276
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
remove telemetry configuration hot reloading #1463
Conversation
Configuration hot reloading is not very useful for telemetry, and is the source of regular bugs that are hard to fix. This removes the support for configuration reloading entirely. Now, the router will reject a configuration reload with an error log if the telemetry configuration changed. A temporary tracing subscriber is created when the router is started, and is used until a subscriber can be created from the configuration and set as global subscriber. That global subscriber will then be used for all the requests and will not change for the entire life of the process.
This comment has been minimized.
This comment has been minimized.
When using the router as a library (example: in integration tests), we might want to use another tracing subscriber than the one created by default in the telemetry plugin. This adds a method to the telemetry plugin to directly provide a subscriber. It will then be modified to use layers for the telemetry exporters and spaceport, so it won't be possible to deactivate studio reportingt that way
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.
Please also remove this comment paragraph in router.rs
This must only be called in the context of Executable::builder() because it relies on custom logging setup to support hot reload.
Looks like |
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.
One big concern about the telemetry unpinning.
The rest looks good to me
Fix #1224
Configuration hot reloading is not very useful for telemetry, and is the
source of regular bugs that are hard to fix.
This removes the support for configuration reloading entirely. Now, the
router will reject a configuration reload with an error log if the
telemetry configuration changed.
A temporary tracing subscriber is created when the router is started, and
is used until a subscriber can be created from the configuration and set
as global subscriber. That global subscriber will then be used for all
the requests and will not change for the entire life of the process.