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
The former uses WebApp.rawConnectHandlers, i.e., we register all of the routes manually and handle all of the logic ourselves (including authorization, parsing the request, etc.).
The latter uses apollo-server-express and wires up using WebApp.connectHandlers.
Now, we see all of the requests in the "HTTP" tab in Monti APM. All of the headers are there, both the number of requests and their timings are correct. But there's a difference about their traces:
REST API has a complete trace, including database operations, async operations, etc.
(We're not using eventStackTrace; we've tried it a year back and it caused a significant performance hit.)
GraphQL API has very basic traces, with all of them looking like this: (Sometimes the first "computation" is not there, and the "async" part reaches 2ms.)
My question is, whether it'd possible to have the same level of detail for the Apollo Server integration?
The text was updated successfully, but these errors were encountered:
Our apps expose both REST and GraphQL APIs.
WebApp.rawConnectHandlers
, i.e., we register all of the routes manually and handle all of the logic ourselves (including authorization, parsing the request, etc.).apollo-server-express
and wires up usingWebApp.connectHandlers
.Now, we see all of the requests in the "HTTP" tab in Monti APM. All of the headers are there, both the number of requests and their timings are correct. But there's a difference about their traces:
eventStackTrace
; we've tried it a year back and it caused a significant performance hit.)(Sometimes the first "computation" is not there, and the "async" part reaches 2ms.)
My question is, whether it'd possible to have the same level of detail for the Apollo Server integration?
The text was updated successfully, but these errors were encountered: