Configure minimum lag at 1 (and not 0) ?

Nobody has claimed this yet.

I try to use Burrow to monitor a bunch of services build with robinhood [*faust* python library](https://faust.readthedocs.io/).

The point is that *faust* has a different understanding of kafka consumer's offset. For *faust* offset is the last event offset, not the "next expected event" offset. see https://github.com/robinhood/faust/issues/73

So a *faust* based services always have a minimal lag of 1 (and not 0). And so burrow set an error status when there is no commit for some times...

In my point of view the issue comes from *faust* interpretation of these offset.
so => https://github.com/robinhood/faust/issues/73

But, anyway, I post this for two reasons :
- for documentation (I couldn't found any reference of this issue on burrow github)
- I wounder if there is a -not-so-dirty- way to configure burrow to handle this minimal lag at 1 ?

btw, thanks for you work on burrow !

Start by reading Burrow's configuration and consumer-lag status handling, then compare its offset assumptions with the Faust offset behavior described in the issue and linked discussion. Done means determining whether a minimum lag of 1 can be configured, documenting the supported approach, or clearly documenting that the behavior is not configurable.

Written by the indexing model from the issue text.