[katello] Auditing metadata changes

A broad auditing question while I wait for the next MDP drop of Katello.

When metadata changes on a host/system, is everything fully audited. I ask
because whilst there is some good auditing in Satellite 5.x, there are some
big holes in there too. e.g. Group changes and Config channel subscription
changes don't show up in the Events list for a system, whereas Software
Channel changes do.

I'm just hoping that this area of auditing is well covered so that the
history of a host/system can be tracked accurately and we can pull out when
changes were made, state before, state after, who applied the change etc.

Is it worth having a ticket for this if it's not been part of plans at this
point?

Cheers

Duncan

Hi,

There are two systems that track the changes/actions in the Foreman/Katello:

Audits: - (Monitor -> Audits) the Foreman's auditing system based around the data in the Foreman's
database, I'm not sure every change at Foreman side is tracked by this (for example,
adding a location/organization to smart proxy was not shown there)

Tasks - (Monitor -> Tasks) This is build around the foreman-tasks and since
Katello uses foreman-tasks/dynflow extensively, you should be able to
see all (although there are still some actions waiting for move to
the foreman-tasks).

The main difference I see between these two is AFAIK, the Audits are more
connected to chagnes in the database, while tasks are more oriented on the user
actions (one of the reasons why audits don't work with Katello very well
is that some actions change the data outside of the Katello database
or don't change data at all: installation of a package is not exactly a change
in databse), and I don't know how hard it would be to do audits for things, that
are not rrelated directly to database changes.

On the other hand, creating tasks for things that don't require Dynflow
is a question few lines and we could probably combine the two approaches,
using the benefits of the audits tracking the before/after values in database
for showing details of the tasks that can be connected to this audits.

Definitely something that deserves a ticket and dedicated resources

– Ivan

··· ----- Original Message ----- > A broad auditing question while I wait for the next MDP drop of Katello. > > When metadata changes on a host/system, is everything fully audited. I ask > because whilst there is some good auditing in Satellite 5.x, there are some > big holes in there too. e.g. Group changes and Config channel subscription > changes don't show up in the Events list for a system, whereas Software > Channel changes do. > > I'm just hoping that this area of auditing is well covered so that the > history of a host/system can be tracked accurately and we can pull out when > changes were made, state before, state after, who applied the change etc. > > Is it worth having a ticket for this if it's not been part of plans at this > point? > > Cheers > > Duncan > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

Where should I post a ticket Ivan?

Cheers

D

··· On Wednesday, 4 June 2014 13:20:27 UTC+1, Ivan Necas wrote: > > > Definitely something that deserves a ticket and dedicated resources > > -- Ivan > > >

Foreman should do it

Greg

··· On 9 June 2014 08:56, Duncan Innes wrote: > Where should I post a ticket Ivan?

I would say Foreman, as this not limited to the content management.

– Ivan

··· ----- Original Message ----- > On 9 June 2014 08:56, Duncan Innes wrote: > > Where should I post a ticket Ivan? > > http://projects.theforeman.org/projects/katello/issues/new should do it > > Greg > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >