Missing trace/span on certain exceptions in DispatcherServlet using ObservationAutoConfiguration #33667
Labels
for: external-project
Needs a fix in external project
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: invalid
An issue that we don't feel is valid
theme: observability
An issue related to observability and tracing
On certain errors we don't get traces/spans in log statements. This happens when using latest Spring Boot 3.3.4 with ObservationAutoConfiguration and the following dependencies (example repo here):
And the following correlation pattern is configured in application.properties:
When starting up the application and running this (invalid) request
...we see the following log entry without trace/span:
Note: logging the happy path works fine.
The text was updated successfully, but these errors were encountered: