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

chore: log if metrics_endpoint but no feature flag #5279

Merged
merged 10 commits into from
Nov 14, 2024

Conversation

hstove
Copy link
Contributor

@hstove hstove commented Oct 5, 2024

When calling start_server_monitoring_metrics, there is an inverse feature flag (not(features = "monitoring_prom")) and log if you've set metrics_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 call start_server_monitoring_metrics - it's still a no-op (with just the log mentioned) if the feature flag isn't provided.

@hstove hstove requested a review from a team as a code owner October 5, 2024 18:59
@hstove hstove requested review from obycode and jferrant October 5, 2024 19:00
obycode
obycode previously approved these changes Oct 5, 2024
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@hstove
Copy link
Contributor Author

hstove commented Oct 5, 2024

Nice, now that @wileyj updated the test runner to use the monitoring_prom flag, we actually caught a failed assertion in a test. Seems small, I'll fix it in this PR.

@hstove hstove requested a review from a team as a code owner October 6, 2024 20:47
@hstove hstove requested a review from obycode October 6, 2024 20:47
kantai
kantai previously approved these changes Oct 7, 2024
jcnelson
jcnelson previously approved these changes Oct 7, 2024
obycode
obycode previously approved these changes Oct 7, 2024
@hstove hstove dismissed stale reviews from obycode and jcnelson via 576fd41 October 7, 2024 21:47
@hstove hstove requested review from obycode and kantai October 9, 2024 13:45
@hstove hstove mentioned this pull request Oct 9, 2024
obycode
obycode previously approved these changes Oct 17, 2024
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

jferrant
jferrant previously approved these changes Oct 21, 2024
@jferrant jferrant self-requested a review October 21, 2024 15:52
@jferrant
Copy link
Collaborator

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.

@hstove hstove dismissed stale reviews from jferrant and obycode via 404d0be October 22, 2024 17:40
@jferrant jferrant requested review from obycode and jcnelson November 8, 2024 21:44
@hstove hstove added this pull request to the merge queue Nov 14, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 14, 2024
@hstove hstove enabled auto-merge November 14, 2024 18:13
@hstove hstove added this pull request to the merge queue Nov 14, 2024
Merged via the queue into develop with commit bac1b07 Nov 14, 2024
1 check passed
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants