Laminr Dashboards

5 dashboards

+ New dashboard

Business

Revenue Report

Business view of billable volume from laminr-prod: processed (billable, status=2) vs submitted loan packages per day with support-ticket load overlaid as a cost signal; time-to-processed p50/p95 from the package state history (packages_historicalloanpackage); customer trends (top 14 customers + Other) with counts/share views; and a range-aware top-customers table with share, billable rate, growth vs the prior window, and new-customer badges. Internal/test tenants excluded (Laminr, demo and pentest accounts). Ranges: 7/30/90/180 days. Support tickets from the Open Support Tracker 'Laminr Tickets' tab. Static snapshot captured Jul 18 2026.

Updated Jul 18, 2026

Customer Experience

Customer-satisfaction view of laminr-prod: unique active customers and users per day and per window (with prior-window growth); time to first terminal state (under review OR processed — how fast the customer gets an answer) vs time to final processed; review rate (share of packages needing support review); and support latency (review → processed — the support team's contribution to wait time). Fast processing = happy customer. Internal/test tenants excluded. Ranges: 7/30/90/180 days. State-history coverage begins Apr 13 2026. Static snapshot captured Jul 18 2026.

Updated Jul 18, 2026

Support

Laminr Tickets Dashboard

Laminr Tickets support dashboard: a global timeframe selector (Yesterday / This week [Mon-Fri] / Weekly / Monthly) at the top drives every widget — KPIs, stacked volume, 100% composition, Laminr-errors-over-time (category or parser sub-type), error-rate-in-context vs. loan-package volume, donut, 3-level breakdown, and an Uhura Full Kill incident report. Legend hover highlights the hovered series. Static snapshot: 919 tickets from the Open Support Tracker "Laminr Tickets" tab, Dec 23 2025 -> Jul 17 2026; loan-package volume from Metabase (laminr-prod · packages_loanpackage), captured Jul 18 2026. Data is a fixed snapshot.

Updated Jul 18, 2026

Parsing

Cashflow Check Waterfall

Parser agreement dashboard over waterfall_cashflowcheckresult + waterfall_parser (laminr-prod). The truth parser is per-unit: the last parser that actually ran on that unit (file × account × statement period) — not necessarily the last parser configured in the waterfall. Each earlier parser's attempt is scored against it: MATCH when both pass or when both extract the same cashflow within tolerance (matching numbers on a bad document count as parsing success), MISMATCH when the extracted cashflow differs. Consistent matches per bank = skip-check / early-parser optimization opportunity; consistent mismatches = parser improvement opportunity. Truth-parser failures are user errors (bad documents) — excluded from metrics, shown for volume. Includes waterfall config with fail_on_cashflow flags, bank × parser agreement matrix, and a Today/Yesterday/7/30/90-day range selector. Static snapshot: data since Jul 18 2026, captured Jul 18 2026.

Updated Jul 18, 2026

Waterfall Operations

Operational health of the parsing waterfall from waterfall_waterfallrun, waterfall_waterfalltaskexecution, and waterfall_filepageparser (laminr-prod). Daily run outcomes (completed / failed / cancelled) with average run duration and stuck-retry counts; per-parser task execution performance (volume, failure rate, avg/p50/p95 duration, retries, skips); pages parsed per day by parser with count/share views (which parser is actually doing the work — cost view); and task errors by type over time with top parser × error hotspots. Rolling 30-day window with Today/Yesterday/7/30-day range selector. Static snapshot captured Jul 18 2026.

Updated Jul 18, 2026