我正在将我们的Spring Boot Admin从1.5.7升级到2.1.6。我们使用Eureka，并且所有服务都在此注册，因此我们想从中获取注册表信息。升级之前一切正常。但是升级后，它无法获取有关注册服务的任何信息。 Spring Boot Admin本身可以在eureka中成功注册自己，但是由于某些原因，它甚至不尝试获取已注册的应用程序。问题可能出在我们的基础架构设置中，因为它非常复杂。但是在这一点上，我至少想了解究竟是什么阻止了它获取此信息。我无法在日志中找到任何东西来指示类似的错误，即使在调试中也是如此。
2020-02-12 12:08:46,008 INFO [main] c.n.d.s.r.a.ConfigClusterResolver: Resolving eureka endpoints via DNS: txt.{tested and working dns record}
2020-02-12 12:08:46,395 INFO [main] c.n.d.DiscoveryClient: Disable delta property : false
2020-02-12 12:08:46,398 INFO [main] c.n.d.DiscoveryClient: Single vip registry refresh property : null
2020-02-12 12:08:46,398 INFO [main] c.n.d.DiscoveryClient: Force full registry fetch : false
2020-02-12 12:08:46,398 INFO [main] c.n.d.DiscoveryClient: Application is null : false
2020-02-12 12:08:46,399 INFO [main] c.n.d.DiscoveryClient: Registered Applications size is zero : true
2020-02-12 12:08:46,399 INFO [main] c.n.d.DiscoveryClient: Application version is -1: true
2020-02-12 12:08:46,399 INFO [main] c.n.d.DiscoveryClient: Getting all instance registry info from the eureka server
2020-02-12 12:08:46,925 INFO [main] c.n.d.DiscoveryClient: The response status is 200
2020-02-12 12:08:46,937 INFO [main] c.n.d.DiscoveryClient: Starting heartbeat executor: renew interval is: 30
2020-02-12 12:08:46,960 INFO [main] c.n.d.InstanceInfoReplicator: InstanceInfoReplicator onDemand update allowed rate per min is 4
2020-02-12 12:08:46,968 INFO [main] c.n.d.DiscoveryClient: Discovery Client initialized at timestamp 1581509326968 with initial instances count: 44
2020-02-12 12:08:46,982 INFO [main] o.s.c.n.e.s.EurekaServiceRegistry: Registering application SPRING-BOOT-ADMIN with eureka with status UP
2020-02-12 12:08:46,989 INFO [main] c.n.d.DiscoveryClient: Saw local status change event StatusChangeEvent [timestamp=1581509326989, current=UP, previous=STARTING]
2020-02-12 12:08:46,991 WARN [main] c.n.d.InstanceInfoReplicator: Ignoring onDemand update due to rate limiter
2020-02-12 12:08:47,025 INFO [DiscoveryClient-InstanceInfoReplicator-0] c.n.d.DiscoveryClient: DiscoveryClient_SPRING-BOOT-ADMIN/i-0ecf2b8785baa7372: registering service...
2020-02-12 12:08:47,137 INFO [main] o.e.j.s.h.C.application: Initializing Spring DispatcherServlet 'dispatcherServlet'
2020-02-12 12:08:47,138 INFO [main] o.s.w.s.DispatcherServlet: Initializing Servlet 'dispatcherServlet'
2020-02-12 12:08:47,198 INFO [main] o.s.w.s.DispatcherServlet: Completed initialization in 56 ms
2020-02-12 12:08:47,308 INFO [DiscoveryClient-InstanceInfoReplicator-0] c.n.d.DiscoveryClient: DiscoveryClient_SPRING-BOOT-ADMIN/i-0ecf2b8785baa7372 - registration status: 204
2020-02-12 12:08:47,370 INFO [main] o.e.j.s.AbstractConnector: Started ServerConnector@6ba4d28b{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2020-02-12 12:08:47,375 INFO [main] o.s.b.w.e.j.JettyWebServer: Jetty started on port(s) 8080 (http/1.1) with context path ''
2020-02-12 12:08:47,379 INFO [main] o.s.c.n.e.s.EurekaAutoServiceRegistration: Updating port to 8080
2020-02-12 12:08:47,388 INFO [main] com.tr.ServerRunner: Started ServerRunner in 38.79 seconds (JVM running for 83.591)
引起我注意的唯一一行是
2020-02-12 12:08:46,991 WARN [main] c.n.d.InstanceInfoReplicator: Ignoring onDemand update due to rate limiter
但实际上，这并不是一个问题。
我们的配置：
management.endpoints.web.exposure.include=*
management.endpoint.health.show-details=ALWAYS
# Eureka
eureka.instance.leaseRenewalIntervalInSeconds=30
eureka.instance.health-check-url-path=/actuator/health
eureka.instance.metadata-map.startup=${random.int}
eureka.client.registryFetchIntervalSeconds=30
eureka.client.registerWithEureka=true
eureka.client.fetchRegistry=true
eureka.client.serviceUrl.defaultZone=https://{Eureka ELB address}/eureka/
我关注了the guide，但也许我错过了一些事情。
任何想法为何SBA都可以如此表现？我还能检查什么？