You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently there is no way to distinguish different GraphQL requests in request monitoring section. Requests all come with the same url which is the base behaviour of GraphQL and request body is not tracked or accessible to be able to distinguish between request.
Also the configuration option networkRequestCallback does not allow the user to somehow access the body and include it with the request info:
BugsnagPerformance.start({
apiKey: 'YOUR_API_KEY',
networkRequestCallback: (requestInfo) => {
/// requestInfo is only consist of { type, url } the body is not accessible.
return requestInfo
}
})
Describe the solution you'd like
I would be nice if we could distinguish requests by GraphQL query names for example.
Describe alternatives you've considered
instead of automatically tracking network requests add a manual option so we can send the requests with their query names.
The text was updated successfully, but these errors were encountered:
Thank you for reaching out. We do have an item on our backlog aimed at adding this support in the future. We do not have a clear ETA on the release of this functionality but we will be sure to keep you posted via this thread once we have more information or an update to share.
Description
currently there is no way to distinguish different GraphQL requests in request monitoring section. Requests all come with the same url which is the base behaviour of GraphQL and request body is not tracked or accessible to be able to distinguish between request.
Also the configuration option
networkRequestCallback
does not allow the user to somehow access the body and include it with the request info:Describe the solution you'd like
I would be nice if we could distinguish requests by GraphQL query names for example.
Describe alternatives you've considered
instead of automatically tracking network requests add a manual option so we can send the requests with their query names.
The text was updated successfully, but these errors were encountered: