Issue

The current Telemetry Report has two limitations that significantly reduce its usefulness in a large enterprise environment:

CSV export is limited to approximately 50,000 devices.

Administrators cannot sufficiently scope the report by location or similar organizational criteria before export.

For an organization with a device population larger than the export ceiling, this prevents administrators from retrieving the complete Telemetry dataset.

At the same time, the lack of granular filtering prevents administrators from isolating a smaller operational scope, such as a specific school, when troubleshooting deployments or agent-health issues.

Operational Impact

These limitations make it difficult to use Telemetry for proactive device and agent management.

Examples include:

validating an agent deployment at a specific school;

identifying devices at one location that did not receive an update;

comparing agent versions across locations;

isolating a suspected deployment issue;

reviewing agent health for a particular organizational group;

exporting the complete district fleet for reconciliation or analysis.

At WCPSS scale, the current 50,000-device limit means a full-fleet export is not possible.

If administrators also cannot narrow the report sufficiently before export, there is no practical way to retrieve either the entire environment or a targeted operational subset.

Requested Enhancement

WCPSS requests that Lightspeed address one or preferably both of the following areas.

Allow administrators to export the complete Telemetry result set.

Possible implementation methods could include:

removal of the 50,000-record ceiling;

significantly increasing the limit;

asynchronous report generation;

paginated export;

multiple-part CSV generation;

another supported method for retrieving the entire dataset.

The specific implementation is flexible as long as administrators can retrieve the complete report.

Allow Telemetry to be filtered before export using meaningful organizational and technical attributes.

At minimum, WCPSS requests filtering by:

school/location;

organizational group where applicable;

operating system;

agent version;

last check-in or reporting status.

Location filtering is particularly important because it allows administrators to isolate a school-specific deployment or health issue without processing the entire district dataset.

Preferred Behavior

Administrators should be able to perform workflows such as:

Location: School A

Operating System: Windows

Agent Version: Below current version

and export only those matching devices.

Alternatively, an administrator should be able to select:

All Devices

and retrieve the complete fleet without the report being truncated at 50,000 records.

Export Transparency

If an export is subject to any limit, the console should clearly indicate:

the total number of matching records;

the number of records included in the export;

whether the export has been truncated.

Administrators should never have to determine after the fact that a dataset was incomplete.

Requested Outcome

Make Telemetry reporting usable at enterprise scale by providing either:

complete fleet export capability;

sufficient granular filtering to retrieve targeted datasets;

or preferably both.

The preferred model is:

Filter to the operational scope needed → export the complete matching result set

while still retaining the ability to export the full fleet when required.

Acceptance Criteria

This request would be considered addressed when:

Administrators can export more than 50,000 Telemetry records or otherwise retrieve the complete matching dataset.

Telemetry can be filtered by school/location.

Additional useful filters such as operating system, agent version, and last check-in are available.

Applied filters are respected by the export.

The interface clearly identifies when an export is incomplete or limited.

Administrators can isolate a location-specific deployment or agent-health issue without manually processing the entire district dataset.

A complete district-wide dataset can be retrieved when required.

Business Value

This enhancement would:

make Telemetry usable at large-district scale;

improve deployment validation;

support proactive agent-health analysis;

reduce troubleshooting time;

allow school-specific investigations;

improve reconciliation with asset and endpoint-management data;

prevent administrators from relying on incomplete exports.

The core requirement is:

Telemetry should support both the size of the organization and the ability to narrow the data to the scope being investigated.