Dynatrace captures and monitors all outgoing requests from your monitored server-side services. This includes web requests that your server-side components send out across the internet.
Note that currently, the feature doesn't support gRPC requests.
To configure Dynatrace to monitor a third-party service provider as a separate service
Go to Services or Services Classic (latest Dynatrace).
To find the Requests to public networks service, place the cursor in the Filter by field, and select External services > Third party services.
On the Requests to public networks page, select View requests to list details about aggregated requests.
Scroll down to the top domains table of domains and select the domain that you want to monitor as a separate service.
The page is now filtered by this domain name.
In the upper-right corner of the page, select More (…) > Monitor as separate service.
The confirmation message is displayed at the bottom of the page.
The requests to that domain are monitored as a standalone service. This service:
Only new data is mapped to the standalone service. Any existing data remains unaffected in the Requests to public networks service.
If you no longer want to have a recategorized third-party service set up as a standalone service, you can return it to third-party status.
Go to Services or Services Classic (latest Dynatrace).
Find and open the required service.
Select More (…) > Revert to 3rd party service status.
Alternatively, you can set a custom rule for service detection that will map certain requests to a standalone service. For more information, see Service detection rules API. You'll need the opaque web requests type of rules.