BABELTRACE2-QUERY-(7)

📦
version 2.1.2 · 6 versions
, in fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

✨ BABELTRACE2-QUERY-(7) ✨

okay so bestie, we're in the Babeltrace 2 manual and this page is literally all about one lil query object 💅 buckle up

🌸 NAME 🌸

babeltrace2-query-babeltrace.trace-infos — Babeltrace 2: Trace infos query object

💖 DESCRIPTION 💖

The babeltrace.trace-infos Babeltrace 2 query object is the one that spills the tea about time range info for specific traces and their streams 🫖✨ It also tells you which output ports of an eventual source component will be the ones serving up the messages for a given stream.

And babeltrace2-convert(1) is obsessed with it — it queries this object from all the source component classes so it can support the --stream-intersection feature. no cap 💅

🎀 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. literally identical, matching, twin energy 👯‍♀️

👑 RESULT OBJECT 👑

The result object is an array of trace info maps (peep the “Trace info map” section below, iykyk).

🦋 Trace info map 🦋

A trace info map contains:

  • stream-infos=STREAM-INFOS [array of stream info maps] — Stream info maps (go look at “Stream info map” below) for this trace.

🌈 Stream info map 🌈

A stream info map contains:

  • range-ns=RANGE [range map] — The time range of this stream, and it's a map containing:
    • begin=NS [signed integer] — Beginning time of this stream (nanoseconds since the origin of the default clock class of the stream class).
    • end=NS [signed integer] — End time of this stream (nanoseconds since the origin of the default clock class of the stream class).
  • port-name=PORT-NAME [string] — For an eventual source component initialized with the same parameters: the 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. (yes, we're counting, and yes, they ate 🔥)

- 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>). don't suffer in silence bestie, tell them 🫶

🧚 RESOURCES 🧚

The Babeltrace project shares some communication channels with the LTTng project (see <https://lttng.org/>). community coded, community approved ✨

🍓 AUTHORS 🍓

The Babeltrace 2 project is the result of hard work by many regular developers and occasional contributors. every single one of them, iconic 👑

The current project maintainer is Jérémie Galarneau <mailto:jeremie.galarneau@efficios.com>.

This query object is part of the Babeltrace 2 project.

Babeltrace is distributed under the MIT license (see <https://opensource.org/licenses/MIT>).

🌟 SEE ALSO 🌟

babeltrace2-intro(7), babeltrace2-query(1), babeltrace2-convert(1)

and that's the whole page, bestie 💅 this was the Babeltrace 2.1.2 version, dated 14 September 2019 — go forth and query, main character 🦋✨

📦 where this page comes from