DOCUMENTATION
Everything you need to run this, written for the first time you try.
12 pages, in the order you will actually need them. Each one states what it assumes, what to do, and what you should see afterwards.
NEW HERE? START WITH THESE
Three pages get you from nothing to a first analysis.
- 01
Install issue reporting
Pick your framework and let the wizard produce the change your codebase needs.
- 02
Connect a project
Create a customer, register a project against your error tracker, and pull in real issues.
- 03
Decide what alerts
Choose which risk levels may interrupt someone, and where the message lands.
ALL PAGES
Search, or browse by what you are trying to do.
12 of 12 pages
Getting started
Using the workspace
- Connect your first projectCreate a customer, register a project against your error tracker, and pull in real issues.7 min
- Read an incidentWhat each part of the incident view means, and what to do with it.5 min
- Add uptime monitorsCheck that a project is reachable every minute, and keep the result.3 min
Configuration
- Choose and configure a model providerHosted or local, and how to change your mind later.4 min
- Send alerts to email, Discord, or TelegramDecide what is worth interrupting someone for, and where it lands.5 min
- Turn a fix into a pull requestConnect a GitHub App so proposed repairs arrive where your team already reviews.8 min
- Apply an approved change over FTP or SFTPFor servers without a repository — with a backup taken before every write.6 min
- Add people, roles, and stronger sign-inInvite the team, decide who can administer, and turn on two-factor or passkeys.5 min
Reference
FROM READING TO RUNNING
The fastest way to evaluate this is to run it.
Install takes three commands, and the workspace is useful from the first synced issue.
- Docker Compose definition included in the repository
- Bring your own AI provider — hosted or local
- Notifications and code changes stay optional