Request-log file

Append every request line as JSONL.

What it is Appends the per-request log line to a JSONL file on local disk.

When to use it A log agent (Fluent Bit, Vector, the platform’s own) already tails files on the box.

CategoryExporter StatusAvailable Built-inNo install step

Overview

The request-log file exporter writes the same per-request JSON line the webhook sink pushes, appended to a file as JSONL (one object per line) for the log agent already running beside Busbar.

Like every other exporter it is a DISTRIBUTION sink only: core builds the projection, this module just ships it. Appends are serialized per instance so two concurrent requests never interleave a line, and each instance carries its own in-flight cap: on a full disk or a hung NFS/EBS mount, lines are shed and counted rather than accumulating a blocked thread and an owned string per request.

Name two instances and you get two files (a local tail file and an audit mount, say), each with its own path, its own rotation setting, and its own cap: a stalled audit mount cannot shed the local file’s lines.

Turn it on

Compiled into the core binary; nothing to download. Name an instance under the top-level export: map:

export:
  req-log-file:
    module: request-log-file
    streams: [logs]
    settings: { path: /var/log/busbar/requests.jsonl, rotate_mb: 512 }

The map KEY (req-log-file) is the instance name; module: is which exporter backs it. Omit rotate_mb and the file is never rotated by Busbar; leave rotation to logrotate if that is what you already run. New in busbar 1.5.3.

Settings

Setting	Required	Default	Description
`path`	Yes	—	The JSONL file each request-log line is appended to.
`rotate_mb`	No	—	Size in MiB at which the file is rotated, best-effort. Absent means never rotate, so hand the file to logrotate instead.

Built into the core: configured under export:, never downloaded.

← Back to the Plugin Store