In an epic battle with my keyboard.
@nodejs core contributor, founded tracing (now diagnostics) working group. I hack on compilers and VMs.
- Vancouver, BC, Canada
- http://stephenbelanger.com
Highlights
- Pro
Block or Report
Block or report Qard
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abusePinned
604 contributions in the last year
Less
More
Activity overview
Contribution activity
March 2023
Created 2 commits in 1 repository
Created a pull request in DataDog/dd-trace-js that received 7 comments
Use SpanContext name, not Span name, as Span name is not updated
What does this PR do? Use span context name for single span sampling rules rather than span name as span name is not changed when framework is set.…
+49
−3
•
7
comments
Reviewed 25 pull requests in 4 repositories
DataDog/dd-trace-js
17 pull requests
- support bundling via esbuild
- Export heap profile on v8 heap OOM
- [ci-visibility] Rename ITR and code cov tags
- Use SpanContext name, not Span name, as Span name is not updated
- Fix typo in comment
- switch to tap for ci/core/tracing/profiling tests
- feat: allow DD_TRACE_AWSSDK_{SERVICE}_ENABLED configuration
- fix using pubsub internal api directly
- Implement new appsec IP header detection
- add link to test failures when reporting via slack
- fix kafka client trying to use ipv6 in tests
- [ci-visibility] Fix logic to validate commit SHAs
- run tests nightly and report package failures via slack
-
Skip incompatible services on ARM64
yarn services -
Switch to
network.destination.portfor client port tag name - add dd-trace-js team to all CODEOWNERS entries
- add runtime.node.event_loop.utilization metric





