Issue Details (XML | Word | Printable)

Key: RIO-172
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dennis Reedy
Reporter: Dennis Reedy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Rio

Threshold Management notification

Created: 24/Mar/09 03:48 PM   Updated: 15/Apr/09 01:58 PM
Return to search
Component/s: Watches
Affects Version/s: 4.0 M2
Fix Version/s: 4.0 M3

Time Tracking:
Original Estimate: 4 days
Original Estimate - 4 days
Remaining Estimate: 4 days
Remaining Estimate - 4 days
Time Spent: Not Specified
Remaining Estimate - 4 days


 Description  « Hide
Threshold Management alert notification is based on the approach that the re-notification of threshold breaches only occurs if the threshold is first breached, then cleared. Subsequent breaches are then sent to interested local and remote listeners.

This causes problems if a threshold watch records values that constantly breach. For example, if a threshold is set to have a low threshold of 45, and a high threshold of 55, an initial recording of 60 will result in a threshold breach notification. If the next value collected is 65, a threshold breach notification will not be sent.

The approach should allow a breach notification to be produced for each measurement collected that is beyond the configured threshold values.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.