Xiadong

> Hi @xdatcloud thanks for the contribution! I'm wondering if there's any advantage to support both JSON and Proto, and if we should just wholly switch to Proto with optional...

Hi @spencergilbert, sorry but I'm not familiar with the process to make a contribution since this is my first PR to Vector. Is there anything I can do to help?

> Interestingly the performance was the same. I'd be content to just making this the one-and-only encoding and dropping the JSON encoder. What do you think @xdatcloud ? Hi @jszwedko,...

> Hi @xdatcloud ! Just wanted to see if you were still interested in contributing this. As mentioned above, I think we can make it the default behavior since there...

Hi @tobz ! I pushed more integration tests to repo. According to the discussion above: >> Interestingly the performance was the same. I'd be content to just making this the...

> @xdatcloud Ah, woops: looks like there's still some lints being hit. Most of them are pretty straightforward, and you can work through them locally by running `make check-fmt check-style...

> @xdatcloud It looks like you fixed the Clippy issues, but not the other linter issues, specifically our style checks (trailing newlines, spaces, etc). > > As mentioned above, you...

> > @xdatcloud It looks like you fixed the Clippy issues, but not the other linter issues, specifically our style checks (trailing newlines, spaces, etc). > > As mentioned above,...

> @kaarolch we are also currently planning on adding OpenTelemetry support to Vector by the end of the year. This should be more definite soon. That sounds great! I found...

I found the [Tracing support RFC](https://github.com/vectordotdev/vector/issues/2661) hasn't complete yet, willing to join discussion about this work.