Tshepang Mbambo

@jothoma1 am curious why the switch away from flowgger

> the default is `false`, and I'm not really sure if it would be wise to change that. I find current behavior surprising, so curious why not change the default...

> I think it would be smart to separate the concerns of trying to be a swap in replacement for Filebeat and sending data to Logstash. For example, a `filebeat_record_former`...

Having this would ease a transition away from Filebeat, by removing the need to coordinate the transition between senders, who are all behind different firewalls (separate customers), and receivers. Implication...

what is outdated @GuillaumeGomez

I have not... thanks for the suggestion, will have a look.

This tool of mine handles both issues without choking. I intend to get back to making it more fancy... I keep postponing.

does it apply only to std though, or should it perhaps move to forge

> As a grain of salt I have to say that I actually do like the aesthetics of the previous diagram more (see below). hm, I find the mermaid one...

Alternatively, maybe remove the `new` call since it does not seem to add anything? One can just do something like: ``` rust let opts = PubOpt::at_least_once() | PubOpt::retain(); // in...