NAME
babeltrace2-query-babeltrace.trace-infos - Babeltrace 2's trace infos query objectDESCRIPTION
The babeltrace.trace-infos Babeltrace 2 query object indicates time range information about specific traces and their streams, and which output ports of an eventual source component will serve the messages for a given stream.PARAMETERS
The parameters for this query operation are exactly the same as you would pass as the initialization parameters of a component created from the queried component class.RESULT OBJECT
The result object is an array of trace info maps (see “Trace info map”).Trace info map
A trace info map contains: stream-infos=STREAM-INFOS [array of stream info maps]Stream info maps (see “Stream info
map”) for this trace.
Stream info map
A stream info map contains: range-ns=RANGE [range map]The time range of this stream, a map
containing:
begin=NS [signed integer]
port-name=PORT-NAME [string]
Beginning time of this stream (nanoseconds
since the stream class’s default clock class’s origin).
end=NS [signed integer]
End time of this stream (nanoseconds since the
stream class’s default clock class’s origin).
For an eventual source component initialized
with the same parameters: name of the output port which serves the messages of
this stream.
EXAMPLES
Result object
Example 1. Two trace infos: one with three stream infos, one with two stream infos.- stream-infos: - range-ns: begin: 1509556764975082000 end: 1509557102181554400 port-name: trace0-cpu0 - range-ns: begin: 1509556764947050800 end: 1509557102182771000 port-name: trace0-cpu1 - range-ns: begin: 1509556764956409300 end: 1509557102182770400 port-name: trace0-cpu2 - stream-infos: - range-ns: begin: 1509556764918082000 end: 1509557103849928400 port-name: trace1-cpu0 - range-ns: begin: 1509556761888820000 end: 1509557109928100400 port-name: trace1-cpu1
BUGS
If you encounter any issue or usability problem, please report it on the Babeltrace bug tracker (see <https://bugs.lttng.org/projects/babeltrace>).RESOURCES
The Babeltrace project shares some communication channels with the LTTng project (see <https://lttng.org/>).•Babeltrace website (see
<https://babeltrace.org/>)
•Mailing list (see
<https://lists.lttng.org>) for support and development:
[email protected]
•IRC channel (see
<irc://irc.oftc.net/lttng>): #lttng on irc.oftc.net
•Bug tracker (see
<https://bugs.lttng.org/projects/babeltrace>)
•Git repository (see
<https://git.efficios.com/?p=babeltrace.git>)
•GitHub project (see
<https://github.com/efficios/babeltrace>)
•Continuous integration (see
<https://ci.lttng.org/view/Babeltrace/>)
•Code review (see
<https://review.lttng.org/q/project:babeltrace>)
AUTHORS
The Babeltrace 2 project is the result of hard work by many regular developers and occasional contributors.COPYRIGHT
This query object is part of the Babeltrace 2 project.SEE ALSO
babeltrace2-intro(7), babeltrace2-query(1), babeltrace2-convert(1)14 September 2019 | Babeltrace 2.0.4 |