How work the external web request rules?

[albertokirey]

Hello,
I'm trying to define a new external web request rule (under Service detection).

My goal is to define an external service that collects all the requests that my application do to a specific external service.

I mean that I want that some of the requests that now I see under "Requests to public networks", they will be under a specific service that I have to define.

I try to use the condition "Host name contains mydomain.com" but I don't see the new external service.

How do these rules work?

Thanks

Alberto

[PedroDeodato]

Hey, Alberto,

Under Service Detection, you'll find settings to detect services running on processes monitored by the OneAgent.

As you're talking about the "Requests to Public Networks", those are "services" running outside your organization, ergo not monitored by your OneAgents 🙂

What is, in fact, happening is that OneAgent sees your Services calling those External services and maps out all that requests to those domains mentioned on the "Requests to public networks" service.

The good news is: there is other way to achieve precisely what you need!

Just go to the "Requests to public networks" service, and click on the domain name you need to sort out:

 

That gets applied as a filter, and the page is refreshed.

Then, just click on the three little dots on the upper right corner.

You'll see "Monitor as separate service": this is what you need, click it! 🙂

Hope this helps!

[Mohamed_Hamdy]

Hey, Alberto,

Adding to the above useful information added by Pedro, you can create a service naming rule the same as the below screenshot:

then you can add the following entityselector to the management zone or tagging:

type(SERVICE),entityName.startsWith("Requests to public networks"),toRelationships.calls(type(SERVICE),tag(add the tag))

[albertokirey]

Thank you @Mohamed_Hamdy and @PedroDeodato for your help.

But I don't understand which is the meaning of the External Web Request Rules and External Web Service Rules. 

When do I use them?

Bye

Alberto

[Mohamed_Hamdy]

Hello @albertokirey

Those rules are related to Service Detection rules If the requests go to external resources and are not detected by Dynatrace, select External web request rules or External web service rules.

Dynatrace automatically detects your deployed applications monitored by OneAgent and related microservices through specific properties of your application deployment and configuration, such as the application identifier, part of the URL, or the server name. In certain cases, information available to Dynatrace might be insufficient or incorrect for high-precision service detection. Service detection rules and the related API enable you to feed Dynatrace the needed information to improve out-of-the-box detection.

for more details please check the following URLs:

https://www.dynatrace.com/support/help/shortlink/rule-based-service-detection

[albertokirey]

Hello @Mohamed_Hamdy ,

thank you for your response. I'm sorry if I continue to ask, but I'm a little bit confused. "External resources" are also the resources that are already present in the "Requests to unmonitored hosts" and "Request to public networks" What is the difference between these and the other ones?

Thanks

Alberto

[Mohamed_Hamdy]

Hello @albertokirey

No problem at all, to make it simple, Dynatrace groups the external services under Requests to unmonitored hosts and Requests to public networks by default, so you can create rules to separate these calls automatically instead of separating them manually.

ex. the following is an external web request rule to create separate services if the top-level domain exists, so all the detected domains under requests to unmonitored hosts & requests to public networks will now be available as external services automatically.

I hope this helps

[albertokirey]

Hi @Mohamed_Hamdy ,

I tried but it seems to not work.

I would like to make available the following service:

So, I created the following rule:

It's correct?

Thanks

Alberto

[Mohamed_Hamdy · Accepted solution]

Hi albertokirey,

I think this should work as I use this to monitor external services separately, you can create it with the top domain exists condition, then give it a couple of minutes and make sure that there is traffic. after that navigate to the services, and filter with external services

if you just want to monitor only one service, I think there is no need to create a rule for that, you just need to filter it and then click on "monitor as separate service"

[Janiceadeltoro]

Those rules are related to Service Detection rules If the requests go to external resources and are not detected by Dynatrace, select External web request rules or External web service rules.

Dynatrace automatically detects your deployed applications monitored by OneAgent and related microservices through specific properties of your application deployment and configuration, such as the application identifier, part of the URL, or the server name. In certain cases, information available to Dynatrace might be insufficient or incorrect for high-precision service detection. Service detection rules and the related API enable you to feed Dynatrace the needed information to improve out-of-the-box detection.