
Following the official Appwrite-Sentry integration documentation (https://appwrite.io/integrations/logging-sentry) I've configured my .env file with:
_APP_LOGGING_PROVIDER=sentry
After running:
docker compose exec appwrite vars
I observe:
_APP_LOGGING_CONFIG=123456;1;my.selfhosteed.sentry.url
_APP_LOGGING_PROVIDER= # empty value
Upon investigating the docker-compose.yml in the main repository (https://github.com/appwrite/appwrite/blob/main/docker-compose.yml)
I noticed that _APP_LOGGING_PROVIDER is only defined in the "appwrite-worker-functions" service, while other services only have _APP_LOGGING_CONFIG defined.
Questions:
Is this the expected behavior? Should the Sentry logging provider be configured differently for the main Appwrite container? If this is correct, should the documentation be updated to clarify this configuration detail?

Additionally, according to the documentation, running:
docker compose exec appwrite ssl --domain="wrongdomain.com"
should generate and log an error in Sentry, but no error is being captured.
Recommended threads
- Relation with Auth User
WIll Appwrite ever add the ability to create a relation to an Auth user? It seems tedious that the solution for this is to create a separate User table and add...
- Dockerizing Appwrite Console Yields Page...
I have this Docker Compose file: ``` services: # Band9Buddy app band9buddy: build: context: . dockerfile: Dockerfile.dev develop: ...
- Upgrading Appwrite 1.7.4 → 1.8.x: What H...
I'm currently running a self-hosted Appwrite v1.7.4 instance that still uses the old Collections/Documents database model. I noticed that starting from v1.8.x,...
