Exporting Business Metrics¶
Export your business metrics in CSV, XLSX, or PDF for analysis, reporting, or sharing.
Business Metrics focus on value delivered — time saved, money saved, errors fixed. For the per-event record of what happened on your targets and errors (approvals, applies, rollbacks, automation toggles), see Audit Logs. For AI tokens and cost, see Usage Analytics.
What can be exported?¶
Business metrics focus on value delivered, for example:
- Time saved — hours and daily averages
- Money saved — from time saved × hourly rate (where configured)
- Error statistics — fixed, failed, rolled back, manual fixes (suggestion / own code), Ignored after reject, Not patchable, Ready to Patch, pending, and totals
- Performance — confidence, success rate, resolution rate, manual burden
- Breakdowns — error sources, Patcherly MTTR (success-only) and Manual MTTR (Settings midpoint) by type, severity
Note: Business metrics exports do not include AI usage billing detail. For token/cost usage, see Usage Analytics.
How to export¶
Step 1: Open Metrics¶
- Go to Metrics in the main menu.
Step 2: Apply filters (optional)¶
- Date range — preset or custom
- Target — one or more targets
- Domains, error types, severities, language, framework, workflow outcomes — when your workspace shows these filters
Fix outcomes export¶
On the Metrics page, Export fix outcomes downloads a CSV of per-error terminal outcomes (success, manual_fixed_suggestion, manual_fixed_own, unresolved_after_reject, rolled back, etc.) for the selected date range and filters. Columns include terminal_outcome, patch_outcome, resolution_path (reject_patch or mark_fixed where applicable), and prompt_version (template-body hash when analysis stamped it). Per-row detail is available for roughly the last 90 days of raw metric events; headline KPI cards on the same page may still reflect longer periods. Requires Advanced analytics on your plan.
Step 3: Choose format (aggregate export)¶
- Click Export.
- Choose CSV, XLSX, or PDF.
- The file downloads (name is based on the date range and format).
Formats¶
- CSV — spreadsheets and tools; plain data.
- XLSX — Excel-friendly workbook with formatting.
- PDF — easy to share or print.
Tips¶
- Apply filters before exporting so the file matches what you see on screen.
- Use CSV for further analysis; PDF for stakeholders.
- Export on a schedule that fits your reporting (weekly/monthly).
Understanding exported data¶
Time saved¶
Based on configured estimates for human vs AI fix time for each error type, compared to what actually happened in the period.
Money saved¶
Money saved = time saved (hours) × hourly rate (from your profile or workspace defaults, where configured).
Success rate¶
Success rate = successful fixes ÷ fix attempts (in the selected period and filters).
Error resolution rate¶
Resolution rate = AI-fixed errors (success terminal) ÷ errors detected (in the selected period and filters).
Ignored vs Ignored after reject¶
Aggregate exports include an Ignored row (errors_ignored) for hide-style rollup counts in the period. That is not the same as:
- Ignored after reject (
errors_unresolved_after_reject) — reject patch → not needed after analysis (its own export row and Metrics card) - Live error status Ignored on the Errors page — Hide / reject-not-needed workflow state
Pre-analysis Hide and pattern-matched ingest ignores do not appear in unique totals the same way as apply outcomes.
Related topics¶
- Understanding metric cards — what each card means and how it's calculated
- Audit Logs — per-event activity record (separate from Business Metrics)
- Usage Analytics — AI token and cost usage
- Data retention on your workspace — Metrics are kept indefinitely; raw error / audit history is pruned by your plan window
- Understanding Errors — error lifecycle
- Introduction — how metrics fit into Patcherly