Note
StateRAMP compliance is not supported by this feature.
The Detection Log provides Safety Admins with complete visibility into all safety detections captured by Samsara cameras. Unlike the Safety Inbox, which only shows incidents that meet specific visibility thresholds, the Detection Log presents every detection in detail. This makes it a valuable tool for validating the full range of Samsara’s event detection capabilities, reducing the time teams spend investigating perceived gaps, and providing transparency.
The Detection Log is compatible with CM31, CM32, CM33, and CM34.
By using the Detection Log, you can access all detections regardless of their status in the Safety Inbox, apply filters and search tools for targeted analysis, and understand why certain detections did not appear in the Safety Inbox.
Note
Detections in the Detection Log may not include accompanying video. Events without video evidence should not be used for coaching, disciplinary action, or other HR-related purposes. Only events with verified video context should be used to support personnel decisions.
For each event in the Detection Log, you can see the following information:
|
Field |
Description |
|---|---|
|
Date |
The date and time when the detection occurred. |
|
Detection |
The type of safety detection captured (for example, Harsh Accel, Max Speed). |
|
Driver |
The driver associated with the detection. This may display as a dash (-) if no driver is assigned. |
|
Vehicle |
The vehicle associated with the detection. This provides context for where the detection occurred. For more details, you can click the link to view the vehicle overview. |
|
In-Cab Alert Played? |
Indicates whether an in-cab alert was triggered for the detection. Values include Yes or No. |
|
Inbox Event? |
Indicates whether the detection also appeared in the Safety Inbox. If the event was promoted to the inbox, you can click the link to review the event details. |
|
Promote? |
Provides an action to manually promote a detection into the Safety Inbox if it did not appear there automatically. When you click Promote to Inbox, a modal appears showing a still image captured around the time of the detection. You can confirm to promote the detection as an event. |
Not every detection or in-cab alert makes it into the Safety Inbox. Depending on system thresholds and your configured rules, detections may be filtered out to reduce noise and highlight only the most actionable events. As a result, drivers may occasionally hear an in-cab alert without a corresponding event appearing in the Inbox. The table below lists the most common reasons why detections can be excluded or alerts may not generate an Inbox event.
|
Reason |
Description |
|---|---|
|
Below G-Force Threshold |
Accelerometer event that did not cross the customer-configured sensitivity settings. |
|
Over Daily/Hourly Limit |
If numerous detections occur in a short timeframe, they may hit the hourly or daily maximums for Safety Inbox events. When these limits are exceeded, drivers still hear in-cab alerts, but no additional Inbox events are created. |
|
Below Confidence Threshold |
AI detection was below the configured confidence threshold, meaning the system considered it a low-confidence event and likely a false positive. |
|
Below Severity Threshold |
AI detection did not meet the customer-configured severity threshold. This applies to features like Inattentive Driving and Drowsiness. Drivers hear all in-cab alerts for inattentive driving, regardless of the severity setting. The severity setting only affects which events appear in the Inbox. For example, if you configure only high-severity events, drivers will still hear low, medium, and high-severity alerts—but only high-severity events are routed to the Inbox. |
|
Geofence Filter |
The detection occurred inside a geofence with a safety event exclusion rule. For legacy customers, drivers will hear in-cab alerts in geofence areas even when safety event exclusions apply. These exclusions only affect which events appear in the Inbox. (Legacy customers can opt out of in-cab alerts within geofence areas in their geofence configuration.) |
|
Below Nudge Threshold |
The frequency of detections did not exceed the customer-configured nudge threshold. When Nudges are enabled, drivers may hear two to four in-cab alerts before any detections are promoted to the Inbox. |
|
Below Speed Threshold |
The detection occurred at low speed (under 5 mph) or below the customer-configured speed threshold. Detections that occur at or above 5 mph are promoted to the Safety Inbox. Drivers may hear alerts at very low speeds (under 5 mph) for some event types, but only detections meeting the minimum speed threshold are promoted to the Inbox. |
|
Nighttime Filter |
The event occurred before sunrise or after sunset. This filter is used for Forward Collision Warning and Inward Obstruction detections. |
|
Off-Trip Detection |
The detection occurred off trip, such as when the vehicle was moving under 5 mph. |
|
Speeding Filter |
Only maximum speed and severe speeding detections are coachable Inbox events. Light, moderate, and heavy speeding are filtered out. |
-
Go to the Intelligent Safety Inbox and select the more actions ( ••• ) menu located in the upper right-hand corner. From the dropdown menu, choose Detection Log.
-
Review the comprehensive list of safety detections that includes:
-
Harsh events and collisions
-
Issues with following distance
-
Mobile device usage
-
Non-compliance with seatbelt use
-
Inattentive driving behaviors
-
Rolling stops
-
Lane departure alerts
-
Forward collision alerts
-
Driver drowsiness
-
Various intensities of speeding instances
-
-
Utilize filters to narrow down the detections by driver, vehicle, time frame, and particular types of detections, such as following distance or mobile phone usage.
-
For occurrences not displayed in the Safety Inbox, any explanation which clarifies which threshold or rule led to their exclusion.
Examples of detailing factors include sub-threshold g-force levels, daily or hourly limit breaches, AI detection confidence issues, and geofencing rules. For more information, see Reasons for Filtered Detections.
Comments
0 comments
Article is closed for comments.