►
From YouTube: 2023-03-21 meeting
Description
Instrumentation: Messaging
B
A
C
D
B
D
Yeah
I
I
did
sync
the
sandbox
main
repo
yesterday.
Let
me
try
and
do
that
again,
but
yeah
as
I
just
put
in
the
notes.
There's
two
issues
that
are
blocking
me
from
adding
the
APA
logs
and
API
events,
which
I
haven't
had
enough
time
to
dig
all
the
way
through
one
was
a
dependency
which
would
just
break
it.
So
if
you
just
clone
the
the
main
sandbox
it
works
and
compile,
it
works
fine.
D
D
E
Hi
all
I'm,
okay,
I,
just
figured
I'd
drop
in
to
see
how
things
are
going
over
here
and
I
might
start
attending
these
sigs
I'm
not
able
to
necessarily
drive
any
stuff
in
the
in
the
realm
space,
because
it's
not
my
area
of
expertise
but
I'm
hoping
to
listen
to
you
all
and
you
know,
try
to
work
with
you
all
and
the
rest
of
the
specification
to
help
you
move
forward.
So
that's
kind.
B
E
B
They've,
been
looking
for,
they've,
been
looking
for
someone
from
the
TC
to
to
join
this
sig
on
a
regular
basis
and
help
us
move
some
things
forward,
and
we
asked
the
grin
to
do
that
and
he
joined
once.
But
then
I
talked
to
him,
I
ping
him
yesterday
and
he
said
that
he
wasn't
sure
that
he
was
gonna,
be
the
one
from
TC
assigned
to
this
sig
and
then
it
he
was
going
to
discuss
it.
B
E
E
You
know
efforts
as
well,
specifically
the
configuration
working
group-
and
you
know
my
involvement
in
in
this
rumstick
has
to
be
kind
of
different
than
configuration
working
group,
because
you
know
we're
over
there.
I
can
kind
of
Drive
the
implementations.
It's
just
not
really
practical
for
me
to
drive
the
implementation
over
here,
which
I
think
is
the
super
essential
part
of
getting
stuff
done.
E
You
need
like
prototypes
and-
and
so
you
know,
I
think
in
order
for
rum
to
have
success,
it
can't
it
necessarily
can't
just
be
me,
because
one
I
can't
drive
the
implementations
and
two,
you
know
I
think
some
of
the
concepts
that
you
all
are
trying
to
work
with.
Are
you
know
they're
they're,
quite
different
than
you
know
this,
this
the
scope
of
the
specification
so
far
and
I
think
that's
why
you
know
you've
been
bumping
into
some
walls.
E
So
yeah
I,
don't
know
how
maybe
yeah.
Maybe
we
have
to
kind
of
shift
our
like
where
we,
where
we
come
and
have
synchronous
conversations
with
you
to
to
this
meeting
or
maybe
like
I'm,
not
sure
you
know,
if
that's
the
main
meeting
on
Wednesdays
and
the
TC
members
can
never
join
because
they
have
conflicts,
then.
A
E
D
B
E
E
And
you
know
just
to
kind
of
reinforce
the
point
that
I
think
there
needs
to
be
two
of
us,
so
I
think
tigran
has
done
a
number
of
things
on
behalf
of
the
you
know
that
I
guess
complement
the
work
in
the
rum
Sig.
You
know
he's
pushed
hard
for
a
long
time
on
the
the
complex
attributes,
type
issue
and
a
couple
of
other
things,
or
at
least
kind
of
been
involved
in
the
conversations,
and
you
know,
despite
tigran
they've,
they've
kind
of
continued
to
stall
and
you've
bumped
into
walls,
and
so
I
guess.
C
E
Right
he's
got
his
hands
full,
that's
kind
of
a
central
theme
of
or
a
recurring
theme
of,
open
Telemetry
right
now
is
that
there's
there's
a
lot
of
areas
that
are
in
Flight
a
lot
of
big
projects
in
flight
at
the
same
time
and
everybody
spreads
a
bit
thin
if
I
had
it
my
way,
we
would
stop
saying
yes
to
new
projects
for
a
while.
While
we
finish
a
lot
of
the
work
that
we've
started
and
I
think
you
know,
tigran's
availabilities
seems
to
be
somewhat
like
a
reflection
of
that.
So.
E
I
feel
the
same
way.
I
feel
like
I'm
stretched
thin
between
a
configuration
working
group
and
the
log
Sig
and,
and
you
know,
improvements
that
need
to
be
made
to
metrics
and
the
Java
implementation
of
this
all
and
then
now,
like
I
kind
of
have
to
be
involved
in
the
rum
stick
to
a
degree.
So
that's
a
lot
of
work
streams
in
flight.
D
E
Know
from
my
perspective,
the
the
events
conversations
are
like
a
bit
of
a
distraction
from
that
in
the
short
term,
although
you
know
they're,
they're
really
important
in
the
medium
term,
so
yeah
I
guess
all
that's
to
say
that
I
don't
mind
that
that
conversation
around
the
the
exact
use
cases
of
events-
and
you
know
their
semantics
I-
don't
think
it's
important
to
flush.
Those
out
right
now,
yeah.
D
And
it
doesn't
need
to
block
logs,
like
you
know,
we're
using
logs
as
the
transport
it
you
know
and
having
the
API
is
nice
because
it
gives
us
that
abstraction,
but
so
we're
not
tightly
coupled
but
yeah.
We
should
not
be
blocking
making
logs
stable,
based
on
talking
about
how
what
events
would
look
like
right.
So
yeah.
D
D
The
proposal
has
now
been
merged
in
Josh
called
out
that
this
does
not
mean
that
any
everything
in
ECS
is
coming
to
hotel
and
everything
hotel
is
going
to
ECS
yeah.
They
said
there's
going
to
be
a
merging
of
the
two,
so
I
guess
for
us.
Ecs
already
have
a
client
namespace,
so
that
might
be
interesting.
D
Their
event.
Namespace
doesn't
include
our
the
sort
of
events
that
we're
talking
about.
They
don't
seem
to
include
client-side
events
in
their
definition
as
far
as
I've
read
it
so
far,
but
there
will
be
some
changes
there
and
I
think
we've
already
seen
that
as
part
of
the
http
stuff,
that
Trask
was
driving
with
the
original
user
agent
change.
D
The
second
one
is
really
there's
a
discussion
going
on
about
splitting
semantic
conventions
out
from
the
existing
specification
repo.
So
that's
just
going
to
affect
where
we
create
our
definitions.
So
that's
really
all
I'm
calling
that
out
there
and
then
the
sandbox
already
mentioned
I
haven't
yet
got
the
API
logs
and
events
from
JS
over
because
there's
two
issues
that
I
need
to
fix
in
the
automated
script.
D
I've
created
the
bug
I've
currently
assigned
it
to
me,
so
I
should
get
to
it.
This
week,
I
have
been
working
on
the
background
in
the
past
week
since
last
meeting
where
I
started
working
on
it,
I
keep
hoping
that
something
will
get
fixed
in
the
JS
in
the
country,
repo,
so
I
kept
syncing
the
main
one,
but
hope
it's
not
a
plan
and
it
doesn't
work
still
so
yep
that
doesn't
mean
we
can't
create
branches.
Now.
C
D
B
D
D
B
Okay,
so
so
that
work,
I,
probably
can
I
probably
have
capacity
on
it
to
participate
in
like
to
work
on
that
one
for
now,
and
so
we
have
and
I
I,
don't
know
like
what
everybody
can
you
know
how
much
time
everybody
can
have
have
to
to
work
on.
You
know
these
things
and
what
their
interests
are,
but
that's
what
I
wanted
to
talk
about
this
like
coordinate
to
work
on
these
these
different
areas
going
forward
I
mean
what
I
would
propose
that
and
told
me
like.
B
If
that
sounds
good
to
you
is
that
we
create
issues
in
this
sandbox
repo
for
four
different
things
that
you
want
to
work
on,
and
then
people
as
they
have
time
they
can.
They
can
take,
take
an
issue
and
work
on
it
so
like
for
the
other
instrumentation
we
have,
we
have
the
you
know
the
events
SDK
work.
B
B
D
Yeah
and
I
just
put
in
the
notes
there
as
part
of
the
merge
I,
did
actually
bring
over
them.
The
Meta
package,
Auto
instrumentation
too,
so
I
just
dropped
a
link
from
Maine
into
there
yeah
it's
called
like
well,
it's
now
called
sandbox
Auto
instrumentation's
web,
but
it
was
just
called
Auto
instrumentation
swipe.
D
B
B
B
B
B
You
also
need
the
events
SDK,
so
the
events
SDK
is
on
top
of
the
well
actually,
the
events
SDK
yeah
it's
on
top
of
the
logs
SDK
and
that's
on
my
branch
in
my
Fork,
so
I
could
bring
that
over
to
the
sandbox
and
but
but
yeah
the
logs
SDK
and
the
instrumentations.
The
instrumentations
depend
on
the
API
on
the
events
API.
So
we
don't
there's
it's
not
blocked
until
we
need.
We
need
the
API
in
the
sandbox.
So
that's
the
other
I
guess.
D
Yeah,
okay,
oh
Fridays,
are
the
days.
I
can
tend
to
do
a
lot
of
stuff
on
on
Hotel,
so
hopefully
I'll
be
able
to
get
to
it
by
then,
in
terms
of
once,
it's
actually
checked
into
JS
and
Contra.
Bring
it
into
the
sandbox
is
actually
fairly
trivial
because
we
run
run
one
action
to
bring
it
into
the
the
repo
staging,
which
only
takes
a
few
minutes
to
run
to
how
long
is
it
going
to
talk,
take
three
minutes
and
just
under
four
minutes
to
run
that
creates
a
PR.
D
We
then
merge
that
PR
and
then
we
run
the
other
one
as
long
as
it
doesn't
break,
which
is
where
we're
at
the
moment
and
that
one
takes
just
over
three
minutes
and
that
also
creates
a
PR
and
then
once
they
merged.
We
were
completely
up
to
date
like,
since
this
meeting
I've
actually
got.
In
fact,
I'm
gonna
accept
this
one
here.
So
now
we
have
a
PR
which
brings
in
another
46
commits
or
46
files
from
yesterday
Okay.
So
you
know
it
it's
nice
and
smooth
to
get
that
done
now.
D
But
let's
say
they
the
script
that
converts
it
and
renamed
everything
they
have
sandbox
in
the
front
that
if
everything
conforms
to
the
same
pattern,
everything
works
fine,
but
the
patterns
keep
changing
in
the
main
repos.
So
that's
the
that's
the
eslint
issue.
That's
currently
in
there
the
dependency
issue
I'm
not
quite
sure
what
that
is
yet
so.
B
D
D
B
D
B
D
D
D
D
We
want
to
be
able
to
say,
which
way
are
we
going
I'm,
not
I,
think
that's
still
a
pretty
optimistic
time
frame,
which
is
what
I'm
telling
from
internal
to
planning,
but
we'll
see
what
happens
in
terms
of
the
mini
web.
Only
SDK
I
bought
that
up
in
the
JSC
last
week,
as
expected,
Daniel
had
some
reservations.
Send
us
I
mentioned
you
quite
a
bit
as
the
driver
for
that
one.
So
we
can
create
the
branch
and
we
can
be
the
owner
of
the
web.
Only
SDK.
D
D
A
D
There
is
already
a
couple
of
instrumentations
which
I
bought
over
in
the
sandbox,
which
are
web,
only
sent
you
another
possibility.
Is
we
just
say,
or
we
propose
a
structure
that
says
web
in
the
main
replays,
and
that
is
the
instrumentation?
Is
then
just
for
the
web,
like
the
document
loaded,
it
doesn't
exist
and
can't
exist
in
node
yeah
unless,
unless
you
synthesize
it
based
on
a
startup
event,
but
sorry.
A
B
You're
joined
a
little
bit
late,
so
I
just
to
kind
of
summarize
what
we
talked
about
as
far
as
the
plan
going
forward,
so
I
created
a
branch
in
the
sandbox
for
the
auto
instrumentation
work
and
my
plan
is
my
plan
is
to
create
issues
in
the
sandbox
repo
for
the
individual
instrumentations
that
we
want
to
work
on
and
add
to
the
branch
and
then
people
can
you
know
as
they
have
availability.
They
can
pick
the
one
that
they
want
to
work
on
and
collaborate
that
way.
Yeah.
B
We
are,
we
are
blocked
on
or
blocked
in
a
couple
things.
The
events
API
and
logs
API
are
not
in
the
sandbox
repo
yet,
but
there
is
a
there's
some
some
build
issue
that
we
need
to
look
into
hopefully
this
week
and
we
can
fix
that
and
move
forward
and
then
I
I
have
my
I.
Have
the
events
SDK
prototype
that
I
started
working
on
is
which
is
on
my
Fork
right
now:
I'll
I'll
move
it
over
to
the
sandbox.