You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TASK: Standardize structured logging and correlation context in domain services #233
Standardize the operational logging baseline for the domain services that participate in the local SIT workflow.
Scope
Emit one-line ECS JSON console events from Customer, Account, Ledger, Transaction, Auth, MFA, Payment, and Notification Services.
Set the canonical service name and runtime environment from application configuration.
Preserve the gateway-provided X-Correlation-ID in the servlet request logging context and response; generate a bounded identifier only at a trusted service boundary when one is absent.
Do not log request bodies, credentials, tokens, account numbers, balances, customer data, payment data, or other prohibited values.
Each service mainline contains the same structured-console configuration and correlation-boundary behavior.
The implementation uses existing Spring Boot/SLF4J facilities and adds no redundant CI workflow or broad endpoint-test expansion.
Existing Maven verification, Helm validation, and container smoke checks remain green for affected services.
Documentation points to the organization logging/redaction contract.
Boundaries
This task does not implement Zipkin infrastructure, immutable audit storage, OpenSearch collection, or AWS deployment. Those remain separately tracked Sprint 6/7 work.
CI verification completed for all eight implementation PRs. Each has passing Maven verification/test phases, Helm validation, and container build/smoke checks:\n\n- customer-service#35\n- account-service#40\n- ledger-service#19\n- transaction-service#21\n- auth-service#9\n- mfa-service#15\n- payment-service#10\n- notification-service#11\n\nNo merge was performed.
All eight structured logging implementation PRs are merged and their CI checks passed. This task is complete; Fluent Bit/OpenSearch collection, Zipkin, audit storage, and AWS deployment remain separate work.
Activity
ramioooz commentedon Sep 5, 2026
Implementation PRs for #233 are open:\n\n- https://github.com/digital-bank-java/customer-service/pull/35\n- https://github.com/digital-bank-java/account-service/pull/40\n- https://github.com/digital-bank-java/ledger-service/pull/19\n- https://github.com/digital-bank-java/transaction-service/pull/21\n- https://github.com/digital-bank-java/auth-service/pull/9\n- https://github.com/digital-bank-java/mfa-service/pull/15\n- https://github.com/digital-bank-java/payment-service/pull/10\n- https://github.com/digital-bank-java/notification-service/pull/11\n\nScope is limited to ECS JSON console configuration, bounded HTTP X-Correlation-ID propagation, safe request-completion events, and service README documentation. No redundant tests or CI jobs were added. Existing focused Maven tests and git diff checks passed before PR creation. CI is running on each PR.
ramioooz commentedon Sep 5, 2026
CI verification completed for all eight implementation PRs. Each has passing Maven verification/test phases, Helm validation, and container build/smoke checks:\n\n- customer-service#35\n- account-service#40\n- ledger-service#19\n- transaction-service#21\n- auth-service#9\n- mfa-service#15\n- payment-service#10\n- notification-service#11\n\nNo merge was performed.
ramioooz commentedon Sep 5, 2026
All eight structured logging implementation PRs are merged and their CI checks passed. This task is complete; Fluent Bit/OpenSearch collection, Zipkin, audit storage, and AWS deployment remain separate work.