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.
We have observed that following metrics:
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 loadedAll of this started to appear after we updated validator ejector from 1.7.0 to 1.8.0.