feat(seer-infra-telemetry): Implement monitoring provider connection API endpoints#117854
Merged
shashjar merged 12 commits intoJun 16, 2026
Merged
Conversation
github-actions
Bot
added
Scope: Frontend
Contributor
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
shashjar
requested review from
srest2021 and
wedamija
and removed request for
a team
shashjar
added a commit
that referenced
this pull request
Jun 16, 2026
… endpoints (#117851) Precursor to #117854. Adding new URL patterns in the control silo for the monitoring provider API endpoints. https://linear.app/getsentry/project/access-infrastructure-monitoring-data-5eb36250e0fa/overview
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
wedamija
approved these changes
Jun 16, 2026
shashjar
deleted the
shashjar/add-monitoring-provider-connection-API-endpoints
branch
vgrozdanic
pushed a commit
that referenced
this pull request
Jun 16, 2026
… endpoints (#117851) Precursor to #117854. Adding new URL patterns in the control silo for the monitoring provider API endpoints. https://linear.app/getsentry/project/access-infrastructure-monitoring-data-5eb36250e0fa/overview
vgrozdanic
pushed a commit
that referenced
this pull request
Jun 16, 2026
…API endpoints (#117854) Recreated after reverting #117478. Depends on #117851. Resolves https://linear.app/getsentry/issue/CW-1499/monitoring-provider-connection-api-endpoints. Adds API endpoints for listing, connecting, and disconnecting monitoring providers (currently Datadog & GCP). These endpoints wrap the existing identity pipeline to let users initiate the per-user OAuth flow for connecting their monitoring provider accounts to Sentry. The identity providers for Datadog & GCP were previously implemented in #117035 & #117279, respectively. All endpoints are gated behind the `organizations:seer-infra-telemetry` feature flag, which is enabled only internally in the Sentry org for now. Note that monitoring provider connections are per-user (each user links their own account via OAuth), not per-organization. There is some provider-specific config baked into this implementation: Datadog requires a `site` parameter in the POST body (e.g. `datadoghq.com`) for site resolution, while GCP needs no extra config. For Datadog, the `IdentityProvider` is not created in the POST endpoint; it is auto-created by `IdentityPipeline.finish_pipeline()` using the Datadog org UUID from the MCP whoami response as the external ID (see #117491 & #117705). For GCP, the `IdentityProvider` is created upfront by the endpoint. `GET /api/0/organizations/{org}/monitoring-providers/` lists the available providers and the current user's connection status. This will be used to inform the monitoring provider settings UI tracked in https://linear.app/getsentry/issue/CW-1500/monitoring-providers-settings-page. `POST /api/0/organizations/{org}/monitoring-providers/{provider}/` represents a request to connect a given monitoring provider for a given user. It initiates the OAuth flow and returns a redirect URL to the provider's authorize page, based on the identity pipeline for that provider. `DELETE /api/0/organizations/{org}/monitoring-providers/{provider}/` represents a request to disconnect/delete a given monitoring provider for a given user. It deletes the current user's linked identity for that provider, if one exists. **Note on support for a single user connecting multiple Datadog orgs:** - For v0, we're mainly considering the case where a user has a single Datadog org connected, but in the future we will support multiple - The GET endpoint currently collapses to one entry per provider type (shows `connected: true` if _any_ exist - The POST endpoint currently allows multiple connections to be created - The DELETE endpoint currently deletes all identities for the provider (`idp__type=provider_key`) --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
billyvg
pushed a commit
that referenced
this pull request
Jun 17, 2026
… endpoints (#117851) Precursor to #117854. Adding new URL patterns in the control silo for the monitoring provider API endpoints. https://linear.app/getsentry/project/access-infrastructure-monitoring-data-5eb36250e0fa/overview
billyvg
pushed a commit
that referenced
this pull request
Jun 17, 2026
…API endpoints (#117854) Recreated after reverting #117478. Depends on #117851. Resolves https://linear.app/getsentry/issue/CW-1499/monitoring-provider-connection-api-endpoints. Adds API endpoints for listing, connecting, and disconnecting monitoring providers (currently Datadog & GCP). These endpoints wrap the existing identity pipeline to let users initiate the per-user OAuth flow for connecting their monitoring provider accounts to Sentry. The identity providers for Datadog & GCP were previously implemented in #117035 & #117279, respectively. All endpoints are gated behind the `organizations:seer-infra-telemetry` feature flag, which is enabled only internally in the Sentry org for now. Note that monitoring provider connections are per-user (each user links their own account via OAuth), not per-organization. There is some provider-specific config baked into this implementation: Datadog requires a `site` parameter in the POST body (e.g. `datadoghq.com`) for site resolution, while GCP needs no extra config. For Datadog, the `IdentityProvider` is not created in the POST endpoint; it is auto-created by `IdentityPipeline.finish_pipeline()` using the Datadog org UUID from the MCP whoami response as the external ID (see #117491 & #117705). For GCP, the `IdentityProvider` is created upfront by the endpoint. `GET /api/0/organizations/{org}/monitoring-providers/` lists the available providers and the current user's connection status. This will be used to inform the monitoring provider settings UI tracked in https://linear.app/getsentry/issue/CW-1500/monitoring-providers-settings-page. `POST /api/0/organizations/{org}/monitoring-providers/{provider}/` represents a request to connect a given monitoring provider for a given user. It initiates the OAuth flow and returns a redirect URL to the provider's authorize page, based on the identity pipeline for that provider. `DELETE /api/0/organizations/{org}/monitoring-providers/{provider}/` represents a request to disconnect/delete a given monitoring provider for a given user. It deletes the current user's linked identity for that provider, if one exists. **Note on support for a single user connecting multiple Datadog orgs:** - For v0, we're mainly considering the case where a user has a single Datadog org connected, but in the future we will support multiple - The GET endpoint currently collapses to one entry per provider type (shows `connected: true` if _any_ exist - The POST endpoint currently allows multiple connections to be created - The DELETE endpoint currently deletes all identities for the provider (`idp__type=provider_key`) --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
shashjar
added a commit
that referenced
this pull request
Jun 17, 2026
…Advanced Settings page (#117758) Resolves https://linear.app/getsentry/issue/CW-1500/monitoring-providers-settings-page. Adds a (temporary, for testing) monitoring providers UI section to the Seer Advanced Settings page, gated behind the `organizations:seer-infra-telemetry` feature flag. This lets users connect and disconnect infrastructure monitoring providers (Datadog, GCP) via the API endpoints previously added in #117854. <img width="1512" height="828" alt="image" src="https://github.com/user-attachments/assets/6caba0ba-0a7d-4404-a2f0-d785a1c3c210" /> - Lists available providers with connection status from `GET /monitoring-providers/` - Connect button initiates the OAuth flow via `POST /monitoring-providers/{provider}/` and redirects to the provider's authorize page - Disconnect button shows a confirmation modal, then calls `DELETE /monitoring-providers/{provider}/` and refreshes the list Note that the Datadog logic hardcodes `site: "datadoghq.com"` for v0 (https://linear.app/getsentry/issue/CW-1501/support-per-site-datadog-connections-in-monitoring-provider-endpoints tracks per-site support for multiple connected Datadog orgs for a single user). --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recreated after reverting #117478.
Depends on #117851.
Resolves https://linear.app/getsentry/issue/CW-1499/monitoring-provider-connection-api-endpoints.
Adds API endpoints for listing, connecting, and disconnecting monitoring providers (currently Datadog & GCP). These endpoints wrap the existing identity pipeline to let users initiate the per-user OAuth flow for connecting their monitoring provider accounts to Sentry. The identity providers for Datadog & GCP were previously implemented in #117035 & #117279, respectively.
All endpoints are gated behind the
organizations:seer-infra-telemetryfeature flag, which is enabled only internally in the Sentry org for now. Note that monitoring provider connections are per-user (each user links their own account via OAuth), not per-organization.There is some provider-specific config baked into this implementation: Datadog requires a
siteparameter in the POST body (e.g.datadoghq.com) for site resolution, while GCP needs no extra config. For Datadog, theIdentityProvideris not created in the POST endpoint; it is auto-created byIdentityPipeline.finish_pipeline()using the Datadog org UUID from the MCP whoami response as the external ID (see #117491 & #117705). For GCP, theIdentityProvideris created upfront by the endpoint.GET /api/0/organizations/{org}/monitoring-providers/lists the available providers and the current user's connection status. This will be used to inform the monitoring provider settings UI tracked in https://linear.app/getsentry/issue/CW-1500/monitoring-providers-settings-page.POST /api/0/organizations/{org}/monitoring-providers/{provider}/represents a request to connect a given monitoring provider for a given user. It initiates the OAuth flow and returns a redirect URL to the provider's authorize page, based on the identity pipeline for that provider.DELETE /api/0/organizations/{org}/monitoring-providers/{provider}/represents a request to disconnect/delete a given monitoring provider for a given user. It deletes the current user's linked identity for that provider, if one exists.Note on support for a single user connecting multiple Datadog orgs:
connected: trueif any existidp__type=provider_key)