Missing Sentry Audit Log Entry for Vercel Disabling from Vercel side
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 624
Description
### Environment
SaaS (https://sentry.io/)
### Steps to Reproduce
- Access the Sentry platform and navigate to the organization's settings.
- Verify that Vercel is currently enabled and integrated with Sentry.
- Note the absence of any explicit log entry regarding the disabling of Vercel within the Sentry audit log.
- Proceed to the Vercel platform and locate the settings or configuration related to the integration with Sentry.
- Disable the Vercel integration or any relevant functionality associated with Sentry.
- Return to the Sentry dashboard and refresh the organization's settings page.
- Review the Sentry audit log to observe if an entry indicating the disabling of Vercel is recorded.
- Notice the lack of a corresponding log entry for the action performed in step 5.
### Expected Result
When Vercel is disabled, an appropriate entry should be recorded in the Sentry audit log, ensuring consistent and comprehensive logging of actions related to the Sentry and Vercel integration.
### Actual Result
Disabling Vercel on the Vercel side does not trigger the creation of an entry in the Sentry audit log. However, other changes made within the Sentry platform are correctly logged, indicating a one-way logging behaviour specific to Vercel integration.
### Product Area
Settings - Integrations
### Link
_No response_
### DSN
_No response_
### Version
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.