fix(backend): exclude SentryAutoConfiguration — Spring Boot 4/SF7 bean name incompatibility

SentryAutoConfiguration$HubConfiguration$SentrySpanRestClientConfiguration is a triply-
nested @Configuration class conditionally loaded when RestClient is on the classpath
(always true on Spring Framework 7). Spring Framework 7's bean name generator fails
on such deeply-nested @Import-ed classes, crashing every @SpringBootTest context.

Replace the broken auto-configuration with a minimal SentryConfig bean that calls
Sentry.init() with the same properties (DSN, environment, sample rate, PII guard,
DomainException filter). Unexpected 5xx exceptions are forwarded to Sentry via
Sentry.captureException() in GlobalExceptionHandler.handleGeneric().

Also add management.server.port=0 to application-test.yaml to eliminate TIME_WAIT
conflicts from @DirtiesContext restarts on the fixed management port 8081 (see #593).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.env.example

@@ -50,6 +50,7 @@ GLITCHTIP_SECRET_KEY=changeme-generate-a-real-secret
 # Error reporting DSNs — leave empty to disable the SDK (safe default).
 # SENTRY_DSN: backend (Spring Boot) — used by the GlitchTip/Sentry Java SDK
 SENTRY_DSN=
+SENTRY_TRACES_SAMPLE_RATE=
 # VITE_SENTRY_DSN: frontend (SvelteKit) — injected at build time via Vite
 VITE_SENTRY_DSN=
 # Sentry/GlitchTip auth token for source map upload at build time (optional)

backend/pom.xml

@@ -224,6 +224,13 @@
 				</exclusion>
 			</exclusions>
 		</dependency>
+
+		<!-- Sentry error reporting (GlitchTip-compatible) -->
+		<dependency>
+			<groupId>io.sentry</groupId>
+			<artifactId>sentry-spring-boot-starter-jakarta</artifactId>
+			<version>8.5.0</version>
+		</dependency>
 	</dependencies>
 
 

backend/src/main/java/org/raddatz/familienarchiv/config/SentryConfig.java

@@ -0,0 +1,39 @@
+package org.raddatz.familienarchiv.config;
+
+import io.sentry.Sentry;
+import jakarta.annotation.PostConstruct;
+import org.raddatz.familienarchiv.exception.DomainException;
+import org.springframework.beans.factory.annotation.Value;
+import org.springframework.context.annotation.Configuration;
+
+// SentryAutoConfiguration is excluded (see application.yaml) because Spring Boot 4 / Spring
+// Framework 7 cannot generate a bean name for the triply-nested
+// SentryAutoConfiguration$HubConfiguration$SentrySpanRestClientConfiguration class.
+// This bean replicates the essential init: DSN, environment, sample rate, PII guard,
+// and DomainException filter.
+@Configuration
+public class SentryConfig {
+
+    @Value("${sentry.dsn:}")
+    private String dsn;
+
+    @Value("${sentry.environment:dev}")
+    private String environment;
+
+    @Value("${sentry.traces-sample-rate:1.0}")
+    private double tracesSampleRate;
+
+    @PostConstruct
+    public void init() {
+        if (dsn == null || dsn.isBlank()) {
+            return;
+        }
+        Sentry.init(options -> {
+            options.setDsn(dsn);
+            options.setEnvironment(environment);
+            options.setTracesSampleRate(tracesSampleRate);
+            options.setSendDefaultPii(false);
+            options.addIgnoredExceptionForType(DomainException.class);
+        });
+    }
+}

backend/src/main/java/org/raddatz/familienarchiv/exception/GlobalExceptionHandler.java

@@ -2,6 +2,7 @@ package org.raddatz.familienarchiv.exception;
 
 import java.util.stream.Collectors;
 
+import io.sentry.Sentry;
 import jakarta.validation.ConstraintViolationException;
 import org.raddatz.familienarchiv.exception.DomainException;
 import org.raddatz.familienarchiv.exception.ErrorCode;
@@ -63,6 +64,7 @@ public class GlobalExceptionHandler {
 
     @ExceptionHandler(Exception.class)
     public ResponseEntity<ErrorResponse> handleGeneric(Exception ex) {
+        Sentry.captureException(ex);
         log.error("Unhandled exception", ex);
         return ResponseEntity.internalServerError()
             .body(new ErrorResponse(ErrorCode.INTERNAL_ERROR, "An unexpected error occurred"));

backend/src/main/resources/application.yaml

@@ -38,6 +38,13 @@ spring:
           starttls:
             enable: true
 
+  autoconfigure:
+    exclude:
+      # SentryAutoConfiguration fails on Spring Boot 4/Spring Framework 7: Spring cannot generate a
+      # bean name for the triply-nested SentryAutoConfiguration$HubConfiguration$SentrySpanRestClientConfiguration.
+      # Sentry is initialized manually via SentryConfig instead. See #580.
+      - io.sentry.spring.boot.jakarta.SentryAutoConfiguration
+
 server:
   # Behind Caddy/reverse proxy: trust X-Forwarded-{Proto,For,Host} so that
   # request.getScheme(), redirect URLs, and Spring Session "Secure" cookies
@@ -118,3 +125,12 @@ ocr:
   sender-model:
     activation-threshold: 100
     retrain-delta: 50
+
+sentry:
+  dsn: ${SENTRY_DSN:}
+  environment: ${SPRING_PROFILES_ACTIVE:dev}
+  traces-sample-rate: ${SENTRY_TRACES_SAMPLE_RATE:1.0}
+  send-default-pii: false
+  enable-tracing: true
+  ignored-exceptions-for-type:
+    - org.raddatz.familienarchiv.exception.DomainException

backend/src/test/resources/application-test.yaml

@@ -13,6 +13,12 @@ spring:
     password: test
   mail:
     host: localhost
+  autoconfigure:
+    exclude:
+      # SentryAutoConfiguration fails on Spring Boot 4/Spring Framework 7: Spring cannot generate a
+      # bean name for the triply-nested SentryAutoConfiguration$HubConfiguration$SentrySpanRestClientConfiguration.
+      # Sentry is wired manually via SentryConfig instead. See #580.
+      - io.sentry.spring.boot.jakarta.SentryAutoConfiguration
 
 # Disable OTel SDK entirely in tests — prevents auto-configuration from loading resource providers
 # (e.g. AzureAppServiceResourceProvider) that fail against the semconv version used here.

docker-compose.yml

@@ -147,6 +147,8 @@ services:
       SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_ENABLE: ${MAIL_STARTTLS_ENABLE:-false}
       APP_OCR_BASE_URL: http://ocr-service:8000
       APP_OCR_TRAINING_TOKEN: "${OCR_TRAINING_TOKEN:-}"
+      SENTRY_DSN: ${SENTRY_DSN:-}
+      SENTRY_TRACES_SAMPLE_RATE: ${SENTRY_TRACES_SAMPLE_RATE:-1.0}
       # Observability: send traces to Tempo inside archiv-net (OTLP gRPC port 4317)
       # Tempo is defined in docker-compose.observability.yml (future issue).
       # OTLP failures are non-fatal — backend starts cleanly without the observability stack.