Telemetry
How is warehousing telemetry different from ordinary inventory transaction data?
Inventory transactions record business events like receipt, issue, or transfer, while telemetry records system and process behavior such as user-session events, warehouse-event execution, and application health signals used for diagnostics.
Where is D365 warehousing telemetry stored for analysis?
It is collected through Application Insights and viewed in Azure Monitor Logs, including the customEvents table queried with KQL.
What does telemetry enable in supply chain control towers?
It enables real-time operational visibility, allowing teams to detect deviations in asset movement, environmental conditions, and process timing before they become service failures.
Telemetry in supply chain inventory and material tracking is the automated remote collection and transmission of operational data from assets, devices, or software systems for centralized monitoring and analysis. In Microsoft Dynamics 365 Supply Chain Management, warehousing telemetry includes diagnostic events and user-session data sent to Application Insights/Azure Monitor to observe warehouse processes and system health.
On a real shop floor, telemetry turns connected equipment and digital workflows into a continuous stream of status signals. Managers monitor device activity, process timing, work execution, exceptions, and environmental conditions from a central console. In Dynamics 365 Supply Chain Management, enabling telemetry means turning on User sessions and Warehouse events under Monitoring and telemetry parameters; data is then mapped to Application Insights and queried in Azure Monitor Logs. This view helps diagnose wave processing delays, stuck work creation, mobile warehouse app behavior, and tenant health before they become labor or fulfillment bottlenecks. For raw material tracking, telemetry adds visibility into location, movement, dwell time, and handling state, supporting exception detection, compliance monitoring, and faster corrective action across receiving, put-away, replenishment, and dispatch. The practical payoff is that teams react to evidence from the actual execution environment rather than guesswork.
False visibility from incomplete data capture: If only some telemetry types are enabled, teams assume full observability while critical events remain missing, allowing scan failures, missing task completions, and processing latency to go undetected.
Alert fatigue and noisy diagnostics: Unfiltered telemetry streams flood operators with high-volume custom events, hiding real problems like slow wave release, stalled mobile sessions, or repeated device retries.
Connectivity gaps at the edge: Intermittent Wi-Fi, cellular, or gateway issues create blind spots where sensors keep measuring but systems receive delayed or partial data, leading to inaccurate inventory-state decisions.