►
From YouTube: 2022-07-27 meeting
Description
OpenTelemetry PHP SIG Meeting
A
D
D
B
B
Yeah,
so
with
this
I
am
facing
one
issue
as
well,
since
the
other
two
b3
single
header
and
b3
multi-editor.
They
are
both
singleton
glass
there's.
The
code
coverage
is
not
100
because
of
the
way
the
order
in
which
the
test
cases
are
running.
I
have
posted
the
issue
in
the
channel
as
well,
so
maybe,
if
somebody
can
have
a
look-
and
let
me
know.
C
B
B
C
B
That's
this
was
regarding
the
pr
second
thing
I
wanted
to
discuss
was
about
the
auto
instrumentation.
So
the
issue
is
we
are
going
for
beta,
but
we
are
not
targeting
auto
instrumentation
in
that.
So
the
question
that
I
had
is
maybe
going
down
the
line.
We
would
have
what
instrumentation
for
framework
by
somehow
using
the
functionalities
that
the
framework
provides.
Have
we
thought
about?
B
How
are
we
going
to
auto
instrument
extensions
so,
for
instance,
if
we
have
mysqli
or
call
extensions
enabled
in
php,
is
there
any
plan
to
monitor
or
instrument
that
as
well?
That
was
going
to
be
my
question.
If
anyone
has
any
suggestions
or
something
please
otherwise,
I
can
bring
it
up
in
the
next
segmenting
as
well.
E
E
We
discussed
with
bob
also
last
sig
meeting
right,
so
it
would
be
good
in
next
meeting
if
timo
and
bob
is
also
there
yeah.
I
have
some
of
the
document
and
the
proposal
and
the
problem
statement.
All
the
things
are
presented
to
everyone
so
that
people
have
your
thought
process
in
front
of
them,
and
then
people
can
comment
down
and.
E
B
D
B
E
Extensions,
so
we
have
some
of
the
prior
thought
basically
again,
based
on
the
experience
of
some
proprietary
solution
which
app
dynamic,
cisco
has
developed.
So
we
would
like
to
bring
those
experience
and
also
open
it
up
with
the
community
in
case
they
have
some
ideas
or
something,
but
one
of
the
challenges
probably
which
kitchen
will
talk
about.
There
is
definitely
the
thought
process
is
coming.
Developing
auto
instrumentation
solution
by
c
plus
plus
technology
would
be
much
busier
and
wiser
than
looking
that
from
the
php
technology
perspective.
E
But
we
don't
have
the
background
when
this
hotel
php
has
started
earlier,
whether
there
is
any
other
additional
thoughts
also.
So
that
is
the
whole
point
of
bringing
this
problem
statement
in
front
of
everyone,
so
you
guys
can
again
think
about
it
in
case
you
guys
have
thought
about
something
previously
and
then
let's
have
a
open
discussion.
D
E
D
E
It
will
be
good,
definitely
put
down
your
thoughts
and
some
of
the
other
things
which
you
have
discussed
with
sanchez
number
in
a
document
so
that
it's
available
in
front
of
everyone
and
then
additional
input.
We
will
be
adding
into
that
document
and
making
that
as
a
running
and
more
like
a
exploratory
document
about
this
auto
instrumentation.
D
F
A
F
Yeah
yeah,
so
actually
I
I
didn't
add
them.
It
was
previously
there
also
that
my
only
thing
is
that
I
didn't
change
it,
so
I
used
all
the
status
code,
which
was
already
considered
as
a
retriable,
but
I
know
I
I
went
through
the
specification
that
you
have
provided
in
the
your
comment
and
in
that
from
that
specification
it
looks
like
this
three
retrieval
codes
or
three
three
status
codes
are
not
retriable,
so
I
mean
do
you
want
me
to
remove
in
the
same
here.
F
F
A
F
A
F
F
C
I
have
reverted
my
changes
according
as
you
said,
and
basically
now
I
wanted
to
ask
whether
the
this
last
comment
of
yours,
where
you've
written
we
could
simply
remove
the
special
handling
of
the
empty
batch
and
is
empty
function,
and
our
span
process
is
called
span
export
with
non-empty
batch.
So
will
there
be
a
case
where
span
exporter
export
will
be
called
with
an
md
batch.
A
C
D
D
D
B
B
E
D
E
E
C
E
E
E
Keeping
finger
cross,
probably
in
a
week
two
everything
should
be
done
and
then
we
should
be
ready
with
the
video
if
nothing
more
comes
up
from
the
community.
So
let's
have
this
discussion
also
in
the
next
meeting
again
and
then,
as
a
team,
we
will
have
the
full
visibility
about
the
release
if
it
is
going
to
go
very
soon.