--- title: "Analyze trace time and detection time of an activity" slug: "analyze-trace-time-and-detection-time-of-an-activity" tags: ["EDR with Forensics (EDRF)", "Endpoint Security"] updated: 2026-08-26T19:31:16Z published: 2026-08-26T19:31:16Z canonical: "docs.trellix.com/analyze-trace-time-and-detection-time-of-an-activity" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Analyze trace time and detection time of an activity You can analyze the difference between trace time and detection time of an activity due to lag in the network. Trace time is the time at which an event is traced on the endpoint. Detection time is the time at which EDRF records the traced event. > [!NOTE] > Note > > Always consider **Detection Time** for searching the historical data of endpoints. Here is an example showing difference in **Trace Time** and **Detection Time** considering different scenarios. | Time and Activity | Scenario 1 (Out of sync with the current time) | Scenario 2 (In sync with the current time) | | --- | --- | --- | | Current standard time | 12 a.m. | 12 a.m. | | Time shown on the endpoint | 1 a.m. | 12 a.m. | | Trace time detected on the endpoint | 1 a.m. | 12 a.m. | | Trace time recorded on EDRF | 12.01 a.m. | 12.01 a.m. | | The result shown on the **Historical Search** dashboard | **Trace Time** — 1 a.m. **Detection Time** — 12.01 a.m. | **Trace Time** — 12 a.m. **Detection Time** — 12.01 a.m. |