View Revisions: Issue #4700

Summary 0004700: Taler components should use tracing identifiers to correlate log statements from one request
Revision 2016-10-02 20:06 by Florian Dold
Description Currently it impossible to trace back log statements to one request, or to correlate multiple log statements.

This makes logs useless, unless they contain a lot of ad-hoc contextual information.

We should make logging more useful by adding a (random) tracing identifier to each log statement. This makes it possible to trace every log statement back to the request that caused it.

The "roots" ofrequests can either be HTTP requests, or periodically run tasks.
Revision 2016-10-02 20:05 by Florian Dold
Description Currently it impossible to trace back log statements that e.g. the exchange makes to a request.

This makes logs useless, unless they contain a lot of ad-hoc contextual information.

We should make logging more useful by adding a (random) tracing identifier to each log statement. This makes it possible to trace every log statement back to the request that caused it.

The "roots" ofrequests can either be HTTP requests, or periodically run tasks.