PurePath Comparison - select columns not showing
I spent alot of effort to bring up a purepath comparison with selected sessions via webstart only to find out that I can't figure out how to get selected columns to show in the comparison call tree panel.
The problem is we work in the Dev environment and they focus almost exlusively on CPU, however the CPU columns are not shown by default. When I try to show CPU columns, they will show in the "source" call tree panel, but not in the "compare" panel. When I right click on the column headers in the "compare" panel and check CPU they show up in the "source" panel, but not the "compare" panel (see screenshot).
This is very fustrating as it makes all the work I did in the app to lauch webstart with the purepath comapre dashlet mostly useless plus it was a feature we were very much interested in addind to our other app.
Is there some workaround or tweak I can do to have them show in both panels? We use a custom dashboard (really just a copy of the purepath compare dashlet), so if I need to hard code some config paramaters so only those columns are shown - that would be fine as long as I can get CPU to show.
We are mostly on ver. 4.1, but I see this in 5.0 as well.
Hi
I can confirm that this is also still the case with 5.5
I've forwarded this to engineering already and will create an internal bug for it. I will see if there is a workaround
Andi
Thanks Andreas
Hi Dean,
In 5.5, the "Table" drop down has four total options:
The ones that map to these two tables are the "PurePath Execution Tree" options. By default, the left side pane PP execution tree table is selected. If you want to have the CPU metrics in BOTH the left and right side, you will need to make the selection for both the "PurePath Execution Tree" Tables.
Here is a screen shot where your requirements are shown:
You can click on the "save as default" option shown in the first screenshot. This will save these headers to your client configs.
I just gave it a try and that looks like it did the trick - thanks Bill!
Thanks - its not intuitive - but good to know it works. I will still follow up with R&D about this
