public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Cooked audit log format
Date: Mon, 12 May 2008 10:50:35 -0500	[thread overview]
Message-ID: <1210607435.6847.14.camel@homeserver> (raw)
In-Reply-To: <200805121119.46856.sgrubb@redhat.com>

Q: Will the (hopefully) soon-to-be released visualization tool have any
influence on this discussion? Also aggregation?

My hope is that I'd only look at human-readable audit data which is
aggregated on one central repository. For me that means the transfer
sizes are important. Ideally to me, the data would be raw/compressed and
sent to a common place with guaranteed delivery.

It would be at that point where the visualization, cooking, translating,
etc. occurs.  The more the better. :) 

Regardless, my original question was would more cooking find its way
into the visualization tool? And any idea of when that may be released?

LCB.

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

  reply	other threads:[~2008-05-12 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 21:40 Cooked audit log format Matthew Booth
2008-05-12 14:43 ` Steve Grubb
2008-05-12 15:02   ` Matthew Booth
2008-05-12 15:19     ` Steve Grubb
2008-05-12 15:50       ` LC Bruzenak [this message]
2008-05-12 16:09         ` Miloslav Trmač
2008-05-12 16:34           ` Steve Grubb
2008-05-12 16:44             ` LC Bruzenak
2008-05-12 16:53         ` Matthew Booth
2008-05-12 16:12       ` John Dennis
2008-05-12 20:56         ` Eric Paris
2008-05-13 12:30           ` John Dennis
2008-05-15 10:28       ` Tony Jones
2008-05-15 12:44         ` Steve Grubb
2008-05-15 15:59           ` John Dennis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1210607435.6847.14.camel@homeserver \
    --to=lenny@magitekltd.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox