Conversation
Summary - Markdown Lint |
Summary - Link Checker
|
sergiothinks2
requested review from
NachoEmbrace,
ferdraghi,
juansc,
mfrishert and
vitaliyf
juansc
reviewed
Mar 4, 2026
docs/best-practices/graphql.md
Outdated
| This happens because the Embrace backend automatically groups network paths with high cardinality | ||
| into wildcard entries. For example, if your app tracks many distinct GraphQL operations | ||
| (`/graphql/getUser`, `/graphql/createOrder`, `/graphql/deleteItem`, etc.), the backend | ||
| may collapse them into a single wildcard entry like `/graphql/*`. When this occurs, individual |
Contributor
There was a problem hiding this comment.
change * to the wildcard we use in the dashboard
vitaliyf
approved these changes
Mar 5, 2026
juansc
approved these changes
Mar 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Context
Two customers (ServiceTitan, Strava) independently reported that their GraphQL operations were not appearing in the Network section of the dashboard. In both cases, the SDK was capturing requests correctly
(visible in session timelines), but the backend was collapsing distinct
/graphql/<operation>paths into a wildcard. The existing docs only covered the SDK-side setup without mentioning this dashboard behavior.