Signal LedgerSynthetic + captured data

Overview

Tickets, incidents and partner issues from a service desk, an incident platform and a partner channel, synthetic by default, plus a handful of real incidents captured once from the owner's own Rootly and Jira accounts, unified into one queue. A personal portfolio demo, not a production tool.

  • Correlated automatically. The same underlying problem reported in two different tools gets linked here with a confidence score and the evidence behind it, not just asserted. Real records from Jira and Rootly were linked this way at 97% confidence. See it linked →
  • Short on time? A two-and-a-half-minute narrated walkthrough covers every screen. Watch it →
  • SLA scored per audience. Internal, consumer and partner get separate scorecards and separately-tiered targets, never one blended number. SLA health →
  • Mostly synthetic, a little real. Rows marked Live are genuinely captured from the owner's own trial accounts, replayed rather than fetched live, and never correlated with the invented signals.
  • Everything here is computed, not scripted. Move the threshold slider, edit an SLA target, or add your own source, and the numbers recompute live in this browser. Connect a source →
  • Nothing you change leaves this browser. Dismissals, SLA edits and the change history are local only, hash-chained so what's logged can be checked, not just trusted.
  • Where to go next. This Queue is every signal in one place; Correlation explains why some got linked and some didn't; SLA health scores the three audiences separately; Connect a source proves the architecture is real. For the full build story, the tech stack and every test that passed, see About →

Unified queue

One list across every connected tool. Each signal keeps its source badge; where separate tools are describing the same underlying problem, the row links to the correlation that explains why.

Signals

31

from 6 sources

Correlation groups

5

likely shared root causes

Signals in a group

15

of 31

Standalone

16

deliberately left unlinked

13 real records captured from Jira and Rootly (latest capture 2 Oct 2026, 11:11 UTC) sit alongside the synthetic signals, marked Live. Real and synthetic signals are never correlated with each other.

Showing 5 of 31

  • Partner ChannelPC-304

    Brightwater Foods: request for updated API documentation

    Brightwater Foods · partner api · open 3h 2m

    PartnerLowOpenStandalone
  • Incident PlatformINC-201

    P2 — elevated latency on partner-facing API gateway

    partner api · open 3h 5m

    Supplier (invented): Hollowfen Hosting

    PartnerHighInvestigatingLinked · 5 signals
  • JiraLiveKAN-4

    Intermittent 502s reported via partner integrations hitting the API gateway

    partner api · open 15d 3h

    Source service: db-production-database · mapped to: partner api (title mentions the API or API gateway)

    InternalMediumOpenLinked · 2 signals
  • RootlyLive7

    [Demo] Intermittent DNS resolution failures on the API gateway

    partner api · open 15d 3h

    Source service: db-production-database · mapped to: partner api (title mentions the API or API gateway)

    InternalHighInvestigatingLinked · 2 signals
  • RootlyLive8

    [Demo] Elevated 5xx errors on the public API

    partner api · open for 19h 17m

    Source service: db-production-database · mapped to: partner api (title mentions the API or API gateway)

    InternalHighResolvedStandalone