Documentation
Homepage
Search…
Getting started
Map
Assets
Condition reports
Issues triggers & alerts
Graphs
Manual measurements
Analytics
Data export
Connectivity environment
Environment settings
Language
Form fields
Condition report types
Users
Quantities and thresholds
Connectivity issue triggers
Audit Log
Integrations
Managed Solutions by Withthegrid
API documentation
Contact us
Powered By GitBook
Connectivity issue triggers
Connectivity issue triggers are all about staying on top of your devices, by making sure that they function as expected. A connectivity issue trigger could be triggered if a device does not report as expected. The unexpected behavior can be caused due to various reasons such as low signal strength, a faulty device, or simply a dead battery.
With connectivity issue triggers you can make sure that when a device does not respond, you will be notified on time. We have 2 types of connectivity issue triggers: Serious and Critical.
A serious issue can help notify you ahead of time that a device does not behave as it should, but is still operational. It meant to give you a warning. A critical issue has an even higher layer of importance.
Based on your application, you can freely configure for both, serious and critical issue triggers
  • Number of missed reports
  • Offline for
For example, a user can select 10 as the number of missed reports and offline for 30 minutes.
This means, that a serious or critical issue will be generated when the device has missed 10 measurement reports and the device has not been online for more than 30 minutes.
Previous
Quantities and thresholds
Next
Audit Log
Last modified 3mo ago
Copy link