I do some work to make it work better in dev env or in public env. That is:
- Support token for security, one can't access the site without the token in
config.php - Support IP whitelists for security and privacy
- Sopport config the interval between ajax requests
- Support load static files from local (for local dev env)
New config items in config.php:
// interval between ajax requests, in milliseconds, use a big number if you want to refresh to see updates
$interval = 30 * 1000;
// access the site with this parameter for security and privacy, if this set, access your site with ?token=mytoken parameter
$token = 'mytoken';
// ip scope which are allowed to access this site
$ipwhitelists = ['127.0.0.1', '192.168.99.1', '123.56.24.0/22'];
// load the static files(js/css/fonts) from local, not cdn; 0 or 1, default 1
$local_static = 1;
中文用户请看：推荐实时查看Web服务器错误日志的软件：LogHappens
See the website: http://loghappens.com
Bug happens. Every developer knows that. The nasty thing is that if you want to see what happened, you have to crawl between hundred lines log files, written in txt format, with no options to see them in an easier format, perhaps grouped by time.
LogHappens aims to fix this lack. It is a simple tool, it will not prevent you from writing bugs, but it will notify you immediately when something has been logged.
Of course it does. While it is true that every software has its own bugs, every software have its own way of logging things too. This is why I have tried to make it as simple as possible to create your own routine for reading log files. No fancy regex strings: if you just want to read the file, you can write a small php routine and group log entries by date/time, just printing the rest of the file. If you are feeling adventurous, you could possibly do whatever you want: highlight words, create tags, split errors... the only limit is your fantasy!
You can use one of the files you see in the logic_templates folder. Edit it according to your needs (e.g. the log path). Move it to the logic folder and refresh the page. Voilà. Use as much logics as you like to track more log files, and edit the way they group logs according to your needs. It should be pretty easy, isn't it?
Of course! As you see, I have placed apache24 and CakePHP 3.x log files in the logic_templates folder. If you have created your own routine, please send it to me, I will be glad to add it to the other templates!
While not currently supported, I am planning to add support for remote logs too. Maybe through SFTP, I don't know yet... I'm open for ideas!
By default, apache log files are not readable by apache itself. Which is a good thing, at least on a production server. If you are on a development machine though you should give those files the correct permissions if you want to use LogHappens. Here's how:
- Edit
/etc/logrotate.d/apache2, find the line sayingcreate 640 root admand replace withcreate 777 root adm. - Add 777 permissions to the apache logs directory:
sudo chmod -R 777 /var/log/apache2/