Pat

@annettejanewilson does this actually work then, I'm not sure if that's what you're saying or requesting?

This would be good to merge, are we ok now @PettitWesley @DrewZhang13 @lecaros ?

@agup006 want me to look at this more generally for packaging? I've added repo config files as well for the Yum-style repos so rather than creating a file you can...

What is the actual problem here for 1.? I don't really understand the issue from what is written so please can you provide some reproducer of the issue or more...

It looks to me like the issue is with Fluentd sending to BigQuery so you probably want to drill down on that and raise in the Fluentd repository for that...

Are you parsing the timestamp from the raw record? If not it will be using the local time.

What's your parser config? What field is it using for the timestamp and is it parsing the fractional seconds?

@pabloxxl can you rebase, we were having issues with the MacOS unit tests that are hopefully resolved now? Yours timeout here.

It would help to have an example. You can specify a different parser per `tail` input, if a parser is not matched then it will just not be applied and...

@changdongkai I would recommend discussions or the Slack channel for general questions. @block011 your feature request sounds like a good idea to me, I'd raise a separate issue on it...