Exception Reports
Package docs status
Section titled “Package docs status”This page is generated from package source documentation in the Capell packages repository and the checked-in manifest. Source documentation is not distribution status. Before running a Composer command, verify that the exact package and compatible 1.x release are available through public Packagist or the authenticated marketplace account.
| Field | Value |
|---|---|
| Composer package | capell-app/exception-reports |
| Package slug | exception-reports |
| Product group | Capell Operations |
| Tier | free |
| Bundle | operations |
| Runtime contexts | console, shared |
| Capell version | ^1.0 |
| Catalogue role | extension |
| Release channel | Beta |
| Source repository | capell-app/packages |
| Source path | packages/exception-reports |
| Docs source | packages/exception-reports/docs |
| Manifest | capell.json |
What This Plugin Adds
Section titled “What This Plugin Adds”Exception Reports is an Available, Schema-owning Capell package in the Capell Operations product group. It ships as capell-app/exception-reports and extends these surfaces: console, shared.
Exception Reports queues sanitized unhandled-exception reports to configured email recipients and optional signed webhook endpoints, with rate limiting and grouped digests.
Operators receive a sanitized email or webhook payload for triage. The package has no admin resource; recipients, privacy options, and delivery behavior are configured at application level.
Status details:
- Status: Available
- Tier: free
- Bundle: operations
- Composer package:
capell-app/exception-reports - Namespace:
Capell\ExceptionReports - Theme key: not applicable
Why It Matters
Section titled “Why It Matters”For developers: A typed report boundary and sanitizer keep request secrets out of queued payloads, while trace, identity, IP, and route-parameter details remain opt-in.
For teams: Operational failures reach the configured owner with enough context to start triage, and repeated signatures can be rate limited or summarized instead of producing duplicate alerts.
Screens And Workflow
Section titled “Screens And Workflow”Screenshot contract: docs/screenshots.json.
- Exception Reports extension card (marketplace, supplementary documentation fixture).
- Illustrative exception reports rendered email preview preview (frontend, supplementary documentation fixture).
Technical Shape
Section titled “Technical Shape”Service providers
Section titled “Service providers”Capell\ExceptionReports\Providers\ExceptionReportsServiceProvider
Config files
Section titled “Config files”packages/exception-reports/config/capell-exception-reports.php
Migrations
Section titled “Migrations”packages/exception-reports/database/migrations/2026_08_22_000001_create_exception_reports_table.phppackages/exception-reports/database/migrations/2026_09_29_120000_remove_implicit_timestamp_updates_from_exception_reports.php
Models
Section titled “Models”ExceptionReport
Actions
Section titled “Actions”QueueRateLimitedExceptionDigestActionRecordExceptionReportActionReportExceptionByEmailActionSendExceptionReportWebhookAction
Data objects
Section titled “Data objects”ExceptionReportDataResolvedExceptionReportWebhookEndpointData
Manifest action API
Section titled “Manifest action API”recordExceptionReport: Capell\ExceptionReports\Actions\RecordExceptionReportActionreportExceptionByEmail: Capell\ExceptionReports\Actions\ReportExceptionByEmailAction
Manifest contributions
Section titled “Manifest contributions”health-check: Capell\ExceptionReports\Health\ExceptionReportsHealthCheckmigration: Capell\ExceptionReports\Manifest\ExceptionReportsMigrationsContribution
Health checks
Section titled “Health checks”Capell\ExceptionReports\Health\ExceptionReportsHealthCheck
Blade views
Section titled “Blade views”packages/exception-reports/resources/views/mail/reported.blade.php
Data Model
Section titled “Data Model”- Required tables:
exception_reports. - Models:
ExceptionReport. - Migration files:
2026_08_22_000001_create_exception_reports_table.php,2026_09_29_120000_remove_implicit_timestamp_updates_from_exception_reports.php. - Migration impact: run host migrations through the package install flow before opening package surfaces.
- Deletion/retention behaviour: Docs gap: migrations and manifest contributions do not prove a cascade, pruning command, or timed retention policy.
Install Impact
Section titled “Install Impact”- Required packages:
capell-app/core. - Admin navigation: no admin page or resource contribution is declared.
- Admin/editor extensions: none declared.
- Permissions: no package permission declarations or Shield gates detected; host access rules still apply.
- Public routes: none declared.
- Database changes: package migrations are declared.
- Config:
config/capell-exception-reports.php. - Settings: no package settings declared.
- Queues or schedules: none declared.
- Cache tags: none declared.
- Commands: none declared.
Common Pitfalls
Section titled “Common Pitfalls”- Keep required Capell packages on compatible v4 releases:
capell-app/core. - Run migrations before opening package resources or public routes.
- Review package configuration before production-like verification:
config/capell-exception-reports.php.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Check | Fix |
|---|---|---|---|
| Package surface is missing after install | Provider or manifest is not loaded | Confirm capell.json, package composer.json, and provider registration | Reinstall the package, refresh Composer autoload, and clear host caches |
| Admin screen or command fails on missing table | Package migrations have not run | Check the tables listed in Data Model | Run host migrations and rerun the focused package test |
Quick Start
Section titled “Quick Start”- Install the package:
composer require capell-app/exception-reports. - Verify the package provider and manifest contributions are registered in the host app.