🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
chore: fix small error in docs (#676)
0xflotusc59ce798b5ef
diff --git a/docs/content/docs/troubleshooting.mdx b/docs/content/docs/troubleshooting.mdxindex c3b8f6655..a30e6bcc9 100644--- a/docs/content/docs/troubleshooting.mdx+++ b/docs/content/docs/troubleshooting.mdx@@ -98,7 +98,7 @@ Regular web analytics events take up almost no space in Clickhouse, so it is ver### 1. You are using session replay-On self-hosted instances where we don't have access to S3 compatiable object storage, session replays are stored in Clickhouse. Each session replay is at least 1000x the data footprint of the web analytics events. So it's very easy to run out of disk space.+On self-hosted instances where we don't have access to S3 compatible object storage, session replays are stored in Clickhouse. Each session replay is at least 1000x the data footprint of the web analytics events. So it's very easy to run out of disk space.We have a 30 day retention policy for session replays events, so if you turn off session replay, your disk space will slowly come back. If you need to immediately free up space, you can truncate the session replays table:@@ -113,4 +113,4 @@ TRUNCATE TABLE session_replay_metadata;In our [docker-compose.yml](https://github.com/rybbit-io/rybbit/blob/master/docker-compose.ymlg), we have a config for Clickhouse that suppresses logs. Clickhouse stores a ton of logs in the log tables by default. This will quickly fill up your disk space if left unchecked.-If you follow the standard installation process, the configs are already mounted for you. If you rolled your own Docker setup, you need to mount the configs manually.\ No newline at end of file+If you follow the standard installation process, the configs are already mounted for you. If you rolled your own Docker setup, you need to mount the configs manually.