losalex

Thanks @chriscalo for opening this issue! It seems that there are multiple issues here, feel free to correct me if I am wrong: 1. I believe that having extra "message"...

Thanks @NeverwinterMoon for providing more context! Below are some points with respect of your observations: 1. When running in serverless environments like Cloud Functions (CF), the `logName` and `resource` fields...

Downgrading priority for now until we clarify this issue with product teams

@chriscalo and @NeverwinterMoon , I was thinking to close this issue - the timestamp issue was fixed and as for `logName`, it might take time to fix - I filed...

@alexander-fenster , is this feature related to this library or needs to be implemented in gapic layer?

@rubiagatra, thanks a lot for reaching out and offering help and sorry for long time it takes to resolve this issue. Feel free to share here any specific samples/comments you...

@xiaozhenliu-gg5 , thanks for filing this issue and apologies for long time to respond. Can I ask you please provide more details on your request? Would it be possible for...

@fpbouchard, feel free to reactivate this issue. I believe that your fix could be checked in, but it requires a configuration value controlling if your fix is enabled or not....

Thanks @fpbouchard for your responses and understanding! Definitely the backward compatibility is an issue here, since the feature is already released and might be used as is today by other...

Sorry on late response @mat105 and @Bmgaynor. Please see corresponding answers to your question: 1. Indeed, if you use both, `stdout` and `LoggingBunyan.stream` you will have duplicate records which I...