rcmnd

SentryCompany

Application monitoring and error-tracking company.

8 things

ClickHouseSoftware

recommended

We ultimately chose ClickHouse after having engineers on the newly-formed Search and Storage Team individually prototype what Snuba could look like on top of the various systems.

Sentry on choosing ClickHouse to back its new Snuba search infrastructure

2019-05-16·blog.sentry.io ↗

Google CloudService

recommended

We made the decision to switch to GCP because the machines are already there, they turn on seconds after we request them, and we only pay for them when they’re on.

Sentry on why it moved its hosted service from bare metal to Google Cloud Platform

2017-10-19·blog.sentry.io ↗

RustSoftware

recommended

As of yesterday, we have dramatically cut down that processing time (and CPU utilization on our machines) by replacing our source map handling with a Rust module that we interface with from Python.

Sentry on replacing Python source map handling with a Rust module

2016-10-19·blog.sentry.io ↗

PostgreSQLSoftware

uses

The application is backed by several PostgreSQL and Redis clusters, Google Cloud Storage, Snuba and Clickhouse clusters, and a bunch of other services like Relay and Symbolicator that are associated with our processing pipeline.

Sentry describing what its monolith is backed by

2023-11-15·sentry.engineering ↗

DjangoSoftware

uses

Sentry is a monolithic Python Django application deployed in several form factors (web servers, Kafka consumers, Celery workers, etc).

Sentry on its monolithic Python Django application

2023-11-15·sentry.engineering ↗

RedisSoftware

uses

For example, we use Redis to cache individual query results, which coalesces some of our more bursty and frequently repeated queries into a single ClickHouse query and removes unnecessary load from the ClickHouse cluster.

Sentry on caching Snuba query results in Redis

2019-05-16·blog.sentry.io ↗

KafkaSoftware

uses

Writing to Snuba starts with reading from a Kafka topic of JSON events that have gone through Sentry’s normalization and processing steps.

Sentry on feeding Snuba from a Kafka topic of events

2019-05-16·blog.sentry.io ↗

PythonSoftware

mixed

This meant that even ignoring any optimizations, just replacing Python with Rust could relieve our chokepoint.

Sentry on Python becoming a chokepoint for source map processing

2016-10-19·blog.sentry.io ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.