improve error message when sending metrics fails #582
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 updates the error message logged when sending client-side performance metrics to segment fails.
See https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/troubleshooting/#why-do-i-see-a-network-request-to-m for background info on client-side performance metrics.
These metrics do not impact customer event delivery, but can cause confusion when showing up on platforms like Sentry when an error occurs. This provides a way to filter out these messages by the new error message preceding the error.
[x] I've included a changeset (psst. run
yarn changeset
. Read about changesets here).