Dashboard description

Once your are in the Grafana: http://YOUR_ANALYZER_HOST_IP:12021, you can connect to it as a viewer with the credentials provided by the onboarding LT team.

These default credentials must be changed on the first use for security reasons.

It is also possible to connect with other roles if needed: admin and editor. If you want to have access to those roles, contact your Latence Technologies vendor.

Content

Once connected, you will have access this tools:

  1. Network status summary
  2. Detailed latency charts
  3. Latency forecast
  4. Latency Heatmap
  5. Bandwidth
  6. Traceroute
  7. Multi-agent comparison
  8. Analyzer Monitoring

Dashboard Menu

Dashboard Menu

For all dashboards, we can select the customer ID for which we want to filter the agents (1).
Similarly, we can select the agent for which we want to see all the data (2).
Besides, it is possible to change the time range and the refresh rate using the top menu (3).
You can navigate to other dashboards by clicking on their corresponding icon (4).

Network Status Summary

Network Status Summary

On this compact dashboard above, we can see the main information for our network before seeing the details in the other dashboards.

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

We can analyze the following data:

  • Connectivity quality indicators (1)
    • Stability: the network stability is computed based on standard deviation, drops, and events.
    • Volatility: the volatility is calculated using the maximum and minimum values in the data range. Having a low volatility means that we have a stable network.
      Volatility formula:
    • Download packet loss rate: number of lost packets divided by the number of measurements during the time range selected for download.
    • Upload packet loss rate Rate: number of lost packets divided by the number of measurements during the time range selected for upload.
    • Jitter: variation in time delay between when a signal is transmitted and received over a network connection, measuring the variability in latency. The formula is mean(abs(differences between values)). It analyzes all the values in the time range selected.
      Example:
      Let’s say we have 5 samples with the following latencies: 136, 184, 115, 148, 125 (in that order). The average latency is 142 - (add them, divide by 5). The jitter is calculated by taking the difference between samples.
      136 to 184, diff = 48
      184 to 115, diff = 69
      115 to 148, diff = 33
      148 to 125, diff = 23
      (Notice how we have only 4 differences for 5 samples). The total difference is 173 - so the jitter is 173 / 4, or 43.25.
  • Connectivity Health indicator (2)
    • This high level indicator takes into consideration stability, volatility, application latency and the threshold set in the agents (expected application latency and expected stability that must be defined at launch by user, 30 ms and 95% otherwise).
    • It can indicate Good when the stability and latency thresholds are respected, Warning when one of the previous condition is not respected and Need attention as soon as the stability and latency thresholds are not respected with a 20% margin.
  • Agent informations (3) are some of the metadatas about the selected agent.
    • Agent ID: Unique identifier for the device that is collecting data.
    • Agent Name: Agent or site name. Must be defined at launch by user, empty otherwise.
    • Hardware: Type/model of equipment where the agent is installed. Must be defined at launch by user, empty otherwise.
    • Address: Agent's physical address. Must be defined at launch by user, empty otherwise.
    • Network name: Name of the network used by the probe to reach the reflector (if applicable). Must be defined at launch by user, empty otherwise.
    • Network type: Network type used (4G, 5G, WIFI, etc). Must be defined at launch by user, empty otherwise.
    • Details: Raw text field for more details about this agent. Must be defined at launch by user, empty otherwise.
    • Docker version: Version of the QoS-Agent used.
  • Latency indicators (4)
    • Application: the application latency is the mean of the HTTP, HTTPs, TCP and UDP latencies.
    • Expected application latency: correspond to the threshold the user created when initializing the agent
    • Network: the network latency is the mean between ICMP and TWAMP latencies.
    • Latency by protocol
    • Latency history
  • Bandwidth indicators (5)
    • Bandwidth data with TCP and UDP upload speed and download speed.
    • The bandwidth history data over the last 12 hours.

Detailed latency charts

Detailed latency charts

On this detailed latency chart dashboard above, we can see the detailed information of latency for each protocol.

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

Then you can analyze the following data:

  • The number of Events and Event rate for each protocols (1): unexpected pattern in the QoS. It's only when we detect multiple events in a row that we can consider it as an anomaly. This event rate is the number of events divided by number of measurements during the time range selected.
  • The mean latency for each protocols for the selected time range (2).
  • A chart (3) in which we can see the history for the time range selected of the latency and the Events marked with a red dot.
  • The last 100 latency samples (4).
  • For the TWAMP protocol, you can also see at the bottom of the page the latency decomposed between the time for a roundtrip and the time for processing.

Latency forecasting

Latency forecast

On the Latency forecasting dashboard above, we can see charts given by a statistical model.

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

After, you can analyze the following data:

  • The predicted latency after 30s using exponential smoothing (1).
  • The latency forecast interval, in milliseconds (2).
  • The confidence level of the forecasting (3).
  • The current latency compared to the forecasted one for the last 5 minutes and the forecasted latency for the next 30 seconds (4).

Latency Heatmap

Latency Heatmap

On this heatmap dashboard, we can visualize the latency measurement in space gathered by a QoS-Agent in motion (for example with the MobileLatency app).

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

Then you can analyze the following data:

  • The heatmap created by the QoS-agent in motion (1).
  • The details of the notes created from the MobileLatency app (2).
  • The last 100 latency samples (3).

Bandwidth

Bandwidth

On this bandwidth dashboard, we can see the details of the bandwidth metrics. For measuring bandwidth we use an Iperf tool inside the QoS-Agent.

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

Then you can analyze the following data:

  • Bandwidth data (1) with TCP and UDP upload speed and download speed.
  • The bandwidth history data over the last 12 hours (2).

Traceroute

Traceroute

On the traceroute dashboard, we can see a map giving the route between the agent and the reflector. A new traceroute is done at the time interval specified in your configuration. Make sure to disable any ad-blockers to use the dashboard. It can take up to 5 minutes to get the data.

First, make sure that the agent ID selected is the one for which you wish to view data (see it here).

You can analyze the map in which we will have the location of the different hop passed by the route.
We have a table which details the IP and delays of these hops.

Multi-agent Comparison

Multisite Comparison

On the Multi-agent comparison dashboard, we can select more than 1 agent ID (1) and display their network informations in order to compare it.

First, select on the top left the agent ID for which you wish to compare data. You can select 1, 2 or more agent ID and their respective panels will appear one below the other.

We can visualize data from the Network Status Summary dashboard as well as data from the Bandwidth dashboard.

Analyzer Monitoring

Analyzer monitoring

The analyzer monitoring dashboard displays various metrics about current status of the analyzer's host:

  • The current status of the analyzer (1) with from left to right the CPU usage, the load average, the memory usage, the percentage disk used, the disk IO and the network IO.
  • The detailed history charts for each indicators (2).

Customized Dashboard

If you need a customized dashboard, please reach out to your Latence Technologies vendor.