Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apollo Server tracing #64

Open
radekmie opened this issue Jul 2, 2022 · 0 comments
Open

Apollo Server tracing #64

radekmie opened this issue Jul 2, 2022 · 0 comments

Comments

@radekmie
Copy link

radekmie commented Jul 2, 2022

Our apps expose both REST and GraphQL APIs.

  • 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:
    image
    (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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant