Connect your first project
Create a customer, register a project against your error tracker, and pull in real issues.
Projects are grouped under customers, so agencies and internal teams can both keep things tidy. Even for a single application you create one customer first.
Get a token from your error tracker
Before you start, collect three values from the tracker your application reports to:
| Value | Where to find it |
|---|---|
| Base URL | The address you use to open the tracker, for example https://errors.yourcompany.com |
| Auth token | User settings → Auth tokens → create a token with read access |
| Organisation and project slug | The two path segments in the URL when you view the project |
Create the customer and project
- Open Customers and create one — a company name is fine.
- Open Projects → New project.
- Fill in the customer, a project name, and the environment (
production,staging, ordevelopment). Environment matters: production incidents score higher. - Paste the base URL, auth token, organisation slug, and project slug.
- Press Verify connection. Do not skip this — it checks the token and both slugs before anything is saved.
- Add the email addresses that should receive alerts, and choose which risk levels may notify.
- Press Create project.
Pull in the existing issues
Open the project and press Sync now. The first sync fetches current issues, creates one incident record per issue, and queues each new one for analysis.
After the first sync, a scheduled job pulls new issues every five minutes. You do not need to press anything again.
What you should see
Within a minute or two, issues appear under Issues with a risk level beside them. A blank list means the tracker has no open issues in that project, which is a good problem to have.