-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please explain the data flow of sentry. #994
Comments
Well, there are multiple sources Basically, https://github.com/getsentry/self-hosted and https://github.com/getsentry/self-hosted/blob/master/docker-compose.yml specifically is the first source of truth about what needs to run with what parameters. If it is not clear from there, you will probably need to dig through sentry source code. There is 2 main parts - sentry itself, which is the web ui, batch job processor and it uses postgres as main datasource. The second part is Snuba which is part data processing part data storage and retrieval framework which uses clickhouse as data store. Check https://getsentry.github.io/snuba/architecture/overview.html for some details. Snuba and sentry is than stitched together with kafka, celery (jobs in python) and redis in kind of a weird way. Some containers consuming or producing nto kafaka are If you go through Sentry commits and pull request you will find out, that they are kind of struggling with rate at which their containers multiply with each new feature. See for example getsentry/snuba#1670 |
Thank you for answer. |
If you need to understand the general architecture of Sentry, this is the page i often go back to: https://develop.sentry.dev/architecture |
This issue is stale because it has been open for 30 days with no activity. |
There are more PODs and I am not sure what role they play.
Can you explain the sentry data flow (configuration diagram)?
Please briefly explain what operation is performed in which POD. :)
The text was updated successfully, but these errors were encountered: