►
From YouTube: 2022-09-14 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
A
A
A
A
A
So
we
are
thinking
of
keeping
or
emitting
both
a
span
and
an
event.
The
idea
is
that
you
know
the
the
moment.
You
load
a
page.
You
you
want
to
emit
an
impression
event
that
hey
your
page
has
loaded,
but
you
don't
yet
have
any
of
the
timing
information
yet
and
we
we
let
the
page
load
completely
and
after
that
we
will
generate
a
span
with
with
the
duration,
a
field
set.
A
D
A
D
A
I
have
a
question
for
those
who
joined
the
JS
Sig
I
I,
don't
I'm,
not
so
familiar
with
the
you
know
how
things
work
there.
I
have
a
question,
so
we
are
introducing
some
new
attributes
in
the
browser
detector
and
we
want
to
drop
some
of
the
attributors
that
are
already
there
and
it
turns
out
that
the
open
Telemetry
resource
package
is
already
stable
and-
and
so
we
cannot,
you
know,
remove
anything
and
the
suggestion
provided
in
the
pr
was
to
introduce
a
new
detector
and
Mark
the
current
one
as
deprecated.
A
But
we
don't
want
to
let
go
of
the
name.
Browser
detector
sounds
more
relevant
than
the
suggested
names,
so
in
general
there
has
to
be
a
way
to
phase
out
functionality,
or
you
know,
make
some
breaking
changes
even
in
stable
code,
especially
you
know.
If
we
are
able
to
plan
ahead,
does
anyone
know
if
there
is
any
precedence
to
doing
such
a
thing.
C
Yeah,
it's
normally
a
case
of
brand
new
version.
You
know
a
brand
new
instance
or
you
go
through
this
phase
of
having
both
and
then
you
have
to
make
a
major
version
change
to
say
that
you're
dropped
in
the
previous
one.
The
alternative
is,
you
have
a
config
that
would
have
to
default
to
the
way
it
currently
operates,
that
you
can
flip.
B
E
Sure,
yeah
yeah
I
haven't
had
time
to
work
on
it
over
the
past
couple
weeks.
It's
definitely
high
up
on
my
list:
I
I'm
trying
to
balance
being
able
to
do
open,
Telemetry,
stuff
and
and
other
other
work
things,
but
yeah
I'm,
hoping
to
get
that
PR
into
a
reviewable
state
in
the
next
week
or
so.
If
anybody
like
wants
to
help
or
yeah
like
if
you
want
to
help
at
all
I'm
I'm
open
to
like
chatting
about
transferring
that
knowledge
and
getting
getting
other
folks
to
to
contribute
to
so.
E
I
need
to
make
sure
that
I
think
the
tests
are
failing
for
some
of
the
node
stuff,
so
I
need
to
verify
that,
like
I
haven't
broken
any
functionality
for
the
node
Proto
exporter
by
the
changes
I've
made
so
yeah
basically
need
to
test.
I
can
make
a
list
on
the
pr
for
I.
Think
I
have
a
list
up
there,
but
the
tests
are
failing,
so
I
need
to
fix
all
of
that
up
before
it
can
go
in.
C
So
I
have
a
PR
App
that
Martin's
already
signed
off
for
making
it
the
the
contrib
repo
and
the
jspo
mergy
into
the
sandbox
I
want
to
get
Daniel
Smith
up
on
that.
Once
that
happens,
I'll
run
my
script
again
to
merge
all
the
history
into
the
new
Sandbox
and
once
that's
done,
I
don't
have
to
find
the
same
time
as
Hershey
was
talking
about
to
massage
that.
C
C
A
C
B
C
As
part
of
that
he's
created
a
spreadsheet
which
he's
linked
off
in
the
doc
to
try
and
identify
what
the
common
attributes
are
going
to
be
yeah,
which
is
the
spreadsheet
here
so
along
the
bottom.
We've
got
I
think
the
set
of
events
or
states
in
the
case
of
the
span
ones
that
we
want
to
try
and
Tackle.
C
First,
where
the
end
goal
is
that
First
Column
a
is
what
we
want
to
establish
and
say
well
for
in
this
particular
case,
the
page
view
event:
what
are
the
fields
that
otel
is
going
to
mandate
and
as
part
of
a
collecting
that
we've
got
all
the
companies
across
in
each
other
column
to
say?
Well,
this
is
what
you
call
it
and
they're
aligned.