[OBSERVABILITY]: Define SLOs and end-to-end tracing for payout operations

[grantfox-oss]

Context

Console logs and product analytics do not answer whether payout creation, application approval, escrow funding, or milestone release is healthy. Operators need correlated telemetry across browser, API, database, jobs, and blockchain dependencies.

Scope

• Define SLIs/SLOs for availability, latency, and successful completion of critical workflows.
• Add structured logs, metrics, and distributed traces with shared correlation/operation IDs.
• Instrument API latency/status, database timing, job queues, escrow confirmation latency, and dependency failures.
• Redact tokens, emails, wallet-sensitive metadata, request bodies, and file URLs by default.
• Build dashboards and burn-rate alerts tied to actionable runbooks.
• Add synthetic probes for public availability and authenticated test-environment journeys.

Acceptance criteria

• A single payout/escrow operation can be traced across all participating components.
• SLO calculations exclude only documented cases and use version-controlled definitions.
• Alerts use multi-window burn rates and link to recovery runbooks.
• Telemetry has explicit sampling, retention, and cardinality limits.
• Automated tests verify redaction of secrets and PII.
• This work integrates with, rather than duplicates, the functional system-log issues Closes #84 Moving from ERC-721 prototype to native Soroban #116 and fix(auth): harden profile/materials API auth, wallet normalization, a… #117.

Relevant areas

API routes, Prisma client, external adapters, escrow hooks/workers, PostHog provider, deployment platform.

[nelly439]

Hi! I'd like to work on this issue.

I have experience implementing observability for distributed systems, including structured logging, metrics, tracing, and SLO-driven monitoring. I can define SLIs/SLOs for the critical escrow and payout workflows, add correlated telemetry across the frontend, API, Prisma, background jobs, and blockchain integrations using shared correlation IDs, and instrument latency, dependency health, queue performance, and escrow confirmation timing. I'll also ensure sensitive data is redacted by default, configure sampling and retention policies, create dashboards with multi-window burn-rate alerts linked to recovery runbooks, and add automated tests to verify PII redaction. I'll coordinate the implementation so it complements the existing system logging work (#116 and #117) rather than duplicating it.

Could you please assign this issue to me? Thank you!

[ebubeb683-ship-it]

I'd like to work on this issue.

[Juwon345]

I would like to work on this issue

[grantfox-oss]

🦊 GrantFox — @Juwon345 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #92)
2. Your PR will be reviewed by the Eduvault-stellar maintainers

Good luck! Track your progress on GrantFox.