From: Philippe Proulx <pproulx@efficios.com>
To: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>
Cc: lttng-dev <lttng-dev@lists.lttng.org>,
tracecompass-dev <tracecompass-dev@eclipse.org>
Subject: [diamon-discuss] CTF2-SPECRC-1.0: Common Trace Format version 2 release candidate
Date: Thu, 25 Nov 2021 14:18:36 -0500 (EST) [thread overview]
Message-ID: <2054450980.2273.1637867916015.JavaMail.zimbra@efficios.com> (raw)
Hello,
Today we're releasing the first release candidate of the Common Trace
Format version 2 specification.
This document, named CTF2-SPECRC-1.0, is available here:
<https://diamon.org/ctf/files/CTF2-SPECRC-1.0.html>
To write CTF2-SPECRC-1.0, many parts of CTF2-PROP-2.0rA [1] were
modified to make the text more easily understood and to formalize some
procedures. I also added a few diagrams to help understand the binary
layout of some fields.
Moreover, the metadata stream and auxiliary streams are now JSON text
sequences [2] instead of a single JSON array/object. This makes decoding
a streamed version of such input easier using any JSON parser, for
example to meet the needs of use cases similar to LTTng live [3].
Feel free to provide feedback!
Philippe Proulx
EfficiOS Inc.
https://efficios.com/
[1]: https://diamon.org/ctf/files/CTF2-PROP-2.0rA.html
[2]: https://datatracker.ietf.org/doc/html/rfc7464
[3]: https://lttng.org/docs/#doc-lttng-live
WARNING: multiple messages have this Message-ID (diff)
From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org>
To: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>
Cc: lttng-dev <lttng-dev@lists.lttng.org>,
tracecompass-dev <tracecompass-dev@eclipse.org>
Subject: [lttng-dev] CTF2-SPECRC-1.0: Common Trace Format version 2 release candidate
Date: Thu, 25 Nov 2021 14:18:36 -0500 (EST) [thread overview]
Message-ID: <2054450980.2273.1637867916015.JavaMail.zimbra@efficios.com> (raw)
Hello,
Today we're releasing the first release candidate of the Common Trace
Format version 2 specification.
This document, named CTF2-SPECRC-1.0, is available here:
<https://diamon.org/ctf/files/CTF2-SPECRC-1.0.html>
To write CTF2-SPECRC-1.0, many parts of CTF2-PROP-2.0rA [1] were
modified to make the text more easily understood and to formalize some
procedures. I also added a few diagrams to help understand the binary
layout of some fields.
Moreover, the metadata stream and auxiliary streams are now JSON text
sequences [2] instead of a single JSON array/object. This makes decoding
a streamed version of such input easier using any JSON parser, for
example to meet the needs of use cases similar to LTTng live [3].
Feel free to provide feedback!
Philippe Proulx
EfficiOS Inc.
https://efficios.com/
[1]: https://diamon.org/ctf/files/CTF2-PROP-2.0rA.html
[2]: https://datatracker.ietf.org/doc/html/rfc7464
[3]: https://lttng.org/docs/#doc-lttng-live
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2021-11-25 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 19:18 Philippe Proulx [this message]
2021-11-25 19:18 ` [lttng-dev] CTF2-SPECRC-1.0: Common Trace Format version 2 release candidate Philippe Proulx via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2054450980.2273.1637867916015.JavaMail.zimbra@efficios.com \
--to=pproulx@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=lttng-dev@lists.lttng.org \
--cc=tracecompass-dev@eclipse.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.