From: Steve Grubb <sgrubb@redhat.com>
To: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Cc: linux-audit@redhat.com, gcwilson@us.ibm.com, bryntcor@us.ibm.com
Subject: Re: [PATCH] auvirt: a new tool for reporting events related to virtual machines
Date: Tue, 24 Jan 2012 15:27:40 -0500 [thread overview]
Message-ID: <201201241527.40706.sgrubb@redhat.com> (raw)
In-Reply-To: <4F1EF3B8.5080303@linux.vnet.ibm.com>
On Tuesday, January 24, 2012 01:08:56 PM Marcelo Cerri wrote:
> I took a look at some anomaly events and I'm thinking to correlate them
> to guests based on the SELinux context or maybe based on the pid field.
>
> Do you think there is another ways to correlate them?
I was thinking to correlate them based on the time and pid. If its within the
time range between startup/shutdown and its the same pid, then you have the
event correlated. If its outside the time range or a different pid, then you do
not have correlation. I would not look at selinux label because not all
systems/distros have it enabled or compiled in. So, pid and time are the most
universal identifiers for correlation.
-Steve
next prev parent reply other threads:[~2012-01-24 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 15:56 [PATCH] auvirt: a new tool for reporting events related to virtual machines Marcelo Cerri
2011-12-20 18:18 ` Steve Grubb
2012-01-05 16:44 ` Marcelo Cerri
2012-01-09 17:00 ` Marcelo Cerri
2012-01-11 21:48 ` Steve Grubb
2012-01-13 17:25 ` Marcelo Cerri
2012-01-13 19:23 ` Steve Grubb
2012-01-13 19:45 ` Marcelo Cerri
2012-01-13 20:56 ` Steve Grubb
2012-01-16 13:05 ` Marcelo Cerri
2012-01-16 15:36 ` Steve Grubb
2012-01-11 21:20 ` Steve Grubb
2012-01-24 18:08 ` Marcelo Cerri
2012-01-24 18:33 ` Marcelo Cerri
2012-01-24 20:27 ` Steve Grubb [this message]
2012-01-25 12:56 ` Marcelo Cerri
2012-01-27 16:37 ` Marcelo Cerri
2012-01-27 17:21 ` Steve Grubb
2012-01-27 17:31 ` Marcelo Cerri
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 17:16 Marcelo Cerri
2012-02-03 18:52 ` Steve Grubb
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=201201241527.40706.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=bryntcor@us.ibm.com \
--cc=gcwilson@us.ibm.com \
--cc=linux-audit@redhat.com \
--cc=mhcerri@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.