Memory & Forever Logs

When you create an issue from a log entry, Loguro saves that log (and its context) to a permanent memory store. These logs never expire — they outlast your plan’s retention window and remain searchable indefinitely.

Why memory exists

Log retention is finite. A 14-day retention window means an error from three months ago is gone from the live stream. But if you filed a ticket for that error, you probably want to know if it comes back — even a year later.

Memory solves this. The logs that matter (the ones tied to real issues) are preserved forever.

How logs get written to memory

Memory is written automatically in two situations:

Issue creation — when you run --task:jira|linear|github, the associated log(s) are written to memory alongside the issue key.
Pattern match — every new log is checked against existing pattern keys. If the message fingerprint matches a known issue, the new log is also written to memory and linked to that issue.

Pattern deduplication

Loguro computes a pattern key from each log’s message — a normalized fingerprint that strips variable parts (IDs, timestamps, values). Two logs with messages like:

Payment failed for order ord_9xk2
Payment failed for order ord_4ab1

…produce the same pattern key. Once the first is linked to an issue, the second is automatically recognized as the same problem and marked accordingly.

This means the issue key appears inline in the console next to any log matching that pattern — even if the original log has aged out of retention.

Searching memory

Use --memory to switch the log source to memory:

--memory
--memory --count
message:"payment failed" --memory
level:error --memory @last-90d

All standard filters work. The results come from the memory Parquet store instead of the live log pipeline.

What you see in memory

The original log(s) attached to the issue at creation time
All future logs that matched the same pattern key
The issue key linked to each log (e.g. ENG-42, #123)

Memory and issue status

Issue statuses sync automatically every 5 minutes. If an issue is closed in Linear/Jira/GitHub, logs in memory are still accessible — the status just updates to reflect the tracker state.

Notes

Memory is not a replacement for retention — it’s a supplement for logs that matter
Only logs tied to created issues enter memory; general logs do not
Memory is project-scoped
See —memory command for the filter bar syntax
See Issue Tracker Integration for setup