From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [lttng-dev] Tracing Summit 2023 Announcement and CFP
Date: Mon, 15 May 2023 15:20:56 -0400 [thread overview]
Message-ID: <cf6c44a7-70e3-edfd-d728-11cd03b8a91e@efficios.com> (raw)
Hello all!
This is a Call for Proposals for the Tracing Summit 2023[0] which will be held in Bilbao,
Spain on the 17th and 18th of September, 2023. This year, the event is co-located with
Open Source Summit Europe 2023 [1].
- Event dates: Sunday, September 17th - Monday, September 18th
- Location: Bilbao, Spain and virtually (co-located with Open Source Summit Europe)
- Registration cost
- In person: $80.00 USD (Free for speakers)
- Virtual: Free
- Call for proposals link: [2]
Important dates:
- Call for proposals close: Friday, June 16th, at 11:59PM EDT
- Call for proposals notifications: Friday, June 23rd
- Schedule announcement: Tuesday, June 27th
- Event dates: Sunday, September 17th - Monday, September 18th
Stand-alone registration is expected to open next week. In the meantime, you can subscribe
to the mailing list to get the latest information on the event: [3]
The 2023 Tracing Summit is a two-day, single-track conference on the topic of tracing. The
event focuses on software and hardware tracing, gathering developers and end-users of tracing
and trace analysis tools. The main goal of the Tracing Summit is to provide space for
discussion between people of the various areas that benefit from tracing, namely parallel,
distributed and/or real-time systems, as well as kernel development.
We are welcoming 30 minute presentations from both end users and developers, on topics
covering, but not limited to:
- Investigation workflow of real-time, latency, and throughput issues,
- Trace collection and extraction,
- Trace filtering,
- Trace aggregation,
- Trace formats,
- Tracing multi-core systems,
- Trace abstraction,
- Trace modeling,
- Automated trace analysis (e.g. dependency analysis),
- Tracing large clusters and distributed systems,
- Hardware-level tracing (e.g. DSP, GPU, bare-metal),
- Trace visualization,
- Interaction between debugging and tracing,
- Tracing remote control,
- Analysis of large trace datasets,
- Cloud trace collection and analysis,
- Integration between trace tools,
- Live tracing & monitoring,
- Dynamic instrumentation,
- Programmable tracing (e.g. eBPF).
Talks can cover recently available technologies, ongoing work, and yet non-existing
technologies (that are compelling to end-users). Talks covering interesting or challenging
tracing use cases are also welcome as they can reveal future directions or tooling needs.
Please understand that this open forum is not the proper place to present sales or marketing
pitches, nor technologies which are prevented from being freely used in open source.
Please send any questions about this conference to <info@tracingsummit.org>.
This event is organized by EfficiOS on behalf of the Linux Foundation Diagnostic and
Monitoring Workgroup [4].
The organizers of this event are Mathieu Desnoyers (EfficiOS), Erica Bugden (EfficiOS)
and Olivier Dion (EfficiOS).
[0]: https://tracingsummit.org
[1]: https://events.linuxfoundation.org/open-source-summit-europe/
[2]: https://cfp.tracingsummit.org/ts2023/cfp
[3]: https://eepurl.com/goakfv
[4]: https://diamon.org/
--
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:[~2023-05-15 19:20 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=cf6c44a7-70e3-edfd-d728-11cd03b8a91e@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=info@tracingsummit.org \
--cc=mathieu.desnoyers@efficios.com \
/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