Abrova
☰ Docs menu · GitHub issues

GitHub Integration

Automatically create GitHub issues from Abrova Trace errors. Each new error becomes an issue with the full message, error details and stack trace.

Last updated: 27 Oct 2026

Automatically create GitHub issues from AbrovaTrace errors. Each new error creates an issue with the error details and full stack trace.

What you'll need.
  • A GitHub account
  • A GitHub repository for tracking issues
  • A GitHub Personal Access Token
Reaching GitHub from Iran.

GitHub is a service outside Iran and may be unreachable from some networks in Iran. To set it up and to read the alerts you need a connection that can reach GitHub, and deliveries only arrive while github.com and api.github.com answer — failed deliveries show in the integration's delivery log. If that is a problem for your team, use the Email or Webhook integration instead, or alongside it.

Which channels your project can use is shown on the Trace → Integrations page in Abrova Console.

Create a GitHub Personal Access Token#

  1. Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)
  2. Click "Generate new token" → "Generate new token (classic)"
  3. Configure the token:
    • Note: "AbrovaTrace Integration"
    • Expiration: 90 days recommended
    • Scopes: Select repo (full control of private repositories)
  4. Click "Generate token" and copy it immediately
Important. You won't be able to see the token again after leaving the page. Save it securely.

Configure in AbrovaTrace#

  1. In Abrova Console, open Trace → Integrations (integrations belong to the selected project)
  2. Click "Add integration" and choose GitHub (or "Connect" on the GitHub card)
  3. Enter a Name and fill in the configuration fields
  4. Click "Save channel" — or "Save and send test" to save and verify it
OptionTypeRequiredDescription
NamestringYesFriendly name (e.g., "acme/web issues")
Personal access tokenstringYesToken starting with ghp_ from step 1; needs permission to create issues
Repository ownerstringYesUser or organisation (e.g., myorg)
Repository namestringYesRepository (e.g., my-app)

After saving

Managing integrations (add, edit, switch on/off, delete, test) needs the admin or owner role; every role can see them and their delivery log. See Roles & Permissions.

The personal access token is never shown again once saved: the form shows it as set. Leave it as it is to keep the saved token, or press Replace to enter a new one.

If you change the repository owner or name, enter the token again as well — a saved token is never used for a different repository on its own.

What Gets Created#

When a new error is detected (the first time it is seen), AbrovaTrace automatically creates a GitHub issue with:

  • Title — [AbrovaTrace] <error message> (e.g. [AbrovaTrace] TypeError: Cannot read property 'map' of undefined)
  • Error Details — project, environment, first-seen timestamp, occurrence count
  • Stack Trace — full stack from the error event
  • Additional Info — page URL and user agent

Spike detection also opens an issue here, and alert rules you connect to this channel open a [AbrovaTrace Alert] <rule name> issue labelled abrovatrace-alert when they trigger.

Best Practices#

Use a Dedicated Repository or Filter

Issues are titled "[AbrovaTrace] …", so they are easy to find with a search filter

Set Token Expiration Reminders

Set a calendar reminder before your token expires

Separate Integrations per Repository

Add one GitHub integration per repository you want issues in

Troubleshooting#

Issues not being created?
  • Verify personal access token is correct
  • Check token has "repo" scope permissions
  • Ensure the repository owner and name are correct
  • Verify repository exists and you have access
  • Test the integration using the "Send test" button
  • Check the delivery log of the integration: a timeout or connection error means GitHub could not be reached
Authentication failed error?
  • Token may have expired — create a new one, then edit the integration and press Replace on the token
  • Token doesn't have sufficient permissions
  • You may not have access to the repository
  • Try regenerating token with "repo" scope
Wrong repository?
  • Enter the owner and the repository name in separate fields
  • Don't include "github.com" or "https://"
  • Correct: owner myorg, name abrova-trace
  • Incorrect: github.com/myorg/abrova-trace
Was this page helpful?
Report a problem