Prevent Nightwatch middleware from being registered multiple times #71
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.
Summary
When the Nightwatch middleware is added to a connector that is reused across multiple requests, the middleware is registered repeatedly on subsequent requests. This results in duplicate middleware execution and inflated Nightwatch metrics.
Problem
The Nightwatch plugin registers its middleware via
addMiddlewareon the GuzzlehandlerStack, which does not de-duplicate entries. When a Connector instance is reused, the Nightwatch middleware is appended again on each request, causing the middleware to run multiple times per request lifecycle.Because Nightwatch is intended to observe outgoing requests once per execution, this leads to significant oversampling.
Fix
Before registering the Nightwatch middleware, remove any existing middleware tagged as
nightwatchfrom the handler stack. This ensures the middleware is only applied once, even when connectors are reused.Tests
mainand passes with this change.