Update sentry config for 24.12.1

site-modules/profile/templates/sentry/relay.yml.erb

@@ -6,7 +6,7 @@ relay:
   host: 0.0.0.0
   port: 3000
 logging:
- level: WARN
+  level: WARN
 processing:
   enabled: true
   kafka_config:
@@ -14,3 +14,10 @@ processing:
     - {name: "message.max.bytes", value: 50000000} # 50MB
   redis: redis://redis:6379
   geoip_path: "/geoip/GeoLite2-City.mmdb"
+
+# In some cases, relay might fail to find out the actual machine memory
+# therefore it makes the healthcheck fail and events can't be submitted.
+# As a workaround, uncomment the following line:
+#
+# health:
+#  max_memory_percent: 1.0

site-modules/profile/templates/sentry/sentry.conf.py.erb

@@ -74,6 +74,18 @@ SENTRY_OPTIONS["system.event-retention-days"] = int(
     env("SENTRY_EVENT_RETENTION_DAYS", "90")
 )
 
+# Self-hosted Sentry infamously has a lot of Docker containers required to make
+# all the features work. Oftentimes, users don't use the full feature set that
+# requires all the containers. This is a way to enable only the error monitoring
+# feature which also reduces the amount of containers required to run Sentry.
+#
+# To make Sentry work with all features, set `COMPOSE_PROFILES` to `feature-complete`
+# in your `.env` file. To enable only the error monitoring feature, set
+# `COMPOSE_PROFILES` to `errors-only`.
+#
+# See https://develop.sentry.dev/self-hosted/experimental/errors-only/
+SENTRY_SELF_HOSTED_ERRORS_ONLY = env("COMPOSE_PROFILES") != "feature-complete"
+
 #########
 # Redis #
 #########
@@ -375,10 +387,6 @@ CSP_REPORT_ONLY = True
 # if you're using it directly like a CDN instead of using the loader script.
 JS_SDK_LOADER_DEFAULT_SDK_URL = "https://<%= @vhost_name %>/js-sdk/%s/bundle%s.min.js"
 
-
-# If you would like to use self-hosted Sentry with only errors enabled, please set this
-SENTRY_SELF_HOSTED_ERRORS_ONLY = env("COMPOSE_PROFILES") != "feature-complete"
-
 #####################
 # Insights Settings #
 #####################