Group :: Development/Python3
RPM: python3-module-eliot
Principal Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
A versão atual: 1.14.0-alt1
Data da compilação: 4 abril 2022, 14:33 ( 103.5 weeks ago )
Tamanho:: 125.07 Kb
Home page: https://github.com/itamarst/eliot/
Licença: MIT
Sumário: Logging library that tells you why it happened
Descrição:
Lista dos contribuidores Lista dos rpms provida por esta srpm:
ACL:
Data da compilação: 4 abril 2022, 14:33 ( 103.5 weeks ago )
Tamanho:: 125.07 Kb
Home page: https://github.com/itamarst/eliot/
Licença: MIT
Sumário: Logging library that tells you why it happened
Descrição:
Python's built-in 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 will might need tools like Logstash and ElasticSearch
to aggregate and store logs if you are using multiple processes across multiple machines.
Mantenedor currente: Vitaly Lipatov 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 will might need tools like Logstash and ElasticSearch
to aggregate and store logs if you are using multiple processes across multiple machines.
Lista dos contribuidores Lista dos rpms provida por esta srpm:
- python3-module-eliot