►
From YouTube: Diagnostics WG meeting 2022 June 28
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Nope,
no,
I
must
say:
okay,
if
not
we'll,
follow
the
standard
practice
of
following
the
agenda
listed
in
issue
number
566
and
there
are
a
bunch
of
those
I'm
thinking
that
some
of
these
things
would
have
been
discussed
in
the
past.
But
let's
just
run
through
those
first
one
is
554,
re-evaluate,
trace,
gc.
B
C
I
think
that's
first
time
to
talk
about
how
could
I
include
the
stuff
that
I
made
in
the
existing
documentation,
but
also
with
discrete
english
rapha.
I
figured
out
that
maybe
it
would
be
more
interesting
for
the
group
if
I
could
evolve
more
time
into
cpu
profile,
stuff
or
memory
excessive
memory
consumption,
something
like
that
that
it
could
be
more
interesting
and
I'll
lie.
B
Yeah,
I
think
that
your
work
was
amazing
and
you
can
just
add
it
to
the
gc
traces
like
merge
your
I.
C
But,
okay,
because
I
think
that
I
was
to
study
which
part
I
could
extract
and
also
like.
I
have
a
limited
amount
of
time,
I'm
trying
to
just
figure
out
how
we
can
improve,
but
yeah.
I
will
keep
it
anywhere.
We
will
keep
it
a
choice
of
that
work
and
today
I
I
just
drop
a
video
for
my
french
audience
and
I
reuse
the
stuff
that
I
learned
here.
So
nothing
laws
already
all
all
these
transform
so
but
yeah
okay.
C
B
Yeah
I
mean
the
the
document
that
I
posted
here
in
the
chat
is
like
using
gc
traces
to
to
track
memory
and
you're
in
the
diagnostic
memory
documentation.
I
think
that
your
work
you
can
mix
like
fill
the
gaps
in
this
document
with
your
your
work.
C
B
So
then
you
have,
you
will
end
up
with
a
complete
document
and
also
I
would
like
to
mention
that
the
memory
is
the
only
the
only
set
of
documentation
that
is
completed
so
yeah.
I.
B
C
C
C
B
B
Yeah
I
mean
I
am
considering
to
do
it
like
we
need
like
to
discuss
with
other
folks
as
well,
but
I
I
considering
to
do
it
because
the
memory
is
a
complete
document
that
we
haven't
diagnosed,
but
if
we
keep
it
there
for
a
long
time
it
will
be
out
of
date
sun.
So
we
need
yeah.
B
Yeah
really,
what
do
you
think
jewish.
A
A
So
I
can't
trace
back
in
the
history
and
definitely
the
main
thing
that
you
said
is
the
documentation
itself
can
go
stale
after
some
point
of
time,
so
the
first
thing
would
be
to
get
it
out
and,
and
probably
who
knows
validating
that
in
public
can
get
us
better
experience,
and
that
would
help
us
to
document
the
other
things
in
a
much
better
way.
We
don't
know.
B
B
The
memory
the
memory
set
of
the
commands
is
done,
so
I
think
we
can
move
it
to
node.jsorg.
B
Cc
node.js
web
we
have
a
just
org
team
website
or
something.
A
B
Do
you
know
if
we
have
in
the
things
in
the
node.js?
We
have
a
specific
thing
to
tag
regarding
like
where
it
should
be
placed.
B
Yeah,
but
we
have
a
website
here.
I
cannot
find
it
yeah.
C
Yeah
yeah
and
I
think
that
it
will.
It
will
be
the
first
thing
that
I
will
work
on
after
this
meeting
this
night
or
tomorrow
just
merge
it.
Then
we
could
work
on
the
the
command
that
you
put
on
issue
501
or
zero
o2
yeah.
B
A
C
C
B
B
Okay,
the
ll,
the
lt
tng
yeah
this
one.
I
never
played
with
these
two
honestly.
B
C
So
I
think
that
when
the
output
of
the
pass
meeting
was
to
say
it's
not
because
we
don't
have
a
tool,
that
is
him,
but
he
can,
he
cannot
become
go
back.
I
mean
what
I
can
say.
If
we
get
rid
of
that
tools
from
the
list,
we
could
report
it
one
day.
Okay,
it's
just
to
give
a
kind
of
state
about
the
current
tools
that
are
commonly
used
more
than
just
say
all.
We
have
all
the
tools
in
this
table.
B
C
A
B
Yeah,
I
also
I
have
asked
because
a
near
forum
has
a
blog
post
about
lttng
like
four
or
five
years
ago,
and
I
asked
ed
matio
about
that.
So
if
this
is
still
watching,
you
know
js,
he
told
my.
He
told
me
that
he
don't
think
so
and
also
it's
like
it's
kind,
useless
right
now
in
2022.
B
C
B
Played
it
pretty
similar
to
the
trace,
so
usually
it
works
only
on
solaris
operational
season
operation
system,
and
I
not
I
I
mean
I
have
played
with
it
a
long
time
ago
and
currently
I'm
not
I'm
not.
B
B
B
C
C
B
You
can
create
if
you
have
to
remove
both
both
at
the
same
time,
by
the
way
and
and
then,
if
someone
play
with
it
likely,
they
will
show
up.
Okay,.
C
B
Yeah
next
one
is
the
0x
right
all
right.
I
love
that
one
yeah
0x
is
still.
I
think
I
personally,
I
have
upgraded
0x
to
support
node
16
and
above
where
the
node
semicolon
prefix.
B
A
B
Yeah,
I
think
that
it
falls
in
the
same
as
know
the
clinic.
Now
the
clinic
provides
a
few.
A
B
B
C
B
B
C
B
A
A
Open
source
monitoring
solution
from
ibm,
I
mean
ibm,
took
the
initiative,
but
though
it's
an
open
source
community
project,
it
requires
monkey
patching
at
the
application
level
or
you
could
require
the
module
and
then
do
the
define
the
metrics
by
yourself
and
export.
It
has
exporters
for
prometheus
and
other
open,
telemetry
stuff.
A
So,
with
respect
to
the
maintenance
status
or
any
decisions
michael,
doesn't,
would
be
able
to
precisely
tell
it,
because
definitely
this
is
this-
is
led
by
ibm
team,
so
he
would
have
for
standard
information.
So
I
think
that
the
approach
you
took
for
etw
and
system
type
kind
of
thing
can
be
taken.
You
can
tag
michael
dozen
to
get
the
precise
information.
A
B
I
I
I
am
currently
raising
a
new
issue
in
the
diagnostic
channel
diagnostic
group,
just
like
to
include
the
link
for
each
two
in
the
support
to
your
list,
because
sometimes
then
the
the
name
is
pretty
similar
to
other
two.
In
other
another
platform.
B
B
B
Three
years
ago,
I
remember
that
we
have
discussed
about
it
mary
that
brought
this
this
issue
to
us.
B
C
B
C
C
B
Level
five
or
something
like
that,
I
suggest
to
let
it
open
for
just
two
more
weeks,
so
I
can
take
a
look
on
that
because
I
use
it
a
lot
currently,
so
I
definitely
interested
in
supporting
it.
So
let
me
just
take
a
look
on
that
see
if
this
is
currently
supported
or
not
and
then
next
meeting
I
can
show
up
with
a
few
with
information
about
that.
If
we
need
to
close,
if
we
need
to
move
the
tier
or
not,
what
do
you
think.
C
B
C
B
Because
just
to
to
keep
tracking
the
how
we
can
move
it
to
node.js,
or
at
least
the
memory
one.
A
A
C
Just
a
question:
this
is
just
an
idea
like
that,
but
we
have
the
node.js
documentation
and
it's
okay.
We
want
to
put
guys
there,
but
maybe
it
could
be
a
good
idea
just
to
discuss
about
this
idea
of
having
our
own
website
or
something
like
that
dedicated
to
diagnostic
and
put
all
the
stuff
that
we
have
here.
B
Yeah,
I
think
that
is
this
is
difficult
to
make.
I
mean.
Currently,
we
have
several
guides
in
the
node.js
itself
documentation,
so
we
have
guides
to
to
create
http
server
to
to
manage
memory
late.
Currently,
we
have
a
ways
to
to
profiling
our
application
in
the
current
guides.
So
I
think
that
the
memory
just
fits
there.
I
mean
we
can't
definitely
think
about
a
new
website
for
that,
but
I
think
that
it
would
be
a
difficult
path
to
like.
Everyone
agree
on.