From: "Wyatt, Curtis R" <Curtis.Wyatt@gd-ms.com>
To: "leamhall@gmail.com" <leamhall@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: RE: Audit log compression
Date: Thu, 28 Jun 2018 16:20:54 +0000 [thread overview]
Message-ID: <fcacbbd482cc49098d1d9cedeb1a12b4@AZDC-MMB02.GD-MS.US> (raw)
Our audit.rules file is governed by requirements, so we cannot reduce the amount of log data being generated.
>logrotate can be configured nicely. First big step is looking at
>what's going into the logs though. Are you logging at INFO level and
>do you need that. I've seen that be 90% or more of the log entries.
next reply other threads:[~2018-06-28 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 16:20 Wyatt, Curtis R [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-27 17:11 Audit log compression Wyatt, Curtis R
2018-06-27 17:14 ` leam hall
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=fcacbbd482cc49098d1d9cedeb1a12b4@AZDC-MMB02.GD-MS.US \
--to=curtis.wyatt@gd-ms.com \
--cc=leamhall@gmail.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