►
From YouTube: 2021-02-04 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).
A
B
Yeah,
this
is
one
it
seems.
Last
week
we
had
a
small
quorum
and
I'm
starting
to
suppose
that
people
are
not
going
to
show
up.
A
A
A
Yeah
the
quest
yeah
there'll
be
a
third
meeting
yeah.
I'm
excited
to
see
about
progress
on
this
front.
B
Yes,
so
we
had
a
first
meeting
that
was
very
good.
There
was
the
presentation
I
think
I'm
alex.
I
think
he
is
from
like
step
right,
yeah,
that's
correct
yeah,
so
he
has
the
collector
extension
he
presented
to
us.
In
the
first
meeting,
the
folks
from
aws
presented
the
python.
B
We
have
some
extensions
that
came
from
actually
signalfx
and
there
is
a
lot
of
work
on
java,
okay,
but
the
discussion
basically
kind
of
stop
it
there.
You
know
last
meeting
we
didn't
have
the
top
folks
from
aws
and
then
we
we
did
them
kind
of
resolved.
We
discussed
some
stuff
shared
some
information.
A
Yeah
yeah,
I
haven't
been
totally
following:
I'm
not
totally
sure
how
much
beyond,
like
you
know,
we
created
the
python
example,
but
yeah,
I'm
not
sure
how
much
more
work
lifestep
is
is
planning
on
doing.
I
also
was
a
little
unclear
why
there
needed
to
be
a
lot
of
language,
specific
work
because
it
seems,
like
you
know,
the
the
big
part
is
like
getting
the
collector
working
as
an
extension
and.
B
Yeah,
I
I
think
I
think
also
that's
the
the
path
that
I
would
like.
My
understanding
is
that
there
is
some
limitation
because
of
the
way
that
they
do
freeze
and
shut
down,
but
if,
if
aws
starts
to
support
correctly
for
extension,
to
do
that,
then
I
think
we
should
really
go
for
that
path.
C
C
So
I
wasn't,
I
didn't
get
a
chance
to
get
here
last
week.
Did
we
review
any
of
the
documentation
that
we
went
through
a
little
bit
at
high
level?
Last
last
meeting,
I
guess
the
first
meeting.
B
I
I
didn't
receive
the
link
for
for
that
doc.
I
think
we
we
talked
about
and
we
didn't
get
the
link
to
the
doc.
C
C
Right
yeah,
I'm
trying
to
figure
out
where
my
team
is
they're
supposed
to
be
contributing
his
documentation
to
review.
A
Yeah
I
was
just
looking
for
an
update.
I'm
gonna
give
a
webinar
next
thursday,
with
nzar
about
some
lambda
stuff.
So
I
was
just
kind
of
curious
to
see
how
it
was
all.
D
D
C
Sorry
about
that
yeah,
so
status
for
lambda
is
pretty
much
on
hold
right.
Now.
We're
we're
working
on
a
lot
of
the
open,
telemetry
1.0
items
and
want
to
get
our
components
out
for
that.
We
still
have
the
we
still
have
the
python
implementation
that
we
haven't
actually
gotten
a
lot
of
feedback
about,
which
is
curious,
but
we
have
been
taking
a
stab
looking
into
some
of
the
javascript
implementation.
C
Is
language
specific,
but
it's
not
like
it's
not
too
specific
from
what
we
were
kind
of
diving
into,
especially
when
adding
the
hooks
into
the
various
auto
instrument,
library,
auto
instrumentations,
to
auto
auto
launch
the
open,
telemetry
language
sdk
seems
feasible
at
least
on
javascript.
It
seems
pretty
straightforward.
We've
taken
a
look
a
little
bit
into
a
wrapper,
that's
upsourced
on
java
as
well,
I'm
not
sure
if
anyone
else
here
has
actually
used
it
at
all.
Yet
I
haven't
heard
anyone
giving
us
feedback.
A
So
these
language,
specific
wrappers,
are
just
about
making
it
so
the
person
who's
writing
the
lambda
functions
doesn't
have
to
install
the
sdk
and
all
that
themselves.
E
Probably
more
than
that,
we
know
that
at
least
we
need
to
instrument
and
lambda
user
lambda
function
right.
We
can
implement
that
by.
We
call
that
empire
called
instrumental
by
raptor
right,
but
what
we
said
lambda
wrapper
actually
is
this:
that's
a
higher
layer
than
lambda
function.
Instrumentation.
This
wrapper
is
for
improving
improving
user
experienced.
E
So
in
this
report
we
can
add
more
functionality,
something
for
example,
we
can
initialize
open,
parameter
components,
for
example
we
initialize
provider,
because
because
collectors
endpoint
is
hardcoded
to
windows,
0.05
h6,
so
we
can
write
some
code
in
here.
For
example,
in
in
python
we
don't
use
a
facial,
we
don't
use
open
parameters,
auto
instrumentation.
We
use
another
solution,
because
this
solution
can
be
a
common
framework.
It
can.
It
can
be
used
also
in
javascript.
E
A
And
yeah
the
the
other
component
is
just
the
the
collector
extension,
but
that's
that's
separate
from
these.
These
language
wrappers
right.
E
C
E
A
Nice-
nice,
though
I
I
heard
I
know
there
was
some
hope
that
by
moving
stuff
into
an
extension,
it
would
be
possible
to
avoid
the
issues
of
freezes
disrupting
the
transmission
of
data.
But
then
I
was
hearing
more
recently.
That
sounds
like
that's
not
the
case,
like
extensions,
also
get
get
frozen.
Unexpectedly,.
E
Properly
yeah
well
even
lambda
does
not
know
that
in
next
moment
it
would
be
closer
or
not
right.
So
there's
no
way
to
receive
this
signal
and
the
laminar
cannot
say
that
before
I
phrase
I
want
to
send
a
signal
to
you,
you
give
me
response,
then
I
give
I
freeze
your
environment.
That's
too
slow.
That's
all
you
think.
A
Yeah
well
just
build
a
new
hypervisor
client,
os
programming,
language
and
web
framework
for
people
to
write
in
and
then
just
re-implement.
All
of
that.
So
it
can
work
properly
easy.
E
Yeah
so
lolita
is
not
here.
I
got
a
response
from
alolita
that
she
still
haven't
finished
the
talk.
Actually,
the
talk
is
finished,
but
but
we
think
before
public
said
we
need
to
polish.
E
Because,
probably
she
is
too
busy
and
the
doctor
is
ready,
I
I
know
but
adjust
the
she
don't
think
he's
a
good
time
to
share
share
with
you
and
from
from
our
side.
Last
week
we
began
to
implement
the
javascript
support,
but
due
to
some
strategy
reason
we
heard
that
in
community
they
are
going
to
release
1.0
right.
We
don't
want
to
release
the
long
run,
support
before
that.
So
we
pause
the
lambda
js
support
project.
E
D
I
know
the
last
at
the
last
sig
meeting
we
talked
about
where
to
code
to
live.
I
I
haven't
done
anything
in
the
repo
around
moving
that
code
around
is
any
thoughts
lay
or
apollo
around
getting
the
net
implementation
or
the
python
implementation
inside
this
hotel,
repo.
B
So
for
the.net,
I'm
I'm
kind
of
actually
in
kind
of
a
weight
mode
to
see
if
it's
worth,
because
we
really
our
preference-
will
be
kind
of
going
in
the
path
of
doing
the
the
extension
path.
But
we
depend
on
that
feature.
But
the
question
is:
do
do
you
want
to
do
that
investment
right
now
to
create
the
wrapper
for
net?
You
know
it's
not
clear
to
me
if
we
should
be
pursuing
that
or
not.
E
E
B
Okay,
so
in
that
case,
if,
if
anyone
one
works
with
us
on
the
dotnet,
it
will
be
good
for
us
to
create
perhaps
on
the
contributor
on
the
dotnet,
the
implementation
there.
You
know
there,
we
have
the
separation
of
projects
and
we
can
offer
that
as
a
new
get
package
that
what
is
needed
for
net.
E
I
can
only
see
that
from
aws
side
we
well,
we
have
no
enough
developer
yeah
so
for
lambda
support.
So
far,
only
one
developer
is
me,
but
now
I'm
moving
to
another
project.
So
now,
at
least
in
recent
three
weeks,
we
have
no
direct
help
on
the
net
number
yeah.
Sorry.
E
But
if
you
can't
submit
the
lambda
instrumentation
first
press.
D
B
Okay,
so
I'll
I'll
try
to
put
this
on
the
contributor
apple
for
dotnet
and
we
go
from
there
and
I
I'll
bring
it
to
the
group
when
it's
when.
E
E
Do
we
have
aws
folder
in
net
country?
I
don't
know
we
have.
B
There
is
for
the.net,
specifically,
there
is
the
contrib
wrapper
for
net,
and
since
there
is
a
red,
aws
client
there,
I
thought
that
was
the
natural
place
to
put
lambda,
also
in
the
same
local,
in
the
same
location,
cool.
B
B
E
I
heard
from
my
team:
he
is
working
on
the
donate
sdk
support.
He
said.
Photonic
language
is
very
special.
It
does
not
have
a
public
id
generator
api
right
hyper.
E
B
B
What
we
can
have
right
now
is
is
the
open
telemetry
working
by
itself,
but
then
there
will
be
no
integration
with
the
x-ray.
B
B
I
know
that
there
is
a
issue
actually
open
at
dotnet
runtime
to
provide
that
when
that's
done,
then
we
can
fix
that,
but
not
before
that's
done.
E
B
E
E
D
E
Yeah
so
yeah,
so
we're
still
reading
a
lot
of
talk
and
after
she
issues
it,
we
should
rename
the
repo
the
current
lambda
exchange
report
called
open,
telemetry
lambda
and
create
a
multiple
folder
there,
yeah
one
for
collector
and
the
other
for
every
language,
stp
languages
and
the
from
my
side
I
can
say
I'm
also
working
on
a
ci
cd
workflow
for
that,
but
this
clcb
workflow
is
just
for
our
downstream
repo
yeah
in
aws
observability,
not
sure
if
you
guys
know
that
my
idea
is
after
we
have
the
repo.
E
E
E
D
E
E
Oh
yeah
yeah.
I
want
to
say
that
the
reason
why
we
want
to
publish
the
layer
in
downstream
that's
because
we
want
to
add
aws
version
of
collector.
You
guys
may
know
that
it's
called
aoc
right,
probably
atoc.
E
I
don't
know
the
public
public
name,
but
basically
we
remove
some
of
exporter
from
collector
and
we
call
this
character
as
aw
version
aws
distro,
whatever
collector.
So
we
don't
want
to
package
a
regional
version
correctly
into
our
laminar
layer.
That's
a
wealth
reason.
E
I
have
no
experience
about
that
in
downstream
report,
because
this
this
report
is
fully
controlled
by
aws,
so
we
can
set
our
recommendation
here,
but
in
r3
I'm
not
sure
yeah,
but
I
think
this
can
be
my.
My
idea
can
be
a
common
generation.
Every
downstream
maintainer
can
create
their
layer,
publish
their
data
based
on
their
requirement.
D
E
The
second
reason
why
it's
hard
to
do
that
because
we
mentioned
before
the
current
collector
binary
is
too
big.
It's
more
than
100
megabytes
right.
That
means,
how
can
we
generate
a
level
a
layer
in
upstream?
If
we
build
a
large
layer,
I
think
it
would
block
some
user
onboard
open
telemetry.
So
my
idea
is
remember
last
meeting
we
mentioned
about
if
customers
can
build
a
layer
based
on
demand
based
on
his
configuration.
A
So
you're
preparing
bringing
in
like
a
build
tool
that
allows
people
to
yeah.
I
think
that's
actually
awesome.
E
A
A
E
Upstream,
we
provide
a
framework
build
to
let
users
build
their
layer
by
one
click.
So
if
you
see
the
current
python
solution,
that's
a
one
click
script.
You
just
need
to
type
wrong.
That's
all
that
it
can
build
the
lambda
layer
in
your
account,
it's
very
easy,
but
the
synthetic
user
has
to
set
up
a
amazon,
sal
sam,
it's
an
aws,
cli
tool.
If
customer
set
install
docker
and
the
same,
that's
all,
then
he
can
build
his
layer
by
one
click.
E
A
Sweet
right,
so
you
move
all
that
stuff
upstream
and
then
you
start
building
your
downstream
stuff
out
of
out
of
that.
That's
great
yeah
yeah,
especially
if
like
the
like
testing
and
security,
stuff
and
whatnot,
can
get
moved
up
stream
as
well.
Yeah,
yes,.
E
So
actually
I
have
this.
I
had
this
idea
more
than
one
month
ago,
probably
at
the
end
of
december,
you
know
only
things.
There
is
sorry
that
the
doctor
is
still
blocked
somewhere.
So
I
want
to
share
this
idea
with
you
guys,
first
before
we
release
that
look.
So
basically
the
talk
is
about
talking
about
this
topic.
E
A
B
So,
just
because,
when
I
mentioned
the
dotnet
contribute,
I
I
I
missed
this
part
about
creating
the
open,
telemetry
lambda,
using
the
same
one
that
we
have
the
extension.
E
D
So
I've
renamed
the
repo.
While
we
were
talking
about
this,
I
tagged
both
you
lay
and
paulo
on
the
issue.
Cool.
C
We
can
talk
about
something
a
little
bit
more
more
technically
interesting.