How it works
Four steps, from an error to a Jira project.
Nothing is inferred from your repository. The browser or your PHP app sends the error. You decide the threshold and the team.
-
01
Create a project and install a client
A project is one site, one PHP application, one Python application, or one Go service. The browser client is a script tag with a public key, so you can restrict which origins may send. Leave that list empty while you try it locally. PHP is tracehawk/sdk plus TRACEHAWK_DSN. Python is the tracehawk package and the same DSN. Go is tracehawk.net/sdk/go and the same DSN. Laravel is one call. Symfony is one bundle line. Django is one middleware line. Flask is one call. Go's net/http is one wrapper. PHP, Python, and Go have no Origin header, so the origin list does not apply. Install notes: JavaScript, PHP, Python, Go, Laravel, Symfony.
Browser<!-- index.html --> <script async src="https://tracehawk.net/api/<key>/snippet.js" crossorigin="anonymous"></script>
.envTRACEHAWK_DSN=https://tracehawk.net/api/<key>
Laravel# bootstrap/app.php use TraceHawk\Sdk\Laravel\Integration; ->withExceptions(function (Exceptions $exceptions) { Integration::handles($exceptions); })Symfony# config/bundles.php TraceHawk\Sdk\Symfony\TraceHawkBundle::class => ['all' => true],
-
02
Events with the same stack become one issue
The fingerprint is the exception type plus the top application frames, without line numbers and without the query string. A second visit to the same bug increments the count and the user total. A different function opens a new issue. The grouping page is the full rule.
readTotalcart.js:44handleCheckoutcheckout.js:218dispatchnode_modules/react-dom→One issue● SHOP-14 -
03
Read it the way you would read a Sentry issue
Open the latest event, or step to an older one. The stack, breadcrumbs, request, and trace belong to that event. Counts, first seen, and last seen belong to the issue. Resolve it, ignore it, or assign it to someone in the organization.
TypeError: Cannot read properties of undefined SHOP-14 · first seen 1.4.1 · last seen 1.4.21,248 events · 611 users -
04
A rule opens one Jira task
Connect Jira Cloud with the site URL, the account email, and an API token. A team has a project key, an issue type, and labels. A rule says how many events, in 15 minutes, an hour, 6 hours, or a day, should file a task for that team. The same episode does not file a second task. If you resolve the issue and it comes back, the rule can open another one.
SHOP-412 Bug · Checkout Opened by TraceHawk Checkout crashes on the card step for 611 users
- Rule
- 50 events in 1 hour
- Episode
- One task, then silence until it is resolved