Audit logs arrive in every shape — comma dumps from databases, pipe-delimited SIEM extracts, space-padded syslog-style lines, tab-separated exports from some internal tool nobody remembers the name of. Audit Log Formatter takes a field list and a delimiter, then restructures every line into a named, column-aligned table you can actually read at a glance, without writing a parser.
You define the field names once, in the exact order they appear in each line, and pick the delimiter that splits your input: comma, pipe, tab, or one-or-more whitespace characters. Each raw line is split on that delimiter and its parts are assigned in order to your named fields, so a five-field pipe-delimited line becomes a record with five clearly labeled columns instead of an anonymous list of values you have to count by hand. Fields where the value is a bare 10-digit number — the classic Unix epoch-seconds timestamp — are automatically converted to ISO 8601 UTC when the epoch option is on, while every other value, whatever field it lives in, passes through completely unchanged, so nothing you did not ask to be touched gets silently rewritten.
The same parsed records export cleanly in three shapes: a padded, column-aligned plain-text table for reading in the browser, a CSV file with a header row and proper quoting for values containing commas or quotes, or newline-delimited JSON (JSONL) with one JSON object per record for piping straight into a downstream ingestion tool. Lines that split into more or fewer fields than your field list are never silently dropped or mis-assigned — they are pulled out and reported separately, with their line number, the field count actually found, and the raw text, so a malformed record is something you notice and fix rather than something that quietly corrupts a column downstream.