General Metrics

The general metrics used in Kentik queries are discussed in the following topics:

Notes:
- The categorization of metrics in the topics below corresponds to the categories by which they are grouped in the Metrics dialog (see Metrics Dialog UI).
- For general information about metrics in Kentik, see About Metrics.
- For metrics that aren't transmitted via a flow protocol, see Non-flow Metrics.
- For metrics that are device-specific, see Device-specific Metrics.
- Metrics that are available as filter or group-by dimensions are covered in the KB's Dimensions Reference (see Per-flow Metrics).
- In addition to being used for query settings in the Kentik portal, metrics are also used for the Query API.

 

About General Metrics

In Kentik, general metrics are metrics that are transmitted via a flow protocol (e.g. NetFlow, sFlow, etc.) and aren't specific to a particular device, such as an individual model of router. The general metrics that are available in a given setting, such as the Metrics Pane of the Query sidebar in Data Explorer, vary depending on the category of the device (Router or Host; see Supported Device Types) as well as the specific device type.

 

Metrics from All Devices

If a given query includes only traffic from data sources (see About Data Sources) in the "Routers" category then only the metrics in the table below are available (for descriptions of the KDE columns from which metrics are derived, see Metrics Columns):

Metric in portal Variations Calculated as... Derived from KDE column(s)
Bits per second Sampled at:
- Ingress and Egress
- Ingress
- Egress
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
in_bytes,
out_bytes
Packets per second Sampled at:
- Ingress and Egress
- Ingress
- Egress
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
in_pkts,
out_pkts
Flows per second N.A. - Average
- 95th Percentile
- 99th Percentile
- Max
- Total
Based on rows per KDE main table
Source IPs - Unique Count
- Bitrate per IP
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
inet_src_addr
Destination IPs - Unique Count
- Bitrate per IP
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
inet_dst_addr
Unique Route Prefixes - Source
- Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
inet_src_route_prefix,
inet_dst_route_prefix
Unique Ports - Source
- Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
inet_src_route_prefix,
inet_dst_route_prefix
Unique ASNs - Source
- Destination
- Next Hop Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
src_as,
dst_as,
i_dst_nexthop_as_name
Unique Countries - Source
- Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
src_geo,
dst_geo
Unique Regions - Source
- Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
src_geo_region,
dst_geo_region
Unique Cities - Source
- Destination
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
src_geo_city,
dst_geo_city
Sample rate - Max
- Average
- Average
- 95th Percentile
- 99th Percentile
- Max
- Total
sample_rate

Notes:
- When "Total" is shown in the "calculated as" list for a metric above, the Total metric will only be available if the chart type is set to Table or Matrix (see Chart View Types).
- Metrics whose name includes "unique" involve evaluating all instances across all queried devices within each individual time slice covered by the query's time range (see Table Time-slicing) but not between time slices.

 

Host Traffic Metrics

If the traffic being queried includes traffic from any devices in the category of "Host" (i.e. kprobe host agent; see About kprobe) then data from those hosts will be stored in KDE to make available host-only metrics, which are covered in the following topics:

 
top  |  section

Host Metrics by Protocol

As shown in the table below, the availability of a given metric varies depending on the protocol:

Metric in portal TCP HTTP DNS Calculated as... Derived from KDE column(s)
Retransmits - Per second
- Repeated per second
- Percent
- Percent Repeated
- Repeated Retransmits
- Retransmitted Packets Out
N.A. - Average
- Percentile (95th or 98th)
- Max
- Total
retransmitted_out_pkts, repeated_retransmits,
both_pkts (for %)
Out-of-order packets - Per second
- Percent
- Per second (In) N.A. - Average
- Percentile (95th or 98th)
- Max
- Total
ooorder_in_pkts,
ooorder_out_pkts,
both_pkts (for %)
Fragments - Per second
- Percent
- Per second - Per second - Average
- Percentile (95th or 98th)
- Max
- Total
fragments,
both_pkts (for %)
Zero Windows - Count
- Percent
- Per second N.A. - Average
- Percentile (95th or 98th)
- Max
zero_windows
Receive Window N.A. N.A. N.A. - Average
- Percentile (95th or 98th)
- Max
receive_window
Latency - Client
- Server
- Application
- First Payload Exchange
- Client
- Server
- Application
- FPEX
- Application - Average
- Percentile (95th or 98th)
- Max
client_nw_latency_ms,
server_nw_latency_ms,
appl_latency_ms,
fpex_latency_ms

Note: When "Total" is shown in the "calculated as" list for a metric above, the Total metric will only be available if the chart type is set to Table or Matrix (see Chart View Types).

 
top  |  section

Host Metrics Descriptions

The following descriptions apply to the host-only metrics listed in the table above:

  • Retransmits: Packets that are re-sent from source to destination; applies only to traffic using a reliable transport protocol such as TCP. Retransmission indicates network delivery issues that can degrade application/service performance. Retransmits are measured per second and also as a percentage of all packets sent, which reveals aggregate efficiency in the full context of expected total capacity.
    Note: "Repeated" represents the number of times a given packet was retransmitted 3 or more times.
  • Out of order: Packets that arrived at the destination out of sequence. A high value indicates potential variability in delivery paths and is particularly detrimental to latency-sensitive traffic such as real-time audio or video. Out of order packets are measured per second and also as a percentage of all packets sent.
  • Fragments/second: Packets per second that have been split into smaller packets for delivery across the network. Fragmentation and reassembly can increase CPU load and also cause retransmits when fragments arrive out-of-order. Fragments are measured per second and also as a percentage of all packets sent.
  • Zero Windows: Count of TCP receive windows with value of zero (indicating full buffer).
  • Receive Window: Size of TCP receive window.
  • Latency: Several different measure of latency are provided:
    - RTT/2 client latency (derived): One-way network latency as measured from the client perspective (in a client-server relationship). High values indicate latency problems in the network or at the server end of the flow.
    - RTT/2 server latency (derived): One-way network latency as measured from the server perspective (in a client-server relationship). High values indicate latency problems in the network or at the client end of the flow.
    - RTT/2 application latency (derived): A measure of one-way network latency that is derived by examining request/response pairs at the application layer (i.e. HTTP GET vs. first response). While this measure can be a reasonable proxy for end-user experience of application response, it only works for application protocols that have clear request/response pairings.
    - First Payload Exchange Latency: Used to measure application response time, particularly when the protocol isn't understood or can’t be decoded (e.g. HTTPS, SQL, etc.). The time, which excludes TCP setup, starts with the first packet sent (typically the request) and stops with the first packet returned (typically the response).
 
top  |  section

Host Metrics KDE Columns

The following table shows the correspondence between the metrics described above and the columns of the KDE:

Metric in portal Type:
value
column
Derived from KDE column(s)
Retransmits bigint
Native
retransmitted_out_pkts, repeated_retransmits,
both_pkts (for %)
Out-of-order packets bigint
Native
ooorder_in_pkts,
ooorder_out_pkts,
both_pkts (for %)
Fragments bigint
Native
fragments,
both_pkts (for %)
Zero Windows bigint
Native
zero_windows
Receive Window bigint
Native
receive_window
Latency bigint
Native
client_nw_latency_ms,
server_nw_latency_ms,
appl_latency_ms,
fpex_latency_ms

Note: The KDE columns corresponding to the metrics listed above are shown in NPM Columns.

 

Application Decodes Metrics

When Kentik's kprobe host agent is used for application decodes (see About Application Decodes) it generates both dimensions and metrics that are stored in or derived from KDE columns. The following table shows the metrics from application decodes that may be used in queries via the metric selector (see Metrics Dialog UI):

Metric in portal Description Type:
value
column
Connection Name TCP connection ID. bigint
UDR
Application Latency One-way network latency derived by examining request/response pairs at the application layer. bigint
UDR
FPEX Latency Elapsed time from first packet sent to first packet returned. bigint
UDR

Note: For dimensions related to application decodes, see Application Decodes Dimensions.

Legacy Application Decodes Metrics

The "legacy" metrics in the table below are from kprobe versions before 1.3.0:

Metric in portal Description Type:
value
column
KDE name(s)
Connection ID TCP connection ID.
Note: Superseded by Connection Name.
bigint
Native
connection_id
Application Latency (ms) One-way network latency derived by examining request/response pairs at the application layer. bigint
Native
appl_latency_ms
First Payload Exchange Latency (ms) Elapsed time from first packet sent to first packet returned.
Note: Superseded by FPEX Latency.
bigint
Native
fpex_latency_ms
© 2014- Kentik
In this article:
×