This is an optional feature designed to cope with overloading gateways, the gateway would deal with the backlog of data queues by discarding out of date cell updates and only processing and publishing the latest cell values. This is a viable alternative to the suspension which essentially loses your monitoring for a period of seconds or a netprobe disconnect which again loses your monitoring.
How conflation works where you have rapid cell updates like below - before the gateway has processed the first update...
The gateway will only publish the latest value. Update cell from 1 to 5
Configuration of Conflation
Operating Environment > Data Quality > conflation
Settings to control conflation of incoming monitoring data.
Operating Environment > Data Quality > conflation > enabled
Whether or not conflation is enabled. Conflation can significantly aid an overloaded gateway and ensure that that all published data is as up-to-date as possible, but it does so by discarding out-of-date cell updates and should not be enabled is this is unacceptable.
For more details on how this setting is used, see the conflation description.
Operating Environment > Data Quality > conflation > strategy
Specify the strategy for controlling gateway conflation, so that conflation is only enabled when required and no updates are unnecessarily discarded.
Operating Environment > Data Quality > conflation > strategy > maxDataAgeThreshold
Under this strategy the gateway does not enable conflation unless the maximum age of backlogged updates (as displayed by the probeData plugin) exceeds a certain threshold.
Conflation works best when it is preventing stale data from building up rather than clearing large backlogs (not only does it have fewer backlogged messages to process, but it minimises the amount of updates conflated away) and the threshold should not be set too high. An ideal value for the threshold is the minimum sample Interval used in the setup. For this reason it defaults to the default sampleInterval of twenty seconds.
Operating Environment > Data Quality > conflation > strategy > maxDataAgeThreshold > threshold
The threshold maxDataAge above which conflation is enabled, in milliseconds. An ideal value for this setting is the minimum sample Interval used in the setup.
Operating Environment > Data Quality > conflation > strategy > alwaysOn
Under this strategy the gateway permanently enables conflation. This strategy will always result in the most up-to-date data being published, but may cause updates to be discarded when it is not strictly necessary to do so and the gateway could have published them all in a timely manner.