Timeline for Server-side event logs through DB or writing to file?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2011 at 14:11 | comment | added | Deets McGeets | In addition, Codism makes the point that file writing is faster and is just as easy to search through a file using regex. While Emmad suggested the many points that one must consider when writing to files (and in turn suggested using a DB). In any case, just because I checked this as the answer, I do not want readers to neglect reading the other excellent answers. | |
| Sep 29, 2011 at 14:08 | comment | added | Deets McGeets | All the answers were very solid and helpful, but this really contains a critical point that makes file-writing the only way to go: It's much more likely that the DB will go down than being unable to write to files. Ethan Post has a great point as well, which is during a particular action / server request, temporarily store the events (queries, etc.) and then if an error is encountered, throw them all to the logfile, so you have the path when there's an error but aren't storing a bunch of unnecessary events. | |
| Sep 29, 2011 at 14:01 | vote | accept | Deets McGeets | ||
| Sep 29, 2011 at 6:34 | history | answered | Marjan Venema | CC BY-SA 3.0 |