Integrations
One project key. Browser or PHP.
JavaScript, plain PHP, Laravel, and Symfony post to the same endpoint. Grouping, the issue page, and a Jira rule do not care which client sent the event.
JavaScript error tracking
A script tag on the page. It reports uncaught errors and unhandled promise rejections, keeps recent clicks as breadcrumbs, and can send a release, a user, and tags. Call TraceHawk.captureException for an error you already caught. The key is public, so set allowed origins before production.
PHP error monitoring
tracehawk/sdk 1.1.0 reads TRACEHAWK_DSN. You initialize it, call TraceHawk::capture for an exception, and call TraceHawk::trackRequest at the end of the HTTP request. Laravel and Symfony do those last two steps for you.
Laravel exception monitoring
The package boots from TRACEHAWK_DSN and reports each HTTP request. One call in bootstrap/app.php sends uncaught exceptions. SQL, outgoing HTTP, cache, and queue work are attached as spans on that request.
Symfony exception monitoring
One line in config/bundles.php. The bundle reports uncaught HTTP exceptions, console errors, and each web request. HTTP exceptions below status 500, such as a 404, are not reported.
Jira issue creation
Jira Cloud connects per project with the site URL, the account email, and an API token. A team carries the project key, issue type, and labels. A rule opens one task when the event count crosses a threshold. Business and Test send it. Base can store the connection and does not send.