Feature Request: Agent Version Compliance and Deployment Health Dashboard
T
Timothy Cogar
Issue
Telemetry provides valuable endpoint information, but administrators still need to transform that information into an operational understanding of deployment health.
WCPSS already has separate needs around identifying agents that stop reporting and around filtering/exporting Telemetry at organizational scale.
A dedicated Agent Version Compliance dashboard would provide an immediate answer to a different operational question:
How healthy is the current Lightspeed agent deployment across the organization?
Requested Enhancement
Add a dashboard that summarizes agent deployment and version compliance across managed endpoints.
The dashboard should provide an immediate overview of:
current agent version;
previous version;
outdated versions;
unsupported versions;
stale agents;
devices that have never successfully reported;
recent check-in status;
version distribution by platform.
Example Dashboard
Windows Agent Compliance
Current Version: 3.4.3
Current: 91.4%
Previous Version: 6.8%
Older Versions: 1.1%
Stale / No Recent Check-In: 0.7%
ChromeOS
Current: 96.2%
Previous: 2.7%
Stale: 1.1%
These values should be selectable so administrators can drill into the underlying devices.
Organizational Filtering
The dashboard should allow administrators to scope results by:
school/location;
operating system;
organizational group;
agent version;
reporting state;
last check-in range.
This is especially important for determining whether a deployment problem is:
district-wide;
platform-specific;
school-specific;
isolated to a deployment group.
Deployment Validation
The dashboard should help administrators quickly identify conditions such as:
rollout stalled at one school;
significant population remains one version behind;
devices stopped checking in after an update;
one platform has a materially lower adoption rate;
an expected deployment has not reached its intended population.
Drill-Down
Selecting any dashboard metric should open the underlying device population.
Example:
327 Devices — Version 3.4.2
Selecting that result should provide the corresponding Telemetry records rather than requiring the administrator to reconstruct the query manually.
Compliance Thresholds
District administrators should be able to establish operational thresholds.
Example:
Compliant: Current version
Warning: One version behind
Noncompliant: More than one version behind
Stale: No report in 7 days
Lightspeed could then provide an overall deployment-health status.
Requested Outcome
Transform existing Telemetry information into an actionable agent-deployment health view.
The desired model is:
Telemetry tells us about individual devices.
Agent Compliance tells us whether the deployment is healthy.
Acceptance Criteria
Current agent-version distribution is visible.
Results can be separated by operating system.
Stale/non-reporting agents are identifiable.
Administrators can filter by location or organizational scope.
Dashboard metrics support drill-down to affected devices.
Version-compliance thresholds can be configured where practical.
Results can be exported or used in scheduled reporting.
Business Value
This enhancement would:
improve proactive agent management;
make deployments easier to validate;
identify rollout failures earlier;
reduce reactive support;
improve upgrade planning;
provide enterprise-scale fleet visibility.
Autopilot
Merged in a post:
Agent Version Compliance and Deployment Health Dashboard
T
Timothy Cogar
Issue
Telemetry provides valuable endpoint information, but administrators still need to manually interpret that data to determine whether the overall Lightspeed agent deployment is healthy.
For large organizations, the critical question is not only:
What version is this device running?
It is also:
How healthy is the deployment across the organization?
Requested Enhancement
Add an Agent Version Compliance and Deployment Health Dashboard that converts Telemetry information into an operational fleet-health view.
The dashboard should summarize:
current agent version;
previous version;
outdated versions;
unsupported versions;
stale agents;
devices that have never successfully reported;
last check-in health;
distribution by operating system.
Example
Windows Agent Compliance
Current Version: 3.4.3
Current: 91.4%
Previous: 6.8%
Older: 1.1%
Stale / No Recent Check-In: 0.7%
ChromeOS Agent Compliance
Current: 96.2%
Previous: 2.7%
Stale: 1.1%
These metrics should be interactive.
Selecting 327 devices on previous version should open the corresponding device population.
Filtering
Administrators should be able to scope the dashboard by:
school/location;
operating system;
organizational group;
agent version;
reporting status;
last check-in range.
This would allow administrators to quickly determine whether a deployment problem is:
district-wide;
location-specific;
platform-specific;
version-specific;
isolated to a particular rollout group.
Deployment Validation
The dashboard should surface conditions such as:
one school significantly behind the rest of the district;
a deployment stalled at a location;
a population remaining on an older version;
agents that stopped reporting after an upgrade;
unexpected platform differences;
devices that never successfully received the agent.
Compliance Thresholds
Administrators should be able to define operational thresholds.
Example:
Compliant: Current version
Warning: One version behind
Noncompliant: More than one version behind
Stale: No successful report in 7 days
Lightspeed could then show an overall deployment-health indicator.
Drill-Down
Dashboard metrics should link directly to the underlying device records.
Administrators should not need to reconstruct the filter manually after seeing an abnormal metric.
Example:
School A — 74% Current
Select the metric → view the devices responsible for the remaining 26%.
Requested Outcome
Transform existing endpoint Telemetry into actionable deployment-health information.
The desired distinction is:
Telemetry tells us about individual devices.
Agent Compliance tells us whether the deployment is healthy.
Acceptance Criteria
Agent-version distribution is summarized.
Results can be separated by operating system.
Stale and non-reporting agents are identified.
Results can be filtered by location and organizational scope.
Dashboard metrics drill into affected devices.
Operational compliance thresholds can be configured where practical.
Results can be exported or incorporated into scheduled reporting.
Business Value
This would:
improve proactive agent management;
simplify deployment validation;
identify rollout failures earlier;
reduce reactive troubleshooting;
improve upgrade planning;
provide enterprise-scale fleet visibility.