-
Notifications
You must be signed in to change notification settings - Fork 49
Trace agent doesn't create new trace id for each request #287
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.api: loggingIssues related to the googleapis/nodejs-logging-winston API.Issues related to the googleapis/nodejs-logging-winston API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.api: loggingIssues related to the googleapis/nodejs-logging-winston API.Issues related to the googleapis/nodejs-logging-winston API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Issue
Log entries are not assigned to specific requests when application is under load.
Value of trace field is same for all log lines but it should be unique.
Environment
NodeJS, Express, Typescript
example project: https://github.com/vtajzich/nodejs-gcp-trace-agent-test
Steps to reproduce
Current
Expected