Skip to content

Commit e626b4b

Browse files
committed
docs(self-hosted): troubleshooting resources spikes
1 parent 4724273 commit e626b4b

File tree

1 file changed

+8
-0
lines changed
  • develop-docs/self-hosted/troubleshooting

1 file changed

+8
-0
lines changed

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

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,14 @@ CSRF_TRUSTED_ORIGINS = ["https://sentry.example.com", "http://10.100.10.10", "ht
1515

1616
See [Django's documentation on CSRF](https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-CSRF_TRUSTED_ORIGINS) for further detail.
1717

18+
## Containers taking too much CPU/RAM usage
19+
20+
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.
21+
22+
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.
23+
24+
Usually, most containers that are not a dependency (like Postgres or Kafka) will consume some good amount of CPU & RAM during startup. If they are experiencing a [bootloop](https://en.wikipedia.org/wiki/Booting#Bootloop), it usually comes down to invalid configuration or a broken dependency.
25+
1826
## `sentry-data` volume not being cleaned up
1927

2028
You may see the `sentry-data` taking too much disk space. You can clean it manually (or putting the cleanup cronjob in place).

0 commit comments

Comments
 (0)