Skip to main content
The metrics endpoint exposes internal node telemetry in Prometheus text format using Micrometer. These metrics can be scraped by a Prometheus server or compatible monitoring system to observe the health and performance of DAG L1 nodes.
All endpoints return the following response headers:
  • X-Id — The node’s public key identifier
  • X-Session-Token — The current cluster session token
  • Request-Signature — Cryptographic signature of the response for verification

​
GET /metrics

Returns Micrometer-instrumented Prometheus metrics for the DAG L1 node. 
curl https://<node-host>:9010/metrics
Response 200 OK Returns a text/html body in Prometheus exposition text format. Metrics include JVM memory and GC stats, HTTP request counts and latencies, consensus round timings, mempool size, peer counts, and block production rates. Example response: 
# HELP jvm_memory_used_bytes The amount of used memory
# TYPE jvm_memory_used_bytes gauge
jvm_memory_used_bytes{area="heap",id="G1 Eden Space",} 6.7108864E7
# HELP http_server_requests_seconds Duration of HTTP server request handling
# TYPE http_server_requests_seconds summary
http_server_requests_seconds_count{method="POST",status="200",uri="/transactions",} 128.0
http_server_requests_seconds_sum{method="POST",status="200",uri="/transactions",} 1.842
To integrate with Prometheus, add a scrape job to your prometheus.yml:
scrape_configs:
  - job_name: tessellation-l1
    static_configs:
      - targets: ['<node-host>:9010']
    metrics_path: /metrics

Build docs developers (and LLMs) love

Get started for freeTalk to us