cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Nice to know, application detection rule failes

henk_stobbe
DynaMight Champion
DynaMight Champion

Hello,

 

In below request header Dynatrace has detected that the request comes from domain localhost:8085

 

This is a intermediate service that gets its request from the actual server

 

henk_stobbe_0-1645265653845.png

 

Easy mistake to make is using the original server domain, but that will not work! You need to use the localhost:8085

 

If you start with the "My web application" the top included domain will show the referer domain from the Request Header not the localhost:8085 you need. So creating or adding to an application here will not work!

 

When you have created a detection rule with the localhost:8085 from scratch, in that application newly created application the top included domain will also contain the referer domain, but the reqeust will start show,

 

KR Henk

 

4 REPLIES 4

dannemca
DynaMight Mentor
DynaMight Mentor

Checking backtrace for the frontend services also helps in some cases.

Site Reliability Engineer @ Kyndryl

Ingrida
Helper

Hi @dannemca,

 

Any short hint how to do this? we were tappling so far in the dark and using rather webinpect to backtrace... any generic recomendations how to proceed on this? or example?

 

Thanks,

Ingrida

dannemca
DynaMight Mentor
DynaMight Mentor

Hi @Ingrida , you can try check for the frontend service backtrace, then on "Calls from unknow hosts" you may see the reffering pages that makes calls to the service.

Try to set up rules for these pages and see.

 

Captura de tela 2022-02-21 091138.png

Site Reliability Engineer @ Kyndryl

Thanks @dannemca,

 

It brings indeed interesting insights to be used for traffic identification

 

Best regards,

I.