From d3aa395baccfe4682caa55c0fee0ba217f9dc2fc Mon Sep 17 00:00:00 2001 From: Theo Butler Date: Tue, 23 Jan 2024 09:35:08 -0500 Subject: [PATCH] docs: add example for manual POI fetch (#554) --- docs/incident-response.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/incident-response.md b/docs/incident-response.md index 03ea6068..ae7a1405 100644 --- a/docs/incident-response.md +++ b/docs/incident-response.md @@ -33,7 +33,14 @@ For indexers, note that automated allocation management might not allocate to a ### Bad/Inconsistent Query Responses -- Graphix is a useful tool to checked if allocated indexers have divergent POIs, and might indicate give hints about which indexers might have the POI driving the bad responses. +- Graphix is a useful tool to check if allocated indexers have divergent POIs, and might indicate which indexers are delivering the bad responses. + + If tools like Graphix are not available, you can query the relevant indexers manually to get their POIs: + ```bash + curl ${indexer_url}/status \ + -H 'content-type: application/json' \ + -d '{"query": "{ publicProofsOfIndexing(requests: [{deployment: \"${deployment}\" blockNumber: ${block_number}}]) { deployment proofOfIndexing block { number } } }"}' + ``` - If a POI is identified that should be blocked, it should be added to the gateway config’s `poi_blocklist`.