I have installed Sentry with containers, following the guide on https://hub.docker.com/_/sentry/.
Thus I have a working Sentry with the following containers and their respective links:
sentry-redis : not linked
sentry-postgres: not linked
my-sentry : linked to sentry-redis and sentry-postgres
sentry-cron: linked to sentry-redis and sentry-postgres
sentry-worker-1: linked to sentry-redis and sentry-postgres
I understand that
my-sentry acts as the server,
sentry-cron acts as the celery beat and
sentry-worker-1 acts as a worker.
Now I believe the server,
my-sentry, is the one receiving the requests and creating tasks for
sentry-cron to dispatch to the sentry worker(s).
But looking at how the containers are linked together, I can see that no direct connection occur between the server and the cron, nor between the worker(s) and the cron. The only link between them is indirect, through postgres or redis.
Could it be that Sentry uses Redis as a message transport?
Could anyone expand a bit on the matter please, or even point me to some docs or code where I could see how that works?
Edit: I have seen this page on the doc: https://docs.sentry.io/server/queue/ that says Redis is the default broker. But yet if anyone could confirm if my understanding is correct that would be nice!