Endpoint experience

Know whether it's the Wi-Fi, the network or the app

Install the collector on the laptops and desktops people work from, and each one tests the apps they use, such as Microsoft 365, Zoom or Salesforce, and traces the network path to them. Every device gets an experience score and a likely bottleneck.

Start free Book a demo Read the docs

Apdex score per device
App templates
Wi-Fi details on Linux

Endpoint experienceMicrosoft 365, Zoom and Salesforce from 38 devicesLast 15 minutes

Endpoints38Endpoints impacted4Avg score87Poor Wi-Fi2

EndpointConnectionExperienceBottleneck

lt-ams-0412Linuxacme-corpch 36 · −58 dBm96Healthy

lt-ams-0388Linuxacme-corpch 6 · −76 dBm54Wi-Fi

mbp-lon-0127macOSNot reported10.31.4.2791Healthy

win-ams-0210WindowsNot reported10.20.64.1863Gateway

lt-nyc-0044Linuxacme-guestch 149 · −61 dBm72App

How it works

From one installer to a score for every device

The same collector that runs on your servers runs on the devices people use, and tests from where they sit.

01Deploy the collectorInstall it on Linux, macOS and Windows devices with the one-line installer, or push it with your device management.
02Pick applicationsStart from templates for Microsoft 365, Teams, Zoom, Salesforce and more, or add your own target.
03TestEvery device tests each app every 1 to 10 minutes and traces the TCP path to it.
04ScoreAn Apdex score from 0 to 100, with a 1 second target, sums up each device's experience.
05PinpointEach app's latest run names the likely bottleneck: Wi-Fi, gateway, network or the app.

Endpoints

One device, from its Wi-Fi to the app

Open an endpoint to see its score, availability and connection, the wireless link it is on and the result of every application test. The bottleneck comes from the latest run of each app, so it describes the problem as it is now.

On Linux, Wi-Fi details include the network name, channel, signal, signal-to-noise ratio and link rate
Each test traces the TCP path from the device to the app, hop by hop
Endpoints are named after their collector's host, never after a person

lt-ams-0388Linux · collector 2.0.50 · policy endpoints-emeaBottleneck: Wi-Fi

Experience54ConnectionWi-FiAvailability100%Signal−76 dBm

Wireless linkSSIDacme-corpChannel6 · 2.4 GHzSNR14 dBPHY rate58.5 Mb/s

Recent app testsTimeResult

Microsoft Teams1.84 sPassed

Microsoft 3652.31 sPassed

Salesforce0.92 sPassed

Bottlenecks

A likely cause, not just a low score

Tracix reads each app's latest run along the path from the device outward. Network faults outrank app faults, so weak Wi-Fi or a silent gateway is named before the app.

Wi-Fi
The collector reports a signal weaker than −70 dBm.
Gateway
An app did not answer, and the first hop sent no reply either.
Network
The first hop answered, but the app was unreachable or probes to it were lost.
App
The app answered its probes, but the test failed or took longer than 4 seconds.

lt-ams-0388Tracix Collector on the laptop

Wi-Fi · below −70 dBm, the Wi-Fi is the bottleneck

Gateway, the first hopNo reply from it: the gateway is the bottleneck

probes lost past the gateway: the network

ISP and WANEach hop with its round-trip time and loss

answers but slow or failing: the app

teams.microsoft.comHTTP test with a 1 second target

Applications

Templates for the apps your teams live in

Monitor application starts from templates for Microsoft Teams, Microsoft 365, Zoom, Salesforce, ServiceNow, Slack and Webex, or from a target of your own. Each one deploys an HTTP test with a TCP network path to every device in the policy.

Tests run every 1, 2, 5 or 10 minutes from each device
Every device reports its own results, so one office or one laptop stands out
A chart of each device's score over time shows when its experience changed

Monitor applicationStep 1 of 3 · Select an application

Microsoft Teamsteams.microsoft.comMicrosoft 365office.comZoomzoom.usSalesforcelogin.salesforce.comServiceNowservice-now.comSlackslack.comWebexwebex.comCustom applicationYour own target

HTTP server test · TCP network pathEvery 1, 2, 5 or 10 minutes

Better together

From one person's laptop to the network behind it

Endpoint tests share a workspace with your synthetic tests, network devices and collectors, so a bad score leads to the hop or device that caused it.

FAQ

Questions IT teams ask first

Talk to an engineer

Which devices can run endpoint tests?

Linux, macOS and Windows devices with the Tracix Collector installed. Wi-Fi details are read on Linux today; on other devices the connection shows as not reported.

Does the experience score include bandwidth or call quality?

No. The score comes from each app's response and availability, and the bottleneck from the network path and, on Linux, the Wi-Fi link. Separate iperf throughput and RTP call-quality probe packages report metrics only, with no dedicated view yet.

Does Tracix track the people using the devices?

No. An endpoint is identified by its collector's host name, platform and version, never by a person, and it only tests the applications you choose.

How is the experience score worked out?

It is an Apdex score over the device's application tests with a 1 second target. A passing test within 1 second counts in full, within 4 seconds it counts half, and slower or failed tests count zero. 85 or more is healthy.

Start with one laptop

Install the collector on a device, pick an application template, and the first scores arrive after one test interval.

Start free Read the docs