Add indexer job retry exhaustion log helper

[Chucks1093]

Summary
Add indexer job retry exhaustion log helper

Scope

• add shared helper for retry-exhaustion logging in indexer jobs\n- include job id/context metadata\n- keep log payload sanitized

Acceptance Criteria

• scoped change is implemented with no unrelated file churn
• docs/tests are updated where applicable
• contributor can validate the outcome locally

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[EmeditWeb]

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

Can I fix this ?. Thank you

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

[Franklivania]

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

Hi, I am Franklin. I have implemented structured logging utilities for background workers, capturing retry exhaustion with contextual metadata while ensuring logs remain sanitized and safe for observability systems. I’ve standardized logging patterns across job processors.

For this issue, I would:

• Create a shared helper for retry-exhaustion logging with job ID and context metadata.
• Ensure payload sanitization to avoid leaking sensitive data.
• Integrate helper into indexer job failure paths.
• Add minimal tests or usage examples where applicable.

ETA: 2–4 hours.

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

[drips-wave]

Congratulations, @EmeditWeb! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @EmeditWeb: 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 marked as completed by a Drips Wave moderator for @EmeditWeb as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented the logging helper with comprehensive sanitization logic (including field redaction and truncation), integrated it into the DLQ workflow, and provided both unit tests and documentation as requested. The work directly addresses all acceptance criteria and appears to be a high-quality contribution.

😎 @EmeditWeb: You earned 100 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.