spring-cloud / spring-cloud/spring-cloud-netflix

Log health contributor status when overall eureka health status changed

Open
#4,135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
5k
Forks
2.5k
Avg merge
1d 2h
Merged PRs (30d)
10

Description

Is your feature request related to a problem? Please describe.
When 1 health contributor report it's DOWN, it will cause the overall eureka health status for that instance to be DOWN. If we look at the health actuator endpoint while the instance is DOWN, we can see which health contributor caused it to go down. However, if it recovered quickly, from logs we only know the instance changed from UP to DOWN, but we don't know which health contributor caused it unless there are logs or errors from that particular health contributor.

Describe the solution you'd like
We don't have to log the status of each health contributor for every health check, but if it caused a status change, it would be nice to log which one caused that change.

Describe alternatives you've considered
Make sure all health contributors log status changes, however, there are a lot of health contributors both from OSS in different projects, and internal ones, it's hard to make sure all health contributors have consistent logs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by locating the entry point that computes the overall Eureka health status and inspect how contributor results are available when that status changes. Done means a status transition identifies the health contributor responsible, without logging every contributor on every check.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.