From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: linux-trace-users <linux-trace-users@vger.kernel.org>,
Diamon discuss <diamon-discuss@lists.linuxfoundation.org>,
lttng-dev <lttng-dev@lists.lttng.org>,
Philippe Proulx <pproulx@efficios.com>,
tracecompass-dev@eclipse.org,
Doug Cook <dcook@linux.microsoft.com>
Subject: [lttng-dev] Common Trace Format 2 (CTF2) specification and sub-specs
Date: Thu, 27 Jun 2024 15:37:09 -0400 [thread overview]
Message-ID: <13eebb98-ddec-404d-81e6-452915b1b819@efficios.com> (raw)
Hi,
Here is the status of the specification and sub-specifications:
- "CTF2‑SPEC‑2.0: Common Trace Format version 2"
https://diamon.org/ctf/files/CTF2-SPEC-2.0.html
This is the official CTF 2.0 spec. The URL https://diamon.org/ctf
points to the latest version of the Common Trace Format spec.
- "CTF2‑DOCID‑2.0: CTF 2 document identifier format"
https://diamon.org/ctf/files/CTF2-DOCID-2.0.html
The CTF 2 specification refers to it.
- "CTF2-FS-1.0: Layout of a CTF 2 trace stored on a file system"
https://diamon.org/ctf/files/CTF2-FS-1.0.html
This document covers how Babeltrace and Trace Compass
will expect the CTF2 files on the filesystem, and how
Babeltrace and LTTng plan to produce them. This is by
all means an "optional" specification, which means it
is up to the implementation to decide whether they want
to abide by it or not.
Philippe plans to soon release a CTF2-FS-2.0 document with
pretty much the same content as version 1.0, but formatted
following the CTF2‑DOCID‑2.0 specification.
We are planning to add an index of those relevant "optional"
specifications within the CTF2 specification so they can easily
be found.
If we end up having a new storage pattern that end up being
commonly used by implementations, e.g. storing a CTF2 trace
within a binary blob in OpenTelemetry [1], we can always create
a new sub-specification similar to CTF2-FS to cover this.
The following specification files were deprecated by the
time the CTF2 specification was finalized:
- https://diamon.org/ctf/files/CTF2-BASICATTRS-1.0.html
- https://diamon.org/ctf/files/CTF2-PMETA-1.0.html
As always, feedback is welcome!
Thanks,
Mathieu
[1] https://github.com/open-telemetry/opentelemetry-specification/issues/3979
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2024-06-27 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13eebb98-ddec-404d-81e6-452915b1b819@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=beaub@linux.microsoft.com \
--cc=dcook@linux.microsoft.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=pproulx@efficios.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox