cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Limit of number of metric dimension values

jegron
DynaMight Champion
DynaMight Champion

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)

jegron_0-1688638617091.png

In Data Explorer there is only 76 "dimensions"

jegron_1-1688639001923.png

 

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 🙂

Observability Engineer at Phenisys - Dynatrace Professional
3 REPLIES 3

AntonPineiro
DynaMight Guru
DynaMight Guru

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

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

jegron
DynaMight Champion
DynaMight Champion

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

Observability Engineer at Phenisys - Dynatrace Professional

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

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

Featured Posts