Skip to content

Administration

How to continuously upload logs from the LogMan.io archive to S3 storage

The LogMan.io Receiver keeps an immutable copy of every raw log in its archive. The archive is your long-term store, but it does not keep data forever: by default, partitions are deleted from the cold phase after 18 months. If you need to retain raw logs longer, i.e. for compliance, forensics, or as an off-site copy, the simplest approach is to continuously upload the archive to S3-compatible object storage.

This guide describes a one-way, scheduled sync from the receiver cold phase to an S3 bucket using the AWS CLI. The same procedure works with AWS S3 and with S3-compatible providers such as Oracle Cloud Object Storage.

Forwarding system tenant logs to a central LogMan.io

This guide describes how to forward logs from the system tenant on a satellite TeskaLabs LogMan.io deployment to a supersystem tenant on a central TeskaLabs LogMan.io system.

The satellite keeps collecting and processing its own system logs. In parallel, LogMan.io Integration Service (lmio-integ) forwards raw events over TCP to a dedicated LogMan.io Collector on the satellite. That collector is provisioned to a receiving tenant on the central system (recommended name: supersystem) and ships the data over CommLink.