0.5.0

Know where every issue comes from: which hosts it happened on, what each event was read from, which package and system it came from, and which worker made each decision.

Hosts

• Log errors and out-of-memory kills now get an issue per host, since the same message often has a cause particular to that machine. Crashes and failed units still group across hosts.
• Existing log error and out-of-memory issues are split by host when the server updates. Each keeps the original's state, decisions, labels and suggestions. Their issue IDs change, so old links to them won't work.
• The issue list has a Hosts column and a host filter, and each issue's page shows how many events came from each host, with when it was first and last seen there.
• GET /api/issues?host= filters by host, and GET /api/hosts lists every host with its event and issue counts.

Events

• Hosts now record the package that owns the program, unit file or kernel behind an event, with its version, plus the OS and kernel. Only events from the current boot get these, since older ones could have run different versions. Packages come from pacman. Hosts without it record the OS and kernel only.
• Events carry a source, journal for now. Older events read as journal.
• Each event card shows everything stored about it: host, source, program, unit, executable, signal, result, killed process, package, OS, kernel and boot.

Decisions

• Decisions and suggestions record who asked for them: the worker's name, or server or cli. The issue page shows it. Older ones show as unknown.

Libraries

• Event has a source field (decoded as journal when missing) and optional package and system fields. The API has HostCount, HostSummary and a hosts group, and IssueDecision and IssueSuggestion have by.