►
From YouTube: 2022-09-07 meeting
Description
OpenTelemetry PHP SIG Meeting
B
C
B
Good
few,
a
couple
of
new
ones,
just
a
broken,
build
from
me,
which
I
think
it's
just
a
php
stand,
update
bob.
If
you
could
just
approve
that
one,
I
think
it's
a
pretty
simple
one.
This
one
was
me
as
well.
I've
started
testing
out
against
8.2
since
it's
gone
to
release
candidate
now
I
think
you
might
expect
it
to
go
live
in
two
or
three
months.
B
B
C
A
C
B
B
I
don't
know.
What's
what's
happened
to
this
guy?
It's
not
important,
and
some
kent
is
not
here
to
talk
about
this
one,
just
getting
getting
kind
of
old,
let's
jump
over
to
control,
because
so
this
one
is
still
demo
prototype
code
just
skip
over
that
one
carol
has
been
in
contact
with
me
today
and
has
completely
reworked
this
into
a
much
less
dodgy
non-monkey
patching
version
which
looks
better.
She
just
needs
to
fix
up
some
tests,
and
then
we
can
go
ahead
and
merge
that
one.
B
C
C
B
B
It's
it's
not
meant
to
be
performant,
although
those
numbers
are
really
horrifyingly
bad.
I,
but
I
also
don't
know
yet
so
step
one
get
them
to
switch
over
to
the
c
extension.
If
that
makes
the
problem
go
away,
then
I'm
probably
happy
I'm
I'm
kind
of
curious
as
to
where
some
of
these
numbers
come
from,
because
they
do
seem
insane.
But
I
don't
know
I
don't
know
how
protocol
works.
I'm
also
not
keen
to
debug
it.
If
I
can
at
all
avoid
it.
C
I
also
wonder
if
they're,
using
the
most
recent
version
of
both
our
library
and
google
proto
buffer,
we
we
had
problems
with
that.
It
worked
when
we
used
to
see
extension.
But,
yes,
I
think
I
have
a
very
strong
feeling
that
they
that
they
are
if
they
use
the
c
extension
they'll,
be
in
much
better
shape.
C
C
B
C
B
B
C
A
B
B
B
C
A
Yeah,
so
this
is
regarding
the
reviewers
here,
so
I
have
put
in
link
to
the
hotel
js
as
well
what
they
do.
They
have
created
teams
in
the
open,
telemetry
space
for
you
know,
because
we
have
php
approvers.
Similarly,
they
have
javascript
approvers
and
rather
than
putting
the
individual
ids
in
our
code
owners
file
in
our
repo,
they
just
put
a
link
to
that
teams.
So
whatever
changes
you
make
there,
those
will
be
reflected
in
the
reviewers
when
a
new
pr
is
raised.
So
I
was
just
wondering:
should
we.
B
A
C
C
B
Take
that
as
yes
right,
so
so
what
I'm?
What
I'm
seeing
on
the
on
the
on
the
slack
channel
is
that
most
people
that
really
like
what
they
see
with
with
devices
extension
as
it
is
now
and
I've
certainly
played
with
it
and
I'm
quite
happy
with
at
least
with
how
easy
it
is
to
to
use
so
where
to
next.
I
know
that
priscilla
was.
I
thought
that
that
was
the
way
to
go.
A
No,
I
think,
tobias
approach
is
quite
it's
very
efficient.
I
would
say
basically
the
extension
that
he
has
created.
It
allows
us
to
hook
any
basically
auto
instrument,
any
function
that
we
want.
So
all
now
we
have
to
do
in
open,
telemetry,
php
country
brepo
is,
you
know,
create
the
pre
and
post
callable
hooks
post
followable
functions
for
any
anything
that
we
want
to
instrument,
and
I
believe
you,
you
have
done
the
same
right
right.
A
B
A
B
I
yes,
yes,
so
there's
a
couple
of
things
we'll
need
to
to
decide.
One
is:
is
device
happy
to
to
contribute
that
extension
over
into
open
telemetry
and
then
we
need
to
worry
about.
You
know:
where
do
we
store
it?
How
do
we
build
it
and
publish
it?
There's
there's
quite
a
bit
to
to
talk
about
there
and
then
I
think
you're
you're
right
amber
that
we
would
probably
look
all
those
different
instrumentations
over
in
in
contro
feels
like
the
right
place
for
them
to
live.