Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I was wondering if you can use REGEX for matching the HTTP parameter existance. I can't ready anywhere something about it yet it seems like you can only use regex at checking the parameter value.
The link is '/pages/cases?162-1.IBehaviorListener.0-caseOverviewForm-caseOverviewResultPanel-casesBody-cases-1-specialAttentionCell' where '162-1.IBehaviorListener.0-caseOverviewForm-caseOverviewResultPanel-casesBody-cases-1-specialAttentionCell' ' is the parameter with no value. The tricky thing is that the parameter changes the number with each case.
So the example link looks like this
So I figured I'll do this through REGEX with: \d.*(-1.IBehaviorListener.0-caseOverviewForm-caseOverviewResultPanel-casesBody-cases-)\d.*(-specialAttentionCell)
That however doesn't work?
Any tips or tricks?
So is the problem statement that you want a BT for HTTP requests that hit the /pages/cases URL ONLY if a parameter of the form you provided exists?
Thats exactly what I want. To clarify it even more.
The url /pages/cases is a business transaction already. I however need to monitor one extra substep that falls under the .pages/cases link. The thing that makes the transaction unique is the HTTP parameter as provided above. The crux is that http parameter can change depending on which case you open. So if I tell Appdynamics to check specifically for the the parameter above It'll only do it for that specific case. so the specific parameter needs to be filtered to a general parameter.
I have not tested, but you could try a rule which matches /pages/cases and configure the following split:
Apply a custom expression on HTPServletRequest
If my regex-fu is right, this will result in 2 BTs called name.true and name.false where name.true is the class of BT you're trying to get at
Just getting back to you. The solution did work however not the way you explained. I've changed the regex expression and right now a transaction wil get the name of the custom rule as soon as the regex matches. Not getting back any boolean. This kind of acts as I wanted (sometimes the results still are weird though. Could be the regex).
Anyways is there any kind of feature coming in the future for performing regex on http parameters names?
Thanks for the solution