Files

T

stefan 59568a42d8 refactor(ping-feature): integrate DI refactor, enhance web build, and update feature workflow

Refactored the `ping-feature` module to adopt centralized `HttpClient` through Koin DI, replacing legacy implementations. Added secure API calls with improved error handling and updated Webpack build scripts to resolve worker path issues. Enhanced `PingScreen` with extended functionality, UI updates, and aligned test cases for the new architecture. Consolidated feature workflows and finalized documentation with a comprehensive feature implementation guide.

2026-01-17 12:05:34 +01:00

1.4 KiB

Raw Blame History

type, status, owner, last_update

type	status	owner	last_update
Journal	ACTIVE	Infrastructure & DevOps Engineer	2026-01-15

Session Log: Infrastructure Zipkin Setup

Zusammenfassung

In dieser Session wurde die Infrastruktur um Distributed Tracing mit Zipkin erweitert, um Latenzanalysen in der Microservice-Architektur zu ermöglichen.

Durchgeführte Änderungen

1. Docker Compose (`docker-compose.yaml`)

Neuer Service zipkin:
- Image: openzipkin/zipkin:3
- Port: 9411
- Network Alias: zipkin
Service Integration:
- Die Services api-gateway, ping-service, entries-service, results-service und scheduling-service wurden konfiguriert, um Tracing-Daten an Zipkin zu senden.
- Umgebungsvariablen hinzugefügt:
  - MANAGEMENT_ZIPKIN_TRACING_ENDPOINT
  - MANAGEMENT_TRACING_SAMPLING_PROBABILITY

2. Dokumentation

Neue Referenz-Dokumentation erstellt: docs/07_Infrastructure/Reference/zipkin.md.
- Enthält Konfigurationsdetails und Troubleshooting-Hinweise.

Betroffene Dateien

docker-compose.yaml
docs/07_Infrastructure/Reference/zipkin.md

Nächste Schritte

Backend-Developer müssen sicherstellen, dass die Micrometer-Tracing-Dependencies (micrometer-tracing-bridge-brave, zipkin-reporter-brave) im Build vorhanden sind.
Neustart der Umgebung mit docker compose up -d.

1.4 KiB Raw Blame History