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.

Sign up for GitHub

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

Jump to bottom

validator_name="Error: Usage information not found" #14

Open
dan-kazenoff-vcc opened this issue Jun 3, 2021 · 1 comment · May be fixed by #23
Open

validator_name="Error: Usage information not found" #14

dan-kazenoff-vcc opened this issue Jun 3, 2021 · 1 comment · May be fixed by #23

Comments

@dan-kazenoff-vcc
Copy link

Certain metrics output an error for the "validator_name" parameter. Examples:

system_usage{job="Helium_Validator", resource_type="CPU", validator_name="Error: Usage information not found for the given command RPC to '[email protected]' failed: {'EXIT', {{case_clause, {error, {no_matching_spec,["info","name"]}}}, [{blockchain_console,command,1, [{file,"blockchain_console.erl"}, {line,16}]}, {rpc,'-handle_call_call/6-fun-0-',5, [{file,"rpc.erl"},{line,197}]}]}}"}

system_usage{job="Helium_Validator", resource_type="Memory", validator_name="Exact ERTS version (10.7.1) match not found, instead using 10.7.1. The release may fail to run."}

Typically, the metric is duplicated and the last "system_usage" in the group correctly displays the validator_name, but the metrics above it display the error.

Other metrics where the same error pops up:
validator_block_age, validator_container_uptime, validator_version_info.

See attached image:

image
@tedder
Copy link
Owner

tedder commented Jun 14, 2021

Yeah, it doesn't handle errors well and it should. Waiting for the new API update unless you/someone wants to do some quick regex style validation on the validator name.

kujenga added a commit to kujenga/miner_exporter that referenced this issue Jun 25, 2021
@kujenga
abort metrics parsing on failed docker exec calls
3851121 
This commit eliminates cases where the commands might exit with
a non-zero code and have the follow-on logic parse stack traces
or other errors that could result in invalid metrics being published.

This should close tedder#14
@kujenga kujenga linked a pull request Jun 25, 2021 that will close this issue
Open
kujenga added a commit to kujenga/miner_exporter that referenced this issue Jul 8, 2021
@kujenga
abort metrics parsing on failed docker exec calls
cf0902d 
This commit eliminates cases where the commands might exit with
a non-zero code and have the follow-on logic parse stack traces
or other errors that could result in invalid metrics being published.

This should close tedder#14
kujenga added a commit to kujenga/miner_exporter that referenced this issue Jul 8, 2021
@kujenga
abort metrics parsing on failed docker exec calls
e116453 
This commit eliminates cases where the commands might exit with
a non-zero code and have the follow-on logic parse stack traces
or other errors that could result in invalid metrics being published.

This should close tedder#14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

abort metrics parsing on failed docker exec calls kujenga/miner_exporter
2 participants
@tedder @dan-kazenoff-vcc