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

Does application detection URL rule look into the query parameters ?

Hi guys,

Customer applications are spitted by URL query parameter (.i.e

Can we catch this parameter with URL detection rule in order to split the applications?

If that will work the other question will be if parameters are masked , will the rule be still use able ?



All parts of url should be considered, but rule based on query will work only for urls that has this parameter visible. All other session will be assigned to default application.

Other option may be adding JS variable to application and define session property based on this (it can be based on css selectors, meta tag, cookie as well. In such cases you will have single application for all your apps but using USQL you will be able to make charts for each of applications separately based on those properties.


Thanks @sebastian k. for the detailed explanation !