-
Notifications
You must be signed in to change notification settings - Fork 681
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
chore: log if metrics_endpoint but no feature flag #5279
Conversation
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.
Lgtm
Nice, now that @wileyj updated the test runner to use the |
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.
LGTM!
simple_neon_integration test seems to be broken and I think by this...it is complaining I think about a metrics response not existing as expected. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When calling
start_server_monitoring_metrics
, there is an inverse feature flag (not(features = "monitoring_prom")
) and log if you've setmetrics_endpoint
but don't have--feature monitoring_prom
. This is helpful in the case that you're trying to setup monitoring, and added the config field, but didn't add the feature flag.This log wasn't getting shown because
start_server_monitoring_metrics
was itself behind a feature flag, so the log never showed up. This PR changes this to always callstart_server_monitoring_metrics
- it's still a no-op (with just the log mentioned) if the feature flag isn't provided.