Hi @mkaniaa. By "resolvers" do you mean using AWS AppSync (AWS's thing for building GraphQL services)? AWS AppSync JavaScript resolver function reference for Lambda - AWS AppSync
I haven't used this myself.
I'm struggling a little bit to understand the architecture of your app/service. Are you able to show more code for context, perhaps giving a name for each of the three resolvers so our conversation can be a little bit more concrete.
It is possible you would be able to use the transaction.name (Transaction API | APM Node.js Agent Reference [4.x] | Elastic) API to tweak the current transaction name to something more meaningful for each different type of call to your Lambda function. I don't know from your description if the resolver name or some GraphQL method name would make sense.
Do you mean in the service "Transactions" view, e.g.:
I'm not sure if there is a way to control sorting here. In the general case this is a sampling of all transactions for the service for the current time range, limited to 500. I had thought they would show up sorted by transaction start time, but I don't know that that's the case.
The Configuration options | APM Node.js Agent Reference [4.x] | Elastic (captureBody) config var exists to capture the HTTP body of incoming requests, but there is no support for capturing the body of outgoing requests, unfortunately.