Closed ktaekwon000 closed 10 months ago
Thanks @ktaekwon000 for opening the issue. By design Logging client libraries call the gRPC Logging API, and the latency in HttpMessage is expected to be protobuf.
We cannot use latency as a single string (e.g. 3.5s) in our code since Duration is a protobuf
structure expected by Cloud Logging service. I believe that the issue needs to be fixed in stackdriver-logging-agent.
The documentation with correct links will be fixed here: https://github.com/googleapis/nodejs-logging-winston/pull/828.
1) Is this a client library issue or a product issue? This seems to be a client library issue.
2) Did someone already solve this? I have searched through issues in the listed repositories but I have been unable to find the issue I am facing.
3) Do you have a support contract? No.
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
@google-cloud/logging-winston
version: 5.3.0Steps to reproduce
I believe this bug is due to a difference in schema where the cloud logging agent expects an output in the JSON format, but the library prints the output in the protobuf format, causing the logging agent to miss this value. (Related issue: https://github.com/googleapis/nodejs-logging-winston/issues/93)