Repository navigation
Home
Ivan P edited this page Aug 28, 2026
·
4 revisions
Implementation wiki for the DITP observability spike (issue #330).
Covers infrastructure requirements, per-service instrumentation plans, and Helm chart changes for adding distributed tracing, metrics, profiling, and frontend monitoring across sovereign OpenShift services.
| Phase | Scope | Effort | Status |
|---|---|---|---|
| Phase 1 — Infrastructure | Deploy Tempo + Mimir via ArgoCD; update Alloy config; import dashboards; validate end-to-end pipeline in dev | ~4–5 days | Done |
| Phase 2 — Service Onboarding | OTel auto-instrumentation + Helm chart updates for the 8 deployed services | ~33h | Tickets filed, not started |
| Phase 3 — Profiling & RUM | Pyroscope profiling + Faro RUM per service | ~27h | Pyroscope deployed; service work not started |
| Phase 4 — Advanced Instrumentation | Custom spans, DIDComm context propagation, wallet/crypto tracing | Ongoing | Blueprint only |
- Architecture & Infrastructure
- Local Development
- Phase 1 — Infrastructure Rollout
- Phase 2 — Service Onboarding
- Phase 3 — Profiling & RUM
- Phase 4 — Advanced Instrumentation
- Helm Chart Assessments
| Service | Stack | Faro RUM |
|---|---|---|
| acapy-agent | Python / aiohttp | No |
| acapy-vc-authn-oidc | Python / Nuxt 3 | Yes |
| bcgov/traction | Node.js / Python / Vue 3 | Yes |
| acapy-endorser-service | Python / FastAPI | No |
| didwebvh-server-py | Python / FastAPI / Jinja2 | Yes |
| credo-ts | TypeScript / Node.js (library) | Yes (consumers) |
| didcomm-mediator-credo | TypeScript / Node.js | No |
| bc-wallet-demo | TypeScript / React / Node.js | Yes |
| digital-trust-common-service | NestJS / TypeScript / React | Yes |
credo-ts is a library rather than a deployed service — it has no pod of its own, so instrumentation lands in the services that consume it (didcomm-mediator-credo, bc-wallet-demo). Phase 2 therefore covers the 8 deployed services, and Phases 3 and 4 treat credo-ts the same way, targeting consuming service charts.