# Resolve DQL Error When Query Returns Multiple Metrics

**URL:** <https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148>\
**Category:** DQL\
**Tags:** dql, dynatrace-managed, anomaly-detection, infrastructure-operations\
**Created:** [December 2, 2024, 11:00am UTC](https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148 "2024-12-02T11:00:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nilkanthj](https://avatars.discourse-cdn.com/v4/letter/n/35a633/32.png) [@nilkanthj](https://community.dynatrace.com/u/nilkanthj)\
**Post date:** [December 2, 2024, 11:00am UTC](https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148/1 "2024-12-02T11:00:35Z")

</div>

created below DQL to monitor the Disk with used.percent and disk.avail condition however we are getting below error message.

Could you please help to fix this issue ?

DQL  
timeseries { averageDiskU = avg(dt.host.disk.used.percent), averageDiskA = avg(dt.host.disk.avail) }, by: { dt.entity.disk, dt.entity.host, host.name, dt.entity.host\_group }, filter: {contains(entityName(dt.entity.disk), “sapdata”) and dt.entity.host\_group == “HOST\_GROUP-B86DECA59DA2RM07” }  
| lookup [fetch dt.entity.disk &nbsp;| fieldsAdd component = arrayFirst(tags)], lookupField:id , sourceField:dt.entity.disk  
| fieldsAdd dt.entity.disk.name = entityName(dt.entity.disk)  
| fieldsadd averageDiskUsed = toLong(arrayLast(averageDiskU))  
| fieldsAdd averageDiskAvailable = toLong(arrayLast(averageDiskA))  
| filter averageDiskUsed \>= 85  
| filter averageDiskAvailable \<= 32212254720  
| fieldsAdd Priority = if(averageDiskUsed \>= 95 and averageDiskAvailable \<= 10737418240 , “P1”, else:(if(averageDiskUsed \>= 90 and averageDiskAvailable \<= 21474836480, “P2”, else:(if(averageDiskUsed \>= 85 and averageDiskAvailable \<= 32212254720, “P3”, else:“OK”)))))

Error message -- The query results in multiple metrics, but anomaly detectors only support single metric

---

<div class="post-metadata">

**Author:** ![izabelarokita](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/izabelarokita/32/41812_2.png) [@izabelarokita](https://community.dynatrace.com/u/izabelarokita)\
**Post date:** [December 17, 2025, 12:08pm UTC](https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148/2 "2025-12-17T12:08:30Z")

</div>

Hey&nbsp;[@nilkanthj](https://community.dynatrace.com/user/77462)&nbsp;,  
I just wanted to check in and see if you still need help with this. If so, I’d be happy to look into it for you!&nbsp;:blush:  
Please let me know what works best for you.

---

<div class="post-metadata">

**Author:** ![danijela](https://avatars.discourse-cdn.com/v4/letter/d/ed8c4c/32.png) [@danijela](https://community.dynatrace.com/u/danijela)\
**Post date:** [May 7, 2026, 7:07am UTC](https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148/3 "2026-05-07T07:07:29Z")

</div>

Hello&nbsp;[@IzabelaRokita](https://community.dynatrace.com/user/67399)&nbsp;,

I would need help with my query:

timeseries {abap\_dumps = sum(log.sap.abap.st22.dumps\_count, rollup:sum), default:0}, by:{log.source},  
filter:{matchesValue(log.source, {“P02”, “P03”, “P13”, “P15”,“P06”})}  
| lookup [fetch `dt.entity.sap:abap:system`], sourceField:log.source,lookupField:entity.name, fields: {id}  
| summarize { dumps=sum(abap\_dumps[]) } , by: {timeframe, interval}  
| fieldsadd sum=arrayMovingSum(dumps, 15)  
| fieldsRemove dumps

---

<div class="post-metadata">

**Author:** ![MaximilianoML](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/maximilianoml/32/25038_2.png) [@MaximilianoML](https://community.dynatrace.com/u/MaximilianoML)\
**Post date:** [May 7, 2026, 8:33am UTC](https://community.dynatrace.com/t/resolve-dql-error-when-query-returns-multiple-metrics/49148/4 "2026-05-07T08:33:20Z")

</div>

Hello&nbsp;[@danijela](https://community.dynatrace.com/user/76973),

In this case the important point is that timeseries returns an array of datapoints. Because of that, you should apply arrayMovingSum() directly on the timeseries array.

The part below changes the shape of the data:

```javascript
| summarize { dumps=sum(abap_dumps[]) } , by: {timeframe, interval}

```

After this, **dumps** is no longer the same timeseries array structure, so arrayMovingSum(dumps, 15) will not behave as expected.

You can try this version below:

```javascript
timeseries {
    abap_dumps = sum(log.sap.abap.st22.dumps_count, rollup: sum),
    default: 0
},
by: { log.source },
filter: {
    matchesValue(log.source, {"P02", "P03", "P13", "P15", "P06"})
}
| lookup [
    fetch `dt.entity.sap:abap:system`
],
sourceField: log.source,
lookupField: entity.name,
fields: { id }
| fieldsAdd dumps_15_intervals = arrayMovingSum(abap_dumps, 15)
| fields log.source, id, timeframe, interval, abap_dumps, dumps_15_intervals

```

I hope it helps you&nbsp;😊
