Red Hat Bugzilla – Bug 1028624
Measurement data points can be supplied to condition processing in different order than generated on agent
Last modified: 2014-04-23 08:30:00 EDT
+++ This bug was initially created as a clone of Bug #1028623 +++
Description of problem:
When measurement data comes in to the server, the alert condition processing relies on the order to be strictly the same as generated on the agent side. I.e. no datapoint should be processed before another that was detected prior to it.
The persistence to the Cassandra storage node is asynchronous and done on datapoint-by-datapoint basis. This means that the datapoints can be persisted in different order than the original order.
When supplying the data to alert condition processing, we use the order of datapoints in which they were persisted, not the one they were created on the agent.
This can lead to subtle bugs in alerting like false positive or negative dampening events.
Version-Release number of selected component (if applicable):
hardly, can be best seen in debugger
Steps to Reproduce:
1. Have a server, agent and some enabled metric schedules for some inventoried resources
2. Once a measurement report comes in, check the order of elements in the input parameter of the MeasurementDataManagerBean#addNumericData() method.
3. Check the order of elements of the data passed to the condition processing in the onFinish() callback inside addNumericData()
The order sometimes differ, depending on the order cassandra cluster happened to store the events
The order of elements passed to the condition processing should be the same as the one coming from agents.
I have updated MeasurementDataManagerBean.addNumericData to ensure data is ordered by timestamp.
master commit hash: 1e3cf0f4ea0
Bulk closing of 4.10 issues.
If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.