spring-projects / spring-projects/spring-boot
Support caching for Actuator endpoint read operations with parameters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Hi.
I'm using Spring Boot 2.6.6 and trying to use time-to-live property for health groups.
The management.endpoint.health.cache.time-to-live=120s property in application.properties works fine to cache health check results when I call /actuator/health, but if I call /actuator/health/deep (where deep is group), I get no cache results.
The management.endpoint.health.group.deep.cache.time-to-live=120s property also doesn't work.
I found a task with this problem on Stack Overflow, but there was no answer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the health endpoint and the deep health group using the two cache properties described in the issue. Inspect the Actuator health endpoint's handling of parameterized read operations and verify that the configured time-to-live is applied to /actuator/health/deep as well as /actuator/health.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100