synapse-product/synapse/logging
Patrick Cloke b076bc276e
Always use the name as the log ID. (#9829)
As far as I can tell our logging contexts are meant to log the request ID, or sometimes the request ID followed by a suffix (this is generally stored in the name field of LoggingContext). There's also code to log the name@memory location, but I'm not sure this is ever used.

This simplifies the code paths to require every logging context to have a name and use that in logging. For sub-contexts (created via nested_logging_contexts, defer_to_threadpool, Measure) we use the current context's str (which becomes their name or the string "sentinel") and then potentially modify that (e.g. add a suffix).
2021-04-20 14:19:00 +01:00
..
__init__.py Support generating structured logs in addition to standard logs. (#8607) 2020-10-29 07:27:37 -04:00
_remote.py Fix additional type hints from Twisted 21.2.0. (#9591) 2021-03-12 11:37:57 -05:00
_structured.py Update black, and run auto formatting over the codebase (#9381) 2021-02-16 22:32:34 +00:00
_terse_json.py Support generating structured logs in addition to standard logs. (#8607) 2020-10-29 07:27:37 -04:00
context.py Always use the name as the log ID. (#9829) 2021-04-20 14:19:00 +01:00
filter.py Support generating structured logs in addition to standard logs. (#8607) 2020-10-29 07:27:37 -04:00
formatter.py Simplify super() calls to Python 3 syntax. (#8344) 2020-09-18 09:56:44 -04:00
opentracing.py Bugbear: Add Mutable Parameter fixes (#9682) 2021-04-08 22:38:54 +01:00
scopecontextmanager.py Simplify super() calls to Python 3 syntax. (#8344) 2020-09-18 09:56:44 -04:00
utils.py Update black, and run auto formatting over the codebase (#9381) 2021-02-16 22:32:34 +00:00