graphprotocol / graphprotocol/graph-node
Better diagnostics for failed GraphQL requests
Open
Nobody has claimed this yet.
area/graphql
monitoring
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
This code logs information about failed requests. It can happen quite a bit that the failure reason is logged as unknown Restructure the code to provide more detail, in particular, to provide a subgraph id when queries fail in more cases.
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
Start with server/http/src/service.rs lines 158-186 and trace how failed GraphQL requests produce the logged failure reason. Identify the failure paths that currently become unknown, then verify that query failures provide a subgraph id in more cases and that the diagnostics contain more detail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100