Eliot: Logging that tells you why it happened¶
logging and other similar systems output a stream of factoids: they’re interesting, but you can’t really tell what’s going on.
- Why is your application slow?
- What caused this code path to be chosen?
- Why did this error happen?
Standard logging can’t answer these questions.
But with a better model you could understand what and why things happened in your application. You could pinpoint performance bottlenecks, you could understand what happened when, who called what.
That is what Eliot does.
eliot is a Python logging system that outputs causal chains of actions: actions can spawn other actions, and eventually they either succeed or fail.
The resulting logs tell you the story of what your software did: what happened, and what caused it.
Eliot supports a range of use cases and 3rd party libraries:
- Logging within a single process.
- Causal tracing across a distributed system.
- Scientific computing, with built-in support for NumPy and Dask.
- Asyncio and Trio coroutines and the Twisted networking framework.
Eliot is only used to generate your logs; you might still need tools like Logstash and ElasticSearch to aggregate and store logs if you are using multiple processes across multiple machines.
- Start here: Quickstart documentation
- Need help or have any questions? File an issue on GitHub.
- Commercial support is available from Python⇒Speed.
- Read on for the full documentation.
“Eliot has made tracking down causes of failure (in complex external integrations and internal uses) tremendously easier. Our errors are logged to Sentry with the Eliot task UUID. That means we can go from a Sentry notification to a high-level trace of operations—with important metadata at each operation—in a few seconds. We immediately know which user did what in which part of the system.”
- Why Eliot?
- What’s New
- Generating Logs
- Outputting Logs
- Reading Logs
- Scientific Computing with Eliot
- Python 2.7 Support
- Contributing to Eliot