Logary makes **metrics** and **structured logs** universally accessible: send to ElasticSearch, InfluxDB, File or a pretty coloured console - Logary's got you covered!
Logary lets you send both app metrics and app logs, ship them or simply see them in your console as you develop your product. It's a classy library, rather than premium-mediocre.
Logary Core is an extensible logging framework with tried-and-tested patterns for logging. The configuration API is here and you can configure to be used like Riemann.io, as a .Net-based stream processing engine.
Logary Targets is a large collection of backends that you can send your metrics and logs to. In Azure? Use the AppFabric target. In GCP? Use the Stackdriver target. Self-hosted? ElasticSearch/LogStash and InfluxDB, perhaps.
Logary Facade for F# and C# lets you add logging to your libraries without taking a logging-framework dependency.
Logary Facade Adapter adapts your library's logging implementation to use Logary, at your application's composition root.
Logary Rutta can be run either as a console app, a windows service or as a docker service. It runs either as a:
- Shipper; sending the logs out from your server/node into a...
- Router; accepting logs and forwarding them to a...
- Router; spawning listeners (for the above), or sending to Logary Targets.
Logary Ingestions; lets you interop with other log shipping software like nxlog, fluentd and logstash, or lets your log from your web site, to avoid burdening the visitor with lots of downloads of third party logging libraries.
Other Logary features:
- Completely written in F# and has an auxiliary C# API.
- Crashing targets are restarted using a supervisor-architecture
- Internal logging is separated from app logging.
- Each Target has a configurable ring buffer that the app feeds into.
- Every logged line can be either:
- sent and forgotten;
- or sent and wait for buffer to accept it,
- sent and wait for all routed target having flushed the metric/event.
Install: paket add Logary or Install-Package Logary -pre
