graphprotocol / graphprotocol/indexer
Improve handling of unsupported subgraph indexing networks
Open
@dwerner is already working on this.
Since Jul 10, 2024.
enhancement
indexer-agent
p1
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
The UX for unsupported subgraphs is leaving a lot to be desired right now.
Why?
- We do not support indexing rules that specify the indexed network, so often subgraphs are identified for allocation that the graph-node cannot support.
- Deployments for unsupported subgraphs are attempted repeatedly and included in prometheus error metrics leading to false alarms in alerting and monitoring
These UX issues are amplified on a larger scale indexer like some of the E&N indexers. If subgraph deployments are hand selected by the indexer these pain points will likely not be exposed.
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.
Assessment
This issue has not been assessed yet.