Integrations / Sentry
Errors tied back to the code that caused them.
Oynix ingests your Sentry issues and links each error back to the code and decisions behind it.
$ oynix connect sentryPrerequisites
- A Sentry auth token (project:read), plus your org and project slugs.
- The Oynix CLI installed and signed in (oynix login).
Setup steps
Install the Oynix CLI
Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:
$ curl -fsSL https://get.oynix.dev | sh- Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
- Paste the line, press Enter, and wait for it to finish — that's it.
- Check it installed: run oynix --version (it should print a version number).
Sign in
Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.
$ oynix login- Run the command; your browser opens automatically.
- Approve the sign-in with GitHub, then return to the terminal.
- If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).
Create an auth token
sentry.io → Settings → Auth Tokens → create one with project:read. Note your org and project slugs (self-hosted: your Sentry URL).
Connect Sentry
Run the command, choose Direct, and enter token + org + project.
$ oynix connect sentrySync anytime
Oynix pulls the issues and links each error to the code that caused it.
$ oynix connectors sync sentryCheck it worked
List your connectors to confirm Sentry shows up and is syncing. Once it's synced, ask the graph a question that should now have an answer from Sentry.
$ oynix connectors- You should see Sentry listed as "connected".
- Try it: oynix ask "what did we decide about …?" — answers can now draw on Sentry.
What gets indexed
Errors
Sentry issues with their stack traces and metadata.
Links to code
Each error linked back to the responsible code.
Freshness
Re-syncs to track new issues.