# infra/sentry/relay/config.yml # # Relay config overlay for the upstream getsentry/self-hosted stack (pinned at # 25.12.1). install.sh copies this file to upstream/self-hosted/relay/config.yml, # replacing the upstream default. Loaded by the `relay` service on startup. # # Goals: # 1. Run in `processing` mode so Relay terminates ingest end-to-end (rather # than forwarding to a parent Relay). This is the standard mode for # self-hosted single-region deployments. # 2. Expose the OTLP HTTP endpoint on the Relay HTTP port so Phase 02 #33 # (OpenTelemetry auto-instrumentation) can ship traces to Sentry without # needing an external collector. # 3. Hard-cap per-project ingest at 100 events/second to prevent abuse via # the public DSN exposed in browser bundles. # 4. Reserve an allowed-domains placeholder; once the public web origin is # known the per-project Sentry UI also enforces it (defence in depth). relay: mode: processing upstream: "http://web:9000/" host: 0.0.0.0 port: 3000 # TLS terminated by Traefik in front of the public nginx; relay itself # speaks plain HTTP on the Docker network. tls_port: null # Logging — surface ingest decisions in container logs without flooding. logging: level: info format: json # Health/diagnostic endpoint stays on the same port; Coolify health-checks # query /api/relay/healthcheck/ready/. metrics: prefix: sentry.relay statsd: null # ---- Processing knobs ------------------------------------------------------- processing: enabled: true # Kafka + Redis come from the upstream compose; these env-vars are injected # by the upstream installer so we just reference them. kafka_config: - { name: bootstrap.servers, value: "kafka:9092" } - { name: message.max.bytes, value: 50000000 } redis: "redis://redis:6379" # Project-config cache TTL. Lower = faster pickup of UI changes, higher = # less load on `web`. 5 minutes is upstream default. projects: cache_expiry: 300 # ---- OTLP endpoint ---------------------------------------------------------- # Relay 25.x exposes OTLP-HTTP at /api/{project_id}/otlp/v1/{traces,logs} # automatically when `processing.enabled` is true and the org feature flag # `organizations:relay` is on (we set that in sentry/sentry.conf.py). The # `aggregator` block below tunes batching for OTLP traces specifically. aggregator: bucket_interval: 10 initial_delay: 30 debounce_delay: 10 max_secs_in_past: 5184000 # 60 days max_secs_in_future: 60 # ---- Rate-limits ------------------------------------------------------------ # Sentry's DSN is public by design (lives in the browser bundle). Without a # rate-limit a botnet can exhaust ingest quota in seconds. Limits here apply # *before* the project hits Kafka, so they protect the whole stack. # # 100 events/sec is a comfortable ceiling for a 3-app deployment; raise per # project in the Sentry UI later if real traffic genuinely needs it. limits: max_event_size: 1000000 # 1 MB per event max_attachment_size: 50000000 # 50 MB attachments (minidumps etc.) max_envelope_size: 100000000 # 100 MB envelope # Per-project ingest cap. Quota-decisions ultimately land in Redis; this is # the in-process backstop Relay enforces before it ever calls into Sentry. quotas: default: limit: 100 window: 1 # seconds reason_code: "relay_per_project_rate_limit" # ---- Allowed-domains placeholder ------------------------------------------- # This is informational — the actual allowed-domains list lives per-project # in the Sentry UI ("Project Settings -> Client Keys -> Allowed Domains"). # Listed here so operators have one searchable place to remember what should # be set: # - https://hivegrid.de # - https://www.hivegrid.de # - https://admin.hivegrid.de # - https://api.hivegrid.de # Leave the array empty in the UI ONLY for the API and Worker projects (their # DSNs are never used from a browser).