Important
Please note that the following sensors will be retired on the 26th of November 2025:
Sensor Name | Equivalent Sensor |
|---|---|
Application Not Responding | Application Fault Application Hang |
Available Bandwidth | Available Bandwidth Below Limit Available Bandwidth Below Average |
Available Memory | Low Available Memory Extended Low Available Memory |
Blast High Average Latency | Blast High Latency |
Blast High Uplink Jitter B | Blast High Uplink Jitter A |
Condense Timeout | Condense Timeout no longer applies now that the agent uses Web Sockets |
CPU High Limit | CPU Throttling Extended High CPU Use High CPU Use |
CPU Load | Extended High CPU Use High CPU Use |
CPU Low Limit | High CPU Ready Time and Low CPU Usage |
High Base RDP TCP Latency | High RDP TCP Latency Increased RDP TCP Latency |
High Base RDP UDP Latency | High RDP UDP Latency Increased RDP UDP Latency |
High Byte Rate | Bytes Sent Bytes Received |
High Connection Count | Network Connection Saturation |
High Network Utilization | Network Connection Saturation Network Issues Application High Network Utilization |
High RDP TCP Latency Alarm | High RDP TCP Latency |
High RDP UDP Latency Alarm | High RDP UDP Latency |
High Retransmission Rate | High Network Usage and Retransmission Rate |
Sensor Update
Mid October 2025
Sensor Name | Category | Details of Update |
|---|---|---|
Critical Business App Hang non-Windows | Applications | New sensor. |
High Kernel Mode CPU Use | CPU | Removed dependency on Major CPU Issues and Real Time CPU Impact sensors. |
Files per sec Get Requests per sec | Network | Removed all references to alarms. The change is a part of the move from using alarms as sensors to using underlying data. |
Long Webpage Load Time 400 - Bad Request 401- Unauthorized 403 - Forbidden 404 - Not Found 407 - Proxy Auth Required 408 - Request Timeout 500 - Internal Server Error 502 - Bad Gateway 503 - Service Unavailable 504 - Gateway Timeout | Web | Web Error Code Sensors now support instancing. |
SCCM Agent Not Running | System | Added the variable Service_Check_Delay. Updated the sensor to check the LAST_CHG time for a stopped sensor is CURRENT_TIME - Service_Check_Delay. Service name added to the payload so it can be passed to an automation as a parameter. |
Default Gateway Latency - Corp Default Gateway Latency - Remote | End-User Experience | Sensor Category changed to Network. |
Low Wifi Affecting Bandwidth Low Wifi Signal Strength Low Wifi Signal Strength Android | Network | Updated sensor names from "Wifi" to "WiFi." |
Early October 2025
Sensor Name | Category | Details of Update |
|---|---|---|
CGI Requests per sec Cur Blocked Async IO Request Current Blocked Bandwidth Bytes Current CGI Requests Current Connections Current ISAPI Extension Requests Files Received per sec Files Sent per sec Head Requests per sec | Network | Removed all references to alarms. The change is a part of the move from using alarms as sensors to using underlying data. |
Context Switch Rate File Control Rate File Data Rate | System | Removed all references to alarms. The change is a part of the move from using alarms as sensors to using underlying data. |
High Disk Activity - High Disk Activity HDD | Disk | A number of changes has been made to this sensor:
|
High Disk Activity SSD | Disk | New sensor. |
Default Gateway Latency - Corp Default Gateway Latency - Remote | Network | The sensors now support a time variable that limits the scope of latency records being checked. This allows for more targeted performance analysis by narrowing the time window for evaluation. |
WiFi Channel Conflict | Network | New sensor. |