Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Audit Logs Overview

An audit log is a record of a sequence of activities that have affected a specific operation or procedure. Audit logs are useful for tracing events and for maintaining historical data.

Audit logs contain information about tasks that are initiated by using the Paragon Automation GUI or APIs. In addition to providing information about the resources that are accessed, audit log entries usually include details about user-initiated tasks, such as the name of the user who initiated a task, the status of the task, and date and time of execution.

Audit logs from microservices, such as healthbot command and config server are collected in the audit log client library, and are stored in the Postgres SQL database. The audit log client library is installed with microservices during Paragon Automation installation.


Device-driven tasks (that is, tasks not initiated by the user) are not recorded in audit logs.

Paragon Insights Commands and Audit Logs

Starting with Paragon Automation Release 21.2, audit logs are generated when you run the following commands from the CLI:

  • add-node
  • remove-node
  • modify-uda-engine
  • modify-udf-engine
  • modify-workflow-engine
  • remove-plugin
  • load-plugin

The audit log generated will include information on who initiated the job, node name, and status of the job. However, with Release 21.2, you must enter credentials (username and password) to run the commands. If you have already set a username (HB_USERNAME) and password (HB_PASSWORD), you are not prompted to enter credentials when you run a command.