Thomas Watson comments

Results 173 comments of


                                            Thomas Watson

Simple support for instrumenting incoming WebSockets

Yes that was my idea

Simple support for instrumenting incoming WebSockets

@nuragic I think the [Get started with a custom Node.js stack](https://www.elastic.co/guide/en/apm/agent/nodejs/current/custom-stack.html) guide is what you're looking for. This describes how to instrument an unsupported framework.

ci: use official system tests GitHub Actions workflow

* **#5884** 👈 (View in Graphite) * `master` This stack of pull requests is managed by Graphite. Learn more about stacking.

feat(debugger): implement intelligent snapshot pruning for oversized payloads

* **#7006** 👈 (View in Graphite) * `master` This stack of pull requests is managed by Graphite. Learn more about stacking.

fix(debugger): don't expect probe config to contain `capture` object

* **#6807** 👈 (View in Graphite) * `master` This stack of pull requests is managed by Graphite. Learn more about stacking.

change release proposal script exclusion label

If the PR in question _only_ contains code that is behind a version flag, it's safe to not include it in the changelog for older versions. However, I can easily...

change release proposal script exclusion label

@rochdev I'm not a fan of `v6-only-changes` either - it was just what I could come up with in the moment. My point was to signal that the PR contained...

change release proposal script exclusion label

> > After the release of v6, we want to be able to land a PR containing changes both targeted v5 and v6. > Isn't that just a normal `semver-patch`...

change release proposal script exclusion label

> _Note: "landing" here means enabling the change since commits always land everywhere._ Understood 👍 My main concern here is also just about how we mange release notes. I'm aware...

chore(deps): bump import-in-the-middle from 1.15.0 to 2.0.0

@dependabot rebase