Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
cmd/geth: actually enable metrics when passed via toml #30781
cmd/geth: actually enable metrics when passed via toml #30781
Changes from all commits
83b532c
f6971a7
1635da8
4abf2e5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Looks flaky...?
Let's assume
metrics
is enabled in toml config. Won't these two behave differently:geth --metrics=false --conf=conf.toml
will correctly setEnabled=false
.geth --conf=conf.toml --metrics=false
will incorrectly setEnabled=true
.?
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.
So in this case, the order of precedence is always flags first, config second. However, the way
init()
is written inmetrics/metrics.go
,Enabled
is always set to true in case either a flag or config specifies it should be. This is also how it was previously.So for both 1) and 2) Enabled will be set to
true
, but we will not actually serve the metrics because that occurs later in the geth command start up. That is where the precedence comes in.How would you prefer to deal with this? I could change the parsing in
init()
so that when the flag metrics is set, it always uses that value, regardless of config value. Otherwise could detect a mismatch (enabled in config, disabled explicitly by flag) during client startup and fail there instead.Otherwise, we can leave as-is. Explicitly setting
--metrics=false
while actually passing a config with metrics enabled is pretty unlikely and we will not serve the metrics as expected. It will just cause geth to record the metrics internally.I think my pref is to just fail when metrics are enabled in config, but explicitly disabled by the flag. It is simple to deal with:
What do you think?