| |||||||||||||
The Journal - a proposed syslog replacementThe Journal - a proposed syslog replacementPosted Nov 18, 2011 18:17 UTC (Fri) by JoeBuck (subscriber, #2330)In reply to: The Journal - a proposed syslog replacement by quotemstr Parent article: The Journal - a proposed syslog replacement This seems ill-advised, because logs might need to be analyzed some point in the future. They are critical data, and you never want to have a problem reading your critical data. I don't care if they leave things loose during the initial design and evaluation, but you don't want to deploy this thing on a server you care about unless they tighten it up.
(Log in to post comments)
The Journal - a proposed syslog replacement Posted Nov 18, 2011 20:14 UTC (Fri) by niner (subscriber, #26151) [Link]
I also keep critical data in a PostgreSQL database which can only be read by a single program - PostgreSQL. It would probably be nice to be able to read it with a text editor, but then I'd probably lose all the benefits PostgreSQL gives me, so I can live with it. As I will with having to use some command like logread on my wireless router to get at the logs.
|
|||||||||||||