[Docs] Add an indexer/realtime operational runbook (replay/reset/status, lag thresholds, RPC-outage recovery)

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Labels: documentation, Stellar Wave, devops, docs

We have plenty of docs under docs/ (SSE architecture, implementation, auth, versioning) but nothing that tells on-call how to actually operate the indexer.

If the Soroban RPC goes down or we miss a batch of ledgers, there's no runbook for recovering. The admin reset/replay endpoints, what indexer lag actually means, and the indexer env vars (INDEXER_POLL_INTERVAL_MS, INDEXER_START_LEDGER, STREAM_CONTRACT_ID) are all undocumented on the ops side. So whoever gets paged is guessing.

What the doc has to cover

• Reading indexer lag from /health and /v1/admin/metrics, and what the thresholds mean
• Reset vs replay: what each does, when to reach for it, and the fact that replay is safe to re-run because the dedup constraint makes it idempotent
• The INDEXER_* vars plus SOROBAN_RPC_URL and STREAM_CONTRACT_ID, and what happens when the indexer is disabled

Done when

• Lag reading + thresholds documented
• Reset/replay endpoints documented, including the idempotency note
• Env vars and disabled-indexer behavior documented

Where to start
Add this to backend/docs/SSE_ARCHITECTURE.md and backend/SSE_README.md. Don't re-document the on-chain data flow that's already in ARCHITECTURE.md. Pure docs, no code changes.

[habnark]

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

hello can i work on this issue

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

[femiolutayo]

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

Hello Maintainer. I would love to resolve this issue for you in no time. Please assign to me 🙏🏾😭. Thank you

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

[Jenola344]

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

Hi maintainer, I will love to work on this

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

[Rampop01]

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

I would like to work on this issue . I understand the assignment and the requirements, and I’m confident in the approach needed to deliver the best solution. Kindly assign this task to me.

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

[Caneryy]

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

Hi, I'd like to work on this issue please.

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

[grantfox-oss]

🦊 GrantFox — @Rampop01 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #849)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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