docs(serverless): add serverless integrations skill#9188
Conversation
Overall package sizeSelf size: 6.7 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.1 | 122.62 kB | 437.94 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 70caa14 | Docs | Datadog PR Page | Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #9188 +/- ##
=======================================
Coverage 96.56% 96.56%
=======================================
Files 918 918
Lines 121396 121396
Branches 20894 20867 -27
=======================================
Hits 117225 117225
Misses 4171 4171 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
BenchmarksBenchmark execution time: 2026-07-09 14:41:09 Comparing candidate commit 70caa14 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 2313 metrics, 45 unstable metrics.
|
ojproductions
left a comment
ojproductions
left a comment
There was a problem hiding this comment.
Docs look thorough, though I'm new to probes. Might also want to get some input from @rithikanarayan and @joeyzhao2018 in case I missed anything.
| @@ -0,0 +1,57 @@ | |||
| # Deployed Serverless Probe | |||
There was a problem hiding this comment.
concept of a probe is new to me. Is this a dd-trace-js thing? or is it specific for this skill? Sounds to me like its a way to deploy real apps for testing. If that's the case would it make more sense for this to be under the testing-guide skill?
There was a problem hiding this comment.
@ojproductions good point. Moved the deployed verification guidance under references/testing-guide.md and added a short definition there: a probe is a temporary deployed sample function/app for provider + Datadog ingestion checks, not a dd-trace-js runtime feature.
| - add span links when multiple upstream contexts are present; | ||
| - tag trigger type, resource, region/account/project identifiers, and runtime metadata with existing tag naming | ||
| patterns where possible; | ||
| - avoid high-cardinality resource names unless existing serverless integrations already use that shape. |
There was a problem hiding this comment.
Is there an example of a high cardinality resource name that should be reused/replicated? because I think "avoid high cardinality resource names" by itself would be ok
There was a problem hiding this comment.
@rithikanarayan yea, agreed. Removed the "unless existing integrations" caveat and made this a direct low-cardinality rule, with examples of values that should never land in resource names: request IDs, message IDs, object keys, event IDs, and payload values.
3bf216e
3bf216e to
7214826
Compare
7214826 to
70c9ffd
Compare
rithikanarayan
left a comment
rithikanarayan
left a comment
There was a problem hiding this comment.
updates looks good to me
3 participants
What does this PR do?
Adds a repo-local Codex skill for serverless integrations in dd-trace-js. The skill routes platform invocation work apart from normal library instrumentation and includes references for architecture, implementation, testing, deployed probes, and existing reference integrations.
Motivation
We need serverless-specific guidance discoverable directly from dd-trace-js before wiring toolkit workflow support. The skill captures current dd-trace-js conventions for root serverless spans, lifecycle ownership, context extraction, and manual/deployed testing expectations.
Additional Notes
Validated with:
Result:
Skill is valid!No runtime code changes.