Forwarding audit logs

Last published : Jun 19, 2026
An audit log includes records of user actions on the CMS, like signing in, signing out, refreshing a host, creating volumes, and so on. This release introduces the Audit Log Forwarding feature, which lets you add the audit logs at specific intervals to the /var/log/messages/syslog file on the local server or on a remote server. You can enable or disable this scheduled activity from the Settings perspective of a Arctera InfoScale Operations Manager Management Server. You can optionally specify the IP address or the name of a specific server where you want these logs to be forwarded.
Note: This feature is applicable to Arctera InfoScale Operations Manager management servers on Linux only.
To access audit log forwarding settings
  1. On the Arctera InfoScale Operations Manager management console, open the Settings perspective.
  2. Click Management Server ; the Server settings tab appears by default.
  3. Scroll down to locate the Audit Log Forwarding Settings section.
    image
By default, audit log forwarding is disabled.
To enable audit log forwarding
  1. Select the Enable audit log forwarding check box.
  2. Use the Audit Log(Min) drop-down list to select the time intervals at which to forward the latest audit logs.
At each scheduled interval, the audit logs that are collected since the last instance are added to /var/log/messages/syslog.
  1. (Optional) To forward the audit logs to a different server, enter the appropriate server name or IP address in the Server IP/Name text box.
    Note: When you specify a server name or IP address, the/etc/rsyslog.conffile gets updated with the that value. The audit logs are then added to the/var/log/messages/syslogfile on both, the CMS and the specified server.
  2. Click Save Settings.
An information message confirms that the change is saved.
To disable audit log forwarding
  1. Deselect Enable audit log forwarding.
  2. Click Save Settings.
An information message confirms that the change is saved.