Persistence requirements for Sentry


#1

Sentry is using a bunch of different datastores, such as “file” (or s3), redis, memcaced and postgres.

I’m trying to figure out which of these need to be persistent, and which work as simple caches where loss of the underlying storage doesn’t result in an unrecoverable system.

I’m assuming that postgres is the “main” datastore, but a short description of the others, and which of them need strong persistence would be an awesome addition to the documentation.


#2

Out of these, the only one that’s ephemeral is memcache. All other datastores will result in data loss.

What that data loss is, varies between them, and how you have things configured, but they all result in some sort of data loss.