diff --git a/apps/docs/docs/ref/self-hosting-analytics/introduction.mdx b/apps/docs/docs/ref/self-hosting-analytics/introduction.mdx index b5f8922112a..a2ce445bf7c 100644 --- a/apps/docs/docs/ref/self-hosting-analytics/introduction.mdx +++ b/apps/docs/docs/ref/self-hosting-analytics/introduction.mdx @@ -18,13 +18,18 @@ The Supabase Analytics server (Logflare) manages the ingest and query pipelines Deployed in a self-hosted environment, with the exception of API edge logs, all logs and views supported by Logflare should match the Supabase Cloud. -All logs are routed to Logflare via Vector. Kong routes API requests to PostgREST so self-hosted or local deployments will use Kong request logs instead of the Supabase Cloud API gateway. +All logs are routed to Logflare via Vector. Kong routes API reque`sts to PostgREST so self-hosted or local deployments will use Kong request logs instead of the Supabase Cloud API gateway. There will be some differences in the log event payloads with self-hosted API requests vs requests handled by the Supbase Cloud API gateway. ### Docker Compose -If you're self-hosting a production application with the Supabase stack and want to use the Analytics server pull in the separate Docker compose. +To start the whole Supabase stack with the Analytics server run: + +```bash +cd docker +docker compose -f docker-compose-logging.yml up +```