Module 1 — Lesson 1 of 8

Overview & Purpose

What is Tanium Performance, why Mercury Insurance invested in it, and how it transforms endpoint monitoring.
📚 Overview
🔧 Deep Dive
🛠 Hands-On
Check
💻
6
Metric Categories
<15s
Fleet-Wide Query Time
📈
DEX
Digital Employee Experience
🛡
0
New Agents Needed

Tanium Linear Chain Architecture

Tanium Server Central Console Zone Server Relay / Bridge Chain Leader Peer 1 Peer 2 Chain Leader Peer 3 Peer 4 Queries relay peer-to-peer, results aggregate back Each chain = hundreds of endpoints in production

Tanium Performance is a module within the Tanium Autonomous Endpoint Management (AEM) platform that extends real-time endpoint visibility into Digital Employee Experience (DEX) -- measuring the quality of the technology experience employees have every day.

It continuously collects telemetry (CPU, memory, disk, boot time, app stability, network latency) from every managed endpoint and aggregates it into actionable dashboards, health scores, and alerts. The goal: detect and resolve issues before the employee even notices them.

Mercury Insurance already had Tanium deployed for patching and software deployment. Adding Performance required zero new agents -- just enabling a module on the existing platform.

Traditional Monitoring vs. Tanium

CapabilityTraditional (SCCM/SCOM)Tanium Performance
Query SpeedMinutes to hoursSeconds ✓
ArchitectureHub-and-spoke pollingLinear chain P2P ✓
Data FreshnessStale (scheduled polls)Real-time ✓
ScalabilityDegrades with fleet sizeLinear scalability ✓
New Agent RequiredYes (per tool)No -- uses existing client ✓
DEX ScoringNot available ✗Built-in health scores ✓

Where Performance Fits in Tanium

Tanium is modular. You start with the Tanium Client + Server, then layer on operational modules:

Tanium Console -- Module Overview
Patch
Deploy
Asset
Comply
Threat Response
Performance
7.6
Fleet Health Score
4,218
Monitored Endpoints
142
Fair/Poor Devices
12
Active Alerts

Performance complements other modules. For example, identify 200 machines with degraded boot times in Performance, then use Tanium Patch to deploy the Windows update that fixes the issue -- all from the same console.

Digital Employee Experience (DEX)

DEX is a discipline within IT focused on measuring and improving the technology stack employees use daily. It answers questions like:

  • How long does it take for a laptop to boot to a usable desktop?
  • Are applications crashing frequently on certain machines?
  • Is a specific group experiencing high memory pressure?
  • After a Windows update, did login times improve or worsen?
Why DEX Matters

Poor digital experience directly impacts productivity, satisfaction, and retention. An employee spending 10 minutes waiting for their laptop every morning loses over 40 hours per year. Across Mercury Insurance, those numbers are significant.

DEX tools transform IT from a reactive model ("something broke, fix it") to a proactive one ("we see degradation forming, let's fix it before anyone notices").

Key Terminology

How Linear Chains Work

When the Tanium Client starts, it registers with the server and receives a list of peer endpoints. The server organizes endpoints into linear chains -- ordered sequences of machines that relay messages to each other.

Server Issues Query

The Tanium Server sends a sensor query to the first endpoint in each chain (chain leader).

Chain Relay

Each endpoint executes the sensor, stores its answer, and forwards the query to the next peer in the chain.

Results Aggregate

Results roll back up the chain. At each hop, data is aggregated and compressed.

Server Receives

Compact, aggregated results arrive at the server in seconds -- even across hundreds of thousands of endpoints.

Zone Servers

In environments spanning multiple subnets (like Mercury Insurance), Zone Servers bridge network boundaries, ensuring linear chains form even across firewalled segments or between office and VPN workers.

Why Mercury Insurance Invested

💡
1
Proactive IT Support
📊
2
Data-Driven Refresh
🎯
3
Measure DEX
🚀
4
Leverage Existing Infra
5
Reduce MTTR
  • Proactive IT Support: Detect degrading endpoints before employees notice, reducing ticket volume.
  • Data-Driven Hardware Refresh: Replace machines based on objective performance data, not just age.
  • Measure the Employee Experience: Quantify DEX across departments, locations, and device types.
  • Leverage Existing Infrastructure: No new agents -- just enable an additional module on the existing Tanium Server.
  • Reduce MTTR: Pinpoint root cause faster with diagnostic dashboards, cutting resolution time from hours to minutes.

🤔 What Would You Do?

A colleague from the Help Desk asks: "I heard we're installing some new monitoring agent on everyone's laptop. Is this going to slow down machines? What does it even do?"

How would you explain Tanium Performance to this colleague?

Exactly right. Tanium Performance is not a new agent -- it's a module on the existing Tanium client. It monitors health telemetry to enable proactive IT support. The CX uses less than 1% CPU and ~30 MB RAM.
Not quite. Tanium Performance is a module added to the existing Tanium client (no new agent). It monitors endpoint health metrics -- CPU, memory, disk, boot time, app crashes -- to help IT detect and fix problems proactively.

Simulated Console: Explore the Platform

Below is a simulated view of the Tanium Console. In the real environment, you would navigate to Modules > Performance to reach this view.

Tanium Console -- Modules
Patch
Deploy
Asset
Comply
Threat Response
Performance
Investigate

Tanium Modules at Mercury Insurance

ModulePurposeStatus
PatchOS and third-party software patchingActive
DeploySoftware deployment and package managementActive
AssetHardware and software inventoryActive
ComplyCompliance and vulnerability scanningActive
Threat ResponseEndpoint detection and response (EDR)Active
PerformanceEndpoint health monitoring & DEX scoringActive

Match the Component to Its Role

Drag each Tanium component on the left to its correct description on the right.

Tanium Server
Zone Server
Performance CX
Sensors
Lightweight component on endpoints collecting telemetry
Central management console issuing queries
Scripts that run on endpoints to return data
Bridges network boundaries for chain formation
All matches correct! You understand the core Tanium architecture components.
Some matches are incorrect. Review the architecture section in the Deep Dive tab and try again.

✍ Knowledge Check

1. What is the primary purpose of Tanium Performance?

Correct! Tanium Performance is focused on monitoring endpoint health metrics and providing Digital Employee Experience (DEX) visibility.
Not quite. While Tanium has modules for patching, security, and asset management, Performance is specifically about monitoring endpoint health and measuring the digital employee experience.

2. What is a CX (Client Extension) in the Tanium ecosystem?

Correct! A Client Extension (CX) is deployed to endpoints automatically and handles data collection for its specific module.
Not quite. A CX (Client Extension) is a lightweight component that runs alongside the Tanium Client on each endpoint, collecting telemetry data specific to the module it supports.

3. How does Tanium's linear chain architecture differ from traditional polling-based tools like SCCM?

Correct! The linear chain architecture enables peer-to-peer communication that delivers real-time results in seconds, regardless of fleet size.
Not quite. Tanium's key differentiator is its linear chain architecture where endpoints relay queries peer-to-peer, enabling answers in seconds across hundreds of thousands of machines.
Mercury Insurance — Digital Workplace Team
DEX Specialization Training © 2026