Write Errors to Log File or Store in DB

rsmith

I've been wondering, as I build up my most recent application, which way the developers here on PHPBuilder prefer to store the error codes and information that their application(s) may generate.

Typically I just have my application create new log files based on date then write all errors to that log file. Next day -> repeat.

But lately I've been thinking of logging all that information to a DB table so I could run reports against it later without having to do things like "find" and string searches. Seems like it is a more practical approach then creating a bunch of .log files that have to be purged or rotated.

Thoughts? Just looking for some input.

NogDog

I guess my main concern would be performance: if something happens such that you are suddenly throwing a "function deprecated" notice or such on every page view, requiring a DB insert each time could potentially be an issue. If, on the other hand, you make saving it to the DB some sort of optional flag in a custom error-handler and reserve it for "important" things (like DB queries that fail), I wouldn't be as concerned.

NogDog

NogDog;11005885 wrote:
...(like DB queries that fail)...

I just had an ugly vision of an infinite loop when your error-logging query fails. 🆒

rsmith

Right... I'm talking about errors that are generated when a user attempts to manipulate data or bypass algorithms in an attempt to trick the scripts into handling an unwanted payload.

In this sense I would store the script generating the error, what was trying to run, the targeted function, and the IP address of the offender.