These are chat archives for spring-cloud/spring-cloud
HeartBeatEventis only published when a new service appears, but not when an underlying node of an existing service (dis-)appears. Is this on purpose? I'd expect that to happen (as it is with eureka). Currently Spring Boot Admin is relying on this and currently new nodes do not show up when using consul discovery...
My guess would be just to query a different resource (use
getCatalogNodes instead of
getCatalogServices) . If I get https://www.consul.io/api/index.html right, the index should change when the nodes change
Endpoints that support blocking queries return an HTTP header named X-Consul-Index. This is a unique identifier representing the current state of the requested resource.