15 Mar
2010
15 Mar
'10
10:22 p.m.
On Mon, 2010-03-15 at 21:26 +0000, Andy Smith wrote:
Hello,
On Mon, Mar 15, 2010 at 09:08:57PM +0000, Andy Loughran wrote:
The only comment I'd have here (which I imagine you'd have thought of,
but its not mentioned, so..) is regarding who can see the logs from my
server.
The only remote syslog implementation I've used aggregates all output
(e.g. /var/log/messages) into one file, so I assume you'd need to
somehow split the logs into ones for each server
(/var/log/message.customerX for example?), otherwise there might be
security, privacy and (possibly?) data protection concerns..
If the solution was adding remote syslog viewing to the Bitfolk Panel,
viewing only by that user, I think that's a super idea - you could even
give customers the option of mandating how long they want the logs kept
for, if they wanted to use some of the space on provisioning (like
currently for backups)...
Regarding your comment earlier that you couldn't even give backups away,
I imagine that some people might be concerned as they wouldn't be able
to control the system the backups were placed on, so wouldn't know what
was safe, who had access etc and I imagine the same would apply to
system logs. Both fixed by a policy statement on the customer support
page, I feel.
Cheers
John
--
John Constable <john(a)kript.net>
I find remote logging quite frustrating.
The best interface I found for it was php-syslog-ng - and now that has been
deprecate in place of logzilla - which is a java blob.
Just to be clear, there's no way I can write any sort of interface
for parsing log files. I'm talking about putting a copy of your log
files somewhere else, where you can't write to them but can read
them. Then you use whatever sort of tools you like on them.