Sentry
Visualize Sentry services, teams, and users, map Sentry users to employees, and monitor changes through queries and alerts.
- Installation guide
- Sentry data model
Installation
To configure this integration, you will need to create an Auth Token in Sentry and provide it in your JupiterOne integration instance.
Configuration in Sentry
To create an API Token:
Navigate to the Auth Tokens page in your Sentry Settings.
Select Create New Token in the top right corner.
Allow the following scopes for the token:
project:read
team:read
org:read
event:read
member:read
Click Create Token
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 a configuration requires the following:
The Account Name used to identify the Sentry account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle 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
DISABLED
and manually execute the integration.Your Sentry API Token generated for use in JupiterOne.
For Organization, enter your Sentry Organization's slug. This is the URL safe version of your organization 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.
Data Model
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_member |
sentry_organization | HAS | sentry_project |
sentry_organization | HAS | sentry_role |
sentry_organization | HAS | sentry_service |
sentry_organization | HAS | sentry_team |
sentry_project | HAS | sentry_finding |
sentry_team | HAS | sentry_member |
sentry_team | ASSIGNED | sentry_project |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
sentry_organization | HAS | *repository* | FORWARD |