Purpose
This document explains how to configure the Heartbeat (HB) Type and Interval to monitor device connectivity status with the Cloud platform.
Heartbeat configuration helps control how frequently the device reports its online/offline status and statistics to the Cloud.
What is Heartbeat?
Heartbeat (HB) is the periodic signal sent by the device to the Cloud to confirm that it is reachable and operational.
Based on the configured HB Type and Interval:
Device status updates are sent
Client and device statistics may be reported
Offline detection speed varies
Monitoring traffic load changes
Navigation Path
Go to:
Monitor → Devices → Select Device → Configure → Wired Uplink
Scroll to Advanced Monitoring
Step 1: Enable Advanced Monitoring
Enable:
✔ Advanced Monitoring
You will see:
HB Type
HB Interval (Seconds)
Heartbeat Type Options Explained
1. Regular
Behaviour
All monitoring data is sent in real-time
Includes:
Device status
Client details
Throughput statistics
Use Case
Default recommended setting
Stable networks
When full monitoring visibility is required
2. Optimized
Behaviour
Heartbeat is sent via UDP
Monitoring data is reduced
Focus is on essential connectivity updates
Use Case
Medium traffic deployments
When monitoring overhead needs to be reduced
3. Optimized-Highly
Behaviour
UDP heartbeat without detailed statistics
Only critical connectivity signalling
Use Case
Large scale deployments
Bandwidth-sensitive environments
When only uptime monitoring is required
4. Fast-Regular
Behaviour
Faster heartbeat interval support (e.g. 5 sec)
Can operate in two levels:
5 Seconds Mode
Only device UP/DOWN status check
Minimal monitoring traffic
1 Minute Mode
Full heartbeat with device, client and throughput stats
Use Case
When quick offline detection is important
Example: Retail, Hospitality, Critical WAN links
5. Fast-Optimized-Regular
Behaviour
Supports multiple heartbeat granularities:
5 Seconds
Only UP/DOWN status monitoring
10 Seconds
Reports client connectivity info
(IP address, MAC address)Does not send usage statistics
1 Minute
Full heartbeat with all monitoring stats
Use Case
Advanced deployments requiring balance between fast failure detection and reduced cloud load
HB Interval (Seconds)
Defines how frequently heartbeat messages are sent.
Example:
5 seconds → Very fast offline detection
60 seconds → Reduced monitoring traffic
Important
Lower interval → Faster device status updates
Higher interval → Less bandwidth consumption
After Saving Configuration
Click Save
Wait for:
Configuration Applied event
First successful heartbeat event
Verification
You can verify heartbeat status from:
Events Tab → Heartbeat Success / Failure
Device Status Indicator / Last seen