26 Mar 2026
05:47 PM
- last edited on
27 Mar 2026
10:36 AM
by
MaciejNeumann
We have these services on our Exchange hosts that are called "Requests on <hostname>:<port_number>"
Something like this:
Inside of this "service" are various incoming requests that should be part of other existing services on the host. For example, we have a bunch of EWS requests that are getting put into this catch-all "Requests on" service instead of the actual EWS app pool service. Basically, most requests are getting properly applied to the proper services, but then others aren't and seem to get pushed into this catch-all service.
Question is, how do we fix that? We don't really use any custom service rules, so it seems to be the default behavior of Dynatrace that is doing this.
01 Apr 2026 05:01 AM
You can fix this by creating service detection rules:
For this, you have to think about how best you can group the required services in a condition. Also the naming you are getting is not great so you should think of some friendly names or that makes sense for the developers/support person/user.
https://docs.dynatrace.com/docs/shortlink/rule-based-service-detection
https://docs.dynatrace.com/docs/shortlink/custom-service-names
Hope this helps.
Featured Posts