Missing Structured Failure Report in Spring Boot WAR Deployments

When a Spring Boot application fails to start, the framework normally logs a structured failure analysis report that includes a description and suggested action.

However, when the same application is packaged as a WAR and deployed to an external servlet container (e.g., Tomcat, Jetty), the container’s lifecycle may surface the raw exception without invoking SpringBoot’s FailureAnalyzer chain, leaving the diagnostic report absent from the logs.

This raises uncertainty about whether the missing report indicates a gap in the built‑in analysis or simply a deployment‑mode limitation, and whether adding a domain‑specific FailureAnalyzer would provide useful guidance.

Does Spring Boot emit a FailureAnalyzer report for startup failures that occur during external‑container WAR deployment?
Under what circumstances does the container suppress or replace the structured analysis output?
Should a custom FailureAnalyzer be registered to capture deployment‑specific failures, and how can its invocation be confirmed in this mode?