1 of 1 people found this helpful
The very detailed data inside a TrueLog would be difficult to extract. TrueLogs can be quite large as they contain most of the data exchanged between the client (the replay engine) and the server as the transaction ran. For that reason they are only stored if there was an error.
DNS lookup time and other low level times, as a proportion of overall time, is in the detailed page timers. By default, the detailed timers are not captured for Workbench scripts but are captured for URL checkers. Be aware that enabling detailed page timers will triple the amount of data that has to be processed putting an extra load on TM ART Central and on the supporting database. Use them judiciously.
And lastly, if DNS is something you particularly want to know, it would be significantly less effort for you to write a script to do DNS lookups than it would be build a general parser for TrueLogs.
Hal thanks for the reply and insight. My interest in wanting to extract the data came from a comparison the customer brought to us with regards to another product that offered this information, although it was no more than what was available in TM ART directly. Obviously, with the integration capabilities available and currently utilized with BPPM (currently they have both products and integrated), the option to see information and have events contain this information would be useful to some degree, but we have instructed the customer to use the TM ART interface to review and sort through this information.
The interest in DNS information was for response time, not nslookup values, but again this is available in TM ART Central. Overall I was interested in how/what others were doing with available data in TM ART and results from transactions and what all would be involved.