topic Re: Default Request Naming for all services in Open Q&A

Default request naming for all services

rick_boyd — Mon, 27 Feb 2023 08:42:24 GMT

Hi,

Is it possible to configure web request naming conventions for all monitored services?
We are currently POCing Dynatrace in a dynamic Kubernetes environment, where feature branches are hosted in namespaces, and our services are configured as {namespace} {pod-name} so devs can view their own services easily. The problem is right now requests are getting aggregated by default to a single bucket called invoke. I followed the guide here (https://www.dynatrace.com/news/blog/track-business-transactions-using-advanced-request-naming-rules/) to successfully get the requests named per the URL path, but it's not feasible for us to do this for every k8s namespace (and hence every Dynatrace service). Can whatever the rule is that is calling these requests "invoke" be de-prioritized against a rule that calls them by their URL path?

Thanks,

Rick B

Re: Default Request Naming for all services

rick_boyd — Tue, 06 Mar 2018 15:11:06 GMT

I am also open to alternative suggestions in how to categorize my services, so long as we don't sacrifice ease-of-use for developers

Re: Default Request Naming for all services

shaun_gautz — Tue, 06 Mar 2018 16:01:21 GMT

As of right now, web request naming rules are only done per service. As you can tell, it's not easy to use across large dynamic environments. They are working on a feature to do global service configuration.

Shaun

Re: Default Request Naming for all services

andreas_grabner — Wed, 07 Nov 2018 14:23:34 GMT

Just an FYI. There is a Configuration API endpoint availble that allows you to define Global Request Naming Rules. Open your API Explorer, switch to the Configuration API and search for those under "Request Naming"