question

James K. avatar image
James K. asked ·

Details regarding applications created from domains in HTTP request headers.

Hi all,

We're looking at setting up some application rules based around HTTP request headers and the first attempt didn't succeed so wanted to clarify a few things.

  1. Is the assumption correct that the 'custom application rules' will override the domains detected from headers? So that if it matches a custom application rule as well as contains the header it will be grouped by the custom rule?
  2. Are there some details as to what criteria must be met before requests matching the header will create an application? I found this >2 year old post and don't know if it is still up to date and would regardless like to see some of the full list of criteria: https://answers.dynatrace.com/spaces/482/dynatrace...
  3. Are there any other considerations or limitations to using headers to create domains/applications?

Thanks!

James

configurationDynatrace ManagedRUMauto-detection
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Answer

Alexander S. avatar image
Alexander S. answered ·

Application rules uses the URLs of incoming http(s) requests to group them to applications. By default all incoming traffic is assigned to the default application called "my web application". Now you can start to group this traffic by adding application rules based on URLs.
As the domain (host) part of the URL is typically set in the host header of an request. But depending on the used infrastructure the host header may not have the original host name and the original host name is in an other header like the x-forwarded-for.
So if a request comes in, Dynatrace checks for some headers for getting the correct domain (host) to build the complete URL. You can see the default headers and the order for this domain detection at the end of the application rule settings view. If needed you can add your own header which is then used for the domain part of the URL.
After the domain lookup, the complete URL will be used for application detection.

Back to your questions:
  1. Application rules are based on URLs (the domain or host name) is part of the URL. The domain matches rules are just shortcuts to make the configuration easier. As the domain (host name) is only available within a header, Dynatrace looks for existence of some typical "host" headers in a given sequence, takes the first one found and uses this for the domain part of the URL.
  2. This old post is not relevant anymore. Applications are not created automatically. You have to define an application rule.
  3. You can use http headers for application creation. Only the host header as part of the full URL is part of the application detection. Of course you can add every header to be considered as host header, but then you will see this header value also as host or domain in all views.

Does this help?

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Yes, this explanation is very clear. Thanks!

0 Likes 0 · ·

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions diagnostic tools session replay permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android