Feature: Endpoint detection strategy should be retried
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- java, spring-boot
- Área
- backend
Línea de trabajo
Start by reading QueryIndexEndpointStrategy and ProbeEndpointsStrategy, which are named in the issue, and trace where SBA switches between them. Identify how endpoint detection failures are handled and where retry configuration belongs. Done means configurable retries occur before fallback to probing; add or update tests for that behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hello.
I'm using the latest 4.1.4 version of SBA and I can observe the following behaviour:
2026-10-10T13:44:03.067+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.QueryIndexEndpointStrategy : Querying actuator-index for instance b8b651c9a040 on 'http://foo:8090/actuator' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.086+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/dump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.086+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/health' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/env' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/trace' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/auditevents' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/mappings' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.087+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/info' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/jolokia' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/metrics' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/threaddump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/httptrace' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/conditions' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.088+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/logfile' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/configprops' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/integrationgraph' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/startup' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.089+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/refresh' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/loggers' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/quartz' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/heapdump' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.090+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/shutdown' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/httpexchanges' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/beans' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.091+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/liquibase' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/flyway' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/caches' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/sessions' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.092+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/scheduledtasks' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.093+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/sbom' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
2026-10-10T13:44:03.093+02:00 WARN 1 --- [Timekeepers Monitoring] [or-http-epoll-3] d.c.b.a.s.s.e.ProbeEndpointsStrategy : Endpoint probe for instance b8b651c9a040 on endpoint 'http://foo:8090/actuator/prometheus' failed: finishConnect(..) failed with error(-111): Connection refused: foo/ip:8090
Basically, if the QueryIndexEndpointStrategy fails, SBA switches automatically to ProbeEndpointsStrategy and starts to flood with requests.
While the behaviour is understandable, it would be nice to have some configurable retries in place before falling back to the ProbeEndpointsStrategy.
- Lenguaje dominante
- Java
- Estrellas
- 12.9k
- Forks
- 3.2k
- Merge medio
- 1 d 35 min
- PR fusionados (30 d)
- 93
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de codecentric/spring-boot-admin
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
codecentric/spring-boot-admin#5812 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
codecentric/spring-boot-admin#5743 ·
Los mantenedores suelen responder en 1 día
-
Bug: Multiple notifications from multiple instancesPosiblemente ocupada @YadavKshitiz la tomó hace 22 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
codecentric/spring-boot-admin#5716 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Bug: Composite health contributors' details are not shownQuizá libre de nuevo @cdprete la tomó hace 31 días y no hay ningún pull request abierto. Abiertotype: enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
codecentric/spring-boot-admin#5534 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Feature: Make browser notifications customizable & navigableQuizá libre de nuevo @abhiramaab la tomó hace 80 días y no hay ningún pull request abierto. Abiertotype: enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
codecentric/spring-boot-admin#5504 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de codecentric/spring-boot-admin
Issues similares
-
Optimize consumer version heatmap aggregation to avoid repeated scansPosiblemente ocupada @praykaria31 la tomó hoy. Abiertotype/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Apicurio/apicurio-registry#10662 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
a:false-positive
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
status: waiting-for-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
spring-projects/spring-boot#52347 ·
Los mantenedores suelen responder en 2 días
-
bug untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
opensearch-project/opensearch-migrations#3480 ·
Los mantenedores suelen responder en 2 días
-
enhancement feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
rsp777/service-pulse-app#28 ·