►
From YouTube: 2023-02-01 meeting
Description
Instrumentation: Messaging
B
A
C
C
B
B
B
C
B
B
B
The
customer
uses
laminas
to
generate
PDFs,
and
so
they
see
a
lot
of
overhead
with
the
current
open,
Telemetry
instrumentation.
They
they
were.
They
weren't
clear
on
whether
it
was
The,
Collector
or
the
instrument.
Auto
instrumentation
network
was
causing
the
cold
start,
but
I
think
it
was
Anthony
that
said
that
it's
very
likely
the
instrumentation,
because
the
collector
doesn't
seem
to
according
to
his
calculator,
his
testing,
The
Collector,
doesn't
seem
to
cause
a
significant
amount
of
overhead.
B
A
C
B
A
B
A
B
C
C
And
maybe
there
are
some
points
here
that
that
we
can
discuss
improving
and
so
I'll.
Just
go
right
to
the
point.
So
I
think.
As
we
understand
the
the
current
system
has
the
the
version
of
the
opportunity
collector
that
is
compiled
specifically
for
for
running
here
in
the
Lambda
layer,
and
then
we
have
the
open,
Geometry
SDK
and
using
forward
slash
at
the
end
of
the
of
the
Lambda
Handler,
to
make
sure
that
the
the
data
is
is
exported
and
as
I
understand
it.
C
Currently,
first
flash
sends
the
the
the
data
to
The
Collector
and
then
synchronously.
We
have
the
collector
exporting
it
to
whatever
is
configured
x-ray
or
anything
else,
and
so,
if
I
understand
right.
Currently
just
said
here
that
everything
is
in
the
same
thread,
so
the
Lambda
code
will
not
terminate
until
the
the
data
is
flushed
to
the
to
the
back
end,
and
unless
there
is
some
timeout
and
so
first
of
all,
I
just
want
to
make
sure
that
I
understand
it
correctly.
C
Okay,
so
it
in
that
case,
I
I,
wasn't
sure.
Why
do
we
need
a
collector
at
all,
because
how
different
it
is
if
the
flashing
was
directly
to
to
the
back
end,
if
it
supports
the
the
the
export
like
an
exporter
for
the
SDK
or
otherwise,
to
another
opportunity,
collector
that
can
run
anywhere
else,
and
then
he
will
push
it
with
a
custom
exporter
to
wherever
needed.
B
So
my
my
thought
on
that
is,
there's
a
big
difference
between
sending
those
traces
to
a
local
ex
of
the
local
collector.
That
should
be
a
relatively
fast
operation,
but
if
we
are
trying
to
send
those
to
a
remote
system,
the
delay
in
sending
those
traces
or
or
whatever
data
can
be
a
lot
more
expensive.
Especially
if
you
have
you
know,
network
issues.
B
C
C
So
this
is
why
I
think
that
it's
currently
where
it
currently
worked
like
that,
and
so
there
is
some
it's
mentioned
here-
that
ideally
we
would
have
more
wanted
that
the
The
Collector
could
have
some
kind
of
event
callback
and
then,
if
he
didn't,
he
didn't
send
the
data
it
will
check
again
after
60
seconds
or
so
and
and
then
send
it.
But
currently
it's
not
possible
in
Lambda.
Unfortunately,.
A
A
C
And
I
I
can
also
say
that
in
in
apps
again
we
also
did
quite
the
same
thing.
I
mean
we
just
we
just
had
to
to
send
the
data
at
the
end
of
the
invocation
and
and
yeah
it's
it's
at
the
invocation
time.
I
guess
that's
the
best
solution
that
we
can
do
is
to
just
propose
the
customers
to
run
an
opportunity
collector
as
close
as
possible
and.
C
No
yeah
in
separate
friends,
but
like
probably
a
container
in
the
same
region,
same
AWS,
account
and
maybe
I,
don't
know
same
availability
zones
and
but
yeah.
If
we
would
love
that
I,
don't
know
exactly
like
what
what
this
recommendation
should
look
like,
but
something
like
that
and
yeah,
and
maybe
also
we
because
there
is
this
problem
with
Lambda.
We
can
propose
some
kind
of
configuration
where
the
data
is
sent
asynchronously
and
there
is
a
risk
that
some
of
it
won't
be
sent
and
maybe
for
some
customers.
C
B
B
B
A
B
B
B
I
mean
this
is
probably
also
related
to
the
this
next
issue.
Semi-Related.
So
apparently
in
the
various
languages
we
have
tracing
being
flushed
properly,
but
the
the
metering
data
might
not
be
flushing
at
the
end
of
the
function
properly.
So
that
is
something
that
should
probably
be
evaluated
for
each
of
the
languages.
A
C
B
C
B
What's
it
the
specification
updates
for
Lambda,
specifically
around
x-ray
propagation
changes?
That's
something
that
it
we
feel
like
we're
at
a
good
State,
where
we've
mostly
come
to
agreement
on
how
to
proceed
with
that
and
I
think
we
just
need
somebody
to
actually
make
the
document
change.
So,
if
either
of
you
are
interested
in
in
doing
that,
let
me
know.
C
A
C
C
No
I
what
sounds
like,
maybe
a
bit
confusing
for
me-
is
that
I
I
guess
it's.
It's
quite
rare
that
you
actually
need
like
have
a
spell.
A
parent
spend
like
both
department
and
spend
link.
So
like
I
mean
it's
possible
that
you
have
the
X-ray
propagation
and
actually
it
won't
connect
to
any
other,
spend
right.
B
I
I
think
it's
possible.
I
mean
the
the
ultimate
problem
here.
I
think
is
that
you've
got
spans
being
reported
to
two
different
systems
right,
so
the
X-ray
spans
that
is
created
by
x-ray,
inherently
is
going
to
report
to
X-ray,
and
then
the
the
the
regular
span
is
going
to
report
to
whatever
tracing
system
is
configured.
C
I
mean
I,
guess
that
if
the
user
configured
like
another
kind
of
propagation,
so
if,
if
that's
work,
that
should
be
good
for
Excel
as
well.
No
sorry
could
you
repeat
that
I
mean
if
the
user
did
config
another
context,
propagation
for
the
Lambda
which
actually
works,
so
if
this
spans
will
be
ingested
to
x-ray,
that
should
work
there
as
well
right,
yes,
so
in
in
what
case?
Do
you
think
that
having
the
X-ray
link
like
will
will
will
help
this
user.
B
I,
personally,
don't
understand
what
that's
for
it's
something
that
AWS
wants
to
have
the
the
environment
variable
propagation,
so
I
assume
they
have
reason
for
it.
You'll
have
to
ask
them
specifically
what
distinction
that
makes
having
it
as
the
span
link
was.
Some
was
I,
guess
the
the
consolation
that
they
were
okay
with
so
I,
don't
want
to
argue
with
them
too
much
on
that
okay,
I.