Historical Incident Search And Replay

via “request history tracking and replay”

Lightweight REST API client with GUI.

Unique: Implements automatic request history as a sidebar panel feature (not a separate modal), making it discoverable and accessible without context-switching, with one-click replay that loads the request back into the editor for modification

vs others: More discoverable than Postman's history because it's always visible in the sidebar, but lacks advanced filtering and export capabilities for audit/documentation purposes

via “historical-incident-search-and-replay”

Hi HN, I'm Robel. I built LogClaw because I was tired of paying for Datadog and still waking up to pages that said "something is wrong" with no context.LogClaw is an open-source log intelligence platform that runs on Kubernetes. It ingests logs via OpenTelemetry and detects anomalies

Unique: Combines searchable incident archive with replay capability, allowing users to not only find past incidents but also re-run detection logic on historical logs to validate rule changes without waiting for new incidents

vs others: More useful than simple log archival because it indexes incidents and allows replay, enabling faster post-mortem analysis and rule validation vs. manually searching raw logs

via “historical event search and filtering”

via “historical log search and analysis”

via “incident-history-retrieval”