Table: sentry_organization_repository - Query Sentry Organization Repositories using SQL

Sentry is an open-source error tracking system that helps developers monitor and fix crashes in real time. It offers the ability to track errors in real-time, with detailed reports and alerts. An Organization in Sentry represents a group of users and encapsulates a set of projects. Repositories in Sentry are references to the remote version control repositories that are connected to your Sentry organization.

Table Usage Guide

The sentry_organization_repository table provides insights into repositories in Sentry that are used by organizations. As a developer or DevOps engineer, you can explore repository-specific details through this table, including repository names, IDs, status, and other related information. This table is beneficial for managing and auditing the repositories associated with your Sentry organization, helping you to monitor and troubleshoot issues more effectively.

Examples

Basic info

Explore which organizations have created repositories, along with their status and creation date. This can be useful to determine the areas in which new repositories are being added and by which organizations.

select
  id,
  name,
  status,
  organization_slug,
  date_created,
  external_slug
from
  sentry_organization_repository;

select
  id,
  name,
  status,
  organization_slug,
  date_created,
  external_slug
from
  sentry_organization_repository;

List repositories which are not active

Explore which repositories are inactive. This is useful to identify potential areas for clean-up or archival in your organization's repository storage.

select
  id,
  name,
  status,
  organization_slug,
  date_created,
  external_slug
from
  sentry_organization_repository
where
  status <> 'active';

select
  id,
  name,
  status,
  organization_slug,
  date_created,
  external_slug
from
  sentry_organization_repository
where
  status <> 'active';

List github repositories

Explore which GitHub repositories are linked to your organization on Sentry. This is useful to understand the status and integration details of your repositories, helping you manage your codebase more effectively.

select
  r.id as repository_id,
  r.name as repository_name,
  r.status,
  r.organization_slug,
  r.date_created,
  external_slug
from
  sentry_organization_repository as r,
  sentry_organization_integration as i
where
  r.integration_id = i.id
  and i.provider_key = 'github';

select
  r.id as repository_id,
  r.name as repository_name,
  r.status,
  r.organization_slug,
  r.date_created,
  external_slug
from
  sentry_organization_repository as r,
  sentry_organization_integration as i
where
  r.integration_id = i.id
  and i.provider_key = 'github';

Schema for sentry_organization_repository

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
date_created	timestamp with time zone		The creation timestamp of the repository.
external_slug	text		The slug of the repository.
id	text		The ID of this repository.
integration_id	text		The organization integration ID for repository.
name	text		The name of the repository.
organization_slug	text	=	The slug of the organization the repository belongs to.
provider	jsonb		The repository provider.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
status	text	=	The status of the repository.
title	text		Title of the resource.
url	text		The url of the repository.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- sentry

You can pass the configuration to the command with the --config argument:

steampipe_export_sentry --config '<your_config>' sentry_organization_repository