Issue 14: Observability – structured logging per request

[Tinna23]

Title
feat(core): add structured request-level logging

Context
Maintainers need insight into usage and failures.

What to Build

• Request ID per request

• Log lifecycle:

  • request received
  • Horizon fetch
  • explanation complete
  • error paths

Acceptance Criteria

• Logs are structured and readable
• No sensitive data logged
• Tests where applicable

Complexity
Small–Medium

---

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Oluwatomilola]

@Oluwatomilola has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I would like to be assigned to this issue (#53).

I have experience implementing structured logging and request-level observability, including request ID propagation, lifecycle logging, and ensuring logs are readable, secure, and free of sensitive data. I will implement request-scoped logging covering the full lifecycle (request received, Horizon fetch, completion, and error paths), and add tests where applicable.

Once assigned, I will implement the feature in line with the acceptance criteria, and submit a PR with clear documentation and test coverage.

Thank you for your consideration.

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

[TomikeDS]

@TomikeDS has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi maintainers

I’d like to work on this issue. I’ll add a request-level ID (generated or propagated), introduce structured JSON logs for key lifecycle events (request received, Horizon fetch, completion, and errors), ensure no sensitive data is logged, and include tests where applicable.

Happy to align with any existing logging conventions before opening a PR.

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

[drips-wave]

Congratulations, @TomikeDS! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

🧑‍💻 @TomikeDS: 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.

⚠️ Important: When opening a PR, please link it to this issue to ensure it gets tracked accurately.

🤠 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 🌊