[Hierarchy] Specify your base logger name in documentation when using __name__ as logger name.
- logging_example.py
- root_logger_issue/main.py
- multiple_loggers/main.py
- log_exception_stacktrace/main.py
- handlers/*.py
- custom_formatter.py
- hierarchy/main.py
- filters.py
- logging_config/main.py
Receives log messages
- level
- propagate
- filters
- handlers
Contain information about the function, file name, full path where the log was requested, the string that was passed, arguments, call stack information, etc. These are the objects that are being logged. Every time we invoke our loggers, we are creating instances of these objects.
- Created automatically by the logger every time something is logged
- Can be created manually via logging.makeLogRecord
https://docs.python.org/2/library/logging.handlers.html#module-logging.handlers
Handlers emit the log records into any output. They take log records and handle them in the function of what they were built for. As an example, a FileHandler will take a log record and append it to a file.
The handler will then use a Formatter to turn the LogRecord into a string and emit that string.
- class
- level
- filters
- formatter
Format a log record for output. Formatters are in charge of serializing the metadata-rich LogRecord into a string. There is a default formatter if none is provided.
- format
- date format
- style (%,{,$)
Control which LogRecord should be emitted
- from Logger ---> Handlers [Filter at logger level]
- from Handlers ---> Formatter [Filter at Handler level]
Users can declare their own filters as objects using a filter method that takes a record as input and returns True/False as output.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent