A collection of Grafana dashboard templates for monitoring x402 payments across multiple merchants in the Faremeter ecosystem. These dashboards provide real-time insights into transaction flows, revenue metrics, and endpoint health for each merchant.
This repository contains merchant-specific dashboard configurations that are generated from a base template. Each dashboard visualizes:
- Revenue Metrics: Total earnings, daily breakdowns, and revenue trends
- Transaction Monitoring: Real-time transaction tracking, signatures, and status
- Endpoint Health: Live endpoint tracking and health status over time
- Network Distribution: Transaction patterns across different blockchain networks
- Merchant Analytics: Unique buyers, total requests, and endpoint usage patterns
The following merchants have configured dashboards:
- DFlow (
dflow-dashboard.json) - Helius (
helius-dashboard.json) - Nansen (
nansen-dashboard.json) - Titan Exchange (
titan-exchange-dashboard.json) - Triton (
triton-dashboard.json) - Yatori (
yatori-dashboard.json)
Dashboard files are automatically generated using a Makefile-based build system.
makejq
To generate dashboards for all merchants:
make allThis will create individual dashboard JSON files for each merchant configured in the Makefile.
To generate a dashboard for a specific merchant:
make <merchant-name>-dashboard.jsonFor example:
make dflow-dashboard.jsonTo remove all generated dashboard files:
make cleanThe generation process:
- Uses
corbits-merchant.jsonas the base template - Substitutes merchant-specific values throughout the dashboard configuration
- Customizes the dashboard title and UID
- Removes generic templating variables
Key variables replaced:
${merchant}→ Merchant name (e.g., "dflow", "helius")${merchant_name}→ Title-case merchant name (e.g., "Dflow", "Helius")
Each generated dashboard includes:
- Total Earnings (USD): Cumulative USDC revenue
- Daily Earnings Breakdown: Time series of daily revenue
- Total Requests: Aggregated transaction count
- Total Unique Buyers: Distinct incoming addresses
- Total Requests: Transaction volume
- Transactions Over Time: Daily transaction trends
- Live Networks: Active blockchain networks gauge
- Live Endpoints: Active endpoint count gauge
Shows the 7 most recent transactions with details including:
- Transaction signature
- Chain/network
- Direction (incoming/outgoing)
- Addresses
- Amount (with proper decimal handling)
- Status and timestamp
- Endpoint Distribution: Pie chart of revenue by endpoint
- Most Valuable Endpoints: Top 3 endpoints by revenue
- API Use Over Time: Daily transaction count trends
- Network Distribution: Transactions by blockchain network
- Health Status Over Time: Endpoint uptime percentages
- x402 News Feed: RSS feed integration for protocol updates
- Corbits Branding: Powered by Corbits with custom logo
- Custom Styling: Orange (#e98428) theme throughout
All dashboards connect to a PostgreSQL database via the Grafana PostgreSQL datasource (UID: ff126r144g1kwe). The data is sourced from:
accountstable: Merchant account informationtracked_addressestable: Wallet addresses per accounttransactionstable: Transaction recordsmetrics.endpoint_healthtable: Endpoint health metrics
- Open Grafana in your browser
- Navigate to Dashboards → Import
- Upload or paste the JSON content from any generated dashboard file
- Verify the PostgreSQL datasource is configured (UID:
ff126r144g1kwe) - Click "Import"
-
Add the merchant name to the
MERCHANTSlist inMakefile:MERCHANTS = dflow \ helius \ nansen \ titan-exchange \ triton \ yatori \ new-merchant
-
Generate the dashboard:
make new-merchant-dashboard.json
-
Test the dashboard by importing it to Grafana
To modify the base dashboard template:
- Edit
corbits-merchant.json - Ensure all merchant-specific values use
${merchant}or${merchant_name}variables - Regenerate all dashboards:
make clean && make all
These dashboards are based on CDP v0.1.0 (Corbits Dashboard Platform) and use Grafana schema version 42.
This project is licensed under the GNU General Public License v3.0. See the LICENSE file for the full text.
For issues or questions, please refer to the Corbits documentation or contact the Faremeter team.