Jesse Szwedko

Newer agents also support receiving multiple datapoints in a single line: https://github.com/DataDog/datadog-agent/tree/20bcaf3df7b9240e14c6ec0394cf582b4b6c5ea2/comp/dogstatsd

Thanks for pushing this forward @zamazan4ik ! Just a note that much of the team is on holiday so it may not be reviewed until the start of next year.

Hi @stavcev ! Thanks for this report. As a workaround you can convert the timestamp to Vector's internal timestamp representation via `to_timestamp` in your `remap` transform. This should correctly encode,...

Ah, interesting, thanks @stavcev . It seems like we should be truncating the timestamp to milliseconds then, before sending it to Greylog. As an additional workaround I think you could...

Hrm, that's weird. Does that mean it cannot receive timestamps with milliseconds? Can you give an example of a valid timestamp that is accepted by Graylog?

Gotcha, I see, thanks for clarifying. I see Graylog is expecting a numeric timestamp. I'd originally thought it wanted a RFC3339 formatted string. As _another_ workaround I think you could...

Bruce had some thoughts about making [the definitions of integration tests](https://github.com/vectordotdev/vector/pull/15249/files) a bit less verbose that he was going to explore in a separate branch for comparison.

> Is it possible for the same tag to have both multiple values _and_ bare tags? That will help inform the data structure we choose to use internally. For posterity,...

> @bruceg @jszwedko Can anything be done about this? There's no reason for Vector to be supporting TLSv1.0, TLSv1.1 > > I can create the PR again if needed. Hey!...

Agreed, this is likely to be a very large and invasive project that we unfortunately haven't been able to prioritize just yet. I realize it would be very useful.