►
From YouTube: 2023-01-11 meeting
Description
OpenTelemetry PHP SIG Meeting
B
B
D
D
Yeah
so
I
work
for
elastic
I
work
on
the
dynamically
typed
APM
agents,
team
I
used
to
work
on
the
Ruby
agent,
but
now
I'm
the
team
lead
so
part
of
that
team
includes
PHP
and
otel
is
becoming
more
and
more
important
to
us.
So
I'm
just
going
to
be
a
fly
on
the
wall,
just
curious
to
see
what
kind
of
things
you
discussed
in
this
meeting
and
how
it
could
fit
into
the
strategy
that
we
have
for
the
APM
agents
at
elastic
I.
Think
one
of
my
colleagues
will
join
as
well.
D
A
D
E
D
D
E
A
A
F
F
F
So
right,
you
have
fun
from
you,
have
a
PR
today
from
for
disabling,
auto
instrumentations.
You've
already
started
talking
about
this
one,
so
let
y'all
continue
down
the
path
traveled
there,
and
then
it
looks
like
right.
You
made
a
it
looks
like
he
made
a
comment
on
this.
One
snow
and
looks
like
it
would
be,
would
be
quite
all
right.
C
F
E
E
F
B
So
so
that
is
important
from
the
usability
and
easy
of
use
so
or
we
we
can
prepare
a
specific
composer
and
Json
that
will
have
all
the
dependencies
to
install
not
only
extension,
as
I
said,
but
also
SDK
and
so
on,
but
also
other
ways
to
have
some
kind
of
I
don't
know
script,
as
is
shown
here
on
this
issue
that
we
will
install
everything
together
with
the
extension.
So
so,
what's
your
opinion
on
that.
F
Yeah
I
think
that
this
is
a
great
place
to
discuss
that
this
I
think
that
initially,
like
anything,
that
we
can
do
to
make
the
developers
experience
easier,
is
good.
I
think
I've
asked
scripted
a
fun
start.
I,
don't
know
what
our
best
practice
would
be
long
term
for
this
I
think.
Maybe
we
should
you.
B
So
when
we
will
have
this
extension
on
this
big
class
storage,
we
will
be
able
to
install
it
via
composer,
but
that's
only
extension,
so
we
will
need
to
also
install
other
packages,
and
so
my
view
is
that
we
should
be
able
to
do
that
in
it.
It
would
be
the
best
to
have
only
one
command
to
do
all
these
things.
E
C
B
G
E
E
F
B
F
E
H
B
H
B
F
B
B
E
B
E
F
F
E
A
F
E
Just
for
me,
I'm
just
just
wondering,
is
there
anything
else
we
can
be
doing
to
advertise
the
fact
that
we're
in
beta
now
you
know
to
to
see
anyone
outside
of
this
room.
No,
that
we're
you
know,
we've
reached
another
stability
Milestone
and
we're
sort
of
looking
for
the
final
testing
and
Bug
fixing
before
we
stamp
it
as
stable.
F
F
A
B
B
B
H
H
B
B
H
H
F
F
So
this
is
the
rest.
This
is
like
the
specification
as
it's
written
by
the
open,
Telemetry
TC,
the
technical
committee,
so
they
review
this
on
Cadence
and
makeup
roots
to
it
or
whatever,
and
the
API
and
the
SDK
live
in
the
we
just
got
the
main
repo
or
the
root
repo
or
whatever
that's
open,
symmetry
PHP
and
then
contribute
is
stuff
like
I
work
at
Amazon,
X-ray
and
I
want
to
and
I
want
to
be
able
to
easily
integrate
open,
Telemetry
PHP
into
Amazon
x-ray.
F
That's
where
that
lives,
so
it
sort
of
leaves
a
separation
between
the
main
API
and
SDK
and
the
all
those
third-party
libraries.
But
we
have
a
cup.
We
have
a
couple
Integrations
there
in
our
in
the
contribute
Pro.
If
you
look
at
some
of
the
other
things
they
have
hens
or
hundreds
with
them.
So
that's
it
and
then
instrumentation
is.
H
C
D
It
wasn't
stupid
so
each
of
these
repos
they
don't
have
the
same
exact
Declaration
of
what
version
of
PHP
to
support.
So
the
open,
Telemetry
PHP
says
that
it
requires
a
PHP
version
of
seven
four
plus
and
then
PHP
instrumentation,
says
eight
plus.
So
what
and
I
mean
I
understand
that
it
says
that
it's
instrumentation
is
based
on
the
Observer
API.
So
that's
why
it
requires
a
plus,
because
that,
from
my
understanding
it
was
only
available
in
a
plus.
So
what
do
you
not
have
like?
D
E
So
there's
an
important
distinction
between
Auto
instrumentation
and
just
user
land
instrumentation,
so
the
extension
just
provides
books
so
what
we
call
the
hook,
which
is
that,
if,
if
this
method
runs
create
a
span,
you
know
run
this
code
before
it
and
run
this
code
after
it,
which
we
used
to
start.
It
start
a
spanner
and
despair
and
that's
a
part
of
a
trace,
but
that
the
actual
all
of
the
work
to
start
sparing
in
the
span
export
it
is
delegated
to
the
main
instrumentation.
E
F
As
an
end
user,
if
you
have
the
ability
to
use
Auto
instrumentation
or
to
slam
dunk,
because
we
don't
have
to
instrument
your
code
but
for
instance,
if
you're
using
php74
or
you
have
you
know,
custom,
PHP
library
or
you
know
whatever
it
might
be,
you
might
have
to
use
the
base
the
base
repos
really
meant
for
Developers
and
like
instrumenting
things
manually
like.
Ideally,
everything
would
be
auto-instrumented,
but
that
would
be
very,
very.
I
I
B
B
H
A
H
H
H
And
by
the
way,
I
don't
want
to
discourage
you,
but
I
tried
many
times
in
my
past
to
write
extension
in
more.
You
know
high
level
language
there
rather
than
C,
but
I
fail
each
time.
So
if
you
go
deeply
inside
that
Zen
engine,
you
have
some.
You
know
issue
but
again,
I
didn't
check
deeply
the
PHP
instrumentation,
yet
I
mean
the
code.
So
maybe
it's
potentially
you
can
do
that.
H
B
H
Not
really
I'm,
looking
forward
to
test
this
library
with
some
projects,
specifically
the
one
here
that
I'm
maintaining
for
the
last
click
that
is
elasticsearch
PHP,
so
I
would
like
to
instrument.
You
know
this,
this
Library
and
also
testing
the
automatic
with
the
xmlop
server
that
I
didn't
test
it.
Yet.
So
it's
a
good
way
for
me
for
for
testing.