Add warning log to validator client if primary node is unhealthy #6611
Labels
good first issue
Issues that are suitable for first-time contributors.
meta-feature-request
Issues to track feature requests.
scope-logging
Issue about logs: hygiene, format issues, improvements.
Problem description
Right now, the validator client is pretty silent about the primary node being unhealthy. We recently added metrics and dashboard panels to show the status of connected nodes (#6415) but we only log requests to fallback nodes to debug which many users do not look at.
Solution description
Add warning log to validator client if primary node is unhealthy as suggested by seamonkey.
We could use the same approach to flag the primary node as unhealthy if score is at 0. This would prevent false positives if just a single request fails which might happen due to other reasons.
Additional context
Related to #6415
The text was updated successfully, but these errors were encountered: