Pagerduty Issue Alert

### Problem Statement

Issue alerts with pagerduty notifications include alert title and event message in this case \[TESSST\] and TypeError... but it can create long messages especially when having many issue alerts

### Solution Brainstorm

Including alert titles should instead be optional or customizable.

### Product Area

Unknown

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

The issue does not name files, tests, or an entry point. Start by locating the PagerDuty issue-alert notification path and determine how alert titles and event messages are assembled; done means defining and implementing an optional or customizable alert-title behavior, with coverage for the resulting message format.

Written by the indexing model from the issue text.