Understanding my Method Call Breakdown (in "metrics" tab)

The "Method Call Breakdown" section of your metrics page provides valuable insight regarding the methods you are using and the communication protocol (HTTP/WebSockets) associated with these calls. It is wise to regularly check the metrics related to your endpoint, as understanding your usage will assist in:

• Determining when a plan upgrade may be necessary.
• Keeping track of your remaining API Credits (found in the "Billing" section of your dashboard) and allowing you to limit usage or upgrade your subscription before exceeding monthly limits. 
• Detecting suspicious activity and potential security risks.
• Ensuring there are no connections that have been left open by mistake.

This last point regarding "open connections" is especially important for event subscriptions over WebSockets. Whether you are streaming pending transactions, listening for new blocks, or actively listening for any other event, it is essential to ensure that this connection is closed when it is no longer needed. Failure to do so may result in unexpected usage and excess on your next bill. Learn more about "unsubscribing" with:

• wscat 
• ethers 
• web3.js & web3.py

All responses received by an open WebSocket connection will be counted under the "ws_subscription" category; we charge per RESPONSE, not per REQUEST.

For example: subscribing to pending transactions results in 1 "call" (request), but it's a subscription that may generate hundreds or thousands of responses. Each of these responses will be counted under the "ws_subscription" category.