Tommaso Allevi

Hi, thanks for your comment. I wouldn't like to configure by myself the log part because: - this is not how other plugins work. In fact I'm able to adding...

`unwrap` in a library still seems to me an ugly stuff... Which approach we can take? Just for knowing if you are interested in this enhancement or no....

Fair enough. If you want, I can submit a PR for that

Can I try to implement this?

Are you interessed in this pull request?

In this way each backends describe which events are listened. I've notice all backends have the same attributes like config, logger and startTime variable. Conceptually all backends are interchangeable. So,...

which changes are you interested?

Hi, I don't understand why you consider this change as domain-specific: from developer point of view, I would like to check which parameters are sent to an endpoint

On my machine too: the docker build fails. ``` [...] = note: /usr/local/musl/bin/../lib/gcc/x86_64-unknown-linux-musl/7.2.0/../../../../x86_64-unknown-linux-musl/bin/ld: /home/rust/src/target/x86_64-unknown-linux-musl/release/deps/librdkafka_sys-eaa9257eeeb95018.rlib(rdkafka.o): in function `fprintf': /usr/include/x86_64-linux-gnu/bits/stdio2.h:97: undefined reference to `__fprintf_chk' /usr/local/musl/bin/../lib/gcc/x86_64-unknown-linux-musl/7.2.0/../../../../x86_64-unknown-linux-musl/bin/ld: /usr/include/x86_64-linux-gnu/bits/stdio2.h:97: undefined reference to `__fprintf_chk' /usr/local/musl/bin/../lib/gcc/x86_64-unknown-linux-musl/7.2.0/../../../../x86_64-unknown-linux-musl/bin/ld: /usr/include/x86_64-linux-gnu/bits/stdio2.h:97:...

I'm not so familiar with `quore!` macro. I've tried to implement but some compile errors appears. Could you suggest me some tools for debugging? Thanks