Update GitHub Enterprise Integration with the Latest GitHub Integration Features
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Environment
SaaS ([https://sentry.io/]())
### What are you trying to accomplish?
I’m trying to achieve full feature parity between Sentry’s GitHub and GitHub Enterprise integrations. Our goal is to have the GitHub Enterprise integration offer the same functionality as the standard GitHub integration, since both platforms use nearly identical APIs. This would ensure that teams using GitHub Enterprise Cloud can take full advantage of Sentry’s advertised GitHub integration features.
### How are you getting stuck?
When connecting our GitHub Enterprise Cloud instance through the GitHub Enterprise integration, many of the features available in the standard GitHub integration are missing. After reviewing the source code, it appears that the Enterprise integration is significantly outdated. Because of this, we’re unable to use several features that are otherwise available to users on [github.com](), even though the underlying APIs are nearly the same. We’d like to understand if there’s a plan or timeline for bringing the Enterprise integration up to date or supporting feature parity.
### Where in the product are you?
Settings - Integrations
### Link
*No response*
### DSN
*No response*
### Version
*No response*
We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.
Examples**:**
* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs
---
**Candidate Metrics (add more below)**
* …
*(please also add ideas, questions or examples in comments)*
Contributor guide
Assessment
This issue has not been assessed yet.