Project

General

Profile

Actions
Copy link

Feature #3861

closed

Better logging/reporting/audit of provisioning including contents

Added by Lukas Zapletal over 10 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Audit Log
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Currently reports only contains Puppet reports. It might be interesting to extend them and allow reporting of provision information - host was booted, anaconda started with installation etc. Along with that, we should be able to provide extra details for a report line, where we could store whole template generated (only visible to users with permissions), which could make investigation easier.

Related issues 4 (0 open — 4 closed)

Related to Discovery - Feature #3862: Audit discovery of new host and provision actionsClosedLukas Zapletal12/12/2013Actions
Related to Foreman - Feature #746: Generate all the Host template when click on Build to avoid errors during installationClosedShlomi Zadok03/15/2011Actions
Related to Foreman - Feature #22493: Add new logging options to integrate with logging-journald gemClosedLukas Zapletal02/02/2018Actions
Is duplicate of Foreman - Feature #13674: Provisioning Templates successful build time stampDuplicate02/11/2016Actions
Actions
Copy link
 #1

Updated by Lukas Zapletal over 10 years ago

  • Related to Feature #3862: Audit discovery of new host and provision actions added
Actions
Copy link
 #2

Updated by Lukas Zapletal about 9 years ago

  • Related to Feature #746: Generate all the Host template when click on Build to avoid errors during installation added
Actions
Copy link
 #3

Updated by Lukas Zapletal about 9 years ago

Everytime we render a template, we should put it's contents to audit as well.

Actions
Copy link
 #4

Updated by Lukas Zapletal about 7 years ago

  • Is duplicate of Feature #13674: Provisioning Templates successful build time stamp added
Actions
Copy link
 #5

Updated by Lukas Zapletal about 7 years ago

  • Status changed from New to Duplicate
Actions
Copy link
 #6

Updated by Lukas Zapletal about 7 years ago

  • Subject changed from Better logging/reporting/audit of provisioning to Better logging/reporting/audit of provisioning including contents
  • Bugzilla link set to 1299024

Including whole content of provisioning templates raises question around security (there's root password). We need to solve that first.

Actions
Copy link
 #7

Updated by Dominic Cleal about 7 years ago

Why are both this and #13674 marked as duplicates? Are they duplicates of a third issue number?

Actions
Copy link
 #8

Updated by Lukas Zapletal almost 7 years ago

  • Status changed from Duplicate to New

It was marked as duplicate as mistake, this is a valid RFE.

Actions
Copy link
 #9

Updated by Lukas Zapletal almost 6 years ago

  • Bugzilla link deleted (1299024)
Actions
Copy link
 #10

Updated by Lukas Zapletal almost 6 years ago

  • Related to Feature #22493: Add new logging options to integrate with logging-journald gem added
Actions
Copy link
 #11

Updated by Lukas Zapletal almost 6 years ago

  • Category set to Audit Log
  • Status changed from New to Resolved
  • Assignee set to Lukas Zapletal

This was implemented as #22493 - all templates contents can be configured to appear in production.log or syslog/journald and this can be further integrated with 3rd party logging solutions. Logger named "blob" must be enabled and the following fields are available: template_digest, template_name, template_context, template_host_name and template_host_id.

Actions
Copy link

Also available in: Atom PDF