[Vercel Serverless] update to include trace and span ID remappers - #2721
Conversation
| "tags" : [ "source:vercel" ] | ||
| "tags" : [ "source:vercel" ], | ||
| "traceId" : "85ea8a46-d63e-4fe3-ad03-ade7c16cd36b", | ||
| "spanId": "1012381427123789198737891237891" |
There was a problem hiding this comment.
In reality, Vercel sends this in hex, while the span ID is actually in decimal. Will update this test in a follow-up PR!
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
The merge request has been interrupted because the build 0 took longer than expected. The current limit for the base branch 'master' is 120 minutes. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
The merge request has been interrupted because the build 0 took longer than expected. The current limit for the base branch 'master' is 120 minutes. |
Ticket, Ticket
What does this PR do?
Updates the existing Vercel Logs OOTB Pipeline to include trace and span ID remappers!
Motivation
The team at Vercel is adding trace and span correlations with logs, so we are adding support for it!
Added steps:
traceIdgets marked as the trace ID for the logspanIDgets marked as the span ID for the logReview checklist
no-changeloglabel attachedAdditional Notes
Anything else we should know when reviewing?