Each ACCP instance in the VUE can be independently configured to collect an RPD statistics sample every 60 to 3600 seconds (default is 60 seconds). During each collection period the ACCP collects information about each channel configured in the RPD/RMD. Example of these statistics are session statistics, out of sequence packets, received packet counts, discarded packet counts, output packet counts, output errors, discarded output packets, etc. The following is a detailed list of all statistics collected by each ACCP instance.

• chStats [array] – An array of channel statistics for each remote device.
• devId (string) – Identifies the remote device's MAC address.
• devAlias (string) – Identifies the device alias as configured on the remote device. A remote device may provide a device alias when it first connects to the VUE. This attribute is not included if no device alias is provided by the remote device.
• timestamp (integer) – Represents the timestamp in milliseconds since midnight of January 1, 1970 of when this sample was taken by the VUE ACCP.
• upTime (integer) – Represents the timestamp in milliseconds since midnight of January 1, 1970 of when this sample was taken by the VUE ACCP.
• mpegCnt (integer) – Represents the timestamp in milliseconds since midnight of January 1, 1970 of when this sample was taken by the VUE ACCP.
• egressThr (number) – Identifies the dropped Egress threshold (in 0.00%) ranging from 0.00 – 100.00%. The dropped Egress threshold represents the number of dropped Egress packets (Δl2tpIn*mpegCnt - ΔchOut) compared to the total number of MPEG packets transmitted (Δl2tpIn * mpegCnt).
• ingressThr (number) – Identifies the dropped Ingress threshold (in 0.00%) ranging from 0.00 – 100.00%.  The dropped Ingress threshold represents the number of dropped Ingress packets (ΔvuePkts - Δl2tpIn) compared to the total number of VUE packets transmitted (∆vuePkts).
• oosThr (number) – Identifies the out-of-sequence threshold (in 0.00%) ranging from 0.00 – 100.00%. The out-of-sequence threshold represents the number of out-of-sequence DEPI packets (∆l2tpOos) compared to the sum of total number of received DEPI packets (Δl2tpIn) and total number of received session DEPI packets discarded (Δl2tpDis).
• stats (array) – An array of statistics for each channel within each remote device. The channel statistics consist of L2TP session statistics and RF channel statistics. The L2TP session statistics represents a count of L2TP session packets where a single L2TP session packet contains 7 or 10 MPEG packets depending on the VUE configuration. The RF channel statistics represents the number of MPEG packets. Both the L2TP session statistics and RF channel statistics are the count of packets since the remote device was last restarted, the statistics were reset or since a statistic as rolled over. Thus, the set of statistics counts are only valid if each statistics count remains the same or increase. Anytime any one of the counts decreases, the entire set of statistics for the channel may be incomplete.
• chId (string) – Identifies the RF port, channel index and type of the channel as “{RF-port}.{Channel-Index}.{Type}” where {RF-port} is 0 – number of RF ports, {Channel-Index} is 0 – number of channels of the given type and {Type} is ‘Q’ for DS SC-QAM channel, ‘F’ for DS OOB SCTE 55-1 channel and ‘R’ for US OOB SCTE 55-1 channel.
• chName (string) – Identifies the channel’s name, if a name has been configured for the channel. This attribute is not included if no channel name exist.
• session (string) – Identifies the L2TP session ID of the DEPI/UEPI tunnel associated with the channel. The value is a hexadecimal string without the leading "0x".
• l2tpOos (integer) – Indicates the number of received session packets that were received out of sequence from the point of view of the remote device.
• l2tpIn (integer) – Indicates the number of received session packets accepted for processing above the L2TPv3 protocol layer. The l2tpIn count excludes packets dropped by the L2TPv3 protocol layer itself (for example, InDiscards).
• l2tpDis (integer) – Indicates the number of received session packets discarded by the L2TPv3 protocol layer itself. This count includes those packets discarded because they were out of sequence.
• l2tpOut (integer) – Indicates the number of session packets conceptually attempted to be transmitted from above the L2TPv3 protocol layer.
• l2tpErr (integer) – Indicates the number of session packets attempted to be transmitted from above the L2TPv3 protocol layer that could not be transmitted below the L2TPv3 protocol layer itself.
• chDis (integer) – Indicates the number of outbound MPEG packets which were internally discarded before transmission, for example, due to lack of buffering.
• chErr (integer) – Indicates the number of outbound MPEG packets that could not be transmitted because of errors.
• chOut (integer) – Reports the number of outbound MPEG packets successfully transmitted on the channel.
• status (integer) – Indicates the current alarm status and the operational status of the channel. The value is set to the operational status plus the sum of all active channel alarms. For the operational status, a 1 indicates the channel is up (i.e. channel is configured and RPD is capable of sending or receiving data on channel) and a 2 indicates the channel is down and not operational. The following is a list of all channel alarms where the following values are: 16 indicates Out Of Sequence Packets Error, 32 indicates a Dropped Ingress Packets Error, 64 indicates a Dropped Egress Packets Error and 128 indicates a Channel Configuration Error. Thus a status value of 49 represents that the channel is up and has 2 active alarms, Out Of Sequence Error and Dropped Ingress Packets Error (1 + 16 + 32).
• vuePkts (integer) – Indicates the number L2TP session packets sent by the VUE since the ACCP was last started or the remote device established a connection with the ACCP.

Internally the VUE maintains another closely related copy of this channel specific data set to support telemetry. When telemetry is enabled on an ACCP instance, Telegraf pushes each unique sample of the http://accpInstanceServer:18079/accp/statistics payload to a time series data base. Telegraf runs on a separate container in parallel with each ACCP instance similar to filebeats. While Telegraf is fully configurable, VUE provides an example configuration file and visualization scheme using the ELK stack. This example configuration provides two new ELK dashboards described in the following sections.

DAA Telemetry

The vue_metrics_dashboard provides a series of visualizations to summarize the statistics provided by http://accpInstanceServer:18079/accp/statistics over time.

The first set of visualizations on this dashboard provides controls to narrow down the channels of interest in subsequent visualizations. By default, only video channels are shown in the visualizations because OOB bit rates are low and variable, throwing off the scaling applied to graphs. Once the source selection parameters are set, the "Metrics Available" control gives a list of the RPDs and number of channels appearing in subsequent plots. In the screenshot below we have one RPD with 16 channels matching the selection criterion. Note the chType Q is video and is derived from the chId parameter of each sample.

Node Health Telemetry

The vue_node_dashboard provides basic server health information. This data comes "for free" once telemetry is enabled. Telegraf supports a rich set of server health information so a user could use this example as a base to capture a far more complete picture of node health. The example shows CPU usage, memory usage, and disk usage over time. For steady state, these should be constant.