Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify usage of BufferingApplicationStartup #25075

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -124,6 +124,7 @@ The following technology-agnostic endpoints are available:
| `startup`
| Shows the startup steps data collected by the `ApplicationStartup`.
Requires the `SpringApplication` to be configured with a `BufferingApplicationStartup`.
More details about the implementations can be found at <<boot-features.adoc#boot-features-application-startup-tracking, application startup tracking>> page.

| `threaddump`
| Performs a thread dump.
Expand Down
Expand Up @@ -486,6 +486,7 @@ Once configured, you can record data by running the application with the Flight
Spring Boot ships with the `BufferingApplicationStartup` variant; this implementation is meant for buffering the startup steps and draining them into an external metrics system.
Applications can ask for the bean of type `BufferingApplicationStartup` in any component.
Additionally, Spring Boot Actuator will <<production-ready-features.adoc#production-ready-endpoints, expose a `startup` endpoint to expose this information as a JSON document>>.
Be aware, that during startup endpoint processing, all the collected steps will be pulled from the buffer, and sent in the response - so the further requests won't get the startup steps again.

[[boot-features-external-config]]
== Externalized Configuration
Expand Down