nicesoftware/logwebmonitor repository overview

This Container is part of the NICE-LogServer Solution. It is under ongoing development so things can change fast here. Currently every commit to the Development Branch of the Project triggers a new build of this image!

For further information see www.nice-logs.de⁠

The NICE-LogServer Solution contains of three main parts:

• The NICE LogAgent (https://hub.docker.com/r/nicesoftware/logagent/⁠): LogAgents can monitor multipe files or folders for changes on logfiles. Everytime a logfile changes the LogAgent gets triggered and sends the new data to the NICE LogService he is connected to.

• The NICE LogService (https://hub.docker.com/r/nicesoftware/logservice/⁠): LogAgents can connect to a LogService and will send new LogData from monitored logfiles to the LogService. It persits the data in an SQLLite DB. Clients like the NICE LogWebMonitor can connect two multiple LogServices to get the data.

• The NICE LogWebMonitor (https://hub.docker.com/r/nicesoftware/logwebmonitor/⁠): This is the actual Client for the NICE LogService. It can connect too multiple LogServices and visualize LIVE (!) LogData from all in oneView. This View can be filtered by streams (the log entry origin basically) and you have a user and groups based rights managment for what you can see. For example: Project Team A sees all LogEntries from Production related to there work live but not the entries related to any other project the LogService has data for. A SQL Server is needed for this Container. Feel free to use https://hub.docker.com/r/nicesoftware/logserverdb⁠ for your tests!

There ist a LogSimulator feature embedded in the LogAgent Container wich can give you a idea for what an active logstream looks like. You can download a docker-compose.yml for a full featured NICE-LogServer from here: https://downloads.nice-logs.de/docker/docker-nice-logserver.zip⁠