Follow three local service logs live with Flik 0.3.0
The API reports a timeout. The worker reports a retry. The authentication service has the first event in the sequence. When those events live in separate local files, following each file independently makes the sequence harder to inspect. Flik 0.3.0 adds live multi-file merge and a three-column view. Here is a small, synthetic example you can reproduce without connecting a cloud account or…
The API reports a timeout, while the worker service generates a retry event. The authentication service initiates the sequence by reporting the first event. To inspect the sequence, individual events are stored in separate local files. Flik 0.3.0 introduces live multi-file merging and a three-column view for enhanced inspection.
To demonstrate the functionality, download the archive for your operating system and SHA-256SUMS file. Compare the SHA-256 hash of the downloaded archive before extracting it. Run 'flik --version' to confirm that the correct version is installed. Create three local input files representing the authentication, API, and worker services:
1. auth.log: 2026-11-12T09:59:59Z INFO request=req-42 token_validated
2. api.log: 2026-11-12T10:00:00Z INFO request=req-42 accepted, 2026-11-12T10:00:03Z ERROR request=req-42 upstream_timeout
3. worker.log: 2026-11-12T10:00:01Z INFO request=req-42 job_started, 2026-11-12T10:00:02Z WARN request=req-42 retry_scheduled
Use the command 'flik -m api.log worker.log auth.log' to follow the events from these files. The events will be merged in a three-column view, with the authentication event first, followed by the API and worker events. Additional events can be added to test the layout in a wide terminal.
The merged file is continuously updated as new events arrive, without reordering previous output. The temporary combined file grows while following the input files. However, truncation is possible if the file size decreases, potentially missing events. The merged file is not a distributed clock reconciliation mechanism.
For accurate results, start with small representative inputs, especially if your services frequently rotate logs. Keep the source labels visible and report any specific ordering or labeling issues with a small synthetic fixture, mentioning your operating system and the version of flik. Do not attach any private production logs.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.