Configuring Jobstream Administration Audit Logging in AAI 24.x

Products

• Automation Analytics & Intelligence

Issue/Introduction

You need to identify and configure the specific loggers required to track Jobstream administrative activities such as additions, deletions, and updates.​​​​​​​‌​​ and know where to find them in the logs.

 

• Administrative changes to Jobstreams are not appearing in the expected log file.

• Jobstream audit data is mixed with general system logs in jaws.log.

• Confusion between Data Insight scheduled report logging(audit.log) and Jobstream audit logging(jaws.log)

 

Environment

AAI 24.3.x

Resolution

1. IDENTIFY THE CORRECT LOGGER:

   The logger com.termalabs.server.auditlog.AUDIT specifically controls Jobstream adds, deletes, and updates and the logging will be in the jaws.log file.

   NOTE: The logger com.termalabs.server.auditlog only controls scheduled Data Insight Report logging and will be in the audit.log file.

2. CONFIGURE VIA CONFIGURATION TOOL:

   Add or update the following loggers through the AAI configuration interface:

   • com.termalabs.server.auditlog.AUDIT: Set level to DEBUG.
          This logger will show details about "Add Job Stream", "Delete Job Straem", "Update Job Stream" that will include the userId that made the change

   • com.termalabs.server.cache.AdminOperationQueuePolicy: Set level to INFO.
          This logger will display messages like "[AdminOperationQueuePolicy] task started: DELETE_JOB_STREAMS" and "[AdminOperationQueuePolicy] task finished: DELETE_JOB_STREAMS"

   EXPECTED: Jobstream activities will now be logged in the jaws.log file.

3. REDIRECT LOGGING TO AUDIT.LOG (OPTIONAL- NOT RECOMMENDED as updates to configuration tool could overwrite this configuration):

   To route audit activities to audit.log instead of jaws.log, manually edit the log4j2.yml file:

   Location 1: com.termalabs.server.auditlog.AUDIT Change AppenderRef from JawsFile to AuditFile.

   Location 2: com.termalabs.server.cache.AdminOperationQueuePolicy Change AppenderRef from JawsFile to AuditFile.

   EXPECTED: After restart, Jobstream activities will route to audit.log.

4. RESTART AAI SERVICE:

   Restart the AAI application to apply any manual yml changes.

VERIFY SUCCESS:

• Check jaws.log (or audit.log if redirected) for "[AUDIT]" tags.

• Verify "Add Job Stream" or "Delete Job Stream" entries appear.

• Confirm AdminOperationQueuePolicy shows "task started" and "task finished" for operations.

Additional Information

By default, Jobstream audit logging is directed to jaws.log. The audit.log introduced in 24.x is intended for Data Insights and does not capture Jobstream activities unless manually reconfigured.