Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
PagerDuty - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="pagerduty-jupiterone-integration-benefits">PagerDuty + JupiterOne Integration Benefits</h2> <ul><li>Visualize PagerDuty services, teams, and users in the JupiterOne graph.</li> <li>PagerDuty users will be mapped to employees in your JupiterOne account.</li> <li>Monitor changes to PagerDuty users using JupiterOne alerts.</li> <li>Produce compliance evidence of system/service monitoring and on-call<br> escalation.</li> </ul><h2 data-id="how-it-works">How it Works</h2> <ul><li><p>JupiterOne periodically fetches services, teams, and users from PagerDuty to<br> update the graph.</p></li> <li><p>Write JupiterOne queries to review and monitor updates to the graph.</p></li> <li>Configure alerts to take action when JupiterOne graph changes.</li> </ul><h2 data-id="requirements">Requirements</h2> <ul><li><p>JupiterOne requires a PagerDuty<br><a rel="nofollow" href="https://support.pagerduty.com/docs/generating-api-keys#section-rest-api-keys">General Access REST API key</a>.<br><strong>NOTE:</strong> Pagerduty hosts two APIs - General Access REST API<br> (api.pagerduty.com) and Events API (events.pagerduty.com). JupiterOne does not<br> currently ingest data from the Events API.</p></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-pagerduty">In PagerDuty</h3> <ul><li><a rel="nofollow" href="https://support.pagerduty.com/docs/generating-api-keys#section-generating-a-general-access-rest-api-key">Generate a General Access REST API key</a></li> </ul><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>PagerDuty</strong> integration tile and click it.</li> <li>Click the <strong>Add Configuration</strong> button.</li> <li>Enter the <strong>Account Name</strong> by which you'd like to identify this PagerDuty<br> account 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.</li> <li>Enter a <strong>Description</strong> that will help your team further identify</li> <li>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.</li> <li>Enter the <strong>PagerDuty API Key</strong> generated for use by JupiterOne.</li> <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>PagerDuty</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> </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>Service</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_service</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Service</code></td> </tr><tr><td>Team</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_team</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Team</code></td> </tr><tr><td>User</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</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">pagerduty_service</code></td> <td><strong>ASSIGNED</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_team</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_team</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_user</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_user</code></td> <td><strong>MONITORS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">pagerduty_service</code></td> </tr></tbody></table> </article> </main>
.png)