You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2023. It is now read-only.
There's this very interesting package called Eliot, that propose a different approach to logging.
For sure, the current way logging works is just very inefficient. Firstly, debug isn't always enabled (and leaving every module's logging level to DEBUG would be a nightmare), and even if it was, it's so painful to look through it, and track on particular thing (concurrency doesn't make things any better).
From what I understand right now, Eliot does it using actions. A program is just a collection of actions, and Eliot monitors them, and record how they behaved. It's seems nicer for debugging and monitoring perfs.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's this very interesting package called
Eliot
, that propose a different approach to logging.For sure, the current way logging works is just very inefficient. Firstly, debug isn't always enabled (and leaving every module's logging level to DEBUG would be a nightmare), and even if it was, it's so painful to look through it, and track on particular thing (concurrency doesn't make things any better).
From what I understand right now, Eliot does it using actions. A program is just a collection of actions, and Eliot monitors them, and record how they behaved. It's seems nicer for debugging and monitoring perfs.
The text was updated successfully, but these errors were encountered: