From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Miloslav Trmač" <mitr@redhat.com>
Subject: Re: log rendering in real time in audit-viewer
Date: Thu, 05 Mar 2015 09:36:58 -0500 [thread overview]
Message-ID: <7202698.dLGuKqTDzG@x2> (raw)
In-Reply-To: <1521044842.29926652.1425491453509.JavaMail.zimbra@redhat.com>
On Wednesday, March 04, 2015 12:50:53 PM Miloslav Trmač wrote:
> Hello,
>
> > Hello Miloslav, and all the guys!
> >
> > We use audit-viewer for events monitoring.
> > Unfortunately, if some log is rather big it takes to much time for
> > audit-viewer to parse and render it.
> > Besides, we need to render log updates in real time, i.e. when a new line
> > appears in a log, it should appear in a viewer too.
> > Can you suggest the better way to extend audit-viewer to meet these
> > requirements?
>
> Well, write the code? Something like inotify could be useful. There isn’t
> any hidden switch to enable these features, if that is what you are asking.
>
> As for performance, I may have missed something but I think I have squeezed
> as much as can be done with Python; improving performance further would
> very likely require a C extension.
And it also uses the auparse library underneath which might could use some
speeding up. There were some performance improvements over the last year. But
I don't know if that is enough to be noticeable in a high level application.
But it would be another obvious place that could be a performance bottleneck.
-Steve
> (audit-viewer is a PyGtk2 application, and at I’m afraid I don’t currently
> have plans to port it to GTK+3/gobject-introspection or do any other
> non-trivial work on the project, at least in the near term.) Mirek
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2015-03-05 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 13:42 log rendering in real time in audit-viewer Xeniya Muratova
2015-03-04 17:50 ` Miloslav Trmač
2015-03-05 14:36 ` Steve Grubb [this message]
[not found] ` <1384025748.230407.1427289658707.JavaMail.zimbra@itsirius.su>
2015-03-25 13:21 ` [PATCH] " Xeniya Muratova
[not found] ` <192757425.240881.1427723539724.JavaMail.zimbra@itsirius.su>
2015-03-30 13:52 ` Xeniya Muratova
2015-03-05 12:45 ` Pittigher, Raymond - Exelis
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 15:26 Arthym Krivo
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=7202698.dLGuKqTDzG@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mitr@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