About
Errors should become issues, not another notification.
TraceHawk is an error tracker for the browser and for PHP. It groups the same failure, keeps the release and the trace, and files work only when a count you set is crossed.
What it is
A project collects errors from a script tag or from the PHP package. Repeats of the same stack become one issue, with a count, the users who hit it, and the release it was first and last seen on. A rule can open one Slack message or one Jira task for that episode, then stay quiet.
Why it exists
A site can throw thousands of errors in a night and still have only a few bugs. A channel that posts every exception turns that into noise people mute. TraceHawk exists so the board stays short enough to read, and so a ticket is filed because the count crossed a line, not because a single stack trace arrived.
The problem it is for
The same bug, reported over and over, is still one bug. Without grouping, the release, and a threshold, a team either wakes up for every event or misses the one that is spreading. TraceHawk keeps the stack, the release, and the trace that were sent, and leaves the decision of when to interrupt a team in a rule you write.
How to reach us
Setup, a plan, or a Jira project key: write to support@tracehawk.net. One inbox. Include the site or the PHP app you want to connect, and do not send an API token in the email.
The page stays on the error, the version, and the ticket.
- Session replay
- Performance profiling
- An APM suite
- An invented root cause
- A chat firehose
If a trace was sent with the error, you see that trace. If it was not, the page does not pretend one exists.