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: Add local SIT distributed tracing with Zipkin #242
Add a local-SIT distributed tracing baseline for the HTTP platform path so operators can correlate one request across API Gateway and downstream Spring services.
Zipkin tracing implementation PRs\n\nOpened the implementation as separate reviewable PRs:\n\n- infra-sit#37: local SIT Zipkin 3.6.1 ClusterIP deployment with in-memory storage\n- config-repo#45: shared SIT exporter endpoint, sampling, and safe default\n- api-gateway#25: managed Spring Boot Zipkin starter\n- customer-service#36: managed Spring Boot Zipkin starter\n- account-service#41: managed Spring Boot Zipkin starter\n- transaction-service#23: managed Spring Boot Zipkin starter\n- mfa-service#16: managed Spring Boot Zipkin starter\n- ledger-service#21: managed Spring Boot Zipkin starter\n\nLocal verification before PR creation:\n- Helm lint/template passed for the Zipkin chart.\n- Existing test suites passed: Gateway 20, Customer 7, Account 64, Transaction 89, MFA 46, Ledger 27.\n- No new tests or CI workflows were added.\n\nMerge order:\n1. infra-sit#37\n2. config-repo#45\n3. service PRs in any order: api-gateway#25, customer-service#36, account-service#41, transaction-service#23, mfa-service#16, ledger-service#21\n4. Roll out Zipkin and the rebuilt services in SIT, then verify one gateway request across at least two services.\n\nThe tracking item remains In progress until the SIT trace-correlation evidence is captured.
The handoff record was refreshed in .github PR #241 with the tracing scope, PR links, verification counts, and post-merge SIT evidence required before closure.
Follow-up hardening was pushed to the six service PRs: the Zipkin exporter is disabled by default for standalone/test execution and is enabled only by the shared SIT profile. Existing suites were rerun successfully with the same counts; no new tests or CI jobs were added.
All implementation PR CI is now green and every PR is open, non-draft, and mergeable. The Zipkin PR set is ready for review. After merge, rollout order remains infra-sit#37, config-repo#45, then the six service PRs, followed by SIT trace-correlation verification.
Tracing implementation wave is complete in reviewable PRs. The existing task remains In progress until the PRs are merged and SIT correlation is verified.
All new service PRs passed local ./mvnw verify, Helm lint/template validation, and git diff --check. GitHub Maven checks are still pending; Helm checks are green. No redundant tests, CI jobs, routes, or business behavior were added.
After merge, deploy the Zipkin backend/config and all instrumented services to SIT, exercise one gateway-to-service request, and verify the trace appears in Zipkin before closing this task.
Zipkin candidate chart is deployed and healthy in digital-bank-sit; /health reports UP.
Rebuilt merged API Gateway and Auth Service tracing images from origin/main with temporary local tags and deployed them to SIT.
A controlled gateway login produced a single trace containing spans from both api-gateway and auth-service; Zipkin service discovery lists both.
Rollout exposed a chart security-context defect because the image user is symbolic; infra-sit PR #39 sets numeric UID/GID 1000 while retaining runAsNonRoot.
The reviewed infra-sit PR STORY: Define service naming, ports, and repository conventions #39 candidate was deployed in the local Docker Desktop SIT cluster with the numeric Zipkin UID/GID correction. Zipkin became Ready and accepted a real API Gateway-to-Auth Service correlated trace across both service spans.
Merged infra-sit#39 was deployed successfully; Zipkin is 1/1 Ready with zero restarts.
Zipkin /health reports UP and its in-memory storage is healthy.
Zipkin service discovery currently includes account-service, api-gateway, auth-service, and transaction-service.
The normal release-tag deployment is therefore healthy after the numeric UID/GID correction.
The task remains open until one fresh gateway request is correlated across at least two service spans after the merged release rollout. AWS tracing and collector mapping remain deferred as documented.
The trace contains the API Gateway server span, the Gateway client span for route account-service-health, and the Account Service server span.
This satisfies the local SIT cross-service trace-correlation acceptance criterion. AWS tracing and collector mapping remain deferred. The task can now be closed with the Sprint 6 observability work item.
Activity
ramioooz commentedon Sep 5, 2026
Zipkin tracing implementation PRs\n\nOpened the implementation as separate reviewable PRs:\n\n- infra-sit#37: local SIT Zipkin 3.6.1 ClusterIP deployment with in-memory storage\n- config-repo#45: shared SIT exporter endpoint, sampling, and safe default\n- api-gateway#25: managed Spring Boot Zipkin starter\n- customer-service#36: managed Spring Boot Zipkin starter\n- account-service#41: managed Spring Boot Zipkin starter\n- transaction-service#23: managed Spring Boot Zipkin starter\n- mfa-service#16: managed Spring Boot Zipkin starter\n- ledger-service#21: managed Spring Boot Zipkin starter\n\nLocal verification before PR creation:\n- Helm lint/template passed for the Zipkin chart.\n- Existing test suites passed: Gateway 20, Customer 7, Account 64, Transaction 89, MFA 46, Ledger 27.\n- No new tests or CI workflows were added.\n\nMerge order:\n1. infra-sit#37\n2. config-repo#45\n3. service PRs in any order: api-gateway#25, customer-service#36, account-service#41, transaction-service#23, mfa-service#16, ledger-service#21\n4. Roll out Zipkin and the rebuilt services in SIT, then verify one gateway request across at least two services.\n\nThe tracking item remains In progress until the SIT trace-correlation evidence is captured.
ramioooz commentedon Sep 5, 2026
The handoff record was refreshed in .github PR #241 with the tracing scope, PR links, verification counts, and post-merge SIT evidence required before closure.
ramioooz commentedon Sep 5, 2026
Follow-up hardening was pushed to the six service PRs: the Zipkin exporter is disabled by default for standalone/test execution and is enabled only by the shared SIT profile. Existing suites were rerun successfully with the same counts; no new tests or CI jobs were added.
ramioooz commentedon Sep 5, 2026
All implementation PR CI is now green and every PR is open, non-draft, and mergeable. The Zipkin PR set is ready for review. After merge, rollout order remains infra-sit#37, config-repo#45, then the six service PRs, followed by SIT trace-correlation verification.
ramioooz commentedon Sep 5, 2026
Tracing implementation wave is complete in reviewable PRs. The existing task remains In progress until the PRs are merged and SIT correlation is verified.
New service coverage:
Existing tracing wave:
All new service PRs passed local ./mvnw verify, Helm lint/template validation, and git diff --check. GitHub Maven checks are still pending; Helm checks are green. No redundant tests, CI jobs, routes, or business behavior were added.
After merge, deploy the Zipkin backend/config and all instrumented services to SIT, exercise one gateway-to-service request, and verify the trace appears in Zipkin before closing this task.
ramioooz commentedon Sep 6, 2026
SIT verification update (2026-09-06)
digital-bank-sit;/healthreportsUP.origin/mainwith temporary local tags and deployed them to SIT.api-gatewayandauth-service; Zipkin service discovery lists both.1000while retainingrunAsNonRoot..github PR #245records this evidence in the handoff.The task remains open until PR #39 is reviewed/merged and the trace is repeated with the normal release tags.
ramioooz commentedon Sep 6, 2026
2026-09-06 candidate verification update:
ramioooz commentedon Sep 6, 2026
Post-merge SIT verification (2026-09-06)
infra-sit#39was deployed successfully; Zipkin is1/1Ready with zero restarts./healthreportsUPand its in-memory storage is healthy.account-service,api-gateway,auth-service, andtransaction-service.The task remains open until one fresh gateway request is correlated across at least two service spans after the merged release rollout. AWS tracing and collector mapping remain deferred as documented.
ramioooz commentedon Sep 6, 2026
Fresh post-merge trace evidence (2026-09-06)
GET /account-service/actuator/healththrough the SIT API Gateway after deploying the merged release tags.200 OK; Account Service reported both liveness and readiness groupsUP.6a9d60564d687c479f9c8a6dc06da9fe.account-service-health, and the Account Service server span.This satisfies the local SIT cross-service trace-correlation acceptance criterion. AWS tracing and collector mapping remain deferred. The task can now be closed with the Sprint 6 observability work item.