Feature #6752
Audit Log File
Description
The Audits page is extremely useful in the web interface but it would be even more useful if that same information was written out to a log file as well. That way one can pipe those logs into Splunk or LogStash etc and create searches, dashboards, alerts and open up auditing to a wider audience without having to give access to Foreman.
Related issues
Associated revisions
History
#1
Updated by Dominic Cleal almost 8 years ago
- Bugzilla link set to 1155817
#2
Updated by Tomer Brisker over 4 years ago
- Has duplicate Feature #22159: Whenever an audit is created, it should create a log entry with the information added
#3
Updated by Marek Hulán over 4 years ago
- Related to Tracker #21879: [TRACKER] Audit every possible resource added
#4
Updated by Marek Hulán over 4 years ago
The logger should be disabled by default, but it would be great to have a way to keep audit information in logs.
#5
Updated by Lukas Zapletal over 4 years ago
Note we already have logger called "audit", there are few messages sent during fact import. Please use that logger and turn it into official audit logger.
#6
Updated by The Foreman Bot over 4 years ago
- Assignee set to Marek Hulán
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5391 added
#7
Updated by Lukas Zapletal over 4 years ago
- Legacy Backlogs Release (now unused) set to 330
#8
Updated by Anonymous over 4 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset be933765ac7a925d63cdea48652f6079c0425313.
#9
Updated by Lukas Zapletal about 4 years ago
- Related to Refactor #23610: Log audits per changed column added
Fixes #6752 - log audit events (#5391)