Setting Up HP BAC and AppManager monitors as syntethic visits.
Hi,
I was wondering, for a current large customer if is possible to define some "well know transactions" (actually HP BAC and AppManager scripts/gets/posts) as Synthetic Transactions (or robot style in Transaction Flow)?
Based on headers, or any arguments found, perhaps it would be possible to define these as synthetic, just like the ones from Gomez, and we can see the difference between real and monitor visits there.
Also, there are some users which identify the synthetic transactions as well, but a split or filter for 4 or 5 users does not seem practical, any thoughts?
Thanks in advance for reading through,
Carlos.
Hi Carlos
In your case it makes sense that you either define your own "Synthetic Request" BT or extend the out-of-the-box Busineses Transaction that comes with a new System Profile by adding additional Filter Measures. You have to create several Filter Measures for each of your identified HTTP-Headers, Parameters or Users - there is no other "built-in" way
Andi
Thanks a lot Andreas,
I already have BTs with Filters based on user (through LOGON USER server variable).
So I can count on the synthetic transactions/BT on synt transactions, is there anything else required to show their "visits" as synthetic transactions/robots on Transaction Flow? Of course, it would be ideal! =)
Thanks again,
Carlos.
Hi Carlos,
If you can modify the transactions then you could just add the x-dynaTrace header (details here - Integration with Web Load Testing and Monitoring Tools#IntegrationwithWebLoadTesting). That way they would be separate in the transaction flow...
Best, Roman
Excellent Roman!
Thanks for the tip, I was missing that "part of reality"...
I'll work on that and comment within 48 hours for sure.
Best,
Carlos.
Hi,
Customer had mostly LoadRunner scripts, so it was just simple as loading the scripts, use the Converter, path them with a single click and that's it, we have synthetic transactions ready!
Working fine!
