graphprotocol / graphprotocol/indexer

Feature request - signal planned maintenance

Open
#154 2 comments 0 reactions 1 assignee View on GitHub

@Jannis is already working on this.

Since Dec 17, 2020.

enhancement indexer-service p3
Dominant language
TypeScript
Stars
262
Forks
148
PR merge metrics
No merged PRs in 30d

Description

Seeing the reliability depends on % of queries sent by the gateway that don't fail, i think we need to have a way to signal planning in maintenance, which on infrastructure his elaborate and complex could easily be a few hours. Being able to do maintenance is important for the security of the servers and reliability of the indexing service.

Potentially this could also be used reactively, when you have observed a significant problem and realise you need time to remediate, to avoid further dropping in reliability score.

We probably want to combine it with a "ready for business again" to be send out when complete.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.