feat(external-mcp): Implement org level ui for configuring datadog integration#119777
feat(external-mcp): Implement org level ui for configuring datadog integration#119777wedamija wants to merge 1 commit into
Conversation
…tegration This adds a UI in that allows us to configure the site, api key and application key for the datadog integration.
|
🚨 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 |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a2ef7ca. Configure here.
| integration_service.update_integration( | ||
| integration_id=self.model.id, metadata=dict(new_metadata) | ||
| ) | ||
| self.model.metadata = dict(new_metadata) |
There was a problem hiding this comment.
Integration name stale after site
Medium Severity
update_organization_config writes the new site into integration metadata but leaves integration.name unchanged. Install still sets the name to Datadog ({site}), so after an org settings site change the list and headers can show the old region while config and API calls use the updated site.
Reviewed by Cursor Bugbot for commit a2ef7ca. Configure here.


This adds a UI in that allows us to configure the site, api key and application key for the datadog integration.
This is just an internal ui, we'll need to improve it a lot if we want to release it to customers.