Problem description

For larger deployments of RDF4J with multiple users, it has proven slightly difficult to trace request execution through logs without adding some notion of a 'request ID' (the thread name contains some information but not enough to fully differentiate requests).

Having such a notion in logs make the request execution more transparent by behind able to trace through all subsystems for any particular execution. Moreover, it also allows for log aggregation tools to group query execution information and glean insights that are useful in debugging and performance optimization.

Preferred solution

Add a 'request Id' to MDC such that it can be (optionally) logged if desired.

Are you interested in contributing a solution yourself?

Yes

Alternatives you've considered

Tried to wrangle Tomcat and Logback for implementing a similar feature but came up short. Looks like Jakarta has tooling to aid in this when we upgrade, but that is out of reach for now it seems.

Anything else?

No response