spring-boot-admin | Object-Relational Mapping library

I am facing issue with spring cloud sleuth as it is leaking memory as I have gone through the dumps of my applications:

What does 13.05mb (40.3%) of Java Static org.springframework.cloud.sleuth.instrument.async.SleuthContextListener.CACHE

Spring Cloud Version: Hoxton.SR8 Spring Boot Version: 2.3.3.RELEASE

Please find the heapdump report below:

https://heaphero.io/my-heap-report.jsp?p=YXJjaGl2ZWQvMjAyMS8wNS8yNS8tLWhlYXBkdW1wLTE2MjE5MjE0MzYyNTMuaHByb2YtNS00Ni0xLmpzb24=

pls find the code repo below, which I am using in my appplication, Also on first run there is no memory leakage issue but on successive runs it shows the memory leakage issue as mentioned in the heapdump report

I have a number of applications reporting to a SpringBoot Admin application using SpringBoot Admin Client. One of our recent projects that's under construction is using a custom JWT/refresh token authentication flow and I want SpringBoot Admin to use that before hitting the actuator endpoints so I can secure those as well.

The flow works by sending credentials to /v1/auth/login, which will give the user a JWT token with expiration date and refresh token. The JWT is only valid for a short time after which it needs to be refreshed and is submitted with the request as a Bearer-token.

I found this this thread which is somewhat related, but I need to be able to see which endpoint it's trying to access since not all of the applications use the same kind of authentication.

Is there some way I can configure it to add the Authorization header with the correct headers given a URL or client name that matches a certain pattern? Preferably as part of some component that could keep JWT/expiry/refresh token as part of it's state, so I could refresh it when necessary.

As the docs state in order to cache the Maven dependencies with GitHub Actions all we have to use is the actions/cache action like this:

I have a spring boot app that I upgraded from v2.2.x to now be v2.4.3.

I saw in their documentation that there is a new actuator endpoint of /startup, however it does not exist when I start my app.

There is no special requirement according to their documentation here

I am using spring-boot-admin-starter-client v2.4.3 which provides spring-boot-actuator v2.4.3, and i even have management.endpoint.startup.enabled=true in my application.properties file.

Has anyone else used this version of spring boot and gotten this actuator enpoint to work?

I have a handful of spring-boot microservices which register themselves with spring-boot-admin (SBA). When I run the microservices and the SBA server locally, the clients are able to register themselves with the SBA server via HTTP.

When I deploy the apps to the Kubernetes cluster, registration with SBA is done via HTTPS (via an Ingress) I get a javax.net.ssl.SSLHandshakeException in the logs

We're using testcontainers-java heavily in our spring-boot-admin project. Since we also want to be able to run our Maven build also on Windows, we added a windows-latest environment to our GitHub Actions Pipeline using a Matrix strategy build (as supposed in this answer) like this:

I've specified a spring expression language filter in my spring boot admin application:

Question regarding the plugin Spring Cloud Kubernetes.

On a very simple main (where there is only one important class):

I'm trying to run spring-boot-admin on ECS Fargate - and after a few minutes the server dies and the logs are filled with 'too many open files in system' errors.

I'm using spring-boot 2.3.1, and have tried 2.2.3 and the 2.3.0-SNAPSHOT of spring-boot-admin. The jar is running on an ubuntu 20.04 base image with openjdk-11-jdk-headless installed. The ECS service has 2gb RAM available, and I've increased Ulimits on nofile and nproc (100000)