►
From YouTube: 2021-12-29 meeting
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).
B
B
Hello-
I
I
don't
have
an
agenda
today,
because
the
holiday
week
I
know
a
lot
of
people
were
not
planning
on
coming,
so
I
figured
I
would
just
join
and
see
if
people
had
anything
to
talk
about
or
questions
or
anything
like
that.
Otherwise,
I
think
you
know
probably
not
much
to
talk
about
today.
B
C
I
don't
have
anything
to
talk
about
hey,
I.
I
have
a
question
so
I
have
started
you
know
using
the
js
in
and-
and
I
noticed
trace
test.
I'm
sorry
rested,
the
implementation
is
not
part
of
the
api,
but
it
shouldn't
separate
package.
I
was
wondering
why?
C
There's
only
simple
interface
in
the
api,
but
the
implementation
is
not
there.
B
C
Correct
so
the
implementation
like
the
tested
implementation
like
setting
you
know
trying
to
you,
know,
create
and
then
set
it
like.
Let's
say
I
want
to
use
some.
You
know,
along
with
the
you
know,
some
trace
trace
contact
information.
I
want
to
send
some
some
user
specific
tested,
there's
no
implementation,
but
as
a
part
of
the
api.
C
I'll
have
to
use
the
open,
telemetry
core-
it's
it's
not
currently
part
of
the
api
I'll
have
to
you
know,
also
install
the
code.
C
And
I
also
have
another
question:
sampling
like
sampling
is
a
sdk
concept,
but
you
know
you
like,
but
they're
part
of
the
open,
telemetry
core.
I
didn't
understand
like
how
how
these
things
are
structured.
You
know
like,
as
I
said,
sampling
is
sdk.
I
was
expecting
it
to
be
there
in
sdk,
but
it's
in
core
and
then
core
again
also
has
addressed
implementation,
which
should
be
in
api.
B
Yeah,
so
the
the
reason
for
those
things
essentially
is
because
a
lot
of
the
code
was
copied
from
open
census
and
that's
the
way
that
they
had
it.
So
though
it
was
not
really,
but
when
I
started
on
the
project,
the
whole
api
was
actually
in
core.
There
was
no
separate
api
package,
so
I
guess
those
are
just
things
that
didn't
get
moved.
C
Yeah,
like
other
other
other
sdks,
also
had
you
know
these
kind
of
insist
inconsistencies
but
like
post
post
1.0,
they
had
like
spec
like
spec
compliant.
We
have
like
implementations
in
the
api
part.
I
stick
a
part.
C
I
was
wondering
why
jssdk
has
these.
You
know
different.
B
I
mean
it
probably
just
because
nobody
got
around
to
it
is
the
the
short
answer
is
probably
not
a.
C
Do
we
want
to
do
something
about
it
because
I
was
expecting
like
I?
I
don't
know
if
anybody
has
brought
up
this
earlier,
but
but
basically,
if,
if
I'm
working
on
multiple
sdks
and
then
see
myself,
not
having
these
implementations
in
you
know
api,
which
is
what
spec
rickman
recommends
would
be.
Is
there.
B
C
At
least
the
the
trace
state
part
right,
so
I
wanted
to
use
in
it.
So
if
I
want
to
instrument
a
library
and
then
leave
the
leave,
the
sdk
to
the
user,
so
in
in
in
the
library
that
I
want
to,
you
know
just
use
the
api
part
right
there.
I
I
needed
a
you
know,
simple
trace
date,.
B
C
And
there's
also
like,
like
setting
setting
the
values
into
the
tray
state,
and
then
you
know
modifying
them
that
implementation
is
only
part
of
the
open,
telemetry
core,
it's
not
there
in
api.
So
I
had
to
install
open
telemetry
code
as
well
to
you
know,
get
that
working.
B
C
But
I
should
be
able
to
do
it
in
the
like,
at
least
the
trace
state.
I
should
be
able
to
do
it
right.
It's
not
the
something
sdk.
I
think.
B
C
Yeah,
exactly
the
library
instrumentation
part
will
always
be
no.
If,
if
you
know
if
no
sdk
is
registered,
but
if
the
sdk
is
registered,
there
will
all
be.
You
know
concrete
implementations
right.
B
C
C
I'm
I'm
not
sure
how
to
say
this,
like
the
tray
state
implementation.
If,
if
it's
part
of
the
apa,
I
can
instantiate
a
new
stress,
trusted
object
and
then
you
know
set
it
in
the
context,
so
that
when
the
sdk
is
stuck
that
that
gets
propagated
across
the
process,
boundaries,
along
with
the
trace
parent
information.
C
But
that
would
knock
it
on
if,
if
this
is,
if,
if
this
is
like
confusing
I'll
open
up
a
issue,
if
that
helps
with
the
you
know,
why?
Why
there's
a
need?
Why
I
am
you
know,
assuming
that
it
should
be
better
apa.
B
I
mean
without
an
sdk
installed,
I
mean
you're
saying
you
should
be
able
to
propagate
like
add
a
trace
state
to
a
span
and
propagate
across
process
boundaries,
but
without
an
sdk
installed,
there's
no
propagation
anyways.
Everything
is
no
longer.
C
That
that's
a
different
concept
right,
like
the.
If
the
sdk
is
installed,
you
get
the
real
spans
and
then
real
information.
That's
fine,
but
the.
But
the
ability
to
you
know
set
it
in
the
context
like
it
should
be
doable
without
having
the
you
know,
sdk
installed
right.
B
B
I
mean
so
we
did
not
add
the
context
manager
to
the
api
intentionally,
because
any
modules
that
build
in
support
for
open,
telemetry
api
directly.
We
didn't
want
them
to
have
to
take
that
dependency
on,
like
the
context
manager,
because
it
has
a
performance
impact.
B
I
mean
I,
I
definitely
see
so
we
in
the
api.
We
have
the
span,
so
you
can
manually
propagate
spans
with
just
the
api.
B
A
Can
ask
a
question
like
how
is
the
flow
with
the
place
that
it's
supposed
to
work
like
when
you
want
to
add
a
new
trace
date?
You
go
to
the
current
span.
It
has
a
spin
context,
there's
a
trace
state
in
there
and
then
you
can
call
set
key
value,
get
back
a
new
military
state
and
then
how
do
you
activate
it.
B
B
But
then
you
there's
just
set
and
get
like
key
values
on
it.
I
mean,
if
that's
what
you're
asking
so
you
would
have
to
create
a
new
one
which
would
be
a
dependency
encore.
So
I
agree
about
that
and
that
should
probably
be
moved
to
the
api
just
for
that
reason,
so
that
you
can
create
it
using
the
api.
B
A
B
B
B
It's
okay
to
override
the
trade
state.
On
the
span
context
I
mean
what
we
should
have
done
is
probably
made
the
trace
state.
I
don't
know
why
it
was
made
optional,
but
it
probably
should
have
been
required,
in
which
case
it
would
just
create
an
empty
one,
but
it's
too
late
for
that
now
so
now
we
just
have
to
remove
the
trace
state
implementation
to
that
api.
B
A
A
C
If
you
guys
like
want
to
hear
another
use
case
where
I
want
to
let's
say
in
if,
like
I'm
not
sure,
if
the
expectation
is
correct,
let's
say
fire
means
implementing
a
news
new.
You
know
internal
custom
propagator
there.
I
also
need
to
have
a
ability
to
you,
know,
access
that
and
like
create
a
new
trace
state
object
and
then
serialize
dc
realize
it
whenever
you
know
setting
it
through
the
headers
there.
Also
I
I
I
know
I
need
that
one.
B
C
Correct,
I
also
want
to
add
you
know
some
new
keys.
Like
let's
say
I
have
a
propagator
that
that
you
know
access
the
incoming
play
state
and
then
adds
add
some.
Let's
say
you
know
some
specific
information,
that's
it
relevant
to
the
theme
and
then
you
know
and
then
serializes
it
back
to
this.
The
previous,
like
the
same
header,.
B
E
C
Yeah
correct,
I
was
like
yeah,
I
was
expecting
to
be
there
in
the
api,
but
I
discovered
that
it's
it's
there
in
the
core,
not
that
you
know
I.
I
have
a
problem
with
that,
but
I
was
you
know,
curious
to
know
why
this
is
structured.
That
way.
B
Yeah,
it's
a
historical
mistake
is
the
short
answer.
It
should
be
probably
in
the
api.
I
also
it
it
would
have
been
solved
if
the
trace
state
was
just
a
required
property
on
the
span
context.
Also,
because
then
the
sdk
would
handle
creating
a
new
one.
B
But
it's
I
think
too
late
for
that
now,
because
if
we
make
the
optional
field
required
and
we
make
the
sdk
create
a
trace
state,
then
I
guess
for
users:
that's
not
really
breaking
I
mean
it's
technically
breaking,
but
it's
very
minor,
but
for
sdks,
then
I'll
have
to
implement
the
new
like
that
new
mode
or
they're
or
they're
broken.
C
F
B
B
We
can
mark
the
one
in
core
as
deprecated
and
say
you
should
use
the
one
in
the
api.
A
B
A
B
Stopping
them
from
using
it-
and
I
don't
see
any
reason
to
block
that,
so
I
think
it's
okay
yeah
I
it
is,
we
have
it
because
of
the
w3c,
but
I
would
say
now
it's
kind
of
its
own
thing,
at
least
within
open
telemetry.
It
can.
It
can
exist
separately
from
the
w3c.
B
C
Yeah
sure,
if
you
know
I'll
open
up
the
issue
first,
like
let's
you
know
so
the
other
people
also
have
idea.
I
think
moving
it
to
the
api
would
be
the
right
thing
to
do
now.
A
B
Has
had
some
vague
wording,
I
don't
know
if
they've
cleaned
it
up
honestly,
but
there
was
some
vague
wording
that
there
was
some
desire
by
some
people
to
use
the
api
to
propagate
context
without
an
sdk
installed
for,
like
you
know,
latency
sensitive
like
if
you
have
a
load
balancer
and
you
don't
want
to
create
spans,
but
you
do
want
to
propagate.
B
Without
modifying
anything,
so
in
order
to
do
that,
you
need
a
propagator
and
some
things
like
that
in
js.
The
way
to
do
that
would
just
be
to
install
because
the
the
propagation
api
is
top
level.
You
would
just
set
a
global
propagator
and
you
can
install
whichever
one
you
want,
but
you
would
have
to
install
the
api
package
and
the
core
package
to
do
that
and
then
in
some
other
languages
they
just
interpreted
it
differently
to
say
everything
needed
for
that
should
be
in
the
api
package.
B
So
you
don't
in
js
need
a
full
sdk,
but
you
do
need
like
the
core
package.
In
order
to
do
that,
I
think
the
reason
it's
different
is
because
in
most
languages
they
only
have
two
packages,
they
have
the
api
package
and
they
have
the
sdk
package
and
then
maybe
like
instrumentations
and
stuff
like
that,
but
it's
very
difficult
to
install
just
one
component
from
the
sdk,
where
in
js
it's
very
easy
to
just
install
the
core
package,
which
is
pretty
small.
B
D
B
Oh
you
guys
for
your
time
and
enjoy
the
new
year,
and
I
will
talk
to
you
next
year.
Bye,
you
too
enjoy.