►
From YouTube: 2021-11-11 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).
C
A
A
All
right
looks
like
we
got
a
bunch
of
people
already,
so
I
guess
we
can
get
started
as
usual.
Please
add
your
name
to
the
attendees
list.
If
you
haven't,
it
also
looks
like
we
got
a
couple
of
new
names
here
that
I
have.
I
don't
recognize.
A
D
Yeah
yeah
hi
hi
everyone
yeah.
This
is
I
I'm
from
india
based
out
of
bangalore.
I
work
in
cisco
subsidiaries
that
I
work
in
is
an
app
dynamics
and
yeah
I'm
happy
to
join
the
community.
A
It
must
be
a
different
yeah
different
time
for
you,
yeah
yeah,
cool
yeah.
So
I'm
I'm
legion,
I'm
one
of
the
maintainers
here.
I've
been
working
on
this
project
since
inception,
pretty
much.
C
A
Almost
like
two
years
now,
yeah
feel
free
to
reach
out
over
to
slack
or
anything.
If
you
need
help
with
anything
to
get
started,
we
always
welcome
new
contributors,
so.
F
Yeah
sure,
sorry,
hello,
my
name
is
diego.
I'm
another
maintainer
this
project,
I
work
for
I'm
located
in
costa
rica
working
at
this
project
for
two
years
or
so
maybe
a
little
less.
C
Nice,
I
can
go
next,
I'm
aaron!
I
work
at
google.
I've
also
been
working
on
this
project
for
about
about
two
a
year
and
a
half
two
years.
I
am
a
approver,
not
a
maintainer,
but
I
am
also
really
happy
to
help
out
reach
out
on
slacker
whatever.
So,
thanks
for
joining
and
nice
to
see
new
people
here,.
B
C
G
Mario,
I
work
at
dynatrace,
I'm
also
I'm
a
contributor
for
the
project.
I
think
it's
almost
two
years
now,
yeah,
that's
basically
about
myself.
E
C
E
Is
my
first
meeting
and
I'm
really
excited
to
be
part
of
this
community.
A
A
I'm
just
looking
at
the
topics
looks
like
I
think,
you're
believing.
C
A
Cool
yeah,
so
it
looks
like
we're
going
to
be
doing
a
release
today.
I
believe
away
has
already
taken
point
on
that.
To
do
the
release,
I
believe
the
two
pr's
for
contributing
core
out.
I
think
one
of
the
the
questions
or
topics
was
that,
since
we
moved
all
of
the
you
know,
logs
and
metrics
to
the
main
branch
now,
I
believe
we're
planning
to
do
an
experimental
release
as
well.
A
Release
workflow
in
each
list,
but
we
haven't
really
tested
it
out
yet
so
I
believe
the
sorry.
The
consensus
last
week
was
that
we
were
going
to
be
releasing
logs
as
experimental
and
we
weren't
gonna
be
listening.
Metrics,
I'm
not
I
don't
remember.
Does
anyone
recall
what
the
conversation
was
like.
C
If
we
like
to
find
experimental,
I
thought
what
we
were
planning
to
do
was
just
since
everything's
now
in
the
same
monorepo
just
release
everything,
and
then
we
were
not
going
to
make
an
announcement
about
metrics
and
we
were
going
to
make
some
sort
of
announcement
about
logs.
So
people
can
try
it
out.
A
Right,
yeah,
sorry,
I
guess
that's
that's
kind
of
that
was
misleading
for
me
to
say
experimental,
but
yeah.
So
as
part
of
this
release,
I
guess
would
just
announce
logs.
How
do
we
think
we
want
to
be
able
to
do
that?
A
Just
like
in
the
release
notes
some
something
in
the
readme?
What
do
you
guys
think.
B
B
A
I
see
I
remember
seeing
the
feature
matrix
from
before
I
don't
recall
seeing
vlogs,
but
I
could
be
mistaken,
but
yeah
I'll.
Take
a
look
at
that.
Let
me
write
that
down.
A
Oh
okay,
but
yeah.
I
think
this
one
should
go
relatively
smoothly.
We
didn't
have
many
or
any
packages
like
moving
around
so
dependencies
should
be
fine,
so
yep
yeah.
We
should
get
those
in
pretty
quickly
thanks
away
for
taking
point
on
that.
A
Cool,
does
anyone
have
any
other
outstanding
topics
not
related
to
pr's
or
issues.
H
A
A
No,
so
is
your
question
when
it's
being
released
or
it's
when
it's
being
marked
stable,.
A
Yeah,
I
believe
eventually
that
would
be
the
case.
Okay,
but
not
in
the
next
release.
F
No
okay,
okay,
I'm
asking
this
because
the
the
error
handling
discussion
that
we
have
been
having
so
far
is
something
that
will
necessarily
impact
everything
metrics
logs
and
tracing.
So
I
have
been
working
in
a
prototype
that
I
hope
I
really
hope
on
crossing
my
fingers
that
can
be
applied
to
the
code
that
we
have
now
without
making
any
breaking
changes
and
that,
if
that's
the
case,
it
will
also
be
necessary
to
apply
it
to
metrics
and
unlocks.
F
F
Have
that
leading
underscore
it
it'll
make
it
easier
to
add
this
error
handling
mechanism
or
some
other
handling
mechanism?
If
that's,
if
that's
the
case,
so
I
wanted
to
inform
you
of
that
that
before
removing
that
leading
underscore,
let's
keep
in
mind
that
we
need
to
do
something
about
about
error
handling
and
if
it's
easier
to
do,
want
to
test
and
to
implement.
While
we
have
that
leading
underground
based
still.
A
Big
change
and
you're
a
maintainer
too,
so
you
have
all
the
visibility
and
when
things
go
in
so.
A
F
Yeah,
I
just
wanted
to
inform
you
of
this
as
soon
as
possible,
because
I
know
it
can
be
frustrating
for
people
who
want
to
make
a
release
of
vlogs
or
something
else
to
certainly
get
an
announcement
that
they
wait.
We
still
need
to
figure
out
their
handling,
so
the
better.
The
sooner.
A
Wait,
did
you
sorry,
diego?
Did
you
move
the
safety
prototype
as
a
prototype
before
or
was
it
an
actual
pr
before?
Okay.
F
The
first
one
was
me
trying
to
add
safeties
for
classes
and
functions,
which
I
found
it
quite
complicated
to
implement
with
the
approach
that
I
was
following,
so
I
I
just
put
that
pretty
much
on
standby,
and
probably
I'm
just
going
to
close
this
this
pr,
because
this
this
approach,
I
don't
think
it's
gonna
work,
probably
the
other
pr,
the
that
says,
if
you
go
back
to
the
that
that
one,
the
ad
safety
prototype
that
prototype,
I
believe
it's
the
most
promising
so
far,
I've
been
making
I've
been
trying
to
make
to
read
the
code
that
we
have
been
tracing
and
to.
F
Make
sure
that
this
prototype
is
working
for
every
coding
detail
that
we
have
in
tracing
because
tracing
is
is
is
what
we
need
to
make
safe
without
breaking
changes,
because
it's
the
only
part
that
we
have
yet
to
release
publicly
right.
So
so
the
the
last
thing
I
did
yesterday
was
to
make
sure
that
this
product
will
work
with
the
context
managers
that
we
have
some
around
the
tracing
code,
and
I
I'm
really
hoping
that
that
this
prototype
can
be
applied
to
tracing
without
breaking.
F
F
A
F
No,
no,
no,
we
don't
need
to
disclose
anything
right
now.
I
just
wanted
to
give
you
all
this
ability
that
this
is
the
plan
that
I
have,
and
this
is
what
I
am
trying
to
do,
because
I
know
that
this
can
affect
lots
and
also
metrics
and,
of
course,
also
tracing
right.
So
I
just
wanted
to
inform
you
as
early
as
possible
the
prediction
that
I
have
so
that.
F
That
you
know
as
early
as
possible
right,
because
I
understand
that
if
someone
is
trying
to
to
make
a
release
of
vlogs,
it
can
be
very.
C
Do
we
have
like
tracking
issues
for
each
signal
for
implementing
these
that
we
can
label
as
like
pretty
stable.
F
F
C
Yeah,
I'm
just
I'm
just
saying
it
sounds
like
what
you're
saying
is
we
don't
want
to
like
really
release
them
or
mark
them
stable
before
the
error
handling
is
ready,
so
I'm
just
suggesting
we
add
issues
that
like.
If
we,
when
we
make
project
boards
or
or
sort
by
labels
and
stuff,
we
can
just
see
that
it's
pending
still.
A
Hey
diego,
do
you
think
the
this
the
error
handling
or
the
metrics
works
takes
priority
in
terms
of
like
what
we
should
get
done?
First,.
F
Okay,
actually
error
handling
is
the
most
important
thing
by
design,
because
that
affects
everything.
It's
the
matrix.
E
F
Both
things,
I'm
not
dedicating
myself
only
to
her
handling,
so
I'm
pretty
much
splitting
my
time
in
half.
It
probably
is
for
that.
A
A
Diego,
if
you
kind
of
just
want
to
like,
do
a
little
short
tldr
of
what
you
just
said
in
the
release
notes.
I'm
sorry
in
the
meeting
notes
for.
C
A
All
right
moving
along
releasing
packages
with
dedicated
owners,
maintainers.
B
I
added
that,
oh
sure,
so
this
is
about
the
aws
sdk
extensions
and
the
propagator,
that's
in
contact
and
right
now,
they're
in
a
releasing
from
from
releasing
standpoint
and
in
viet
state.
So
our
release,
automation,
always
bumps
their
version
number,
and
then
we
have
to
manually
reset
it
back
to
what
it
was
and
and
the
code
owner
nathaniel
in
this
case
has
the
ability
to
release
them
independently.
B
B
So
that's
one
thing
we
could
do,
but
I
was
thinking
that
the
reason
we
added
code
owners
is
not
that
we
don't
release
these
as
part
of
country
flow,
but
that
we
allow
god
owners
to
issue
standard
releases
when
they
want.
So
we
could
maybe
just
include
them
in
the
country
please
and
we'll
just
bump
them
like
any
other
package,
but
the
narration
that
nathaniel
can
have
the
ability
to
issue
enough
releases.
A
My
understanding
was
that
we
were
going
to
completely
ignore
them,
but
regardless
like
for
the
second
one,
we
would
have
to
modify
the
release
script
a
bit
anyways
right,
because
the
stable
ones
are
always
going
to
have
different
versions.
Yeah.
B
A
Yeah
I
was
talking
to
nathaniel
and
his
understanding
was
the
first
one
as
well.
Okay,
but
yeah.
It's
not
not
a
huge
deal,
but
I'm
okay
with
the
first
solution.
Just
to
add
like
a
ignore
everything
in
specific,
stable
folders.
So,
okay,
all
right.
A
All
right,
nice
does
anyone
have
any
other
topics.
They
don't
talk
about
or
go
into
pr's
in
the
shoes.
A
All
right,
nice,
okay,
so
I
was
taking
a
look
at
the
way
that
java
was
doing
the,
so
we
have
a
feature
called
exclude
url
for
a
lot
of
our
http
based
instrumentations
right
now.
The
current
way
that
it
works
is,
I
believe,
we
set
environment
variables
and
I
think
it's
read
through
the
context.
I
believe
as
sorry.
Sorry,
it's
not
not
through
it
right
through
context.
A
It's
says:
environment
reals
and
we
just
read
it
from
the
environment
as
like,
a
comma
delimited,
regex
string,
which
is
cool.
It's
I've
just
just
come
to
my
attention
that,
like
java,
does
this
in
a
different
way
in
which
they
actually
instantiate
a
custom
sampler
in
which
they
apply
like
a
bunch
of
rules,
the
exclude
url
being
one
of
those
rules.
A
I
think
like
on
the
surface.
This
has
like
a
couple
advantages
like
one.
We
don't
have
to
like
change
this
for
every
single
instrumentation
that
we
want
this
for
and
two.
A
I
don't
believe
our
method
handles
the
use
case
in
which
we
want
to
exclude
a
span
being
created
from
the
initial
url
call
but
like
if
that
http
request
calls
like
another.
A
A
This
is
so
yeah
like
I
was
wondering
if
like
it
would
be
worth
it
for
us
to
do
this
or
if
that
issue
isn't
really
going
to
come
up,
at
least
for
for
our
python.
What
do
you
guys
think.
C
C
Yeah
I
mean
that
makes
sense.
Is
there
I,
I
guess
the
benefit
of
the
context
approach
is
just
to
like
way.
The
pros
of
that
is,
you
can
do
it
more
dynamically
from
higher
up
in
the
call
stack
right.
A
Whereas
the
sampler
only
applies
during
the
span
creation.
C
Yeah
during
the
creation
right,
yeah
yeah,
I
mean,
if
it's
just
for
url
exclusion,
then
it
sounds
like
like
that.
Should
work
fine
with
the
sampler,
but
I
know
that
the
the
issue
with
samplers
is:
if
it's
like
a
late
bound
attribute
or
something
like
that,
then
you
can't
right
change
this
decision,
so
yeah.
I
think
for
this
one.
It
makes
sense.
I'm
curious
what
other
people
think.
C
C
C
How
how
would
what
do
you
mean
specific
one,
sorry
so
like
right
now,
it's
an
environment
variable
and
in
the
instrumentation
it
checks
for
that
environment
variable
and
we'll
just
not
create
this
benefits
there.
If,
if
you
do
it
with,
if
you
keep
the
same
environment
variable,
and
you
want
to
swap
the
implementation
with
a
sampler
that
means
at
initialization,
you
have
to
set
the
sampler
right.
C
Yes,
how
would
that
work.
B
B
Yes,
yeah,
but
also
yeah
you're
right.
In
that
case,
we
would
have
like
a
breaking
change
in
some
sense,
but
instrumentation
packages
are
not
one
that
over
yet.
So
I
guess
I
guess
breaking
change
is
not
not
a
concern
but
yeah
you're
right
people
would
have
to
add
who
are
doing
manual
instruments
and
would
have
to
add
the
center
right.
B
C
B
C
Think
I
think
the
I
think
there
are
cases
where
someone
might
want
to
do
it
via
environment
variables
so
like
if,
if
the
config
is
part
of,
like
you
know,
like
kubernetes
or
something
like
that,
so
the
environment
variables
are
embedded
in
there
and
they
want
to
swap
it
on
the
fly
or
or
have
it
separate
from
the
application
right.
C
H
Like
are
you
talking
about
like?
There
are
two
environment
variables
you
know
where
we
like
they
can
configure
the
sampler
based
on
the
env
like
hotel,
sampler
and
sampler
underscore
arc
that
that
they
can
use
to
configure
the
sampler.
Are
you
talking
about
those
environment
variables?
Are
you
talking
about
the
instrumentation
in
vx.
B
C
Yeah
and
that
would
have
to
happen
in
the
in
the
actual
sdk
right,
yeah.
B
C
Right,
yeah-
and
I
think
I
think,
like
somebody
mentioned,
we
could
probably
stick
with
both
since
the
sampler,
the
sampler
will
catch
the
child
spans
and
and
then
that
way
it
won't
break
people
who
are
using
the
existing
mechanism.
A
B
B
I
think
we
should
implement
the
sampler
as
a
general
purpose
center
based
on
url
rules
and
keep
the
auto
instrumentation
feature
for
now
and
once
it's
in
then
we
can
like
add,
like
a
compatibility
layer
on
top
of
it.
If
you
want
to
support
existing
instrumentation
variables
with
the
sample,
I
guess
we
can
split
the
issue
into
two
and
like
implement
concept,
deal
with
them
separately.
B
There's
also
a
global
environment
variable
which
was
recently
added,
and
it
basically
does
the
same
thing
as
the
instrumentation
specific
ones,
but
for
every
single
instrumentation.
So
this
sampler
could,
by
default
work
on
that
environment
variable
and
then
we
will
discuss
whether
to
support
the
instruments
specific
ones
or
not.
We
could
maybe
just
remove
support
for
them,
but
that
could
be
one
direction
we
can
take.
A
All
right
cool
does
anybody
else,
have
any
other
prs
issues
they
want
to
bring
up.
A
All
right,
if
not,
then
I
believe
that's
everything
on
the
agenda.
I
will
see
you
guys
next
week
then.