Skip to content

Optimum Gateway Metrics

Gateway Metrics

When telemetry_enable: true, metrics are exposed at http://localhost:48123/metrics.

All gateway metrics include the gateway_id label.

Always Present (at startup)

MetricTypeDescription
optp2p_gateway_optimum_gateway_app_build_infoGaugeBuild info: version, commit, go, public_ip
optp2p_gateway_optimum_gateway_opt_peersGaugemump2p peers connected
optp2p_gateway_optimum_gateway_opt_peer_connected_totalCounterCumulative mump2p peer connections
optp2p_gateway_optimum_gateway_aggregation_included_totalCounterMessages included in emitted aggregated protobufs
optp2p_gateway_optimum_gateway_system_cpu_coresGaugeLogical CPU cores
nodes_active_totalGaugeActive nodes in the proxy (0 when running gateway without proxy)
optimum_p2p_active_topicsGaugeActive mump2p topic subscriptions

With CL Peer Connected

When a CL client connects to the gateway and subscribes to topics, these metrics appear:

MetricTypeLabelsDescription
optp2p_gateway_optimum_gateway_cl_peersGaugeCL peers connected to gateway
optp2p_gateway_optimum_gateway_cl_peer_connected_totalCounterCumulative CL peer connections
optp2p_gateway_optimum_gateway_cl_peer_disconnected_totalCounterCumulative CL peer disconnections
optp2p_gateway_optimum_gateway_cl_peers_per_topicGaugetopicCL peers connected per topic
optp2p_gateway_optimum_gateway_libp2p_total_messagesCounterMessages delivered into all libp2p topics
optp2p_gateway_optimum_gateway_libp2p_published_messages_per_topic_totalCountertopicMessages published to libp2p per topic
optp2p_gateway_optimum_gateway_optimum_total_messagesCounterMessages sent to mump2p
optp2p_gateway_optimum_gateway_optimum_published_messages_per_topic_totalCountertopicMessages published to mump2p per topic
optp2p_gateway_optimum_gateway_opt_peers_per_topicGaugetopicmump2p peers per topic
optp2p_gateway_optimum_gateway_opt_peer_disconnected_totalCounterCumulative mump2p peer disconnections
optp2p_gateway_optimum_gateway_mump2p_messages_from_origin_totalCounterorigin_gateway_idMessages received from each origin gateway
optp2p_gateway_optimum_gateway_mump2p_messages_from_upstream_totalCounterupstream_peer_idMessages received from each upstream mump2p peer
optp2p_gateway_optimum_gateway_message_size_bytesHistogramtopicSize of messages received over libp2p
optp2p_gateway_optimum_gateway_message_size_minGaugetopicMinimum message size (bytes)
optp2p_gateway_optimum_gateway_message_size_meanGaugetopicMean message size (bytes)
optp2p_gateway_optimum_gateway_message_size_maxGaugetopicMaximum message size (bytes)
optp2p_gateway_optimum_gateway_processing_time_nanosecondsHistogramprocessProcessing duration; process is cl_processing or opt_processing

Block Arrival & First-Seen Metrics

When telemetry is enabled and both CL and mump2p paths are active, these metrics track per-block performance:

MetricTypeLabelsDescription
optp2p_gateway_optimum_gateway_block_arrival_mump2p_msHistogramBlock arrival latency via mump2p relative to slot start (ms)
optp2p_gateway_optimum_gateway_block_arrival_libp2p_msHistogramBlock arrival latency via libp2p relative to slot start (ms)
optp2p_gateway_optimum_gateway_blocks_first_seen_mump2p_totalCounterBlocks where mump2p delivered strictly before libp2p
optp2p_gateway_optimum_gateway_blocks_first_seen_libp2p_totalCounterBlocks where libp2p delivered before or equal to mump2p

Geolocation

MetricTypeLabelsDescription
optp2p_gateway_det_coordinates_geo_locationGaugecountry, latitude, longitudeGateway geolocation coordinates

Process Metrics

Standard Go and process metrics (go_*, process_*) are exposed for resource monitoring.

Quick Checks

sh
curl -s http://localhost:48123/metrics | grep optp2p_gateway

With CL connected: cl_peers ≥ 1, libp2p_total_messages increments, optimum_total_messages increments.