topic Re: Limit of number of metric dimension values in Alerting

Limit of number of metric dimension values

jegron — Thu, 06 Jul 2023 13:04:34 GMT

Hi,

I am working with metrics event and metric selector.

I don't understand why there is so much dimensions with this simple request :

sql-server.host.cpus:splitBy("dt.entity.sql:sql_server_host"):max:rollup(avg,5m)

In Data Explorer there is only 76 "dimensions"

Also the documentation is unclear about the behavior once the limit has been reached :

THROTTLED: The configuration reached the query limits of the metric selector.

Does the alert stop working for the next 24 hours?

Thanks for your help 🙂

Re: Metrics Events - How to understand number of metric dimension?

AntonPineiro — Thu, 06 Jul 2023 11:09:42 GMT

Hi,

I would split it per host groups or hosts, if that is possible. It means, creating more than one and filtering entities.

Best regards

Re: Limit of number of metric dimension values

jegron — Mon, 07 Aug 2023 08:43:16 GMT

Thanks @AntonPineiro . Sadly adding splitby fields does not change the number of dimension in my case.

Re: Limit of number of metric dimension values

AntonPineiro — Tue, 08 Aug 2023 07:46:00 GMT

Hi,

I do not see another option than reduce scope. Maybe, you can ask Dynatrace ONE or raising some product idea. It is design limitation.

Best regards

Re: Limit of number of metric dimension values

nicolas_nguyen — Fri, 02 Aug 2024 15:25:05 GMT

Hi,
We have the exact same problem here , and we also have the same questions unanswered

sql-server.databases.state:splitBy("dt.entity.sql:sql_server_database",instance,server,database,"database.state","database.recovery_model"):filter(in("dt.entity.sql:sql_server_database", entitySelector("type(sql:sql_server_database),tag(INOP-Plateforme-Bd:SB)")),and(ne("database.state",RESTORING)))

Re: Limit of number of metric dimension values

dannemca — Fri, 02 Aug 2024 20:58:24 GMT

I am also facing the same... in my case, I am testing the Davis Anomaly Detection app, with good results.