Creating Offline BT from Offline Session
Hi All,
I am using DT 6.0.0.7000 and since my customer does not has much storage available i have exported a session to analise data later.
This Session that I have exported I loaded in another DT client as offline session.
Since I do not have a BT ready to see some data, I decided to create one based on my Offline session. The problem is that it does not work.
I mean, when trying to create it by going to system profile->BT -> Create, nothing happens.
Even if I go to the web request desired and, from that web request, create a BT and it does not work either.
Is this an expected behavior ?
Can´t I create a BT from an offline session?
It sounds like your client has some kind of bug? I'd try reinstalling the client to see if that helps.
But to answer your question, yes, you are able to create BTs and test them in an Offline session. Once you get around to creating the BT you have to right click on the session and "Process Configuration Changes" in order to test things out.
Thanks Thomas.
Do you use the same client version?
Also I have tried doing that in two different desktops.
The first, I could create the BT, but after applying "Process Configuration Changes", my BT does not show nothing (which is a split by client ip web request).
In the second deskop I could not even create the BT.
I will try uninstall and install again and see.
Thanks.
My customer is in the process of upgrading to 6.1 so I tested the offline BT on both 6.0.0.7014 (custom fixpack) and 6.1.0.7880. Both worked as expected.
For the first time you created the BT and processed the changes, do you mean the BT was still there but no splitting/values were showing? Could it be possible that the BT was configured in a way where nothing was filtered into it?
Community Member of the Month
September 2018
Announcing Dynatrace's Community Member of the Month for September 2018, Muthu P.! Click here to read more! Employee Member of the Month
September 2018
Announcing Dynatrace's Employee Member of the Month for September 2018, Kris Z.! Click here to read more! 