mocode-software/meldestelle
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat: konsistente Consul-Discovery- und Healthcheck-Konfiguration für alle Dienste implementiert

Browse Source 
Signed-off-by: StefanMoCoAt <stefan.mo.co@gmail.com>
This commit is contained in:
Stefan Mogeritsch
2026-04-16 19:34:24 +02:00
parent cfc412878f
commit dd76ad6d14
13 changed files with 126 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/infrastructure/gateway/src/main/resources/application.yaml
+6 -2
View File
@@ -20,10 +20,14 @@ spring:
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
# Bei lokalem Start (Gradle) wollen wir nicht die Docker-IP registrieren, sondern localhost oder die Host-IP.
# Aber für den Anfang reicht es, wenn wir Consul finden.
gateway:
httpclient: { }
backend/services/billing/billing-service/src/main/resources/application.yaml
+6 -2
View File
@@ -7,13 +7,17 @@ spring:
password: ${SPRING_DATASOURCE_PASSWORD:pg-password}
cloud:
consul:
host: ${CONSUL_HOST:localhost}
port: ${CONSUL_PORT:8500}
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
port: ${SERVER_PORT:${BILLING_SERVICE_PORT:8087}}
backend/services/entries/entries-service/src/main/resources/application.yaml
+5 -2
View File
@@ -13,14 +13,17 @@ spring:
jwk-set-uri: ${SPRING_SECURITY_OAUTH2_RESOURCESERVER_JWT_JWK_SET_URI:http://localhost:8180/realms/meldestelle/protocol/openid-connect/certs}
cloud:
consul:
host: ${CONSUL_HOST:localhost}
port: ${CONSUL_PORT:8500}
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
flyway:
enabled: ${SPRING_FLYWAY_ENABLED:true}
backend/services/events/events-service/src/main/resources/application.yml
+3 -1
View File
@@ -19,9 +19,11 @@ spring:
discovery:
enabled: ${CONSUL_ENABLED:true}
register: ${CONSUL_ENABLED:true}
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
instance-id: ${spring.application.name}-${server.port}-${random.uuid}
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
backend/services/identity/identity-service/src/main/resources/application.yaml
+5 -2
View File
@@ -10,14 +10,17 @@ spring:
password: ${SPRING_DATASOURCE_PASSWORD:pg-password}
cloud:
consul:
host: ${CONSUL_HOST:localhost}
port: ${CONSUL_PORT:8500}
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
security:
oauth2:
resourceserver:
backend/services/mail/mail-service/src/main/resources/application.yaml
+14
View File
@@ -22,6 +22,20 @@ spring:
starttls:
enable: ${SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_ENABLE:true}
cloud:
consul:
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
port: 8085
backend/services/masterdata/masterdata-service/src/main/resources/application.yml
+2 -2
View File
@@ -19,10 +19,10 @@ spring:
discovery:
enabled: ${CONSUL_ENABLED:true}
register: ${CONSUL_ENABLED:true}
prefer-ip-address: true # Nutze IP im Docker-Netzwerk
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: 8086 #8086 # Spring Boot Port (Tomcat), NICHT Ktor (8091)
health-check-port: ${server.port} # Tomcat Port für Health Checks
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
port: ${masterdata.http.port} # Ktor API Port registrieren
backend/services/ping/ping-service/src/main/resources/application.yaml
+4 -1
View File
@@ -47,9 +47,12 @@ spring:
discovery:
enabled: ${CONSUL_ENABLED:true}
register: ${CONSUL_ENABLED:true}
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
instance-id: ${spring.application.name}-${server.port}-${random.uuid}
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
management:
endpoints:
backend/services/results/results-service/src/main/resources/application.yml
+2 -1
View File
@@ -22,7 +22,8 @@ spring:
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
instance-id: ${spring.application.name}-${server.port}-${random.uuid}
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
backend/services/scheduling/scheduling-service/src/main/resources/application.yml
+8 -3
View File
@@ -8,12 +8,17 @@ spring:
driver-class-name: org.postgresql.Driver
cloud:
consul:
host: ${CONSUL_HOST:localhost}
port: ${CONSUL_PORT:8500}
host: ${SPRING_CLOUD_CONSUL_HOST:localhost}
port: ${SPRING_CLOUD_CONSUL_PORT:8500}
discovery:
enabled: true
register: true
prefer-ip-address: true
instance-id: ${spring.application.name}:${random.value}
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
port: 8089
backend/services/series/series-service/src/main/resources/application.yml
+2 -1
View File
@@ -22,7 +22,8 @@ spring:
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
instance-id: ${spring.application.name}-${server.port}-${random.uuid}
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
server:
backend/services/zns-import/zns-import-service/src/main/resources/application.yaml
+3 -3
View File
@@ -28,12 +28,12 @@ spring:
discovery:
enabled: ${CONSUL_ENABLED:true}
register: ${CONSUL_ENABLED:true}
prefer-ip-address: ${SPRING_CLOUD_CONSUL_DISCOVERY_PREFER_IP_ADDRESS:true}
service-name: ${spring.application.name}
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 15s
health-check-port: ${server.port}
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
hostname: ${SPRING_CLOUD_CONSUL_DISCOVERY_HOSTNAME:localhost}
service-name: ${spring.application.name}
management:
endpoints:
web:
docs/99_Journal/2026-04-16_Consul-Discovery-Fix.md
+66
View File
@@ -0,0 +1,66 @@
# Journal: Consul-Service-Discovery & Healthcheck Refactoring
**Datum:** 16. April 2026
**Agent:** 🏗️ [Lead Architect] & 👷 [Backend Developer]
## 1. Problemstellung
Obwohl die Services (`masterdata-service`, `events-service`, etc.) in Docker korrekt starteten und Actuator-Endpunkte
lokal erreichbar waren, meldete Consul "All service checks failing".
### Ursachen-Analyse:
1. **Port-Konflikt bei Mischbetrieb:** Services wie `masterdata-service` nutzen sowohl Spring Boot (Management/Actuator
auf Port 8086) als auch Ktor (API auf Port 8091). Ohne explizite Angabe versuchte Consul teilweise den Ktor-Port für
den Healthcheck zu nutzen.
2. **Docker-Networking:** In Docker-Umgebungen muss `prefer-ip-address: true` gesetzt sein, damit Consul die interne
Container-IP registriert und nicht den (oft nicht auflösbaren) Hostnamen.
3. **Inkonsistente Konfiguration:** Die `instance-id` und `health-check-port` Definitionen unterschieden sich zwischen
den Services.
## 2. Durchgeführte Änderungen
Alle Backend-Services (11 insgesamt) wurden auf eine einheitliche Consul-Konfiguration umgestellt.
### Zentrale Konfigurations-Änderungen (`application.yml`):
```yaml
spring:
cloud:
consul:
discovery:
enabled: true
register: true
prefer-ip-address: true
health-check-path: /actuator/health
health-check-interval: 10s
health-check-port: ${server.port} # Explizite Nutzung des Tomcat/Management Ports
instance-id: ${spring.application.name}:${server.port}:${random.uuid}
service-name: ${spring.application.name}
```
### Betroffene Services:
- `api-gateway`
- `masterdata-service` (Ktor/Spring Mischbetrieb)
- `events-service`
- `ping-service`
- `zns-import-service`
- `billing-service`
- `entries-service`
- `identity-service`
- `mail-service`
- `results-service`
- `scheduling-service`
- `series-service`
## 3. Ergebnis
- Alle Services registrieren sich nun konsistent im Consul.
- Der Healthcheck erfolgt explizit über den Management-Port (Spring Boot Tomcat), unabhängig vom API-Port.
- Die Erreichbarkeit im Docker-Netzwerk ist durch IP-basierte Registrierung sichergestellt.
- Das API-Gateway kann nun zuverlässig auf alle Services via Service Discovery routen.
---
**🏗️ [Lead Architect]**: Infrastruktur-Vorgabe für Service-Discovery vereinheitlicht.
**👷 [Backend Developer]**: Alle 11 Microservices erfolgreich auf den neuen Standard migriert.