Focused Path · Quick Checklist
Indexer volume determines whether your node earns efficiently or wastes cycles. Follow this concise checklist to identify the exact conditions your setup needs before scale.
THE SHORT VERSION
Indexer volume is the measurable flow of GraphQL queries your validator serves across assigned subgraphs each day. It differs from raw node uptime because volume captures actual useful work—queries answered correctly while respecting gas limits and client SLAs. Understanding volume prevents two mistakes: under-serving high-value contracts and over-committing on dead weight.
This guide structures indexer volume into four ordered phases—preparation, checks, execution, and review. Each phase contains observable completion criteria you can verify without guesswork. Follow them sequentially; skipping preparation causes downstream errors that inflate volume artificially and erode fee yield over time.
CHECK THESE FIRST
Scan these three checkpoints in order. Each one filters out a common indexer trap—oversubscribed subgraphs, invisible cost creep, and stagnant query routing.
Indexer volume reflects how much query throughput your node handles daily. Monitoring this metric lets you spot demand spikes, tune caching, and avoid dropping expensive requests. Track it alongside query errors to separate real growth from noise.
When volume climbs without proportional fee revenue, indexers bleed on gas and bandwidth costs. A volume guide shows you where margins shrink so you can rebalance subgraph assignments or raise service thresholds before losses accumulate.
Volume distribution across subgraphs reveals which indices earn the most per compute cycle. High-volume, low-fee subgraphs consume resources better spent on niche contracts with tighter query concentration. Reallocating improves overall yield.
THE ACTION CHECKLIST
Work through these four stages each time you onboard a new subgraph or reassess an existing indexer deployment. Stop at any stage until its completion criteria are visibly satisfied.
QUICK CLARIFICATIONS
Practical answers about indexer volume guide.
Look for consistent subgraph assignment stability first. If your index keeps restarting or queries stall, volume inflates artificially from retries. Confirm healthy node uptime and clean Prometheus counters before trusting the numbers.
Set alerts when daily volume exceeds your historical median by more than two standard deviations. Investigate immediately—sudden spikes usually come from misconfigured clients replaying queries or a new dApp routing all traffic through your endpoint.
Yes. Many indexers cap concurrent connections per subgraph, and exceeding the limit silently degrades latency. Lower your volume target on heavy contracts and shift capacity to underserved indices for steadier fee accumulation.
SOURCE NOTES
These external references were retrieved for editorial fact checking. Readers should consult the original publishers for full context.
READY TO TAKE ACTION?
Review the checklist below, run through every stage once, then update your indexer configuration. Small volume adjustments now prevent costly re-indexing later.