Release Notes March 13, 2024 v8.2

Below are the notes for the release that went out on 3/13. 

• Improvements
  • Simplified version of the Synthetic Availability Graph on the Real Browser and API Checks Performance Details pages 
  • Original graph will remain in tab titled "Detailed View"
  • Adding a Minimum Sample filter on the Domain Trends page when looking at RUM data
    • Previously, RUM enforced a minimum sample of 10 in order to show any given resource.  Now we will let the user be able to change that lower limit to see low volume resources
  • Add Widget process revamped
    • Broken out by widget type, data type, and insight type to be easier to find what you are looking for
  • AB Segment Filter on the Data Science page will allow the option to do a manual test
  • Highlighting CWV on the RUM Performance Overview table to show red/yellow/green based on the recommended values provided by Google
• Bug Fixes
  • Fix for an issue on our synthetic filmstrips where single page filmstrips and the first step in a multi step measurement always had the first frame displayed twice
  • Fix for an issue on the Synthetic Site Health preconfigured dashboard where if you click on a page in a step in the session (right side) scatterplot, then looked at a filmstrip, then tried clicking another dot on the right side scatterplot, it would not load in a new filmstrip
  • Fix for an issue on the API Checks Performance Details page where the Detailed Site Availability graph was erroneously showing a line going above 100%
  • Fix for an issue on the Data Science page (and in the API) where doing a group by a custom category and looking at session level information would produce an error and cause the graphs to never return
  • Fix for an issue on the Performance Details dashboard widgets where selecting your metrics via the gear icon, then changing the filters would cause the lines to not stay sticky
• Upcoming Changes
  • In order to improve the performance and reliability of the API, measures have been made to control the rate of API requests that may be initiated to the Blue Triangle Public API. This change will affect less than 1% of connections and will results in a HTTP 429 message so that a backoff and retry method may be utilized.
  • In an effort to make SMS Alerts easier to consume we have aligned the amount of detailed information. The following information is included: site name, alert name, status, error code, as well as a link back to the Blue Triangle Customer Portal where detailed historical information is available.