Cindy Peng

To fix this issue in nodejs logging repo, @dashpole suggested importing OpenTelemetry Api and using nodejs `spanContext` to retrieve current traceId and spanId:https://github.com/googleapis/google-cloud-go/issues/9302#issuecomment-1930391821 @aabmass David mentioned that you may help...

Hi @patrickchho, you will need to set up authentications correctly for logging: https://cloud.google.com/docs/authentication/provide-credentials-adc Could you share more details about the authentication set up in your application?

Flaky test: https://btx-internal.corp.google.com/invocations;p=250644331956?q=target:cloud-devrel%2Fclient-libraries%2Fnodejs%2Fcontinuous%2Fgoogleapis%2Fnodejs-error-reporting%2Fnode14%2Fsystem-test

Thank you @benjaminfiliatrault for the fix!

Flaky test: https://fusion2.corp.google.com/invocations?q=target:cloud-devrel%2Fclient-libraries%2Fnodejs%2Fnightly%2Fgoogleapis%2Fnodejs-logging%2Fnode14%2Fsystem-test

Hi @seeARMS, are you still running into this issue? If the [GRPC options ](https://github.com/googleapis/gax-nodejs/issues/157#issuecomment-345335610)didn't work for you, could you also share the parameters you set?

Hi @rr923 , just want to follow up, are you still running into this issue?

Hi @dashpole , do you know if this logic works the same for other language version of otelhttp? > When a user has instrumented their application with OpenTelemetry, the trace...

Hi @aabmass , I am currently working on similar fixes for this issue in [nodejs-logging](https://github.com/googleapis/nodejs-logging) and[ java-logging](https://github.com/googleapis/java-logging) repos. I am looking for similar approaches as following to to get SpanContext...

Thanks @dashpole! There is another impacted scenario for App Engines, Cloud Functions and Cloud Runs with automatic tracing(https://cloud.google.com/trace/docs/overview#configurations_with_automatic_tracing). As a fix for these environments, do you think we should generate...