getsentry / getsentry/sentry

Sunset inactive accounts

Open
#24,647 6 comments 3 reactions 0 assignees View on GitHub
Security
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

## Summary

Sometimes users sign up, and they start using Sentry right away. A year later they are happy customers. Other times, it takes a few months for them to get going. And then sometimes a user signs up, and drifts away, never to return. It can be a signal that we're in charge of our situation if we deactivate or delete these accounts after a year or two.

## Motivation

Not sure how much this matters in terms of resource consumption or security surface, and how much is simply hygiene and projection of with-it-ness.

## Additional Context

I'm ticketing this from [a Twitter thread]() where a user with a six-year-old inactive account is wondering why we never cleaned up.

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.