Add error reporting to your code
Connect
SPIRITT
Bug RecorderBug Recorder
Every failure on the record
SPIRITT reports errors into Bug Recorder from the apps, jobs and automations it builds and runs, with domain, message, context and stack trace, so your configured alerts fire the moment something breaks.
What you can do with Bug Recorder.
Errors with context
Each record carries the domain, message, diagnostic context and stack trace your team needs.
Alerts that already work
Every recorded error fires the notifications set up on your Bug Recorder account.
Coverage for agent-run work
Scheduled jobs, data syncs, checks and webhooks SPIRITT operates report their own failures.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for monitored apps, jobs and integrations.
02
Connect Bug Recorder
Add your Bug Recorder API key, plus the systems SPIRITT should watch.
03
Hand over the watch
Tell SPIRITT what must never fail silently. It builds the checks and reports every failure.
Hand over a mission.
Choose a mission. Make it yours.
Put Bug Recorder to work.
Never miss a failure again
Questions
Bug Recorder, with SPIRITT.
01What does SPIRITT send to Bug Recorder?+
One record per error: the domain, a readable message, diagnostic context and the stack trace when there is one.
02Will my team get alerted?+
Yes. Each recorded error triggers the notifications already configured on your Bug Recorder account.
03Which failures can it report?+
Any server-side failure in the apps, syncs, webhooks and scheduled checks SPIRITT builds or runs for you.
04Can it add error reporting to existing code?+
Yes. SPIRITT adds reporting to your repositories and opens a pull request with the change.
05Can it summarize errors over time?+
Yes. SPIRITT logs each error it records to a sheet or database, so digests and trends come from the same events.
06What does the connection need?+
A Bug Recorder API key. Repositories, hosting and paging tools connect separately.