Add structured log for webhook delivery attempt with response status and duration

[Chucks1093]

Summary

Each webhook delivery attempt (successful or failed) currently produces no structured log. An info-level log on every delivery attempt would give operators visibility into delivery rates and latency without having to query the webhooks table.

Scope

• Emit an info-level log on every delivery attempt with fields: webhook_id, event_type, attempt_number, response_status, duration_ms, success
• Callback URL must not appear in the log
• Log emitted after the HTTP response is received (or after timeout), not before the attempt
• success is true for 2xx responses, false for all others including timeouts

Acceptance Criteria

• Log emitted after every delivery attempt
• All six fields present with correct values
• Callback URL absent from log
• success: true for 2xx, success: false for non-2xx and timeouts
• Log level is info

ETA: 12 hours

---

Coordinate on Telegram

[ebubeb683-ship-it]

After reviewing the issue, I believe I can implement the required changes effectively. Kindly assign this issue to me.

[Ghoost-404]

@Ghoost-404 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hello, i'd like to work on this issue please

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

[Timrossid]

@Timrossid has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer, I’ve reviewed this issue and I would love to work on this. I am confident that I will be able to resolve it neatly.

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

[ONEONUORA]

@ONEONUORA has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi
I am a backend developer with 5 years of experience designing arch and endpoints

I believe i can handle this issue

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

[drips-wave]

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

🧑‍💻 @ONEONUORA: 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 🌊

[drips-wave]

This issue has been completed by @ONEONUORA as part of the Stellar Wave Program's 7th Wave 🥳

😎 @ONEONUORA: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.