This sounds really interesting, but I can't seem to ascertain what it actually does.
> The log data is buffered in-memory (potentially journaled for reliability) and sent over a configurable transport.
What are the options for this 'configurable transport'? What is/are the endpoint(s)? Does LoggerFS have facilities for storing and reading-back logs, or does it rely on other services for this?
The post only seems to /hint/ at answers to these questions.
Backend/Aggregator agnostic (includes multiple log transports)
Supports any Syslog-based log manager
Loggly, Splunk, Logstash, Rsyslog/Syslog-ng
ZeroMQ
NSQ transport – used internally at AutoRef.com
Generic UDP/TCP
And soon: AMQP and Redis (and later: Scribe? Fluentd?)
It deals with the specific problem of collecting the logs from the applications on your servers and shipping them to an aggregator (of which there are already many, e.x. Loggly, Splunk, Logstash)
> The log data is buffered in-memory (potentially journaled for reliability) and sent over a configurable transport.
What are the options for this 'configurable transport'? What is/are the endpoint(s)? Does LoggerFS have facilities for storing and reading-back logs, or does it rely on other services for this?
The post only seems to /hint/ at answers to these questions.