Actually they want to see this key request in the service flow as a speared service and to be able to see its measures in terms of response time cpu failures and throughput as any other service since for them those request play a major role in their application.
Hello. I have received two requests similar to this from my customer (SAP). Is there any way at all to separate requests just by their URLs? The reason they want this is:
a) Because their endpoints in their apps are only distinguished by URL. Filters would not be enough in this case, because this are actually separate endpoints and they want the full functionality a service provides.
b) Because they wanted to create a service from 3rd party providers (https://www.dynatrace.com/support/help/server-side... but domains (sap.com) are too big, and they would want to separate by subdomains (hana.sap.com, test.sap.com).
Is there any chance this could be supported in the future?
You can go to the service flow, and add a filter from that page for the specific request. Example:
Notice that the /prescriptions request is being shown here, so all of the information in the service flow corresponds to only that request. You can add this filtering on several views throughout Dynatrace, as well as even pin some of these to dashboards. I believe this gets you most of the information you are looking for based on your comment back to Michael.