Forum Moderators: coopster
we use syslog [php.net] to log everything we can
we have other logfiles we use for specific things like login attempts, data that didnt validate and anything else we want a specific history for.
all db errors are trapped to a single file and also get sent to my phone
hmm, testing, testing and more testing.
>> What types of db errors are you monitoring
any and all, there should never be one on production. A db error happens and I get the wake up call, doesn't matter if it's a bad select.
<added> very serious, it goes to me and the sysadmin as well and we check it out.
I took a quick look at the syslog() function and it looks like it may be what I need to use. So, the way I understand it this function needs you to supply the error message to it right? What happens if you want to log the actual PHP error message that has the line number, etc?