Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
A 'device' is a physical entity in the system and is comprised of several resources.
Used in:
The name of the device.
The id of this device, unique in a single trace.
The resources on this device, keyed by resource_id;
Describes a process that appears in the trace.
Used in:
A 'resource' generally is a specific computation component on a device. These can range from threads on CPUs to specific arithmetic units on hardware devices.
Used in:
The name of the resource.
The id of the resource. Unique within a device.
Describes a thread that appears in the trace.
Used in:
A 'Trace' contains metadata for the individual traces of a system.
The devices that this trace has information about. Maps from device_id to more data about the specific device.
All trace events capturing in the profiling period.
The root response message representing a delta-compressed trace.
Sequence of standard duration events.
Sequence of asynchronous events.
Trace metadata describing the hierarchy of processes and threads.
A centralized list of strings used throughout the trace data. `name_ref` fields in other messages are indices into this array.
Details for the trace (e.g., flags for the frontend).
The full timespan of the trace (start time and end time in picoseconds).
Used in:
The id of the device that this event occurred on. The full dataset should have this device present in the Trace object.
The id of the resource that this event occurred on. The full dataset should have this resource present in the Device object of the Trace object. A resource_id is unique on a specific device, but not necessarily within the trace.
The name of this trace event.
The timestamp that this event occurred at (in picos since tracing started).
The duration of the event in picoseconds if applicable. Events without duration are called instant events.
Extra arguments that will be displayed in trace view.
Metadata for a specific occurrence of a trace event. This contains optional fields that are not present on every event.
Used in:
A value associated with the event (e.g., for counter events).
Represents a sequence of trace events, grouped by their metadata (e.g., same process, thread, and name). To save space, the timestamps are delta-encoded.
Used in:
Delta-encoded start timestamps of the events. The first element is the absolute start timestamp of the first event. Subsequent elements are the time differences from the previous event's timestamp.
The durations of each event in the series. The length of this array should match the length of `deltas`.
Optional name references for individual events within this series, pointing to indices in `interned_strings`. Used if events in the series have different names.
Metadata for the events in this series.
Metadata identifying a unique series of trace events. A series is typically defined by the process, thread, and the name of the events it contains.
Used in:
Contains all metadata relating to the processes and threads in the trace.
Used in: