Migration guide

Move historical or live logs into LoggerMan from other providers.

Papertrail

Export events from Papertrail (search → Save Search → download as JSON or use their API). Map each event to a LoggerMan ingest payload:

  • message ← event message
  • source ← hostname or program
  • level ← map severity (e.g. error → ERROR)
  • metadata ← remaining fields (timestamp, facility, etc.)

POST in batches of up to 100 via /api/projects/:id/logs/batch with your Bearer token.

Logtail (Better Stack)

Export logs from the Logtail UI or query API, then transform to LoggerMan batch format. Preserve metadata.traceId if present for correlation after cutover.

Self-hosted JSON

If you have newline-delimited JSON or an array export:

  1. Normalize each row to message, optional type, source, metadata.
  2. Use the SDK sendBatch or the batch HTTP endpoint.
  3. Throttle to your plan ingest rate — watch X-RateLimit-Remaining.

Cutover strategy

Run dual-write for a few days: keep the old sink and add LoggerMan via SDK or syslog forwarder. Compare volume in Analytics before disabling the legacy pipeline.