Where do I dump my big pile of logs?

SASL error logging

The SASL application adds a handler that formats and

writes log reports to disk as specified by the sasl
config parameters

[{sasl, [
{error_logger_mf_dir, "."},
{error_logger_mf_maxbytes, 1024},
{error_logger_mf_maxfiles, 10}
]}].
 report browser
1> rb:start().
rb: reading report...done.
{ok,<0.43.0>}
2> rb:list().
No Type Process Date Time
== ==== ======= ==== ====
5 progress <0.31.0> 2010-02-10 11:27:24
4 progress <0.31.0> 2010-02-10 11:27:24
3 progress <0.31.0> 2010-02-10 11:27:24
2 progress <0.31.0> 2010-02-10 11:27:24
1 progress <0.24.0> 2010-02-10 11:27:24
ok
3> rb:show(1).

PROGRESS REPORT <0.5.0> 2010-02-10 11:27:24

============================================================
application sasl
started_at nonode@nohost
 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
Cons
• no remote access
• logs from separate VMs are siloed
• no web interface
• not very realtime
 SASL error logging and report browser
Pros
• easy setup
add sasl config values and rb:start()

• supports simple filtering and grepping

Cons
• no remote access
• logs from separate VMs are siloed
• no web interface
• not very realtime
 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
rb:list(error_report) and rb:grep("asdf")
Cons
• no remote access
• logs from separate VMs are siloed
• no web interface
• not very realtime
 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
Cons
• no remote access
rb runs locally as a gen_server and can't load logs from other nodes

• logs from separate VMs are siloed

• no web interface
• not very realtime
 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
Cons
• no remote access
• logs from separate VMs are siloed
it can be useful to view logs from distributed nodes in a unified timeline

• no web interface
• not very realtime
 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
Cons
• no remote access
• logs from separate VMs are siloed
• no web interface
this limits access by multiple users

• not very realtime

 SASL error logging and report browser
Pros
• easy setup
• supports simple filtering and grepping
Cons
• no remote access
• logs from separate VMs are siloed
• no web interface
• not very realtime
rb requires rescanning new log entries because it stores scanned logs
in gen_server state
 log_roller
• distributed nodes broadcast messages to a
central disk log
• SASL-like configuration of max size and
number of files in your rotating disk log
• filter log messages into partitioned
"buckets" based on node names, log types,
and regexp matching
• full featured web interface for log
monitoring, grepping and polling