getsentry / getsentry/sentry

Custom title created via fingerprint rule not showing in slack alerts

Open
#54,613 6 comments 6 reactions 0 assignees View on GitHub
Improvement Metrics Product Area: Alerts
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

1. Create a slack alert
2. Create a fingerprint rule that changes the issue title, for example: `level:"error" -> title="Slack alert"`
3. Trigger the alert

### Expected Result

Issue title created via fingerprint rule is shown in slack alert.

### Actual Result

Alert uses error.type and error.value, not the issue title.
Title in Sentry:

![Screenshot 2023-08-11 at 07 39 02](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/bec9cbc4-ea11-4a40-9c9c-d7f30993a58b/dfbd916e-9469-40bb-9585-6f95c2057afd?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi9iZWM5Y2JjNC1lYTExLTRhNDAtOWM5Yy1kN2YzMDk5M2E1OGIvZGZiZDkxNmUtOTQ2OS00MGJiLTk1ODUtNmY5NWMyMDU3YWZkIiwiaWF0IjoxNzY5MjEwNzAzLCJleHAiOjE4MDA3ODEyNjN9.YHZWg1rBc2gux2d75uhQqMxEPGpB0MID38YU6TsviDc)

Slack alert:

![Screenshot 2023-08-11 at 07 39 11](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/93eba45b-3d10-4db8-af85-88c18b2fda2d/19f80862-c486-4248-9ba5-b72d339fb078?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi85M2ViYTQ1Yi0zZDEwLTRkYjgtYWY4NS04OGMxOGIyZmRhMmQvMTlmODA4NjItYzQ4Ni00MjQ4LTliYTUtYjcyZDMzOWZiMDc4IiwiaWF0IjoxNzY5MjEwNzAzLCJleHAiOjE4MDA3ODEyNjN9.QKai3YmZEIPR3KlsRqI_ltqeLit9VtMPvHAZ4clMMnQ)

### Product Area

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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.