graphprotocol / graphprotocol/subgraph-dips-indexer-selection
ops: Configure Rootly alerts for IISA service
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 8d 17h
- Merged PRs (30d)
- 1
Description
Overview
Configure Rootly alerting for the IISA HTTP service to ensure operational visibility and rapid incident response.
Context
IISA runs as a separate containerized service that dipper depends on for indexer selection. The service has two operational modes:
- Inference (per-request): Fast selection using pre-computed weights
- Training (daily): Linear regression job updating weights (~15 min, 32GB+ RAM) (via CronJob, technically no longer managed insid the IISA container)
Failures in IISA will cause dipper to fall back to random indexer selection after 6 hours (per PR #532), but alerts should fire well before that threshold.
Alerts to Configure
- Inference Failure: IISA service unreachable or returning errors for indexer selection requests
- Training Failure: Daily regression job failed to complete
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the containerized IISA HTTP service, its inference requests, and the daily regression CronJob, including the fallback context in PR #532. Confirm how Rootly integrations are configured for this project; done means alerts exist for inference unavailability or errors and for a training job that fails to complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, python
- Domain
- devops, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100