feat/message handling
- Jul 20, 2024
-
-
Bartek Jaskulski authoredIn situation, when we don't collect verbose logs, but we still may be interested in any errors occurring on client's website and being able to investigate those after gaining access, we may make use of `action_level` option in `SimpleLoggerFactory`. With this option set to some level, we configure `FingersCrossedHandler` which will ensure, when action level is hit, all log stack is persisted. Signed-off-by:Bart Jaskulski <bjaskulski@protonmail.com>
-
Bartek Jaskulski authored
Signed-off-by: -
Bartek Jaskulski authored
Following previous commit, remove check for WP log usage, and treat it only as fallback handler. Signed-off-by: -
Bartek Jaskulski authored
Remove option, allowing to disable WooCommerce logger. If WC is available, this log should always be used unconditionally. Signed-off-by: -
Bartek Jaskulski authored
Signed-off-by: -
Bartek Jaskulski authored
For better discoverability of singular request, include uid in log context. This way it should become trivial to inspect actions, even on high-concurrency websites. Signed-off-by: -
Bartek Jaskulski authored
Add PSR processor, to handle inline variables in log statements, like "Registering user {id} with name {full_name}". https://www.php-fig.org/psr/psr-3/#12-message Signed-off-by:
-