theia-trace-extension

theia-trace-extension copied to clipboard

Specify data required for Views

3

Currently, the UI doesn't show data requirements for views. So, it's not possible to determine what kinds of traces (ex. kernel and/or userspace) and what events (ex. sched switch) are...

ebugden

e.g. Improve chart titles and descriptions As a user I need to be able to view **descriptive** yet **concise** analysis titles, axis labels, legends and units clearly labeled, so that:...

ebugden

Open some default views when a trace is opened

3

Opening a couple views that go from high-level to low-level has several benefits for users: * Quick feedback when I open a file (indicates that open trace was successful) *...

ebugden

As someone who traces repeatedly, I need a quick way to discover new trace data, and load it when it’s ready, so I can get started with a new analysis....

ebugden

All chart types need to be able to handle typically sized traces (ex. 1 G) without struggling. Without this, we can’t call the product viable. Currently the XY charts can’t...

ebugden

Sometimes interesting, but most often take up a lot of vertical space

ebugden

ebugden

Leftmost columns should contain the most useful data. A user survey respondent proposed that the following fields were the most useful: timestamp, tid, pid, cpu, event type and content

ebugden

Text matching search doesn’t make sense for timestamps.

ebugden

Allow filtering out all events that don’t match the search criteria.

ebugden