lidofinance / lidofinance/validator-ejector
Metric for exit messages left (number/percentage) shows the wrong value
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 19
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 7
Description
We have observed that following metrics:
# HELP validator_ejector_exit_messages_left_number Number of exit messages left
# TYPE validator_ejector_exit_messages_left_number gauge
validator_ejector_exit_messages_left_number{app="validator-ejector"} 0
# HELP validator_ejector_exit_messages_left_percent Percentage of exit messages left
# TYPE validator_ejector_exit_messages_left_percent gauge
validator_ejector_exit_messages_left_percent{app="validator-ejector"} 0
show that the validator ejector has 0 exit messages left, but it is clearly processing the messages:
2025-07-18 11:48:53 info: Loading messages from '/ethereum/lido/withdrawal-automation' folder
2025-07-18 11:48:53 info: Parsing loaded messages
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
2025-07-18 11:48:55 info: File already loaded
All of this started to appear after we updated validator ejector from 1.7.0 to 1.8.0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the exit-message metric calculation between validator-ejector 1.7.0 and 1.8.0, using the reported metrics and processing logs as the reproduction. Trace where the number and percentage are produced; done means both metrics reflect messages still being processed rather than reporting zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100