We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Geth version: 1.13.2-stable CL client & version: prysm v4.0.8 OS & Version: Linux Commit hash :
Options specified in config should enable metrics collection.
[Metrics] Enabled = true EnabledExpensive = true
These options are ignored. Metrics server starts on 6060 port, but metrics are all zeroes, unless --metrics CLI arg is specified.
--metric
Add this lines to config.toml
[Metrics] Enabled = true EnabledExpensive = true HTTP = "0.0.0.0" Port = 6060
Start geth with flags --pprof --pprof.port=6060 --pprof.addr=0.0.0.0
--pprof --pprof.port=6060 --pprof.addr=0.0.0.0
Go to /debug/metrics/prometheus endpoint and all metrics will be zeroes.
/debug/metrics/prometheus
[backtrace]
The text was updated successfully, but these errors were encountered:
Yes, this is a known issue. See for example #24178
Sorry, something went wrong.
I'll investigate the issue.
Successfully merging a pull request may close this issue.
System information
Geth version: 1.13.2-stable
CL client & version: prysm v4.0.8
OS & Version: Linux
Commit hash :
Expected behaviour
Options specified in config should enable metrics collection.
Actual behaviour
These options are ignored. Metrics server starts on 6060 port, but metrics are all zeroes, unless
--metric
s CLI arg is specified.Steps to reproduce the behaviour
Add this lines to config.toml
Start geth with flags
--pprof --pprof.port=6060 --pprof.addr=0.0.0.0
Go to
/debug/metrics/prometheus
endpoint and all metrics will be zeroes.Backtrace
The text was updated successfully, but these errors were encountered: