Skip to content

Commit fa9b4e5

Browse files
committed
docs(self-hosted): specific note on why it's happening
1 parent e626b4b commit fa9b4e5

File tree

1 file changed

+1
-1
lines changed
  • develop-docs/self-hosted/troubleshooting

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ If you're seeing a higher incoming traffic load, then it's expected. If this is
2121

2222
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.
2323

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.
24+
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.
2525

2626
## `sentry-data` volume not being cleaned up
2727

0 commit comments

Comments
 (0)