UI suggestions

[gbanksy]

Help > About:

• correct the version and year (1.3.x, 2015)
• Link to github should be added - https://github.com/tslater2006/Trace-Wizard
• include a 'how to' screenshot of the suggested trace values on login page and Trace PeopleCode/SQL pages (or the text of them like you have on github)

Execution Path:

• new option - View > Unfold all
• new option - View > Unfold all (like Notepad++ does for XML)
• new option - View > Drill down to slowest part
• new option - Right click on a line to load the actual trace file at that part in Notepad++
• new option - Right click on a line to select the app package/peoplecode object so you can open up app designer on the object (similar to Copy Stack Trace)

Finally, I loaded up a trace of searching the HCM Company Directory for an employee, and the trace doesn't show where the delay is (other than it's in PTSF_ES_ESINPL.JsonService taking 4.8s) - I'm guessing it's within IB but not sure how your tool could help with these third party calls (like calling cobol, app engine, etc via PeopleCode)

[tslater2006]

Hey thanks for the suggestions here. I'll get the Help -> About pieces fixed for sure.

For the execution path changes, I have some concerns over a thing like View -> Unfold All, especially with large traces (we had someone recently load a 5GB trace into Trace Wizard). Perhaps a warning first and then if they proceed the outcome is on them.

I like the idea of a "drill down to slowest", I'd imagine that is just a "find the slowest call and take me to it"?

The right click -> Select app pacakge/PPC object is a great idea, I would imagine you mean to navigate the user to that node on the PPC Objects tab, vs putting something on the clipboard?

My biggest concern and not something I think i'm prepared to add to Trace Wizard is the ability to open a trace file to a specific line with Notepad++. My concern here is a few things

1. I like it being a self contained application
2. Not everyone would have Notepad++
3. Not everyone would have Notepad++ on their path (which means TraceWizard would have to know where it was located)
4. Not sure Notepad++ supports opening a file to a specific line

With that said, it might be interesting to implement a file view directly in Trace Wizard from which I could open the trace file to a specific line. And obviously this wouldn't be allowed if you opened a twiz file instead (since there is not trace file in that case).

[tslater2006]

[gbanksy]

wow that was quick!

"* new option - View > Unfold all" is meant to say "* new option - View > Fold all"

"The right click -> Select app package/object" what I mean is if I am interested in viewing the PeopleCode that is slow, right now I would, in App Designer do File > Open > select object type and then type in the app package (or record or component) name. Just trying to be lazy and not have to type the object name.

"notepad++ integration" - you could put under edit > settings a text editor field that I could save "c:\Program Files\Notepad++\notepad++.exe %1 -n%2" into, or how about just displaying the line number down the bottom / on the right click like "Copy stack trace" so I can do it manually

"I like the idea of a "drill down to slowest", I'd imagine that is just a "find the slowest call and take me to it"? - exactly

New ones:

• Edit > Find to bring up the dialog (I found it via Ctrl-F)
• Show filename in the title bar
• Some more stats on the Execution Path (e.g. number of paths found, total duration of log, number of lines, longest step)
• Only show me execution paths that took longer than X seconds?

[tslater2006]

@gbanksy

and the trace doesn't show where the delay is (other than it's in PTSF_ES_ESINPL.JsonService taking 4.8s)

This is exactly where the slowness is :) PTSF_ES_ESIMPL:JsonService is the app class that is used to actually query a search index from Elastic. So it would appear that the query took 4.8s to run. That seems to imply the search index itself is slow and should be the target for any optimization work.