Skip to main content

Overview

The metrics API provides comprehensive performance data for a specific blockchain chain, including provider statistics, RPC method performance, and system resource usage.

Endpoint

Path Parameters

string
required
The chain identifier (e.g., ethereum, polygon, arbitrum)

Response

string
required
The chain identifier
integer
required
The numeric chain ID (e.g., 1 for Ethereum)
integer
required
Unix timestamp in milliseconds when metrics were collected
object
required
VM and system resource utilization
object
required
Aggregated performance metrics for the chain
array
required
Performance metrics for each provider
array
required
List of RPC methods that have been called on this chain
array
Detailed RPC method performance organized by provider
array
Detailed RPC method performance organized by method
integer
required
Timestamp when metrics were last updated

Response Example

Error Responses

Chain Not Found

HTTP Status: 404 Not Found

Missing Chain Parameter

HTTP Status: 400 Bad Request

Use Cases

Monitor Chain Performance

Track overall performance metrics for a blockchain:

Provider Performance Comparison

Compare performance across different RPC providers:

RPC Method Analysis

Analyze performance of specific RPC methods:

System Resource Monitoring

Monitor system resource usage:

Performance Dashboards

Integrate with monitoring tools like Grafana, Datadog, or Prometheus:

Notes

  • Metrics are updated in real-time based on actual RPC traffic
  • Performance percentiles (p50, p95, etc.) are calculated over a sliding window
  • Provider scores are calculated based on a combination of latency, success rate, and reliability
  • The rpc_performance_by_provider and rpc_performance_by_method fields provide the same data organized differently for convenience
  • System metrics reflect the Erlang VM’s resource usage, not the underlying host system