scottfrederick on main
Avoid adding layers for buildpa… Merge branch '2.6.x' into 2.7.x… Merge branch '2.7.x' Closes gh… (compare)
scottfrederick on 2.7.x
Avoid adding layers for buildpa… Merge branch '2.6.x' into 2.7.x… (compare)
scottfrederick on 2.6.x
Avoid adding layers for buildpa… (compare)
wilkinsona on 2.7.x
Upgrade to Dependency Managemen… Merge branch '2.6.x' into 2.7.x… (compare)
wilkinsona on 2.6.x
Upgrade to Dependency Managemen… (compare)
wilkinsona on main
Upgrade to Dependency Managemen… Merge branch '2.6.x' into 2.7.x… Merge branch '2.7.x' Closes gh… (compare)
Endpoint
which is removed from exposure.exclude and added into exposure.include in a BeanPostProcessor. Now that I'm moving away from @ConditionalOnEnabledEndpoint
to @ConditionalOnAvailableEndpoint
it's returning 404 and is not actually exposed. I guess available endpoint is the combination of enabled and exposed. With @ConditionalOnEnabledEndpoint
it works fine, so I assume it's enabled. It's also exposed in the BeanPostProcessor. My guess of the problem is that by the time of Condition is evaluated, the bean processor has not exposed it. But how to solve this problem? FYI, this is in an internal spring-boot library.
@Endpoint
s. When I expose it in the properties file in tests, it works fine as those properties are resolved and evaluated before AutoConfiguration
decides with @ConditionalOnAvailableEndpoint
, however, I want to avoid forcing everyone to manually put some configs, and rather I expose it programmatically
application.yml
/metrics
endpoint. Bydefault, it's /actuator/prometheus
Too many open files
I tried several solutions until migrating spring boot 2.2.2 then jetty but after a while I still receive org.eclipse.jetty.server.HttpChannel - handleException /api/sender java.io.IOException: Too many open files
What can be the problem ? Thank you
EnvironmentPostProcessor
gets evaluated before those @Conditional...
s are evaluated? 2. If I add it there, then if clients want to say exclude it in their application.yml
, then what's the behaviour? what takes the precedence? My guess is that it can be handled in the EnvironmentPostProcessor
:)
management.endpoints.web.exposure.include
is that it takes a comma-separated list. So in this case, if you add a new property source for each endpoint (in my case they are in different modules and each has its own EnvPostProcessor), then the one which is first in the order, is the one that's exposed, and the rest is not exposed. In this case, is it fair to solution to scan through environment.propertySources
and find the first instance where management.endpoints.web.exposure.include
is defined and alter (append new endpoint) it there? Or is there a better way?