The main purpose of LoFiMo is, as the name states, to monitor log files. It does this in real time, i.e. shows the contents of log files as they are changing. The user can connect to LoFiMo with a Web browser or use the console for plain text output. When using a Web browser, the output can be formatted with cascading stylesheets, which the user can define. Thus, it is possible to highlight certain log entries with different colors and fonts. It is also possible to play sounds or execute commands (send an email, play sound with a custom player, etc.) when a log entry matches a filter. LoFiMo can parse Apache style log files and syslog style log files. Among others, there are filters that can parse iptables logs and merge multiple log lines of Postfix into a single one.
ProviderTool Internet server administration program with email protection. The software is divided into a subcomponent Admin Tool, Customer Tool, and a Reseller Tool. Each subcomponent tool manages a separate zone that is setup for the specific needs of your administrator, end user, and reseller. If you have a Red Hat, SuSE, or Debian Internet or intranet server, you will be able to add, delete, and change settings and users with just a couple of clicks. ProviderTool is delivered with a separate Apache and PHP server environment. There is also an email protection tool included.
MCS MyVoIP very accurately measures the quality and performance of Internet connections for Voice over IP (VoIP) usage by simulating UDP voice data traffic between a server and browser clients. Connections are tested for jitter and packet loss and rated for the supported level of sound quality. The VoIP test can be set to various codecs or customized by packet size, packet rate, and test length. The test can further be combined with a bandwidth speed test or network route diagnostics for more in-depth connection analysis.
apache-top provides real-time display of the active processes from a remote apache server. It shows: the active apache processes with the associated PID, the status, the active seconds, the CPU usage, the associated VirtualHost, the accessing IP and the request (POST or GET, the file being accessed, and the used protocol); the server uptime and the time it was last restarted; CPU usage; requests per second, Kb per second, and the average Kb per request; the number of active and inactive processes; and a graph with the inactive and active processes and their status.