Adding metadata header to client requests #696
Merged
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.
This PR adds in basic client telemetry that for now only includes timing information. The telemetry is sent back as a sidecar payload in an HTTP header of:
X-Stripe-Client-Telemetry
With a JSON payload format of:
By sending as a sidecar http header we avoid an extraneous network call at the cost of only being able to track the previous request.
Adding in this telemetry will allow stripe to help diagnose latency and other connection issues as well as provide a space to augment future telemetry data.
Telemetry needs to be opted into by setting:
And can be disabled at any time by toggling that flag (the value is not cached)