The katip-elasticsearch package

[ Tags: bsd3, data, library ] [ Propose Tags ]

See README.md for more details.


[Skip to Readme]

Properties

Versions 0.1.0.0, 0.1.1.0, 0.2.0.0, 0.2.1.0, 0.3.0.0, 0.3.0.1, 0.3.0.2, 0.3.1.0, 0.4.0.0, 0.4.0.1
Change log changelog.md
Dependencies aeson (>=0.6 && <1.3), async (>=2.0.1.0 && <2.2), base (>=4.6 && <5), bloodhound (>=0.13.0.0 && <0.16), bytestring, enclosed-exceptions (>=1.0.0 && <1.1), exceptions, http-client (>=0.3 && <0.6), http-types (>=0.8 && <0.10), katip (>=0.2.0.0 && <0.6), retry (==0.7.*), scientific (>=0.3.0.0 && <0.4), stm (>=2.4.3 && <2.5), stm-chans (>=3.0.0.2 && <3.1), text (>=0.11 && <1.3), time (>=1 && <1.9), transformers (>=0.2 && <0.6), unordered-containers (>=0.1.0.0 && <0.3), uuid (>=1.3.12 && <1.4) [details]
License BSD3
Copyright Soostone Inc, 2015-2016
Author Ozgun Ataman, Michael Xavier
Maintainer michael.xavier@soostone.com
Category Data
Uploaded Fri Sep 15 19:01:48 UTC 2017 by MichaelXavier
Distributions NixOS:0.4.0.1, Stackage:0.4.0.1, Tumbleweed:0.3.1.0
Downloads 466 total (27 in the last 30 days)
Rating 0.0 (0 ratings) [clear rating]
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2017-09-15 [all 1 reports]
Hackage Matrix CI

Modules

[Index]

Flags

NameDescriptionDefaultType
lib-werrorDisabledManual

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for katip-elasticsearch-0.4.0.1

[back to package description]

Katip Elasticsearch Build Status

katip-elasticsearch is a scribe for the Katip logging framework that sends structured logs to ElasticSearch.

Features

  • Built in bounded buffering.

  • Configurable pool of logging workers to help with high write volume.

  • Optional field type annotation to avoid mistyping values.

  • Optional automatic date sharding, so logs can be filed into monthly, weekly, daily, hourly, every minute indices. You can even specify your own index routing logic. This pattern can be seen in the ELK stack as a way of keeping indexes reasonably sized and easy to optimize, rotate, and manage.

  • Customizable retry policy for temporary outages and errors.

  • Automatic index and mapping setup.