Overview
Observability shows your account's traffic, usage, performance, errors, and transactions in the Quicknode dashboard. It is available to all users.
The main tabs are Traffic, Usage, Performance, Errors, and Transactions. Integrations is also available from the Observability navigation.
Where Filtered by team access appears, results include resources your active teams can access and resources not assigned to a team.
Traffic
Traffic shows recent successful requests and metered data usage. The summary cards show requests, data, credits, and active methods. Below them, time windows break activity down by method, with request rate, data usage, and credits for each window.
Choose a time range to watch traffic. Last 5 minutes and Last 15 minutes update live; choose a refresh interval or pause updates. Use Filters to narrow the view. Failed requests are investigated in Errors.
Usage
Usage has Usage and API Credits views. Use the time range and Cumulative control to inspect usage over time.
The Usage view has separate charts for Endpoint API calls, Metered endpoint data, Webhooks, Streams, Key-Value Store, SQL Explorer, and IPFS. The Endpoint API calls and Metered endpoint data charts offer grouping, filters, and expandable breakdowns.
Performance
Performance charts method response time. Select a time range, use Filters to narrow the data, and choose a percentile or Filter outliers when investigating a spike. Expand Breakdown below a chart to inspect its contributors.
Errors
Errors shows the error rate alongside HTTP status and chain error summaries. Switch between All, Chain, and HTTP issues, or search by code, method, or endpoint. Expand an issue to inspect it, and expand a chart when you need more room to read it.
Transactions
Transactions lists transactions sent through your endpoints, with their network, status, endpoint, and number of tries. Filter by time range or status, then search by transaction hash or signature. Search applies within the selected time range and filters. Expand a row to inspect a transaction.
Observability Usage and Billing Usage
Observability Usage shows account activity. Billing Usage shows consumption for a billing period.
| View | Use it for |
|---|---|
| Observability → Usage | Investigating account traffic and usage alongside performance, errors, and transactions. |
| Billing → Usage | Reviewing usage for your billing period. Billing opens on Plan; select Usage for billing-period usage. |
Programmatic access
The Admin API and CLI provide access to selected data shown in Observability:
| Data | Admin API | CLI |
|---|---|---|
| RPC credit usage | Usage totals and usage by endpoint | qn usage summary, qn usage by-endpoint |
| Time-series metrics | Account metrics and endpoint metrics | qn metrics account, qn metrics endpoint |
| Request logs | Endpoint logs (Enterprise) | qn endpoint logs (Enterprise) |
The metrics API includes method calls, response status, and response-time metrics. The logs API returns individual endpoint requests with status and error codes. The current public Admin API reference does not document an equivalent for the live Traffic feed or transaction-hash search in Observability.
The Admin API requires a paid plan; endpoint logs and the Prometheus Exporter are Enterprise features.