[Mike] 25. Request tracing instrumentation

[mikewheeleer]

Implement Request tracing instrumentation

Description

Add tracing spans for API, DB, and RPC operations.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Repository scope: Talenttrust/Talenttrust-Backend only
• Keep implementation aligned with existing project architecture and coding standards

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/backend-25-request-tracing-instrumentation
• Implement changes
  • Write code in: src/index.ts and modularized src/* files for add tracing spans for api, db, and rpc operations.
  • Write comprehensive tests: src/**/*.test.ts with integration and unit suites
  • Add documentation: README.md and docs/backend/
  • Include NatSpec-style comments where applicable (or equivalent structured doc comments)
  • Validate security assumptions and threat scenarios

Test and commit

• Run tests
• Cover edge cases and failure paths
• Include test output and security notes

Example commit message

feat: implement request tracing instrumentation with tests and docs

Guidelines

• Minimum 95 percent test coverage for impacted modules
• Clear documentation with reviewer-focused structure
• Timeframe: 96 hours

[Chucks1093]

@Chucks1093 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I will approach this by adding OpenTelemetry spans at the Express middleware level and wrapping each DB and RPC call site so every request carries a full trace from entry to response.

I will also make sure integration tests assert span names and parent/child relationships are correct for API, DB, and RPC operations before the PR is opened.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chucks1093 to this issue.

[drips-wave]

Congratulations, @Chucks1093! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Chucks1093: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊