scMarkus

Hi catching up on this one to explain a use case we would have with getting data ingested. we are a medium sized mostly cloud native company within a larger...

Is there a good way of representing `u8` as characters in the documentation? I can not think of anything else then changing the datatype in the config to strings an...

@jszwedko any thoughts on how to best solve this? I am by no means an rust or vector expert but I am happy to put in the work given some...

@jszwedko thanks a lot for those hints. what I found out so far (in the end I will ask for your intuition), is the generated json schema file, which is...

Hi @tobz thanks a lot for your input. you seam to be quite right. I naively added your idea. ```rust /// The field delimiter to use when writing CSV. #[configurable(metadata(docs::type_override...

I am having the exact same issue and spent some time digging into the code tracking the behavior down to this line: https://github.com/vectordotdev/vector/blob/0fb8d7dd8ec61e53eba4687a487bd544aedb922f/src/codecs/encoding/transformer.rs#L153-L155 I would like to work around that...

As a temporary workaround one could add an additional field in Graylog and deleting the original timestamp field by using the following VRL code in a remap transformer: ```rust .timestamp_nano...

@jszwedko what are your thoughts on this one?

Thanks for your response @neuronull. After tinkering around a bit a actually would like to suggest another approach to the issue. The [gelf documentation](https://archivedocs.graylog.org/en/latest/pages/gelf.html) explicitly states that `timestamp` field always...

We are looking into this as well. Having a certificate based authentication would be greatly appreciated. Opensearch nicely supports [admin certificates](https://opensearch.org/docs/latest/security/configuration/tls/#configuring-admin-certificates) already. Any thoughts on this?