Metrics¶
Type |
Name |
Labels |
Comments |
|
---|---|---|---|---|
Counter |
roq_counter |
Gateway specific. |
||
Histogram |
roq_inter_process_latency |
|
|
|
Histogram |
roq_latency |
|
Gateway specific.
Typically measuring transport level ping/pong latency as |
|
Histogram |
roq_profile |
|
Function profiling |
|
Counter |
roq_clients |
|
Counts number of client events, e.g. |
|
Histogram |
roq_events |
|
Profile incoming events. |
|
Counter |
roq_exceptions |
|
Counts client requests rejected by the gateway. |
|
Histogram |
roq_heartbeat_latency |
|
( |
|
Counter |
roq_process |
|
Process information, e.g. |
|
Histogram |
roq_round_trip_latency |
|
|
|
Counter |
roq_updated |
|
Counts number of state changes for a connection.
States may include e.g. |
|
Counter |
roq_event_log |
|
Counts activity, e.g. |
|
Histogram |
roq_market_data_latency |
|
|
|
Histogram |
roq_request_latency |
|
Measures request round-trip latency, i.e. request send time to ack receive time.
The |
|
Histogram |
roq_journal_latency |
|
|
|
Histogram |
roq_end_to_end_latency |
|
|
|
Gauge |
roq_rate_limiter |
|
Exchange rate limiter usage (pass-through, i.e. no attempt to normalize). |
|
Notes¶
The
source
label has the name of the component (usually the--name
flag). Used when measuring something at the component level, e.g. function profiling.The
sender
andreceiver
labels are also names of components. Used when measuring something happening between two components, e.g. heartbeat.The
category
label is used with event-logs to enumeratepublic
andprivate
data streams.The
name
label is typically used withcategory
to identify a measurement point.The
event
label is used to indicate a specific event.Histograms used for profiling anything internal to the process use the following buckets (in nanoseconds)
500, 1000, 2000, 5000, 10000, 20000
Histograms used for profiling anything external to the process use the following buckets (in nanoseconds)
10000, 100000, 1000000, 10000000, 100000000, 1000000000