-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
.1. need to determine endpoint
2. from Christian's doc in v2 context:
Flow Metrics: Skupper 1.x
Currently skupper exports seven different flow metrics. These metrics are inferred in the collector by correlating pairs of Flow events as the sender and receiver side of a connection or request/response exchange and relating them to processes on either side of the exchange. Each of these metrics shares a common set of labels.
Common Labels
address: The VAN address that traffic is being measured over.
sourceSite: The VAN site originating the traffic being measured. An amalgamation of the skupper site name, a magic sequence @_@, and the site ID.
destSite: The VAN site receiving the traffic being measured. An amalgamation of the skupper site name, a magic sequence @_@, and the site ID.
direction: The direction of traffic being measured. For traffic sent from a client to server “incoming”, from server to client “outgoing”.
protocol: The protocol at which skupper is operating. tcp, http, http2
sourceProcess: The name of the process originating the traffic being measured.
destProcess: The name of the process receiving the traffic being measured.
Metrics
flows_total depending on the protocol, either the number of connections or distinct requests made.
octets_total total bytes routed
active_flows the number of flows currently active - this includes open tcp connections as well as in flight http requests.
address_last_time_seconds time since a flow was last observed
flow_latency_microseconds latency as observed by the data plane while routing traffic
http_requests_method_total count of http requests by method
Additional label: method - the http request method: ex GET, HEAD, POST, etc.
http_requests_result_total count of http requests by response code
Additional label: code - the http response code: ex 200, 403, 503