Logging in StorageLink

TLDR

Purpose: Find the StorageLink log files for troubleshooting, user activity, and license events

Log Files:

• /opt/swiftgw/log/application-*.log — Java application events and errors
• /opt/swiftgw/log/audit-*.log — user actions and authentication
• /opt/swiftgw/log/license-audit-*.log — license events such as activation, expiry, and cluster binding (new in 1.3.0)
• /var/log/swiftgw/cloudinit.log — server issues at first launch

Retention: Logs in /opt/swiftgw/log/ are kept for 30 days or 3 GB, whichever comes first

Forwarding: 1.3.0 marketplace images send the license-audit log to CloudWatch or Google Cloud Logging with the other logs. After an in-place upgrade, add it to the log agent configuration. On Azure, collect all three logs with the Azure Monitor Agent.

Containers: All three streams go to standard output as JSON, tagged application, audit, or license-audit

Product: StorageLink by Thorn Technologies — cloud storage gateway for secure file sharing

Overview

This article covers the various log files used by StorageLink.

Log file locations

These are the logs of interest when troubleshooting StorageLink:

/opt/swiftgw/log/application.log
/opt/swiftgw/log/audit.log
/opt/swiftgw/log/license-audit.log
/var/log/swiftgw/cloudinit.log

info

The Application and Audit logs have the date included in their name.

The log files within /opt/swiftgw/log/ have a retention of 30 days, or 3 GB (whichever of these comes first).

And this is what these logs do:

• application.log: Java events and errors.
• audit.log: User actions and authentication.
• license-audit.log: License events — activation, replacement, expiry, binding to the cluster, user-cap import skips and activation rate limiting. New in StorageLink 1.3.0; kept separate from the audit log so compliance records and user file activity do not interleave.
• cloudinit.log: Server related issues that happen at first launch

Forwarding the license-audit log

Instances launched from a 1.3.0 marketplace image forward license-audit-*.log to CloudWatch or Google Cloud Logging alongside the application and audit logs. An instance upgraded in place writes the file locally but does not forward it until you add it to the log agent configuration. On Azure, the Azure Monitor Agent article collects all three logs and shows how to add the license-audit log to an existing setup.

Container deployments write all three streams as JSON on standard output, each line tagged application, audit or license-audit; see the Container Deployment Reference.