Search Results for "client server"

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...

Inputs watch log files for changes, send new log messages to the server, which broadcasts to web clients. Log messages are tagged with stream and source information based on user configuration. log.io has no persistence layer. File inputs are informed of file changes via inotify, and log messages hop from input to server to web client via TCP and socket.io, respectively. log.io uses a stateless TCP API to receive log messages.

ClickHeat is a visual heatmap of clicks on a HTML page, showing hot and cold click zones. Requires Javascript on the client to track clicks, PHP and GD on the server to log clicks and generate the heatmap. You should download it on Github where the project has moved: https://github.com/dugwood/clickheat

Log File Paladin is a wxWdigets based client and PHP based server application for automated monitoring of remote logs. It is designed to help technicians effortlessly monitor client machines which would otherwise receive no attention.

IPLClient is part of a Client-Server technology for IPLocation and visualization. It will manage log-file transfer and handle data delivered by the IPLServer for proper visualization. Modules and plugins may be applied to the client.