Web Requests - Null Parameter Values
Hello,
Customer is extracting a value from a Web Request parameter (e.g. UserID=123456). Customer claims that some web requests occasionally do not have an assigned value.
Will the purepaths for the transactions that have a null parameter value still be visible as their own split in the business transaction?
Thanks,
Joel B
Unfortunately not, we are experiencing this at my customer right now. There is an RFE to allow null values through here: Possibility to have null splitting values in business transactions
Thanks, Rick...
Follow up question:
Do you know if I look at the details of the purepath in the call tree, where I usually see "UserID=12345", if the parameter was null, would it still show up as USERID=&NEXTPARAM? (Does that make sense?)
Depends. The parameter can be null as in "UserID=" (in this case you will see what you say there), or null as in doesn't exist for that request, in which case you won't see anything.
You could try to setup a filter with "not regex" and try something like ".+".
That would in theory only let purepaths through that didn't contain any username.
I guess contains "" would do the same thing but I don't think I'm answering your question :/
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 