
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
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
- Issue - Migration From Cloud > Self Host...
Hi team, I’m trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in “archive mode” due to th...
