PagerDuty improvements

Creating this issue to collect and prioritize issues for PagerDuty integration:

- [X] Bug fix: [https://github.com/getsentry/sentry/issues/83084]()
- [ ] Add auto resolution for alerts:
- [https://github.com/getsentry/sentry/issues/34372]()
- [https://github.com/getsentry/sentry/issues/82574]()
- [https://github.com/getsentry/sentry/issues/55745]()

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)*

Review the linked auto-resolution issues #34372, #82574, and #55745, along with the lightweight metrics documentation linked in the issue. The work is not ready to start until the PagerDuty scope, candidate metrics, affected SDKs, and acceptance criteria are defined.

Written by the indexing model from the issue text.