on master help sign in
Fix errors in sdist step
commit8fe41bcee01ab401601ece41eccb8ad3a63be006 authorMichael Xavier <michael@michaelxavier.net> dateMon 29 Feb 2016, 13:24 (11 years ago) parentdfc37da
3 files changed+26−5
README.md+1−3 katip-elasticsearch/katip-elasticsearch.cabal+1 katip/katip.cabal+24−2
README.md+1−3
@@ -1,9 +1,7 @@
11
22# Katip
33
4−A structured logging framework for tagging each log message with its
5−surrounding context.
6−
4+A structured log framework.
75
86## katip
97
katip-elasticsearch/katip-elasticsearch.cabal+1
@@ -1,4 +1,5 @@
11name: katip-elasticsearch
2+synopsis: ElasticSearch scribe for the Katip logging framework.
23version: 0.1.0.0
34license: BSD3
45license-file: LICENSE
katip/katip.cabal+24−2
@@ -1,7 +1,29 @@
11name: katip
22version: 0.1.0.0
3−synopsis: A structured logging framework for tagging each log message with its
4− surrounding context.
3+synopsis: A structured logging framework.
4+description:
5+ Katip is a structured logging framework with following design goals:
6+
7+ * Logs are structured, meaning they can be individually tagged with
8+ key value data (JSON Objects). This helps you add critical
9+ details to log messages before you need them so that when you do,
10+ they are available. Logs are also namespaced to help filter
11+ different subsystems.
12+
13+ * Critical details for monitoring production systems such as host,
14+ PID, thread id, module and line location are automatically
15+ captured.
16+
17+ * Can be easily extended (even at runtime) to output to multiple
18+ destinations at once (known as scribes). See @katip-elasticsearch@
19+ as an example.
20+
21+ * Designed to be highly configurable. Can be adjusted both with
22+ verbosity, which dictates how much of the log structure should
23+ actually get logged, and severity. Each individual scribe can be
24+ configured to a different log severity.
25+
26+ A note on the name: Katip is Turkish for scribe.
527license: BSD3
628license-file: LICENSE
729author: Ozgun Ataman