getsentry / getsentry/sentry

Enable PR Comments for other SCM integrations

Open
#64,955 1 comment 1 reaction 0 assignees View on GitHub
Feature Metrics
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

Requires abstraction to map a "PR comment" to other SCM integrations

1. GitLab

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

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by reconciling the request for PR comments across SCM integrations with the unrelated SDK metrics text, then clarify the intended GitLab behavior and the abstraction boundary. Done is not currently defined beyond supporting GitLab.

Written by the indexing model from the issue text.

Assessment

Tech stack
gitlab
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.