Autobricks Log 0.2.31 (linux)

Autobricks Log stores selected rsyslog messages as daily log files on the
Autobricks WORM filesystem.

Packages

Choose the package matching the Ubuntu release and CPU architecture:

• Ubuntu 22.04 amd64
• Ubuntu 22.04 arm64
• Ubuntu 24.04 amd64
• Ubuntu 24.04 arm64

Installation

Download the matching .deb file and install it with APT:

sudo apt-get update
sudo apt-get install ./autobricks-log-0.2.31-ubuntu-24.04-amd64.deb

During installation, select:

1. the private SOURCE directory used for WORM backing data;
2. the system-wide retention period in days.

The package installs /usr/bin/ablog and enables ab-worm.service and
autobricks-log.service. The fixed WORM mount is /mnt/worm-storage.

Verify the installation:

sudo ablog check
systemctl status ab-worm.service autobricks-log.service rsyslog.service
findmnt /mnt/worm-storage

Route program logs

Applications continue to use the normal syslog API. Configure rsyslog to send
only selected program names to Autobricks Log. For example, an rsyslog omprog
action for example-service uses:

if $programname == "example-service" then {
    action(
        type="omprog"
        binary="/usr/bin/ablog ingest example-service"
        confirmMessages="on"
        action.resumeRetryCount="-1"
        queue.type="Disk"
        queue.filename="autobricks_log"
        queue.saveOnShutdown="on"
    )
}

Use the complete template and queue configuration in HOWTO.md. Validate and
restart rsyslog after making changes:

sudo rsyslogd -N1
sudo systemctl restart rsyslog.service

Send a test message:

logger --tag example-service --priority local0.notice \
    "policy decision completed"

The daily file is created as:

/mnt/worm-storage/example-service/ablog-YYYY-MM-DD.log

Verify stored files with:

sudo ablog verify example-service

See INSTALL.md, HOWTO.md, and README.md for the complete installation,
sshd-only routing, storage, retention, and removal instructions.