Other service references — reference notes

Review Fastvue's recorded purpose and storage-sizing notes, plus the Edge user-agent extension's context, deployment and operation notes. These are separate service references.

What is Fastvue?

Fastvue (https://www.fastvue.co/) is an internet filter/firewall reporting tool. It ingests, cleans, categorises, displays and reports on user and network activity; alerts on safeguarding concerns; and allows proactive and reactive approaches to managing student internet use.

Storage

For several reasons, having the data for Fastvue on a separate data disk is desirable. When determining the initial size of the disk, Fastvue recommend starting with a rough estimate of 15Mb per user per day.

In Fastvue Settings -> Data Storage -> Settings area you can specify your desired days to retain and a maximum size of data and it will tell you, based on your current ingest rate, whether you'll likely hit the size limit or date limit first. You will need some properly indicative days for this to be meaningful, however.

Context

A small number of sites used by CCM staff for official purposes - teacher registration, training etc. - specify Chrome as required, yet without technical justification.

Those same sites work normally if the user-agent reported by the browser identifies itself as Chrome, not Edge.

To support CCM's push towards a single supported browser across all devices and functions, a simple extension has been developed to automatically change the user-agent on specified sites. Those sites are centrally managed, not user configurable.

Deployment

The extension must be hosted in the Edge extension store for cloud deployment. The extension has been submitted for review at the moment.

The extension will be pushed through the Edge Management Service.

Domains and URLs

These are stored in a json array, saved as domains.json in the ccmschools Azure blob storage CCMpublicfiles

Operation

The extension reads the list of domains and URLs at browser launch, on-demand through user-action, and automatically every 3 hours.

If a destination matches an entry in the source data, the User Agent has the Edg/<ver> token removed to restore the UA to a Google Chrome ID. This dynamic approach ensures the UA never becomes stale.

The UA is modified in two locations:

  • The main DNR record
  • The Javascript main context