Goal

• Each system role should write its fingerprint to the system journal log in order to identify role usage on managed nodes
  • The system roles team would like to identify customer usage - which roles are being used? How often are they being used?
  • The system journal is collected by SOS reports. We could extract system roles usage from those reports

We already use a fingerprint like "system_role:ROLENAME" for some of our system roles that manage config files, but 1) some roles do not manage config files directly (e.g. using apis/dbus to manage config), or do not manage files at all 2) not all of the files managed by system roles are collected by sosreports or insights.

We could have a task that runs as the first thing in the role tasks/main.yml - all it does is write a fingerprint message like "system_role:ROLENAME" to the system journal. Maybe another task that runs at the end of the role so that we could measure role duration.

We may have to adjust the fingerprint message to make it more unique if "system_role:" returns too many hits when searching the log.

Acceptance criteria

• Verify that the fingerprint string is easily searchable in journal logs
• All system roles write a fingerprint
• All system roles have a test to verify the fingerprint - we could add this to each role tests/tests_default.yml