Currently, PRTG does not provide a way to determine how long a sensor has been in a warning state. This makes it difficult to distinguish between sensors that just entered a warning state and those that have been generating warnings for extended periods (hours, days, or weeks).

Feature Request:
Please add warning state duration information to PRTG with the following components:

API Access (Most Important):
- Add a "warningduration" or "timeincurrentstate" field to the sensor API endpoints
- Enable filtering/querying sensors by warning duration via API parameters
- This would allow for automated reporting and custom monitoring solutions

User Interface:
- Display warning duration as an additional detail line in sensor status data in the sensor overview (right list)
- Add a "Warning Duration" or "Time in Warning State" column option
- Enable filtering sensors by warning duration (e.g., "in warning for >24 hours", ">7 days", etc.)
- Allow sorting sensors by how long they have been in their current warning state

Use Case & Benefits:
This feature would help identify "noisy" sensors that consistently remain in warning states without escalating to error or returning to normal. These sensors often indicate:
- Thresholds that need adjustment
- Non-critical issues that should be addressed but get overlooked
- Devices that require maintenance or replacement
- Sensors that may need to be reconfigured or paused

By easily identifying long-standing warnings (especially via API for automated workflows), administrators can prioritize cleanup efforts, reduce alert fatigue, and maintain a cleaner, more actionable monitoring environment.