►
From YouTube: Diagnostics WG meeting 2019-07-03
Description
A
Guess
I
need
to
close
the
little
bit
all
right,
yeah!
Well,
stop
anyway,
very
good.
Okay,
let's
stop
so
welcome
again.
This
is
the
energy
foundation
by
Leslie
working
group,
meeting
July
3rd
and
let's
first
of
all,
before
we
go
to
the
agenda,
is
anything
which
is
not
on
that
one
though,
and
if
you
always
shoot
these
guys,
I.
A
So
there
is
one
item
which
we
also
discussed
briefly
last
week
this
was
labeled
in
the
main
noches
repo.
This
is
the
a
spin
hooks.
Do
not
recognized
execution
context
we
invented,
processing
enables,
and
last
time
we
agreed
that
it's
not
really
clear.
What
would
be
the
action.
I
can
and
I
don't
see
any
comments
instead.
So
does
the
button.
The
working
group
has
any
more
context
on
that,
or
should
we
go
to
the
next
item
right.
A
B
A
A
So
last
time
we
had
a
presentation
by
IBM
and
there
new
exciting
to
come
in
which
we
are
capable
to
protect
surveillance,
agree,
pods
and
basically
the
TRD
air
was
that
it's
under
the
process
of
getting
Oakland
sauce
I'm,
not
sure.
If,
if
you
have
any
more
context
on
that
the
issue
didn't
have
an
update
since
that
yeah.
B
A
Thank
you.
Dan
next
item
is
there
is
the
proposal
by
Aleksey
on
the
run,
the
inspect
protocol
and
I?
Think
it's
on
me,
because
I
should
ask
Alexa
to
join
this
meeting
if
he
wants
to
do
progress,
so
I
feel
the
next
action
item
would
be
actually
for
me
to
to
be
sure
that
is
on
the
next
meeting
sounds
good.
A
Next
item
is
the
user
journey
is
initiative
on
last
time
we
actually
not
so.
On
the
summit
last
summit,
we
discussed
if
you'd
like
to
make
kind
of
a
user
survey
to
being
able
to
decide
what
are
the
supported
environments
and
the
first
use
cases.
If
you
want
to
start
to
work
on
that
and
I
created
an
issue
in
the
no
just
iron
stick
repo
with
the
proposed
or
what
the
survey
content
could
be
and
with
some
ideas
how
we
could
broadcast
it
and
I
get
some
feedback
Michael
and
other
things
really.
A
Thank
you
for
that.
I
incorporated
those
feedbacks,
so
the
next
step
would
be
basically
stick
with
the
distribution
partners
and
start
to
send
out
the
survey
just
to
be
completely
honest.
I
have
never
done
a
survey
before
so
I'm,
not
sure
that
this
is
the
good
amount
of
question
am
I,
making
the
questions
in
the
right
way,
so
I'm
open
to
any
kind
of
feedback.
All
right
who.
B
B
A
Mean
hopefully,
the
foundation
can
help
us,
but
other
than
that
I
reached
out.
Actually
the
summit
I
spoke
with
on
a
phone
book
book
up.
She
mentioned
that.
Maybe
they
can
use
that
with
their
channels
because
they
have
an
experience
we
did
yeah.
In
the
meantime,
I
spoke
with
my
oil
company
advising
stack.
They
are
also
happy
to
to
use
their
distribution
channels
I'm,
not
sure
whether
someone
was
mentioning
that
maybe
MPM
I
am
not
sure
what
what
other
options
we
have
right.
B
B
C
B
A
B
C
A
D
At
least
we
have
some
actions
that
can
be
done
on
the
diagnostic
perspective,
how
we
use
a
journey
back
comes
in,
and
how
do
we?
How
do
we
shape
those
things
up,
but
then
waiting
for
that
is
also
a
good
idea,
at
least
if
we
are
which
opened
for
the
crash
Diagnostics.
If
some
of
you
can
have
a
look
and
make
some
proposals-
or
at
least
say,
looks
good
from
your
perspective,
then
that
will
make
us
work
on
the
next
set
of
documents.
If,
if
this
option
layout
is
having
some
consensus
right.
A
A
B
A
B
B
Like
you
know,
we
can
leave
the
issue
there,
but
it's
been
on
so
long
and
we
haven't
done
anything.
It's
just
I
think
noise
at
this
point
right,
Wow
in
fact,
yeah.
It's
fine
to
leave
it
open,
but
okay,
I,
just
took
the
issue
of
the
agenda
off
so
at
least
won't
show
up
next
time.
People
can
always
add
it
back
in
if
there's
nothing
to
talk
about
on.
A
A
B
Baby,
that's
what
I'm,
just
yeah
so
I'm,
adding
a
comment
that
says
off
robots.
You
still
able
to
champion
this.
Oh
okay!
Thank
you,
yeah.
That
way,
at
least
if
the
answer
I
think
the
answer
may
be:
no
because
he's
busy
on
other
things,
but
at
least
then
we
have
no
champion.
Maybe
we
need
to
take
it
off
the
issue
for
now
and.
A
B
Think
he's
gonna
be
able
to
push
it
forward.
I
I
was
talking
with
Joe,
who
was
doing
some
work
on
the
promises
front
and
also
on
tc39
were
like
we
move
this
forward.
We,
you
know,
how
would
we
discuss
with
teeth
the
tc39,
but
I?
Don't
necessarily
have
agreement
that
we're
gonna
push
this
forward,
so
I
think
for
now
maybe
leave
the
issue
and
we'll
take
it
off.
The
agenda
makes
sense.
Okay,.
B
Was
like
a
sink
context,
formalization
was
around
the
concept
and
there's
a
document
and
deck
that
put
together
a
concept
of
some
terminology
and
something
that
would
likely
need
to
be
implemented
in
in
the
in
the
V.
That
was
engine
itself.
That
would
let
you
more
generically
than
animation
hooks
deal
with
a
some
context
and
propagation.
D
A
C
A
So
we
are
taking
notes
on
on
the
meeting,
so
it's
an
easy
to
follow,
what's
happening
in
that
working
group,
but
the
TR
do
is
basically
there
are
lots
of
conversations
are
now
that
general
open
telemetry
specification,
because
it's
mainly
driven
by
Java
and.net
people,
but
simply
by
the
nature
that
they
are
showing
up
and
do
not.
People
are
not
that
many
I'm,
not
that
active.
There
are
lots
of
conversation.
How
we
can
bring
your
perspective
because
note
is
different
and
Java
and.net,
so
it
doesn't
necessarily
good
API.
A
Well,
what
is
it's
built
for
those
languages
for
non
and
I
think
what
will
be
interesting
for
the
magis
dynastic
working
group
is
that
we
started
to
have
some
conversation
or
and
the
trace
propagation
in
the
process,
so
the
that's
kind
of
related
to
the
async
hooks
and
and
all
that
kind
of
how
to
do
this
booty
tracing
yeah,
that's
that's
it
er
there.
You
already
have
some
code
in
the
node
repo
for
open
telemetry,
but
it's
it's
not
much.
It's
more
more
interfaces!
A
B
A
A
I
feel
maybe
the
propagation
is
the
most
important
for
us,
because
we
are
not
happy
with
the
current
solution.
We
are
not
happy
with
the
monkey-patching.
There
were
lots
of
conversations
on
the
previous
summits.
How
we
could
make
it
better,
I
think
that's
where
maybe
we
can
learn
from
it
or
they
can
learn
from
us.
I
know
that
if
you
use.