Home / server / Questions / 52893
Accepted
benlumley
Asked: 2009-08-12 11:26:09 +0800 CST

Graphing/Reporting PHP Errors

  • 772

Whats the best way to get reports on php errors?

To give a bit of background, have some legacy PHP applications/websites that generate various errors/warnings etc, currently going to apache log.

Would like to be able to graph these somehow to have showing on a screen in the office the developers are in.

The hope is that increasing the visibility of these errors will firstly make people aware quickly if an upgrade increases the error rate, and also help in the longer term quest to drive the errors down towards zero.

For extra points, it would be nice to be able split the errors up by a part of the path to the file causing the error (ie: split the errors by site).

Whats the best tool for this? I was looking at cacti, and have used zenoss for other monitoring before. But can't find info on doing exactly this with either - hoping someone else has done it!

php logging apache-2.2 monitoring

3 Answers

    • 2

  2. You can do that (and much more) with my logs management project Octopussy, but it's probably a little bit complicated for just what you need...

    But if you want to try it, I could probably help on that particular need.

    • 1
  3. Best Answer

    What I did at work was simply to set up a bunch of terminals running tail on a big screen. It's been very effective, as you get all the errors in real time.

    Basically; - Set upp logmonitor account on all related machines, make sure it can read the log files, and not much else. - Generate SSH private/public keypair on the computer doing the monitoring and set it up on the machines you will be accessing. - Set up a bunch of terminal windows to.automatically load on boot and connect to each server and start tail'ing the logfiles.

    Make sure you use tail -F instead of tail -f, otherwise the log will stop scrolling when it's rotated.

    We set this up on a mac running Leopard, so it camke with everything we needed from scratch, ssh, terminal with "window groups" and profiles for running a custom command instead of the normal shell on connect.

    Of course, the next. Level of this would be to set upp your sysloggers to collect all the logfiles from all the different machines in one place.

    • 1