docs(self-hosted): troubleshooting resources spikes (#14472)

Some folks are asking for help troubleshooting their self-hosted issues,
complaining that their systems use lots of CPU, only to find out it's
due to Kafka or something else. Hopefully, by adding this section, we
can point them in the right direction (e.g., checking logs, bumping
resources).

Author: aldy505

develop-docs/self-hosted/troubleshooting/sentry.mdx

@@ -15,6 +15,14 @@ CSRF_TRUSTED_ORIGINS = ["https://sentry.example.com", "http://10.100.10.10", "ht
 
 See [Django's documentation on CSRF](https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-CSRF_TRUSTED_ORIGINS) for further detail.
 
+## Containers taking too much CPU/RAM usage
+
+If you're seeing a higher incoming traffic load, then it's expected. If this is the case, you might want to increase your machine resources.
+
+However, if you have very low incoming traffic and the CPU/RAM constantly spikes, you might want to check on your `top` (or `htop`, or similar) command to see which process are taking the most resources. You can then track down the corresponding Docker container and see if there are any logs that might help you identify the issue.
+
+Usually, most containers that are not a dependency (like Postgres or Kafka) will consume some good amount of CPU & RAM during startup, specifically for catching up with backlogs. If they are experiencing a [bootloop](https://en.wikipedia.org/wiki/Booting#Bootloop), it usually comes down to invalid configuration or a broken dependency.
+
 ## `sentry-data` volume not being cleaned up
 
 You may see the `sentry-data` taking too much disk space. You can clean it manually (or putting the cleanup cronjob in place).