Skip to content

Request: a way to trace number of JSON RPC requests sent by the graph container #3712

@yuriychabanov

Description

@yuriychabanov

Hello,
we are running a private graph container with 2 subgraphs(standard 721 and 1155 from OZ). Infura is used as provider with 1M/day requests plan. Blockchain - Polygon PoS. Until recently it wasn't a question of number of requests since the 1M tier was always enough. Now I'm seeing ~3M requests daily in Infura billing stats, with eth_GetTrancationReceipt usage dominating 10x times over the rest of methods. To advance your questions, all the past blocks since contracts deployment have already been indexed far before the billing notice(I guess, half a year or so). Does the number look realistic? Is there a way to trace real invocation count and methods breakdown? That would help if we start disputing their billing. Thanks.
P.S.: Infura updated their billing mechanism a month ago - now they count batch requests individually. W/o the numbers from the graph it's only my assumption of possible reason though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions