►
From YouTube: 2023-03-28 meeting
Description
Instrumentation: Messaging
A
B
Seems
like
we
have
a
good
representation
of
people,
we
can
keep
adding
some
agenda
items
for
the
next
next
couple
minutes.
B
Okay,
I
think
we're
ready
to
get
started
so
I
want
to
talk
first
briefly
around
the
Lambda
release.
Work,
so
I
want
to
give
I
guess
just
two
kind
of
resourcing
updates
to
our
side.
B
We
we
do
have
resources
assigned
to
the
JavaScript
and
python
instrumentation
layers,
so
we're
hoping
to
have
that
done
by
the
end
of
April,
and
we
have
some
contributor
out
of
offices
and
vacations,
and
things
like
that,
so
the
target
date
yeah
end
April,
ideally
kubecon,
but
not
holding
our
breath
on
that,
and
we
also
have
some
resources
dedicated
to
The,
Collector,
Standalone
layer,
I
think
we're
more
hopeful,
that'll
Land
by
kubecon,
but
once
again,
that's
kind
of
on
a
like
end
of
April
timeline,
probably
as
well
so
just
an
FYI
for
everyone,
the
first
kind
of
community
assets,
or
at
least
the
ones
we
have
resources
dedicated
to
that's,
like
the
timeline.
C
I
have
one
question:
so
I
was
looking
through
some
of
the
tooling
and
the
GitHub
actions
that
are
available
in
the
ADOT
repo
and
I
was
curious.
So
there's
a
you
know:
there's
a
bunch
of
integration
tests,
silk
tests
that
are
available
in
that
repo
and
I
was
curious.
If
this
is
something
we
wanted
to
pull
in
or
do
we
want
to
do
it
as
like
the
second
pass
at
getting
this
out,
I
just
I
I
think
it
would
probably
add
some
amount
of
complexity
to
the
overall
picture.
C
But
anyways
I
was
just
wanted
to
ask
that
question
here.
A
I
think
I
would
suggest
starting
just
with
getting
something
working
and
out,
and
then
the
soap
testing
and
the
like
can
be
pulled
in
if
we
find
that
there's
value
in
that
I,
don't
like
I
I,
don't
want
to
say
it's.
It's
not
super
valuable,
but
I
also,
don't
know
that
it's
identified
any
significant
issues
for
us.
A
D
A
The
tests
basically
take
the
sample
apps
that
exist
in
the
Upstream
repo
play
them
and
validate
that
traces
make
it
through
to
the
end
destination.
Okay,.
D
D
B
Yeah
makes
sense
cool
anything
else.
We
want
to
discuss
around
the
Lambda
release
stuff,
any
any
questions
we
have
for
the
group.
Anyone
also
dedicating
some
resources
to
this.
D
Cool
yeah
and
we
likely
tend
to
at
least
me
and
possibly
more.
B
All
right,
yeah
that'd,
be
great,
so
I,
think
Tyler
and
Alex
or
I
was
going
to
put
people
here
so
Tyler
and
Alex.
Just
so
y'all
are
aware
and
then
Martin
Cuba
JavaScript
there
you
go
Furtado
I,
think
double
check
that
python,
so
y'all
are
rare,
feel
free,
feel
free
to
reach
out
to
them
on
the
cncf
slack
or
anything
like
that.
B
So
another
kind
of
this
is
a
more
generic
question,
but
we
need
functions,
documentation
or
single
sorts
of
truths
for
like
lambdas,
for
Azure
functions
and
for
gcp
as
well.
Aaron
I
see
you're
on
the
call,
so
I'd
love
to
talk
about,
maybe
the
Google
needs
and
what
you
all
are
looking
to
do
from
your
perspective.
But
we
also
need,
as
far
these
releases
regulanda
stuff
documentation
as
well.
So
I
just
wanted
to
kind
of
call
this
out
as
a
major
item.
We
need
to
deliver.
E
Hey
so
I'm,
actually
here
for
in
place
of
David
ashbull
he's
usually
been
coming
here.
I,
don't
have
a
ton
of
context
here,
but
I
can
try
to
help
out.
However,
you
need,
but
do
you
think
you
could
give
me
some
sort
of
high
level
context
on
on
what
you
need.
B
Yeah
sure
so
this
is
like
this
was
previously
the
Lambda
group,
but
when
we
restarted
the
sick,
we
kind
of
rebranded
it
as
the
functions
as
a
service
kind
of
generic
sick
and,
of
course,
lambdas
are
very
important.
We
have
Community
assets
around
those,
but
there's
a
lot
of
open
customer
questions,
both
around
Azure
functions
and
gcp
functions
and
best
practices
is
kind
of
like
the
base
level
ask
of
like.
Is
there
documentation
available?
How
am
I
supposed
to
use
open
Telemetry
in
these
platforms,
then
there's
a
kind
of
another
question
of.
B
E
Okay,
got
you
and
is:
is
the
goal
to
like
compile
some
set
of
documentation
on
the
open,
Telemetry
site,
or
was
there
yeah
I?
Think
I
missed
I
heard
some
folks
talking
about
kubecon
as
well.
E
Oh
no
I,
I
think
I
forget
who
said
that,
just
like
five
or
ten
minutes
ago,
somebody
mentioned
having
something
together
for
a
cute.
B
Club,
oh
yeah,
yeah,
so
yeah
targeting
some
releases
around
kubecon
I
think
it'd
be
great
to
have
equal
function,
stuff,
I
I
doubt
we'll
have
the
Lambda
documentation
ready,
then,
just
because
we're
producing
the
community
assets
which
will
then
point
to
in
the
docs.
So
there's
a
little
bit
of
a
you
know:
dependency
train
there,
but
we
can
produce
Google
function,
documentation
by
Keep
Calm.
That
would
be
amazing
and
it
would
be
great
to
have
if
it's
relatively
lightweight
but
I'm
not
super
familiar
with
gcp.
E
B
Yeah
I'll
keep
calling
in
general,
it's
just
a
nice
time
to
announce
things
in
a
good
kind
of
date
to
you
know,
build
towards,
but
we're
not
yeah
super
unflexible
when
it
comes
to
stuff
like
this
so
Tristan
I
know,
you've
been
adding
a
bunch
of
kind
of
agenda
items,
even
though
you
can't
make
it
so
it's
great
to
have
you
to
actually
speak
to
these
in
person.
What's
going
on
with
you,
foreign.
D
Yeah
I
had
to
just
one
about
the
Telemetry
API
logs,
because
it's
sitting
there
and
hasn't
really
had
interaction
in
a
while
and
would
be
good
to
get
in,
so
logs
can
be
flowing
from
Lambda.
B
Yeah,
it
seems
like
no
one's
responded
since
at
least
February
20th,
so
I
think
this
is
an
ask
for
Alex
or
Anthony.
If
y'all
can
take
a
look
at
this
and
do
a
refreshed
review,
that
would
be
that'd
be
excellent.
When
you
all
the
time,
is
there
anything
Tristan
specifically,
you
want
to
draw
attention
to.
Besides
just
some
approver.
D
B
And
then
interesting,
I
think
you
raised
this
question
over
GitHub
or
over
slack
I.
Think
it's
a
good
one
and
we
should
probably
start
doing
some
more
around
it,
but
I
think
the
community
overall
is
trying
to
push
customers
towards
stack
of
overflow
or
users.
So
the
question
is
kind
of
like
how
do
I
want
to
approach
this
as
a
group
and
manage
that
process
too,
but
trust
him.
If
you
have
anything
else,
okay,
go
ahead.
D
Yeah
I
just
brought
it
up
because
there's
been
a
number
of
people
recently
asking
in
slack
in
the
hotel
functions
as
a
service
Channel
questions
that
are
specific,
often
to
languages,
so
I
mean
it's
easy
enough
to
ask
them,
but
we
shouldn't
even
really
ask
them
to
move
to
like
the
hotel,
Js
Channel,
because
those
are
really
for
development
of
Hotel
JS,
so
asking
them
to
raise
their
question
on
stack.
D
Overflow
is
more
in
line
with
what
the
community
has
sort
of
decided
would
be
best
to
get
those
channels
cleaned
up
to
be
about
development,
but
then
we
obviously
need
to
actually
also
be
checking
it
and
reading
them
and.
B
D
Idea
from
the
maintainers
meeting
was
for
each
Sig
meeting
to
spend
like
five
minutes
at
least
just
checking
it
for
questions
that
are
related
to
that
Sig
and
either
answering
them.
If
they're,
quick
or
you
know,
dulling
them
out
to
people
so.
B
Yeah,
that
makes
sense,
do
we
have
an
opinion
as
a
Sig
on
if
we
should
have
a
specific
tag,
so,
like
Anthony
I,
see
like
this
AWS
Lambda
tag,
but
I'm
not
sure
if
we
want
to
like
points
people
or
ask
people
to
like
submit
questions
with
certain
things
for
us
to
find.
A
Yeah,
that
was
just
a
a
query
that
I
did
trying
to
look
for
issues
and
when
I
used
Lambda
as
the
tag.
There
was
a
note
at
the
top
saying:
don't
use
this
for
AWS
lamb
to
use
AWS
Lambda
so
apparently
stack
Overflow
has
opinions
on
that,
but
I
don't.
B
Yeah
interesting,
okay,
so
I
guess
the
let's
copy
this
over
to
our
notes.
B
Okay,
four:
any
other
topics,
comments,
concerns,
jokes,.
B
I
want
this
golden
great
well,
we
can
go
ahead
and
call
this
meeting
here
thanks.
Everyone
for
joining
some
follow-ups
are
just
around
the
release,
tooling
and
resourcing
in
general,
for
the
the
relevant
layers
so
feel
free
to
reach
out
to
those
contributors
or
myself
to
get
connected.