►
From YouTube: 2021-06-17 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
A
Welcome
to
another
edition
of
the
weekly
python
city
meeting
great
to
have
all
of
you
here.
Please
add
your
names
to
the
attendees
list
and
he.
A
C
I
think
he
said
he
might
not
make
it
today
all
right.
Actually,
I
only
have
28
minutes
left,
but
20
minutes.
A
C
That's
all
good.
It
could
be
that
this
meeting's,
pretty
short,
it
doesn't
look
like
there's
a
ton
of
topics
to
discuss
some.
Oh,
we
do
have
a
do.
You
have
a
new
attendee,
though
correct
the
chant.
D
Hey,
hey
guys,
yeah
suppression
welcome
yeah,
so
thank
you,
yeah!
I'm
joining
here
like
on
behalf
of
aws,
so
me
and
my
other
teammate
carol.
I
guess
she
would
be
joining
soon,
so
we
kind
of
would
be
working
on
supporting
remote
sampling
with
x-ray,
so
yeah.
It's
it's
mostly
would
be
carol's
internship
project,
I'm
just
helping
her
out
with
that.
D
So
yeah,
I
guess
once
she
joins,
she
can
introduce
herself
and
just
get
a
feel
of
say
getting
comfortable
and
yeah
as
we
work
towards
adding
that
x-ray
remote
sampler
we'll
be
leveraging
the
sig
more
and
more
for
inputs
and
help
so
looking
forward
to
it
excellent.
E
A
So
if
anyone
has
some
topics
they
would
like
to
discuss,
please
add
them
to
the
topic
section
or
if
they
have
near
specific
repo
issues
or
pr's
as
well,
please
send
them
to
their
respective
sections.
I
think
srikant
who
like
to
discuss
the
pr
thinks
the
only
thing
that
we
have
in
our
agenda
today.
B
D
I
was
just
talking
with
the
folks
here
that
yeah
what
we
would
be
working
on
to
get
to
be
good
to
introduce
yourself
as
well.
F
Yeah,
of
course,
hi.
My
name
is
carol.
I'm
the
new
sde
intern
with
the
aws
x-ray
team,
I'm
currently
going
into
my
senior
year
at
uc,
irvine
studying
software
engineering.
So
I'm
very
excited
to
work
with
all
of
you.
A
Perfect
yeah.
E
A
Thanks
for
joining
and
welcome
yeah,
we
have
had
excellent
contributions
from
interns
before
so
we're
very
excited
to
have
you
here
as
well.
A
Hey
alex,
so
I
think
we
can
start
with
the
topics.
I
think
she
can
have
something
you
would
like
to
discuss.
Yeah
all
right.
You
can
see
that
please.
E
Yeah
right
so
this
this
is
related
to
auto
instrumentation,
so
the
open,
telemetry,
auto
instrumentation,
does
not
like
work
on
its
own.
People
have
to
install
distribution.
I
have
seen
a
lot
of
people
running
into
that
issue,
not
knowing
that
they
have
to
install
open,
telemetry
distribution
and
so
yeah.
E
So,
while
discussing
that,
oh
I
suggested
we,
we
update
our
getting
started
guide
to
just
you
know,
install
recommend
them
to
install
open,
telemetry
distribution
and
then
know
which,
which
pulls
in
sdk
api
everything
that
that
that
improves
the
like.
If,
if
somebody
like
knew
looking
at
the
open,
telemetry
python,
like
learning
about
like
propagator
provider,
exporter
otlp
like
whole
thing
can
be
little
overwhelming.
So
doing
this,
I
think
like
it
improves
the
the
experience
really
to
a
great
extent.
So
yeah
I
was
wondering,
what's
your
thoughts
on.
A
I
guess
so
it
seems
like
people
need
the
open
source
to
be
throw,
but
they
don't
know
that
they
need
it
right.
That's
more
or
less
issue.
A
All
right
can
we.
C
I'm
sorry
sorry,
I'm
here
I
have
a.
I
have
a
question:
do
you
have
a
sense
for
where,
where
people
are
entering
the
documentation
to
get
into
this
situation,
I'm
I'm
curious
because
if
you
look
at
the
like,
the
getting
started
guide
doesn't
actually
talk
about
all
auto
instrumentation
anywhere
right,
like
it
doesn't
talk
about
it
until
we
get
to
the
auto
instrumentation
examples
like
I'm
curious,
if
you,
if
you
get
a
sense
for
where
this
is
coming
from.
E
E
What
what's
their
usual
experiences
when
they,
when
they
look
at
the
getting
started
like
they'll,
have
to
learn
a
lot
of
concepts
like
you'll
have
to
understand.
Tracer
provider
propagate
exporter
like
this
this
this
can
be
like
a
lot
of
cognitive
load
for
them,
so
they
they.
They
don't
even
read
the
getting
started
guide
and
then
they
try
to.
You
know,
go
to
the
auto
instrumentation.
E
C
Yeah
yeah,
okay,
so
I
guess
maybe
maybe
the
thing
that
we
should
do
is
instead,
we
should
add,
like
a
section
of
how
to
get
started
quickly
like
as
part
of
our
getting
started.
Maybe
and
and
this
could
involve
the
stro
installation
and
using
auto
instrumentation
for
like
someone
who
just
wants
to
like
they
just
have
an
application
that
just
want
to
get
it
working
as
fast
as
possible
kind
of
thing,
because
I
think
you're
right.
The
getting.
A
E
I
I
do
not
know
like
I
I
I
don't
remember
if
there
was
any
reason
why
it
does
not
like
depend
on
distribution,
it's
yeah.
I
I
don't.
I
don't
remember
why
why
it's
the
case
but
but
open
telemetry
like
the
auto
instrumentation
command,
like
instruments,
bootstrap
install
like
observe,
like
these,
it's
useless
if
they
don't
install
the
distribution.
A
Yeah
because
it
kinda
looks
like
it
should
be
like
that
right
man,
yeah
srikanta,
would
you
like
to
open
up
a
discussion
about
this
so
that
we
can
keep
track
of
this
issue
somewhere.
A
Nice
see,
second,
is
there
something
else?
Would
you
like
to
discuss
about
this
topic.
E
A
All
right
cool,
I
think
we
don't
have
any
issues
in
our
agenda
today,
so
I
think
we
can
move
to
the
prs.
So
you
can
just
think
you
have
an
otlp
handler
related
vr
like
to
discuss
it.
C
Wait
one's
like
am
I
saying
that
daniel's
joined
the
meeting.
C
G
G
Thank
you
for
the
last
four
months
I
went
back
to
school
and
I
just
graduated
in
april.
G
G
Me
now,
I'm
I
mean
I
took
a
month
break
and
then
I'm
actually
back
at
aws
full-time.
So
I'm.
G
A
All
the
new
folks
danielle
here
used
to
contribute
to
this
project
some
time
ago,
and
he
made
some
big
amazing
contributions
very
glad
to
have
him
in
this
sick
again.
Are
you
planning
to
do
more
contributions.
G
A
We
will
definitely
have
a
bunch
of
stuff
that
we
can
assign
to
you.
So
that's.
A
All
right,
so
second,
would
you
like
to
discuss
europr.
E
Yeah
sure
so,
like
the
bigger
question
here
is,
do
we
do
we
want
this
this
handler
to
be
part
of
the
sdk
or
do
we
want
to
keep
it
as
a
separate
package?
I
I'm
inclined
to
keep
it
in
the
sdk
like
this.
There's
no
external
dependency,
like
it's
really
simple,
you
know
people
don't
have
to.
You
know,
find
it
another
package,
for
you
know
doing
something
very
common,
so
yeah
that
that's
what
my
thoughts
are
alex
has
you
know
this
question?
What
do
you.
E
B
A
Okay,
I
owe
you
a
review
on
this
pr.
I
haven't
still
taken
a
look
at
it,
but
I'll
definitely
try
to
do
this
today.
A
Alex
see
that
you
have
already
commented,
do
you
have
any
questions
or
comments
you'd
like
to
mention
now.
C
No,
my
the
only
question
is
already
npr
and
it
was
just
about
where
the
where
the
otlp
handler
should
go.
I
I
don't
know
that
we
have
anything
else,
that's
otlp
specific
in
the
sdk
itself
and
that's
why
I
was
asking
the
question,
but
I
don't.
I
don't
have
strong
feelings,
one
or
the
other.
A
Okay,
all
right
yeah
I'll,
definitely
take
a
look
at
this
pr
and
if
I
have
some
thoughts,
I'll
definitely
add
them
here.
In
the
comments.
A
All
right,
hey
by
the
way,
if
we
can't
excellent
progress
on
this
on
this
project,.
E
Yeah
so
once
once
this
gets
merged
in
I'll
I'll
be
I'll,
be
sending.
I
I
have
like
work
in
progress
for
log
processor
once
like
once
this
handler,
like
we
decide
on
like
if
this
goes
into
http.
If
you
want
it
to
be
software
package,
I'll
then
send
the
next
pr
for
the
log
processor.
Once
once
that's
run,
I
have
under
you
know,
ready
another
one
ready
for
otf
log
exporter
support
once
yeah.
E
That's
that
will
be
that
will
make
it
complete
and
then
remaining
work
will
be
above,
like
adding
extra
documentation
and
some
examples.
A
Perfect
all
right,
looking
great
somebody
else,
has
any
more
comments
on
this
topic.
A
Okay,
if
not
I'll
move
to
the
next
topic,
this
is
the
vr
all
right.
This
one's
mine,
I'll
share
my
screen,
real,
quick.
A
A
Right
so
prs
metrics!
Okay,
I
think
I.
A
Added
some
stuff
on
this
vr
and,
of
course,
it's
supposed
to
be
controversial.
I
added
a
bunch
of
classes.
I
wanted
to
explain
myself
a
little
bit
why
you'll
find
a
massive
amount
of
classes
here.
Okay,
as
I
told
you
before,
I
was
planning
on
having
the
this.
A
Grouping
and
synchronous
and
synchronous
by
the
classes
right
by
using
classes
right,
so
I
completed
that
part,
at
least
so
this
class
model
works.
I
have
tests
that
prove
that
they
can
inherit
and
there
any
methods,
work
and
everything
else
just
to
explain
myself
a
little
bit
better.
I
think
I'll
show
you
this
first.
This
is
a
table
that
shows
these
classes
that
we
have
for
the
instruments
and
how
they
inherit
from
synchronous,
synchronous,
adding
grouping
montana
and
finally,
they
all
inherit
from
these
main
class
instruments
right.
A
So
it's
summarizing
now
you
some
people
may
ask.
So
why
do
we
have
a
class
that
does
nothing
right
so
like
this
one
on
this
one,
this
one?
The
idea
behind
this
is
that
you
can
query
an
instrument
and
ask:
are
you
an
adding
instrument
or
your
grouping
instrument
and
by
using
this
instance,
you
can
figure
that
out
so
yeah
lots
of
code
being
added
here,
I'm
now
working
on
views.
A
A
C
A
Working
at
med
with
metrics
long
time
ago,
at
some
moment
I
had
the
need
to
know
if
something
was
grouping
or
not.
That's
how
I
came
to
this
idea
of
separating
this
into
classes,
so
I
think
the
need
is
there.
I
don't
remember
exactly
what
the
use
case
was,
but
it
was
a
use
case.
A
The
thing
that
led
me
to
design
things
in
this
way.
On
the
other
hand,
it
serves
some
practical
purposes,
because
you
can
just
put
common
code
in
one
class
and
you
can
it
minimizes
the
code
that
you
have
to
copy
and
paste
all
over
the
place
right
so
serves
like
that
specific
purpose.
H
Was
there?
Was
there
any
like
implementation
in
them?
It
looked
like,
for
instance,
like
the
grouping
clot.
They
were
just
like
marker
interfaces.
Right
sorry,
like
adding
grouping
monotonic
non-monotonic,
they
just
sort
of
have
they're
just
pass
faster
right
like
are
they?
Are
they
just
marker
interfaces
or
okay,.
A
H
A
Chilling,
no,
I
mean
I
pretty
much
wanted
to
let
you
know
people
how
things
are
going
so
that
you
can
take
a
look.
E
A
I
don't
know
if,
because
the
the
sdk
and
the
api
of
metrics
is
still
very
experimental
yet
so.
C
We're
gonna
hey
jacob,
have
you
have
you
had
a
chance
to
take
this
back
to
the
the
folks
that
are
working
on
the
metrics
like
riley
and
and
those
guys.
A
Yeah,
I've
shown
this
to
riley
before,
in
fact
he
he
commented
already
and
added
some
fixes.
I've
made
some
progress
after
after
that,
and
I
can
being
rally
again
to
show
these
implementation
with
multiple
classes
to
get
some
feedback
from
riley
as
well.
I
think
I
can
do
that
today
here.
C
A
What
else
what
else
yeah
somebody
else's
comments,
questions
about
this.
H
A
Is
and.
A
Increase
it
and
decreases
the
implementation
of
what
we
had
before
we're
adding
new
things
and
we're
also
removing
some
other
things.
For
example,
we're
we
will
not
have
in
this
implementation
because
of
the
bound
instruments
yeah,
so
that's
been
removed,
but
we're
already
in
some
new
things.
So
it's
a
bit
of
a
mix.
H
Yeah
yeah,
okay,
yeah.
I
think
what
alex
said
is
a
good
point.
Like
the
are
you
going
to
join
the
sig
today,
the
api
sdks,
the
metrics
yeah.
A
Yeah,
I
should
I've
been
attending
for
the
past
few
weeks,
so
I'll
be.
H
Yeah
yeah,
I
think,
because
I
think
they
sort
of
just
want
to
like
find
out
which
things
are.
I
don't
know
like
underspecified
or
problematic.
I
know
I
talked
to
like
my
co-workers,
doing
the
job
implementation,
josh
surett
yeah.
I
think
he
said,
there's
some
weird
stuff
with
like
the
locking
that
he
found
with
the
current
design.
H
So
I
think
there's
like
an
sdk
prototype
dock
that
has
like
three
main
components:
there's
like
instruments
and
then
there's
something
like
I
forget
what
it
was
called
like
something
processor
and
then
all
all
the
walking
was
happening
in
there.
Did
you
find
anything
weird
with
that.
A
A
H
A
All
right:
well,
this
is
our
our
last
topic.
Nobody
else
has
any
other
comments.
I
think
we
can
call
it
for
today,
new
people
there
is
a
slack
channel
in
the
cncf
workspace
named
hotel
python.
A
Our
general
conversations
are:
are
there
so
encourage
you
to
join?
If
you
have
any
questions,
please
feel
free
to
contact.
Any
of
us
we'll
be
happy
to
help
in
any
way
that
you
can.
G
A
All
right,
if
there
are
no
other
topics
well,
I
think
we
can
fully
done
and
wish
everybody
a
awesome
day.