On Monday, June 27, 2016 at 12:34:34 AM UTC-7, Dominic Cleal wrote:
>
> On 24/06/16 00:08, Thomas Cheng wrote:
> >
> >
> > On Thursday, June 23, 2016 at 2:55:38 PM UTC-7, Christopher Pisano
> wrote:
> >
> > I have a clustered setup as well and somewhere around 1.10-ish even
> > though settings like unattended url and the like are the same on
> > each of my nodes in the config file and set through the UI I still
> > get that they have been changed in the Audit log. I haven't had time
> > to dig into it yet though. . . really busy with other stuff and it
> > doesn't seem to be impactful.
> >
> > Agree. The major effect is that human changes (needed to be audited) are
> > immersed in these messages.
> >
> > I can select, have a pick, these audited messages with the following
> > command:
> >
> > mysql> select * from audits where auditable_type='Setting' and
> > action='update' and auditable_name in ('unattended_url', 'ssl_priv_key',
> > 'ssl_certificate', 'foreman_url') and audited_changes like '%default:%'
> > limit 3\G
> >
> > So, question is: is it safe to remove/purge the above audited messages
> > (generated by Foreman itself) with 'mysql delete ...'? any other tables
> > or foreman codes refer to some fields of this table, directly or
> > indirectly? Thanks a lot.
>
> Yes, it should be safe to remove these.
>
> Great. I'll setup a cron to clean it from time to time. Thanks for
confirmation.
> --
> Dominic Cleal
> [email protected] <javascript:>
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
