How to detect high request cardinality in Services?

[AntonioSousa]

Sometimes, Services are detected with a high number of different requests. That mainly happens when requests have UUIDs/IDs/etc that Dynatrace doesn't manage to automatically clean from web request names. High cardinality is not desirable of course, because at the limit, all requests are different...

The question is how we can detect these Services? I believe it has to be through API calls, but before digging heavy into this, has someone tackled this?

[RazTN7]

Hello @AntonioSousa 

Today I have similar requirement for one of the client where I need to clean trnxID from thousands of request URLs to make it distinct.
Here is where I'm going to start with by creating one clean up rule for the web request.

Just need to work on right regex for this.

Thanks,

RN

[Julius_Loman · Accepted solution]

@RazTN7  see my tip PRO TIP - Global request naming for REST services you can do it the same way.

@AntonioSousa this is not possible with API at the moment, afaik. With traces in Grail this is likely possible. I'd start with something like this:

fetch spans
| filter span.kind == "server"
| summarize count(), by:{dt.entity.service, code.function}
| summarize count(), alias: `request_names`, by:{dt.entity.service}
| sort request_names desc