Add structured log for webhook delivery success with response time and status code

[Chucks1093]

Summary

Successful webhook deliveries are currently not logged. A structured log after each successful delivery makes it easy to confirm a specific webhook fired and how long the callback took to respond.

Scope

• Emit a structured info log after each successful webhook delivery with fields: webhook_id, creator_id, event_type, response_status, response_time_ms, delivered_at
• Log only fires on 2xx response from the callback URL
• Non-2xx responses use the existing retry/failure log path

Acceptance Criteria

• Info log emitted after every successful delivery with all six fields
• Log only fires on 2xx callback response
• Non-2xx response does not trigger the success log

ETA: 12 hours

---

Coordinate on Telegram

[BigJohn-dev]

Pls allow me fix this

[BigJohn-dev]

Pls allow me fix this

[BigJohn-dev]

Pls allow me fix this

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[Peaostrel]

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

i can handle this quickly

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

[Arome8240]

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

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue.

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

[aliyuHabibu]

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

Hi please assign this issue to me. Thank you

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

[dedukpe]

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

Please can you assign this to me
Thank you

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

[teethaking]

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

Hey maintainer! I'd love to take care of this issue and add structured logging for successful webhook deliveries. Tracking these metrics is incredibly helpful for monitoring health and latency on the receiver's end.
Here is how I plan to implement it:

1. Track Request Metrics in the Webhook Dispatcher

Inside the webhook dispatcher service, I will capture a high-resolution timestamp right before executing the outgoing HTTP call to the callback URL. Once the response returns, I'll calculate the total elapsed time in milliseconds (response_time_ms).

2. Implement 2xx Filtering & Structured Logging

I will wrap the response handling logic to explicitly check for a successful status code. If the response status code falls within the 2xx range, I will emit a structured info log containing all six required tracking fields:

• webhook_id
• creator_id
• event_type
• response_status
• response_time_ms
• delivered_at (current ISO timestamp)

{
  "level": "info",
  "message": "Webhook delivery successful",
  "webhook_id": "wh_84920",
  "creator_id": "cr_3012",
  "event_type": "creator.updated",
  "response_status": 200,
  "response_time_ms": 145,
  "delivered_at": "2026-06-28T11:44:02Z"
}

3. Isolate from Failure Paths

I'll ensure this logic is completely separated from non-2xx scenarios so that failing or retrying webhooks continue passing through the existing retry/failure log pipelines without duplicate or conflicting success logs.
I can get this wrapped up and ready for review well within the 12-hour ETA. Please feel free to assign it to me!

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

[victorEdeh]

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

i want to work on this issue

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

[drips-wave]

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

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