Count value of ingested Gauge metric not in DQL

[macosta]

Sorry if this was asked before but I couldn't find a clear explanation documented.
We are ingesting a gauge metric using "api/v2/metrics/ingest"  like this:

test-metric-ingest.novedades.cantidadGa,dt.entity.custom_device="CUSTOM_DEVICE-B558D0293AAAAAAA",entidad=suplementos  gauge,min=17.1,max=17.3,sum=34.4,count=2


If i check the metric in Data Explorer using the Count aggregation it shows 2, as expected sisnce that was what we ingested:

But, when moving to Grail and DQL,  modern Dashboards/Notebook panel always shows count=1 :

So, is it useless to ingest gauge metrics with different counts for modern panels? Will this be corrected in the future?
 

[sujit_k_singh]

Hi @macosta 

Grail no longer distinguishes between gauge and count formats at ingest time — it treats each ingested data point as a single observation regardless of the count parameter you pass Troubleshooting — Dynatrace Docs

In Grail's model, your single API call = 1 data point, so count=1. The count=2 in your ingest payload is metadata the classic engine honors but Grail does not propagate the same way.

This Means. Data Explorer: Respects the full gauge envelope (min, max, sum, count) as ingested
Grail/DQL (modern panels): Treats each ingest call as one sample — the count field from the gauge payload is effectively ignored for aggregation purposes.

This appears to be a known architectural difference rather than a bug that will be "fixed," as Grail was designed with a different data model.

Thanks,

Sujit