Add structured log for creator list query with applied filter params and result count

[Chucks1093]

Summary

Debugging creator list queries is difficult without visibility into which filter params were active and how many results came back. A structured log after each creator list query provides this context without enabling verbose query logging.

Scope

• Emit a structured debug log after every GET /creators query resolves with fields: result_count, filters (object of active filter params), sort, query_duration_ms
• Only include filter keys that were actually provided in the request
• Do not log cursor values

Acceptance Criteria

• Log emitted after every creator list query
• filters object contains only active filter params
• Cursor value absent from log output
• query_duration_ms reflects actual query time

ETA: 12 hours

---

Coordinate on Telegram

[adepoju2006]

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

I have experience adding structured debug logging to backend query handlers. I'll emit a structured log after every GET /creators query with result_count, active filters, sort, and query_duration_ms, giving immediate observability into filter behavior and performance without enabling verbose query logging globally.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adepoju2006 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.

[Okorie2000-code]

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

Hi maintainer, can I work on this?

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

[chizzy192]

@chizzy192 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 @chizzy192 to this issue.

[EmmyKay0026]

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

Hello @accesslayerorg, I came across your project and will love the opportunity to work on it. I would complete it promptly and without conflicts.

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

[drips-wave]

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

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