Release Notes

Please refer to this FAQ section to update your solution to the latest version.

Rel-1.12 - October 15th, 2024

Functionality

  • Added Customer (Network) ID to manage multiple networks
  • Added dashboards on Packet Loss and SLA Management
  • Removed TraceRoute dashboard due to issues. To be added back in next release

Beta Features

  • QoS improvement suggestions using GenAI

Documentation

  • Adapted documentation

Rel-1.11 - June 11th, 2024

Functionality

  • New real-time RestFul APIs (and data extraction scripts) for integration with external systems
  • Introduction of LIFBE (Low Intrusive Fast Bandwidth Estimation) protocol for frequent throughput monitoring
  • Improved latency prediction feature using mix of ML-based technology
  • Improved calculation of packet loss rate

Beta Feature:

  • Second “Beta” iteration of our Diagnostics & Recommendations tool

Data

  • New LIFBE-based throughput metrics

Documentation

  • Added documentation on LatenceTech Insight APIs and scripts

Rel-1.10 — February 20th, 2023

Functionality

  • Traffic Shaper, a complementary tool to the QoSAgent to induce perturbations to the network interface to test various QoS levels & use cases
  • Twamp bug resolution of the frequency of measures too high
  • Issue and recommendation dashboard powered by LLM (Beta)

Scalability

  • Performed tests to confirm scalability of Analyzer to 10k+ QoS-Agents

Data

  • N/A

Security

  • Continued advanced integration of security processes to achieve SOC2 compliance (66% done)

Rel-1.9 — December 14th, 2023

Dashboards

  • Addition of an optional 95th percentile filter to enhance your latency tracking experience. This feature allows you to view the latency history with limited spikes, enabling you to focus on the overall latency trends.
  • Addition of a high-level indicator that allows the user to quickly assess the status of their connectivity health. 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.
  • Addition of metadata (name, network type, hardware, etc.) to the QoS-Agent to give more context in the dashboard (and allow advanced analysis)

Reliability

  • Performed accuracy proof of our measurements

Deployment

  • Added support for Kubernetes deployment and Openshift deployment

Data

  • Enhanced API and scripts for QoS data extraction with location coordinates

Security

  • Continued advanced integration of security processes to achieve SOC2 compliance (60% done)

Rel-1.8 — September 27th, 2023

Solution

  • Creation of an installation script for the Contextual Agent (enabling the collection of contextual data in addition to network quality and latency measurements, such as GPS data, equipment type, or data from an MQTT bus)
  • Support for Kubernetes deployment for the Analyzer using Helm templates

Dashboards

  • Addition of “jitter” as a new quality indicator
  • Enhanced volatility calculation
  • Added a predictive dashed line for latency over the next 90 seconds
  • Updates to latency indicators (Application and Network)

Documentation

  • Documentation for dashboards updated with more details on our indicators
  • Added documentation for using Helm templates for Kubernetes deployment
  • Documentation updated for installation on a Cradlepoint modem

Security

  • Initiation of advanced security process integration to achieve Soc2 compliance

Rel-1.7 — July 13th, 2023

Dashboards

  • New multisite dashboard allowing you to compare latency, bandwidth and network stability of 2 or more sites (agents) on the same dashboard
  • New network topology dashboard displaying the main key results of the monitoring topologically

Documentation

  • Added documentation to deploy an agent on a Cradlepoint E3000 modem
  • Added documentation to use a secure DNS instead of an IP address for your analyzer
  • Added new medium configuration for Analyzer
  • Added documentation to extract data from Kafka
  • Updated online documentation

Solution

  • Update of the Open Source components used in the Agent/Reflector/Analyzer

Data

  • Creation of a script to extract data from Kafka

Rel-1.6 — March 24th, 2023

Mobile App

  • Improved UI/UX on several real-time dashboards
  • Added UDP protocol for latency measurement
  • Added HTTPS protocol for latency measurement
  • Added IPERF3 protocol for bandwidth measurement
  • Possibility to select your own Analyzer instance (instead of the default one)
  • Added licensing support for Pro version
  • Trial mode limit up to 3 minutes for usage without a valid license
  • Added possibility to scan a QRcode for the reflector and the license key
  • Added initial splash screen
  • Removed embedded charts as too hard to read
  • Add field to enter specific notes to be added to the latency heatmap

Protocols

  • Added UDP protocol for latency measurement and to dashboards
  • Fixed bug with IPERF3 - sampling rate was wrongly interpreted
  • Fixed bug with IPERF3 - UDP result interpretation was incorrect

Dashboards

  • Added table of recent samples to detailed latency chart dashboard
  • Fixed network stability formula that was showing negative values

Documentation

  • Updated online documentation

Rel-1.5 — January 2nd, 2023

Protocols

  • Fixed bug that prevented iperf from testing bandwidth using UDP
  • Fixed stability issues
  • Changed ports to non-standard ones, thus avoiding potential collisions
  • TWAMP: restricted UDP ports to a range of 20 ports — configurable
  • Added possibility of turning of sampling by specifying -1 as sampling rate

Dockers

  • Switched to using environment variables instead of configuration files
  • Switched to docker-compose and yml files for launching dockers

Dashboards

  • Improved layout and performance
  • Added network stability calculation (based on variability, events and drops)
  • Added display of drops on main dashboard and charts

Analyzer

  • Refined installation script for better user experience and stability
  • Wrapped analyzer's dockers wrapping dockers, thus reducing the amount of volumes to be mounted
  • Refactored DB field names and architecture for better consistency