Note
To manage workflows you must have a Full Admin role or custom role with the following Alerts permissions as needed:
-
View and download alerts
-
Create, edit, and remove alerts
You can configure DVIR Defect Alerts to be automatically notified of any defects or potentially unsafe DVIRs in your fleet. With DVIR Defect Alerts, you can assess any vehicle downtime (from unsafe vehicles) and plan maintenance activities.
You can use one or more of the following options to receive DVIR notifications:
-
Set Up DVIR Defect Alerts with Samsara: You can configure defect alerts directly in the Samsara dashboard. The defect alerts will display along side any existing Samsara alerts in the Alerts Incidents report.
-
Set Up DVIR Defect Alerts with Webhooks: You can create Webhooks to enable Samsara to send an Hypertext Transfer Protocol (HTTP) request to your application program when an event is triggered (such as geofence or speeding alerts).
After Alert Configuration through the Samsara dashboard, the alert is triggered any time a new individual defect is detected on a newly submitted safe or unsafe DVIR. For example, if a DVIR has five defects reported on it, five alerts and five incidents will be triggered, one millisecond apart. Alerts are not created for pre-existing defects.
To receive a notification for submitted DVIRs:
-
Select the Alerts icon (
) to view Alert Incidents.
-
Select + Create Alert.
-
Within the Maintenance category, select DVIR Submitted.
-
Enter a descriptive alert name.
-
Within the Triggers settings, select one or more of the following Conditions:
-
Safe DVIR (No Defects): Alerts when a driver submits a DVIR that is marked as safe (does not include defects).
-
Safe DVIR (With Defects): Alerts when a driver submits a DVIR that is marked as safe (includes defects).
-
Unsafe DVIR: Alerts when a driver submits a DVIR that is marked as unsafe.
-
-
(Optional) Choose a DVIR Duration.
This will trigger an alert if the selected DVIR types are submitted in an amount of time shorter than the selected threshold.
-
Choose one or more assets or tags the trigger will Apply To.
-
(Optional) Choose to include the following conditions to the alert:
-
+ Add Geofence: Receive alerts relative to a geofence (Inside Geofence, Outside Geofence).
-
+Add Engine On/Off: Receive alerts based on engine state (Asset Engine On, Asset Engine Off).
-
Time Range: Select the Time Range condition for the alert (Active between, Inactive between).
Incidents will only be logged during the time range selected.
-
-
In the Actions category, add Recipients to receive notifications of alerts.
You can add Recipients using the following options:
-
Search bar: Search for users or contacts to receive notifications.
-
+ New Contact: Create a new contact (inside or outside your organization) that can receive notifications of alerts.
Scheduled repots will be sent to the email address of the contact, whereas alerts can be sent by text or email.
-
Manage Contacts: Manage and view your existing Alert Contacts.
-
-
(Optional) Select + Add Action to add the following notification options:
-
Send Slack Notification: Choose an existing Slack integration to which you want to send notifications or Manage to set up or modify a Slack integration.
-
Send Webhook: Choose an existing Webhook configuration to which you want to send notifications or Manage to set up or modify a Webhook integration.
-
-
Select Save.
A webhook is a method of one-way data delivery that connects two application programs to provide real-time communication. When an event is triggered, such as a geofence alert, webhooks enable Samsara to send a HTTP request to your application program. You can use webhooks to request DVIR details such as DVIR defects. Webhooks are configurable for all currently available DVIR alerts. To learn more about the use-case, prerequisites, and workflow, visit the webhook documentation.
The webhook payload includes the following DVIR details:
|
Payload Item |
Description |
|---|---|
|
Vehicle |
Samsara vehicle Id and vehicle name. |
|
Trailer |
Samsara trailer Id and trailer name. |
|
Driver |
Samsara driver Id and driver name. |
|
DVIR Id |
The Samsara DVIR Id that can be used for Samsara API endpoints. |
|
Odometer |
This is the numerical value from the DVIR, not the vehicle cable. The odometer value in the webhook payload is always in meters. |
|
Inspection type (pre-trip or post-trip DVIR, or unset) |
String enum matching the return value from Samsara API endpoints. |
|
Photos |
DVIR photos delivered as pre-signed S3 URLs that is valid for 24 hours. |
|
Safety status Upon reporting (safe or unsafe) |
String enum matching the return value from Samsara API endpoints. |
|
Defects |
A list of defects created, each with:
|
