As a user, I would like to know how I can make use of the Kylo Audit capabilities
From Scott Reisdorf [3 months ago]
Kylo tracks audit changes to Feeds and Templates in the kylo.AUDIT_LOG table.
Job execution changes (i.e. Fail/Abandon a job) and alert changes (i.e. handle/clear an alert) are tracked in Kylo and are stored with the entity and viewed at the Job Execution or Alert page
NiFi tracks all changes to its templates (not sure about deletes), but you can view all processor/services changes in NiFi or via the REST api. Note when changing via Kylo, we use a single REST service account to login and update NiFi so the user it will be the same single user that is making the changes in NiFi's audit log.
If you need to add other change activity you could do so and possibly tie into Kylo's Event mechanism and upon the save/update of an entity do something else with it.