Hi, I am trying to consolidate all the auto detected applications to a smaller list by having user defined applications with the patterns defined manually. When i define i used "contains" and put all the server names. For example mobile uris will definitely have a the host so i have added that. Attached screenshot. But In the purepaths some middleware transactions are showing up under mobile application. i have checked those purepaths to see if they have mobile host name anywhere and i could not find. Not sure how they are coming under mobile application. Do we need to define using "starts with" instead of contains? any suggestions?
Also - once i have user defined Apps, i am not seeing any traffic under auto detected applications as user defined apps have high priority? So how do i validate if i am covering all the patterns or not by using user defined apps? initially i thought of comparing traffic from user defined Apps vs auto detected apps. Looks like that is not possible unless i delete user defined apps and get the traffic numbers from auto detected Apps and then add user defined Apps and get the traffic and compare. It would be nice to have a feature of making them active and inactive.
Answer by Venkata T. ·
Another question on this is, instead of adding the application patterns from the GUI client, can we add them somewhere in profile.xml, etc? If we have to do some experiments by deleting and adding the application definitions, it will take time for me to do this from the GUI. So wondering if there is a way to do that way.
As to this question. There is no REST interface that we have right now. The only thing you could do is manually edit the system profile xml file. For that you need to a) stop the server b) edit the *.profile.xml file and then c) start the server again
ATTENTION: It is not recommended doing manual edits to the System Profile - but it is an option
Andi
Answer by Andreas G. ·
Hi
Let me answer your questions
a) If you open your System Profile and click on Applications you can see the list of all Application Rules. You also have the ability to define the Priority - that means that we match incoming PurePaths by looking at these rules from top to bottom. Custom Rules also have higher priority than auto-detected ones
b) If you have PurePaths that are "incorrectly" assigned to an application you can go to the PurePath and check the Details of the Entry Point Node - that is typically the node captured on the Web Server or Servlet. In the details you should find the host name and the URL. have a look at these details and see what values there are
Andi
Thx Andi. I have verified on the entry node and i don't see anything related to the pattern which i defined. i have attached screenshots. You can see that it is showing the application as BV - Mobile (i have sent you the defined pattern in the previous screenshot). So not sure how it is identifying them as BV - Mobile. Any idea? is it a Bug?
Well - you have specified "contains" "m.grainger.com" in your rules. So - the screenshot that you added has this as "m.grainger.com" in the host name - therefore it makes sense that this is identified with that application. correct me if I am wrong or attach a session so that I can have a look at it
Where do you see m.grainger.com in the host? that is not m.grainger.com that is different host name. Which screenshot are you referencing?
If I look at screenshot2.png I can see that the host value is ... gcom.grainger.com:8080 - therfore would match the condition "contain" "m.grainger.com"
Andi
So it does match if it contains part of the pattern. So i have to find another pattern then. Ok Let me try few more things then. Thanks Andi.
Andi,
when I define the pattern, it says the pattern is for Uri or adk. Uri does not contain host name right? Ideally it should be using the auto detected rule as it could not find a pattern in the user defined pattern?
The pattern you define actually matches on the FULL URI (including host), e.g: http://www.yoursite.com/shop/catalog.jsp
Every Web Request that comes in will be analyzed against the defined patterns. If you have a custom pattern that matches then this application will be assigned to that PurePath. If no custom pattern matches and you have auto-detect applications turned on we for instance take the host name.
With ADK we mean our Mobile ADK. In this case you do not specify the Pattern in the System Profile but you "code" it into your iOS or Android app. to give you a complete picture we display apps defined using the Mobile ADK in the list of applications as well
hope this makes sense
Yep it makes sense and it is clear now. Thx Andi. Say if i turned off auto detection and whatever i defined is not covering all the traffic, then the "not covered" traffic will be under default application or we won't see that traffic at all? My concern is if i turn off auto detection, i shouldn't be missing any traffic that i used to see with the auto detection on.
Correct. Everything that is not detected by a custom pattern will in that case end up in "Default Application". That makes sure that EVERY PurePath, EVERY Page Action and EVERY Visit will be assigned to an application
Your above statement is true for the existing traffic only or is it true for new traffic. Meaning i turn off auto detection, and if some new traffic comes, that will still be detected and put under default or the traffic won't be detected at all as i turned off auto detection.
If you change rules the changed rules will only be applied to new incoming traffic. So - if you turn off auto-detecdtion and you dont have a rule that matches it will be put into "Default Application"
Thanks. I was worried that if turn off auto detection, new traffic might not be accounted for even under default application. Thanks for clarifying this.
There is traffic from Cassandra which does not have any URI. On the entry node it self it is calling a method. How can we define pattern for these kind of applications. If we cannot define, then do we need to ask the app team to define a webapplicationID in the web.xml? I have attached a screenshot.
Our Application Detection ONLY works on Web Requests right now. For calls that dont start on the Web Server or in the Servlet layer we do not match against any patterns. In this case these requests end up in the "Default Application"
JANUARY 15, 3:00 PM GMT / 10:00 AM ET