From: Steve Grubb <sgrubb@redhat.com>
To: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: EOE events in auparse output
Date: Mon, 05 Dec 2016 10:54:30 -0500 [thread overview]
Message-ID: <8276321.D6A7ZRxJEI@x2> (raw)
In-Reply-To: <029e3140-0633-ad77-b0d9-c4af223c10d7@redhat.com>
On Monday, December 5, 2016 5:34:12 PM EST Nikolai Kondrashov wrote:
> However, since libauparse is supposed to provide the service of
> communicating event boundaries to its users, does it make sense for it to
> return the EOE record? Especially as a separate, empty event, which doesn't
> add any information?
I suppose it could be stripped from the event as its real purpose is locating
the event boundary. Since I don't know if the event will be relayed on to
another analytic processor I've just kept it there. For example, you could
have a realtime plugin that passes its information to another process for
correlation and escalation. In that case keeping the record makes sense. But
for xml/json it can be dropped because it has its own way of defining an event
boundary.
-Steve
next prev parent reply other threads:[~2016-12-05 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 13:00 EOE events in auparse output Nikolai Kondrashov
2016-12-05 15:27 ` Steve Grubb
2016-12-05 15:34 ` Nikolai Kondrashov
2016-12-05 15:54 ` Steve Grubb [this message]
2016-12-05 16:49 ` Nikolai Kondrashov
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=8276321.D6A7ZRxJEI@x2 \
--to=sgrubb@redhat.com \
--cc=Nikolai.Kondrashov@redhat.com \
--cc=linux-audit@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