About timestamp and duration in Dynamics 365 Business Central telemetry

Dynamics 365 ERP - Development

A time interval in telemetry is defined by a start and end datetime, with the timespan being the calculated duration between these two points.
In Dynamics 365 Business Central, telemetry signals lack standardization in names for custom dimensions, leading to difficulties in determining start and end times for events.
To accurately analyze specific time frames, it is necessary to calculate time intervals and determine overlaps with investigation time frames.
For example, when analyzing report execution signals, the start and end times must be considered to accurately capture relevant data.
Enlarging investigation time frames may result in an influx of noise signals, making it crucial to keep the window short and focus on inbound and outbound timestamps.
Creating a customized dashboard in Azure Data Explorer can help separate and analyze relevant signals like Long Running AL Methods, SQL Queries, Reports, Job Queue, and Incoming Web Services.
Calculating corrected start and end times based on execution time can ensure accurate filtering of relevant signals within the investigation time frame.
Including running duration in the analysis can provide insights into how long each signal was running until hitting the upper bound of the investigation time window.

Registered users can view the full text for FREE!