Re: Subscription / first update

[Michael Davidsaver <mdavidsaver@gmail.com>]

On 01/14/2016 12:50 PM, Andrew Johnson wrote:
> My discomfort with per-client deadbands like this is that each client
> needs to know how big its deadband should be, and gets no hint at all
> from the record. With the existing IOC deadbands, the database designer
> can set 2 different deadband sizes for regular and archive monitors.

I'll second this.  For the archiver appliance, I ask for, and Murali
provided, a means of deadband filtering on the archiver (client) side. 
However, this is such a pain to configure that it wasn't get used much*.

* I still have hopes as this does allow for interesting policies like
retroactively applying a deadband to old data.  For example, keep full
data for 2 weeks, then decimate w/ deadband.