Node Application Metrics provides a foundational infrastructure for collecting resource and performance monitoring data for Node.js-based applications.
It would be nice to have a probe that is able to log the response time and perhaps also the response size of apollo/graphql (field) resolvers.
That way it becomes easier to trace down the slow resolvers, and focus on optimizing those first.
If we log the path of the resolver, we could even use it to see if deprecated resolvers are still being used, and adjust our deprecation plan based on those statistics.
So stats that would be useful to me are:
response time
response size
resolver path
Note that a single graphql request, can result in statistics of multiple nested resolvers. Perhaps the apollo tracing data can be used for this. It already contains timings per child resolver.
It would be nice to have a probe that is able to log the response time and perhaps also the response size of apollo/graphql (field) resolvers.
That way it becomes easier to trace down the slow resolvers, and focus on optimizing those first.
If we log the path of the resolver, we could even use it to see if
deprecatedresolvers are still being used, and adjust our deprecation plan based on those statistics.So stats that would be useful to me are:
Note that a single graphql request, can result in statistics of multiple nested resolvers. Perhaps the apollo tracing data can be used for this. It already contains timings per child resolver.