Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
Sentry - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="sentry-jupiterone-integration-benefits">Sentry + JupiterOne Integration Benefits</h2> <ul><li>Visualize Sentry services, teams, and users in the JupiterOne graph.</li> <li>Map Sentry users to employees in your JupiterOne account.</li> <li>Monitor changes to Sentry users using JupiterOne alerts.</li> </ul><h2 data-id="how-it-works">How it Works</h2> <ul><li><p>JupiterOne periodically fetches organizations, projects, teams, and users from<br> Sentry to update the graph.</p></li> <li><p>Write JupiterOne queries to review and monitor updates to the graph, or<br> leverage existing queries.</p></li> <li><p>Configure alerts to take action when JupiterOne graph changes, or leverage<br> existing alerts.</p></li> </ul><h2 data-id="requirements">Requirements</h2> <ul><li><p>JupiterOne requires an Auth Token. You need sufficient access in Sentry to<br> create an Auth Token with the following scopes:</p> <ul><li><code class="code codeInline" spellcheck="false" tabindex="0">member:read</code></li> <li><code class="code codeInline" spellcheck="false" tabindex="0">org:read</code></li> <li><code class="code codeInline" spellcheck="false" tabindex="0">project:read</code></li> <li><code class="code codeInline" spellcheck="false" tabindex="0">team:read</code></li> </ul></li> <li><p>You must have permission in JupiterOne to install new integrations.</p></li> </ul><h2 data-id="support">Support</h2> <p>If you need help with this integration, please contact<br><a rel="nofollow" href="https://support.jupiterone.io">JupiterOne Support</a>.</p> <h2 data-id="integration-walkthrough">Integration Walkthrough</h2> <h3 data-id="in-sentry">In Sentry</h3> <p><a rel="nofollow" href="https://docs.sentry.io/api/auth/">Sentry API Documentation</a></p> <p><a rel="nofollow" href="https://sentry.io/settings/account/api/auth-tokens/">Generate am Auth Token</a></p> <ol><li>Navigate to the Auth Tokens page in Sentry Settings.</li> <li>Select <strong>Create New Token</strong> in the top right corner.</li> <li>Select <code class="code codeInline" spellcheck="false" tabindex="0">project:read</code>, <code class="code codeInline" spellcheck="false" tabindex="0">team:read</code>, <code class="code codeInline" spellcheck="false" tabindex="0">org:read</code>, and <code class="code codeInline" spellcheck="false" tabindex="0">member:read</code> and then<br> click <strong>Create Token</strong>.</li> </ol><h3 data-id="in-jupiterone">In JupiterOne</h3> <ol><li>From the top navigation of the J1 Search homepage, select <strong>Integrations</strong>.</li> <li>Scroll to the <strong>Sentry</strong> integration tile and click it.</li> <li>Click the <strong>Add Configuration</strong> button and configure the following settings:</li> </ol><ul><li><p>Enter the <strong>Account Name</strong> by which you'd like to identify this Sentry account<br> in JupiterOne. Ingested entities will have this value stored in<br><code class="code codeInline" spellcheck="false" tabindex="0">tag.AccountName</code> when <strong>Tag with Account Name</strong> is checked.</p></li> <li><p>Enter a <strong>Description</strong> that will further assist your team when identifying<br> the integration instance.</p></li> <li><p>Select a <strong>Polling Interval</strong> that you feel is sufficient for your monitoring<br> needs. You may leave this as <code class="code codeInline" spellcheck="false" tabindex="0">DISABLED</code> and manually execute the integration.</p></li> <li><p>Enter the <strong>Auth Token</strong> generated for use by JupiterOne in the Sentry steps<br> above.</p></li> <li><p>Enter Sentry organization slug in the <strong>Organization</strong> field. This is the URL<br> safe version of your organization and can be found in your Sentry URL at<br><em>sentry.io/organizations/<code class="code codeInline" spellcheck="false" tabindex="0">organization-slug</code>/...</em></p></li> </ul><ol start="4"><li>Click <strong>Create Configuration</strong> once all values are provided.</li> </ol><h1 data-id="how-to-uninstall">How to Uninstall</h1> <ol><li>From the top navigation of the J1 Search homepage, select <strong>Integrations</strong>.</li> <li>Scroll to the <strong>Sentry</strong> integration tile and click it.</li> <li>Identify and click the <strong>integration to delete</strong>.</li> <li>Click the <strong>trash can</strong> icon.</li> <li>Click the <strong>Remove</strong> button to delete the integration.</li> <li>Navigate to the Auth Tokens page in Sentry Settings.</li> <li>Click the <strong>Remove</strong> button to the right of the appropriate Auth Token that<br> was in use for this integration.</li> </ol><h2 data-id="data-model">Data Model</h2> <h3 data-id="entities">Entities</h3> <p>The following entities are created:</p> <table><thead><tr><th>Resources</th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> </tr></thead><tbody><tr><td>Member</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_member</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr><tr><td>Organization</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_organization</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>Project</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_project</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Project</code></td> </tr><tr><td>Team</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_team</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">UserGroup</code></td> </tr></tbody></table><h3 data-id="relationships">Relationships</h3> <p>The following relationships are created:</p> <table><thead><tr><th>Source Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Relationship <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> <th>Target Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_member</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_project</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_team</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_team</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_project</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_team</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">sentry_member</code></td> </tr></tbody></table> </article> </main>