Alerts and incidents
Create alert rules, assign optional recipients, and acknowledge incidents on a separate Incidents page.
What is an alert?
An alert is how Trakngo tells you that something worth attention happened in your fleet—speeding, a zone crossing, movement outside hours, low tracker battery, or ignition left on while stationary.
- Alert rule
- The configuration you create: what to watch, the threshold, when it may trigger, which vehicles and assets it covers, and optionally who receives the incident.
- Incident
- A recorded occurrence from a matching rule or a geofence crossing. Incidents are what your team reviews, is emailed about when recipients are set, and acknowledges.
Rules and incidents
Monitoring → Alerts is where you configure rules. Monitoring → Incidents is the queue your team reviews. A rule defines what to watch, when it can trigger, and which vehicles or assets it covers. An incident is a recorded match or geofence crossing that can be acknowledged.
Alert rules
Create, edit, enable, or disable the conditions monitored across your fleet, and optionally assign recipients.
Incidents
Filter current events by severity, type, or acknowledgement status and record that they were reviewed.
Create an alert rule
- 1
Start a new rule
Open Monitoring → Alerts, then select New alert rule.
- 2
Choose the condition
Enter a clear name, choose the Alert type, and provide the threshold required by that type.
- 3
Set the Trigger schedule
Allow the rule to trigger at any time, or choose the days and time windows when matching events should count.
- 4
Choose the scope and recipients
Turn on Entire organisation to cover every current and future vehicle and asset, or leave it off and select specific vehicles and assets. A rule that is not organisation-wide and has no members will not fire. Optionally pick Recipients who should be emailed and who should see the incident. Leave recipients empty so anyone with Alerts permission can see it; no email is sent.
- 5
Save and confirm it is enabled
Return to Alerts to verify the rule shows the expected type, schedule, scope, and Enabled status.
Available alert types
Geofence crossings are not configured as an alert type. They are raised by the geofence itself and appear on Incidents as type Geofence. The meaning and units of a rule threshold depend on the alert type and tracker configuration.
Choose the right schedule
The schedule controls when matching events are accepted. Outside those windows, matching events are ignored. Use Always active for safety or equipment conditions that need continuous coverage.
Review and acknowledge incidents
1. Open Incidents
Use Monitoring → Incidents and the summary cards to scan active, critical or high, and recent events. If recipients were assigned, only those people see that incident.
2. Narrow the queue
Filter by search text, severity, alert type, or acknowledgement status.
3. Select Acknowledge
Acknowledge an incident after it has been reviewed or actioned. This records its status; it does not change or disable the underlying rule or geofence.
Permissions
Viewing incidents, acknowledging them, and managing alert rules are separate permissions. If you can see Incidents but cannot acknowledge them or open Alerts, ask an organisation admin to review your role.
Related guide
OperationsGeofences →
Draw zones and choose who is notified when a vehicle or asset crosses them.
Getting startedLive map and tracking →
Locate the vehicle or asset connected to an incident and inspect its recent movement.