chore(crashtracking): check v2 telemetry payload structure#6348
chore(crashtracking): check v2 telemetry payload structure#6348
Conversation
cbeauchesne
left a comment
There was a problem hiding this comment.
AGTM, but could you get a review from someone familiar with the feature ?
|
|
I own crashtracking, so I will go ahead with merging in a bit if you do not have any objections |
This comment has been minimized.
This comment has been minimized.
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
gyuheon.oh@datadoghq.com unqueued this merge request |
|
/remove |
|
View all feedbacks in Devflow UI.
|
|
/merge -@ in 3 hours |
|
View all feedbacks in Devflow UI.
Pull Request scheduled to be added to the queue on Fri, 20 Feb 2026 03:06:51 UTC
This pull request was merged directly. |
Motivation
v2 telemetry logs are in the form
payload:{logs:[]}. We should handle this case too. Libdatadog was updated in v27 with this PR: [fix(telemetry)!: fix logs payload format APMSP-2590](DataDog/libdatadog#1498) to send crash logs in this form.Changes
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present