Search Results for "anything"

The main goal is to allow libraries to receive a Psr\Log\LoggerInterface object and write logs to it in a simple and universal way. The LoggerInterface exposes eight methods to write logs to the eight RFC 5424 levels (debug, info, notice, warning, error, critical, alert, emergency). Every method accepts a string as the message, or an object with a toString() method. Implementors MAY have special handling for the passed objects. If that is not the case, implementors MUST cast it to a string....

Arlogd provides remote logging. A daemon on a client host watches all fifo's in some directory. Anything written to a fifo is appended to a corresponding file on the loghost. It is not necessary to change or reconfigure logging applications ; you can just replace a log by (a symlink to) a fifo.

Serverstats is a simple tool for creating graphs using rrdtool. Serverstats does not have any features to manage the created rrd-files, if you change anything you have to delete and recreate the files. Perhaps you can avoid this using third-party-tools

LogShark is a simple log monitor. It can monitor multiple directories, and for each directory a different set of filename patterns can be used. Because LogShark does not lock anything, it does not prohibit removal of the files and/or directories.

DirJack is a java written tool to monitor directories in your filesystem. The main feature is to react on changes within a directory i.e. you can define the behaviour what to do when files are added, edited or removed.