our
> logs into elastic search just for added real time convenience and want to
> make that step optional. Essentially, if we fall behind writing to ES, we
> would prefer to just skip ES (since we have a more durable channel for
> higher latency querying of the same data). Optional Channe
nce and want to
> make that step optional. Essentially, if we fall behind writing to ES, we
> would prefer to just skip ES (since we have a more durable channel for
> higher latency querying of the same data). Optional Channels seemed to fit,
> but we haven't had much success.
> &
n the right direction. We're indexing our logs
>> into elastic search just for added real time convenience and want to make
>> that step optional. Essentially, if we fall behind writing to ES, we would
>> prefer to just skip ES (since we have a more durable channel for highe
ch just for added real time convenience and want to make
> that step optional. Essentially, if we fall behind writing to ES, we would
> prefer to just skip ES (since we have a more durable channel for higher
> latency querying of the same data). Optional Channels seemed to fit, but we
l for higher latency
querying of the same data). Optional Channels seemed to fit, but we haven't
had much success.
First, we set our config to have a Memory Channel and made it optional. If the
ES sink fell behind, the channel would fill and reject new events. However,
the channel
