barectf rust parser crate available

[jonlamb-gh]

Hi there, this isn't an issue, just wanted to share a new rust crate I've put together to parse barectf-generated CTF streams.

https://crates.io/crates/barectf-parser

It's definitely not intended to be as feature-rich as babeltrace, but it may be helpful for folks who are trying to make bespoke collection tools like myself. For example, I'm working on an embedded system with an RTT barectf platform impl where logical components/apps have their own stream class and all the packets funnel down the same channel (pulled off target via a debug probe).

[eepp]

Nice!

I'm curious about this, but the repository doesn't seem to exist?

This one: https://github.com/auxoncorp/barectf-parser

[jonlamb-gh]

Sorry about that! Forgot to flip the public switch. Should be visible now.

[eepp]

Thanks.

So if I understand correctly, it's essentially a CTF data stream reader using a barectf effective YAML configuration as metadata instead of the generated TSDL file.

I'll try to find a spot to refer to your project, probably where I mention other consumers.

You should know that we published a new, backward-compatible (at the data stream level) major version of CTF almost a year ago.

The latest Babeltrace release, as well as the next LTTng one (experimentally for this one) support it. barectf doesn't generate CTF 2 yet.

It's of interest to you because the metadata format is plain JSON (well, almost, it's actually JSON text sequence to allow streaming), therefore you could eventually transform your barectf-specific reader into a full CTF 2 reader which could read the output or any compliant CTF 2 producer. I'm sure you could reuse a lot of code.

[jonlamb-gh]

So if I understand correctly, it's essentially a CTF data stream reader using a barectf effective YAML configuration as metadata instead of the generated TSDL file.

Yep, exactly.

I'll try to find a spot to refer to your project, probably where I mention other consumers.

Thanks!

You should know that we published a new, backward-compatible (at the data stream level) major version of CTF almost a year ago.

I've been following along with those developments and definitely agree, that'll be a pretty smooth transition.