Search Results for "remote host"

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data...

Logspout is a log router for Docker containers that runs inside Docker. It attaches to all containers on a host, then routes their logs wherever you want. It also has an extensible module system. It's a mostly stateless log appliance. It's not meant for managing log files or looking at history. It is just a means to get your logs out to live somewhere else, where they belong. For now it only captures stdout and stderr, but a module to collect container syslog is planned.

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.