Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Retry for endpoint detection

Open
#1,939 3 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading ProbeEndpointsStrategy and tracing the endpoint detection failure path. Implement a retry available only after an error, without periodic detection or a UI button; done means a failed detection can be triggered again without restarting the instance.

Written by the indexing model from the issue text.

Description

type: enhancement

When endpoint detection fails (e.g. due to network issues), then SBA will not know about the endpoints of that instance and there is no option to trigger the detection again. The current solution would be restarting the instance.

Endpoints should not change while the application is running, so we do not need a periodic trigger or a button in the ui. Only in error case there should be a retry. See ProbeEndpointsStrategy.

Dominant language
Java
Stars
12.9k
Forks
3.2k
Avg merge
15h 10m
Merged PRs (30d)
86

Getting set up

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.

More from codecentric/spring-boot-admin

All issues in codecentric/spring-boot-admin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.