Sentry
Visualize Sentry services, teams, and users, map Sentry users to employees, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
Installation
To configure this integration, you will need to create an auth token in Sentry and provide it, along with your organization slug, when you create the integration instance in JupiterOne.
Prerequisites
Create a Sentry auth token whose scopes cover the data this integration ingests. A personal token lets you select custom scopes in the UI and is the token type used below; an organization token carries a fixed scope set and may not include all of the scopes required here.
The token must carry the following scopes:
org:read— read organization details, projects, teams, and repositoriesmember:read— read organization membersteam:read— read team membershipsevent:read— read project issues
Configuration in Sentry
To create a personal auth token:
- In the top left, open the account dropdown and go to User Settings > Auth Tokens to open the Auth Tokens page.
- Select Create New Token.
- Select the scopes listed under Prerequisites.
- Select Create Token and copy the generated token.
Copy the token when it is created; Sentry does not display it again.
Configuration in JupiterOne
To install the Sentry integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Sentry. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Sentry account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
The Auth Token you generated in Sentry.
-
For Organization, enter your Sentry organization slug. This is the URL-safe version of your organization name and can be found in your Sentry URL at
sentry.io/organizations/{organization-slug}/....
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Finding | sentry_finding | Finding |
| Member | sentry_member | User |
| Organization | sentry_organization | Account |
| Project | sentry_project | Project |
| Role | sentry_role | AccessRole |
| Service | sentry_service | Service |
| Team | sentry_team | UserGroup |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
sentry_member | ASSIGNED | sentry_role |
sentry_organization | HAS | sentry_service |
sentry_organization | HAS | sentry_project |
sentry_organization | HAS | sentry_team |
sentry_organization | HAS | sentry_member |
sentry_organization | HAS | sentry_role |
sentry_project | HAS | sentry_finding |
sentry_team | ASSIGNED | sentry_project |
sentry_team | HAS | sentry_member |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
|---|---|---|---|
sentry_organization | HAS | repository | FORWARD |