The lifecycle of a
StartupStep goes as follows:
- the step is created and starts by calling
the application startupand is assigned a unique
- we can then attach information with
- we then need to mark the
end()of the step
Implementations can track the "execution time" or other metrics for steps.
- Brian Clozel
Nested Class Summary
Method SummaryModifier and TypeMethodDescription
end()Record the state of the step and possibly other metrics like execution time.
getId()Return the unique id for this step within the application startup.
getName()Return the name of the startup step.Return, if available, the id of the parent step.
getNameString getName()Return the name of the startup step.
A step name describes the current action or phase. This technical name should be "." namespaced and can be reused to describe other instances of similar steps during application startup.
getIdlong getId()Return the unique id for this step within the application startup.
getParentIdReturn, if available, the id of the parent step.
The parent step is the step that was started the most recently when the current step was created.
key- tag key
value- tag value
key- tag key
Supplierfor the tag value
endvoid end()Record the state of the step and possibly other metrics like execution time.
Once ended, changes on the step state are not allowed.