ref(bun): Streamline auto-instrumentation integration handling - #23392
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f86c2ed. Configure here.
| ...autoPerformanceIntegrations.filter(integration => !replacedOtelIntegrationNames.has(integration.name)), | ||
| ...channelIntegrationInstances, | ||
| ]; | ||
| return getAutoPerformanceIntegrations(); |
There was a problem hiding this comment.
Missing AWS auto-instrumentation
Medium Severity
Switching Bun performance defaults to getAutoPerformanceIntegrations() drops awsIntegration, which the old channelIntegrations swap previously installed when the Bun plugin injected channels. The plugin still transforms AWS SDK packages, but those channels no longer have a subscriber in Bun defaults, so AWS SDK spans stop being recorded.
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit f86c2ed. Configure here.
size-limit report 📦
|
f86c2ed to
4dcb7be
Compare
4dcb7be to
0f9e132
Compare
0f9e132 to
2609eb6
Compare
No longer necessary to handle in bun specifically - we just add the node auto instrumentation and be done with it, they will noop without orchestrion but nothing changes there.
2609eb6 to
cec2750
Compare


No longer necessary to handle in bun specifically - we just add the node auto instrumentation and be done with it, they will noop without orchestrion but nothing changes there.
This also allows us to drop this export from server-utils.