{"id":492914,"date":"2026-08-31T09:45:22","date_gmt":"2026-08-31T09:45:22","guid":{"rendered":"https:\/\/savepearlharbor.com\/?p=492914"},"modified":"-0001-11-30T00:00:00","modified_gmt":"2026-08-31T09:45:22","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=492914","title":{"rendered":"Time for Sentry to retire\u2026 Metric is ready to take over"},"content":{"rendered":"
\n
\"Sentry<\/p>\n
Sentry vs. Metric<\/figcaption><\/div>\n<\/figure>\n

Disclaimer:<\/strong> this article is written with bias, bile, and tables. The author believes infrastructure should work for you, not the other way around. If you\u2019re a Sentry fan \u2014 read to the end; you\u2019ll have plenty to bring up in the comments. <\/p>\n

Act one, in which we buy a ticket to the zoo<\/h3>\n

Everyone who has ever stood up a self-hosted Sentry remembers this moment. You clone getsentry\/self-hosted<\/code>, run .\/install.sh<\/code>, and go make coffee. You come back, and Docker is still pulling images. You open docker-compose.yml<\/code>, and the fun begins: time to meet the family.<\/p>\n

Here is the official Compose file for release 26.7.2. It contains 65 (sixty-five) service definitions<\/strong>. Sixty-five, Carl! That\u2019s not a typo and not an exaggeration for dramatic effect \u2014 it\u2019s a file from the official repository<\/a>; open it and count for yourself. Yes, some of them are profiles and one-shot jobs. But even the \u201cproduction\u201d cast includes: Sentry web, workers (several kinds!), Relay, Snuba (API + consumers), Kafka, ZooKeeper, ClickHouse, PostgreSQL, Redis, Memcached, Symbolicator, Vroom, cron, and so on down the list until your eyes get tired.<\/p>\n

Sixty-five services. To catch stack traces. Words fail me.<\/p>\n

Let\u2019s put this in perspective. A stack trace is text. A JSON document of a few kilobytes. Humanity learned to accept JSON over HTTP around 2005. And to store that JSON and show it in a web UI, Sentry asks you to run a Kafka message broker (with ZooKeeper included, naturally), the ClickHouse columnar analytical database, a separate PostgreSQL relational database, two different caches, the Relay proxy layer, Python queue workers, a standalone Snuba service that translates internal API queries into ClickHouse\u2019s dialect, and the Vroom profiler \u2014 and that\u2019s still not the whole list.<\/p>\n

Now, the hardware. The official system requirements<\/a>:<\/p>\n