GraphQL mutations to bisect POI divergences and fetch entity changes and cache contents metadata

[neysofu]

No description provided.

[fordN]

Placing a strawperson proposal here to kick off discussion around the interfaces we use here.

type mutationRoot {
    deploymentPOIReport(deployment: String!): DeploymentPOIReport
    divergenceReport(deployment: String!, blockNumber: String!): Divergence
}

type DeploymentPOIReport { 
    deployment: String!
    uniquePoisCount: Int!
    latestBlockPois: [POI!]
    divergences: [Divergence!]
}

type Divergence {
    block: Block!
    deployment: String!
    uniquePoisCount: Int!
    poiReports: [POIReport!]
}

type Block {
    number: Int!
    hash: Bytes!
}

type POI {
    block: Block!
    hash: Bytes!
    deployment: Deployment!
    indexersCount: Int!
    allocatedTokens: BigInt
    indexers: [Indexer!]
}

type POIReport {
    poi: POI!
    blockCache: BlockCache
    callCache: CallCache
    entityChanges: entityChanges
}

[neysofu]

I think it's a good start! I have a few suggestions, in no particular order:

• Block should also have a network field.
• I don't think there's yet any plans to include allocatedTokens in POI. We can leave the field optional and not populate it, for now.
• I think there's some confusion in the schema with regards to subgraph versus deployment. A POI should have a subgraph field, and possibly deployments instead of indexers.
• Subgraph should have the manifest hash and network.
• Deployment should have a latestKnownPoi.

Still unsure how we should model divergences, but I think the proposed mutations are too high-level. The workflow that I imagine requires the investigator persona to look at a dashboard, notice that are e.g. 3 different POI values at the latest block, and launch investigations between those POIs. We may automate more of it in the future but the "primitive" investigation capability is between two POIs, fundamentally.