From 38fdb3f1ee1d9940d68c54a8ad2ab8d61f4a0e6d Mon Sep 17 00:00:00 2001 From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com> Date: Thu, 18 May 2023 12:22:31 +0200 Subject: [PATCH] [v9.5.x] Service graph: Fix error when service graph metrics are aggregated (#68691) Service graph: Fix error when service graph metrics are aggregated (#68613) make service graph work with aggregated metrics (cherry picked from commit e1c2eb8c107365188a88e56ad23d912b4663c32e) Co-authored-by: Domas --- public/app/plugins/datasource/tempo/datasource.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/app/plugins/datasource/tempo/datasource.ts b/public/app/plugins/datasource/tempo/datasource.ts index 9b0ab037e82..1aece9609ff 100644 --- a/public/app/plugins/datasource/tempo/datasource.ts +++ b/public/app/plugins/datasource/tempo/datasource.ts @@ -744,7 +744,7 @@ function makePromServiceMapRequest(options: DataQueryRequest): DataQ refId: metric, // options.targets[0] is not correct here, but not sure what should happen if you have multiple queries for // service map at the same time anyway - expr: `rate(${metric}${options.targets[0].serviceMapQuery || ''}[$__range])`, + expr: `sum by (client, server) (rate(${metric}${options.targets[0].serviceMapQuery || ''}[$__range]))`, instant: true, }; }),