Ongoing Work & Feedback

## Hello there! 👋

Self-hosted is a big part of Sentry and has provided many benefits to companies and communities, helping them track errors and performance. I believe you already know what Sentry can do. Through this issue, we're aiming to be open and transparent about: (1) our priorities; (2) our backlogs; (3) the features you can expect to see in self-hosted Sentry; and (4) how to submit feedback.

If you want to submit feedback (not just asking for help or explaining what went wrong with self-hosted -- but also things that made you happy while maintaining self-hosted Sentry), feel free to comment on this issue!

For known existing backlogs, you can visit this GitHub Project: https://github.com/orgs/getsentry/projects/109

---

### What we are prioritizing

These issues are being worked on by us (in order of priority).

- [ ] https://github.com/getsentry/self-hosted/issues/3083
- [ ] https://github.com/getsentry/self-hosted/issues/4192
- [ ] Objectstore S3 backend implementation
- [ ] https://github.com/getsentry/self-hosted/issues/4142
- [x] https://github.com/getsentry/self-hosted/issues/3952 -- New feature requires extensive clickhouse query, it's slow!
- [x] https://github.com/getsentry/snuba/issues/7516
- [x] https://github.com/getsentry/self-hosted/issues/4286
- [x] https://github.com/getsentry/self-hosted/issues/4193
- [x] https://github.com/getsentry/self-hosted/issues/1808 -- Current nodestore lives in Postgres and is causing lots of disk storage issues. We're trying to move to S3 or filesystem-based implementation. A draft for S3 with Garage is available here as a blueprint https://github.com/getsentry/self-hosted/pull/3498
- [x] Enable logs for 25.9.0 release
- [x] https://github.com/getsentry/self-hosted/issues/369 -- PR link: https://github.com/getsentry/self-hosted/pull/3673 -- supported now! Some follow ups are:
- [ ] https://github.com/getsentry/self-hosted/issues/3839
- [ ] https://github.com/getsentry/self-hosted/issues/3840
- [x] Enable uptime monitoring for 25.7.0 release -- Available now!
- [x] https://github.com/getsentry/self-hosted/issues/1573
- [x] https://github.com/getsentry/self-hosted/issues/1866 -- It is long overdue
- [x] https://github.com/getsentry/self-hosted/issues/3593 -- We're there! Just a couple of testing and tweaks until we can fully say it's done
- [x] https://github.com/getsentry/self-hosted/issues/1585 -- Available now!

### What features you can expect to land on self-hosted

- [x] https://github.com/getsentry/self-hosted/issues/3830
- [x] https://github.com/getsentry/self-hosted/issues/3993
- [x] https://github.com/getsentry/self-hosted/issues/4182 (coming very soon)
- [ ] https://github.com/getsentry/seer (AI/ML/Autofix features -- still a long way) (Q: Is it a private repo? A: yes, [here's why](https://github.com/getsentry/self-hosted/issues/3625#issuecomment-3026047421))
- [x] https://github.com/getsentry/self-hosted/issues/3304
- [x] https://github.com/getsentry/self-hosted/issues/3592
- [x] https://github.com/getsentry/self-hosted/issues/3560

This is a coordination and feedback tracker rather than a scoped code change, and it names no file, test, or entry point to inspect. Review the linked GitHub Project and priority issues first; the issue would be done only when its feedback or planning purpose is clearly resolved.

Written by the indexing model from the issue text.