So, you've written this glorious web application, and it all works perfectly (well, almost perfectly) and your boss loves it. It's amazingly useful and people are saying that it'll be the best thing to hit the company since old what's his name took over. Then, your boss comes up to you and asks you that one last question - "So, how can we tell who's using it?" A lump develops in your throat as you rush back to your workstation to add something, anything into the app that would log, but where do you start? Well, if you find yourself there, DevShed is offering you a hand to help you out.

In their latest, Logging with PHP, they take a quick look at the various mechanisms available to log script activity via PHP, demonstrating both built-in functions and add-on classes that allow you to add logging functionality to your applications.

Logging in your application doesn't have to be complex, but I always try to include some kind of logging, especially on apps that are more "critical" than others. Too much logging is always better than not enough. DevShed dd good with this article, showing you everything from just a simple "page hit" logging all the way up to creating scripts to parse the results of the logs.