Conversation
…ent payload Split startupLog into three independent functions so config is logged immediately at init (via proxy.js) while integrations are logged later on first agent payload (via writer.js). This gives users config info faster without losing the integrations_loaded field that was regressed in #7470. Also fixes broken agent error logging introduced in #7212 where `startupLog({ agentError: err })` didn't match the expected `{ status, message }` shape. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Contributor
Overall package sizeSelf size: 4.87 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.6 | 81.92 kB | 816.75 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
bm1549
added
semver-patch
AI Generated
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7643 +/- ##
=======================================
Coverage 80.28% 80.29%
=======================================
Files 738 738
Lines 31897 31908 +11
=======================================
+ Hits 25610 25622 +12
+ Misses 6287 6286 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
BenchmarksBenchmark execution time: 2026-03-03 19:36:19 Comparing candidate commit cf2f59b in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 232 metrics, 28 unstable metrics. |
bm1549
requested review from
khanayan123 and
rochdev
and removed request for
a team
rochdev
approved these changes
Mar 6, 2026
dd-octo-sts bot
pushed a commit
that referenced
this pull request
Mar 7, 2026
#7643) * fix(startup-log): emit config early at init, integrations on first agent payload Split startupLog into three independent functions so config is logged immediately at init (via proxy.js) while integrations are logged later on first agent payload (via writer.js). This gives users config info faster without losing the integrations_loaded field that was regressed in #7470. Also fixes broken agent error logging introduced in #7212 where `startupLog({ agentError: err })` didn't match the expected `{ status, message }` shape. Co-Authored-By: Claude Opus 4.6 <[email protected]> * ci: re-run CI --------- Co-authored-by: Claude Opus 4.6 <[email protected]>
Merged
juan-fernandez
pushed a commit
that referenced
this pull request
Mar 10, 2026
#7643) * fix(startup-log): emit config early at init, integrations on first agent payload Split startupLog into three independent functions so config is logged immediately at init (via proxy.js) while integrations are logged later on first agent payload (via writer.js). This gives users config info faster without losing the integrations_loaded field that was regressed in #7470. Also fixes broken agent error logging introduced in #7212 where `startupLog({ agentError: err })` didn't match the expected `{ status, message }` shape. Co-Authored-By: Claude Opus 4.6 <[email protected]> * ci: re-run CI --------- Co-authored-by: Claude Opus 4.6 <[email protected]>
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Splits the startup log into three independent log events so config is emitted early while integrations
are logged later:
startupLog()— LogsDATADOG TRACER CONFIGURATIONimmediately at init (called fromproxy.js#updateTracing). Excludesintegrations_loadedsince plugins haven't loaded yet.logIntegrations()— LogsDATADOG TRACER INTEGRATIONS LOADEDon first agent payload (calledfrom
writer.js), by which time the app has loaded its dependencies.logAgentError()— LogsDATADOG TRACER DIAGNOSTIC - Agent Error: ...separately with proper{ status, message }shape.Each function has its own
alreadyRanguard.tracerInfo()is unchanged (still includesintegrations_loadedfor the flare module).Motivation
flagged —
integrations_loadedwas always empty because plugins hadn't loaded yet at init time. Revert "fix(startup-log): emit immediately after init and send to stderr" #7478reverted fix(startup-log): emit immediately after init and send to stderr #7470 entirely, and fix(startup-log): send startup logs to stderr #7502 only re-applied the stderr level change.
startupLog({ agentError: err })didn't match thefunction's expected
{ status, message }shape, soagentError.messagewas alwaysundefined.Additional Notes
configInfo()(private helper) doesn't referencepluginManagerat all, making it structurallyimpossible for
integrations_loadedto leak into the early config log.still excludes integrations" scenarios.
startupLogsconfig flag.