graphprotocol / graphprotocol/dipper
ops: Configure Rootly alerts for dipper service
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 1
- Avg merge
- 37m
- Merged PRs (30d)
- 3
Description
Overview
Configure Rootly alerting for the dipper service to ensure operational visibility and rapid incident response.
Context
The Dipper service consists of:
- RPC Servers: Admin and Indexer RPC endpoints
- Worker: Background job processing for indexing agreements
- Database: PostgreSQL for persistent storage
Alerts to Configure
- Service Unhealthy: Dipper container unreachable or failing health checks
- Database Connection Failure: Unable to connect to PostgreSQL
- Worker Job Failures: Sustained job failures beyond normal retry/backoff
Contributor guide
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
No files or tests are named. Start by locating the dipper deployment, health-check, RPC, worker, and PostgreSQL configuration, then determine how Rootly should receive signals for an unhealthy service, database connection failures, and sustained worker job failures. Done means all three alert conditions are configured and their notifications can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, rust
- Domain
- databases, devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100