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

Why is isp not an available dimension for custom USQL User Session Metrics?

36Krazyfists
Helper

Super annoying...  isp is available as a filter for custom USQL metrics, but it isn't available as a dimension?  Why?  That doesn't make any sense to me...  I tried using carrier but that value is null for all of our user sessions.  I need to be able to use isp as a dimension. 

Is there a workaround that anybody can think of that will allow me to create a custom USQL metric with isp as the dimension?

2 REPLIES 2

tyler_rowe
Dynatrace Helper
Dynatrace Helper

ISP is a high cardinality dimension, which means it could create a significant amount of dimensions, and we do have a dimension tuple limit:

https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/metric-v...

There are much higher cardinality properties that are available as a dimension though.  ISP isn't really that high cardinality to be honest...  Like, there's no way ISP is higher cardinality (or at least much higher) than BrowserMajorVersion, ScreenHeight/Width, displayResolution, osVersion, region, and carrier (if carrier had data for us...).

 

And while yes, there are cardinality limits, we should still have the option of using dimensions like this as long as we stay under the overall limits.  It'd be fine if it wanted to give us a warning, but not even offering it as a valid dimension is definitely aggravating, especially given how useful it would be to find trends with our users' ISPs, especially if we could then break them down by region or city (another dimension we can't use because I assume its too high of cardinality) .

 

I mean, I can still get this data, but I'll have to just create a custom script automation to do it using the Ingest Metrics API.  So, all removing this dimension from being selected does is make our use of Dynatrace that much less convenient...

Featured Posts