Feature Request: Add Centralized Logging with ELK Stack + Ansible Deployment

[medfa12]

Summary

Currently, the project has excellent support for distributed tracing (Zipkin) and metrics (Prometheus/Grafana), but lacks centralized log management. Logs are scattered across individual service files (${ROOT}/target/*.log), making debugging in a microservices environment difficult.

Proposal

Add ELK Stack (Elasticsearch, Logstash, Kibana) integration with:

1. Filebeat on each microservice to collect logs
2. Logstash pipelines with Grok filters for Spring Boot log parsing
3. Elasticsearch for indexing
4. Kibana dashboards for visualization
5. Ansible playbooks for automated deployment (Infrastructure as Code)

Benefits

• Complete the observability stack (tracing + metrics + **logging **)
• Correlate logs with traces using Spring Sleuth trace IDs
• Easier debugging across microservices
• Reproducible infrastructure via Ansible

Implementation Plan

• Add Logback configuration for JSON logging
• Create docker-compose extension for ELK
• Write Filebeat configurations per service
• Create Logstash pipelines with Spring Boot patterns
• Build Kibana dashboards (error rates, service logs, etc.)
• Write Ansible playbooks for deployment automation
• Update documentation

I'd be happy to implement this as part of my university capstone project (PFE).
Would the maintainers be interested in this contribution?