instrumentation of apollo-server-*
See original GitHub issueWhen using express-graphql
requests/transactions are grouped by query/mutation name, but this is not the case when using apollo-server-express
, where transactions is simply grouped by the route.
It would be nice if transactions through apollo-server-*
was grouped by query/mutation name.
I’m happy to help, but a little guidance on where to start would be nice.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
OpenTelemetry in Apollo Federation - Apollo GraphQL Docs
OpenTelemetry is a collection of open-source tools for generating and processing telemetry data (such as logs and metrics) from different systems in a ......
Read more >Monitor Apollo Server with OpenTelemetry - New Relic
Learn how to measure federated and non-federated Apollo Server at every phase of the query cycle with OpenTelemetry and New Relic.
Read more >instrumentation-graphql doesn't work with apollo-server ...
Implement tracing with instrumentation-graphql in order to trace GraphQL resolvers running on Apollo Server with generated federated schema.
Read more >AppSignal Now Automatically Instruments Apollo for Node.js ...
We're happy to announce a new version of AppSignal for Node.js, and support for instrumenting Apollo Server v2+. This means that we'll save ......
Read more >GraphQL: Instrumenting your API and unlocking superpowers
Instrumentation is adding the proper amount of logging to your ... enable the tracing flag when creating your instance of ApolloServer, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@levanvunam please create a new post on https://discuss.elastic.co/c/apm. If you provide debug logs there, following https://www.elastic.co/guide/en/apm/agent/nodejs/current/troubleshooting.html#debug-mode, you may have a better chance of someone being able to spot the issue.
This how now been released i v1.14.0