►
From YouTube: 2022-07-12 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
B
B
But
there's
a
whole
lot
of
plants
and
we
have
a
garden
and
orchards
there's
a
lot
of
like
fruit,
trees,
fruit,
bushes
and
stuff,
like
that,
like
raspberries,
strawberries,.
B
I
put
anything
on
the
I
either.
B
A
At
yes,
I
looked
at
this.
The
one
thought
I
had
here
was
about
peer.
C
A
Attributes
extractor
and
whether
that's
even
needed
for
library,
instrumentation.
B
Yeah
it's
funny
because
it
was
in
the
jaffa
agent
instrumentation
api
artifact
in
the
first
place,
but
then
we
move
it
to
the
library
instrumentation
api
yeah.
It's
probably
not
needed
at
all.
I
think,
although
I
like
I'm,
not
really
opposed
to
leaving
it
there,
I
mean
the
instrumentation
api
as
it
is
now
because
well,
it's
still
the
unstable
part
of
the
of
the
instrumentation
api
for
one
thing
and
it
kind
of
reflects
the
spec
I
mean
the
peer
service
is
mentioned
in
this.
B
I
guess
something
that
you
might
want
to
do
and
well
there's
an
extractor
for
the
view.
B
For
some
reason,
we
should
use
a
map
instead
of
just
setting
a
peer
service
attribute
so
yeah
we
could
move.
A
Yeah,
do
you
remember,
did
you
happen
to
notice
what,
when
we
moved
it
and
why
we
moved
it.
B
B
Have
been
one
that
thing
and
the
other
thing
that
we
wanted
to
use
it
like
the
telemetry
builders
themselves
and
you
know
not
to
have
not
to
be
forced
to
inject
it
in
the
java
agent.
But
that's
what
I
ended
up
doing
anyway,
and
it's
not
so
much
trouble
so.
C
C
A
C
A
Okay,
I
didn't
season
two
I
just
finished
watching
for
like
the
third
time,
and
one
of
the
the
characters
asks
a
couple
of
times
like
is
this
now
because,
like
like,
and
the
whole
second
season,
like
jumps
between
different
times,
so
you
just
get
really
lost,
which
is
why
I
had
to
watch
it
so
many
times.
But
yes,
I
feel
like
that.
Now
I
already
read
this
like
yeah.
I
was
just
about
to.
A
It's
really
good
yeah
yeah,
so
they
had
a
the
third.
The
first
two
seasons
were
really
good.
I
highly
recommend
the
third
season
was
was
so
so
and
they
just
came
out
with
a
fourth
season.
So
that's
why
I'm
going
back
and
re-watching?
Okay.
B
B
B
Service
method
that
if
it
was
called
it
said
a
constant
attribute
extractor
that
extracted
the
constant
that
was
provided.
But
if
it
wasn't
set
in
the
library
instrumentations,
then
the
fallback
would
be
to
just
use
the
pure
service
extractor,
which
used
the
config
mapping.
B
A
A
So
if
we
move
did
do
we
have
anything
that
resembles
this
outside
of
the
instrumenter
api
I
mean:
do
we
even
have
a
place
for
it
to.
A
Okay,
so
I
guess
the
the
next
question
then
it
would
keep
it
in
instrumentation
api.
Do
we
want
to
hook
it
up?
Oh,
I
guess
that
makes
all
of
those
other
questions.
I
guess
that
makes
that
kind
of
irrelevant.
Once
we
have
it
there
yeah
we
may
as
well
use
it.
A
A
Cool,
I
will
look
back
I'll
finish.
Reviewing
this
then,
as
is,
I
think
you
had
a
couple
pr's.
Do
you
need
this
one?
Do
you
have
any
work
pending?
On
top
of
this
one.
B
B
A
And
you
have
a
couple
of
so
this
one,
I
think,
is
really
important.
Was
there
anything.
B
Yeah,
oh
there's
the
yeah
I'll
create
a
iron
issue
on
that.
Okay,
because
I
mean
it's,
it
turned
out
fine.
In
the
end
I
mean
that
we
don't
really
need
the
no
web
api
functionality
at
all.
It's
there
in
the
sdk.
B
I
had
one
topic,
I'm
just
like
mostly
a
theoretical
topic,
which
is
motivated
by.
C
B
B
So
the
user
here
reports
that
really
you
said
related
to
which
pr
the
kafka
matrix
pr
by
jack,
okay,
yeah,
so
the
user
here
has
some
has
had
some
issue
with
micrometer
which
he
disabled,
but
it
ended
up
not
being
disabled,
because
there
is
another
instrumentation
that
does
the
same
thing.
If
you're
using
spin
like
this
pink
autoconfigure,
instrumentation
and
yeah,
there's
a
long
story
here
and
lots
of.
A
B
Yeah
yeah,
the
actuator
and
the
most
important
part
that
I
wanted
to
touch
upon
today
is
the
last
command
here.
So
the
user
suggested
that
hey,
if
like
metrics,
are
turned
off.
Then
why
enable
this
this
instrumentation
at
all
and
this
the
connection
to
like
jack's
pr
here
is
that
do
we
want
to
sort
of
have
separate
instrumentations
for
metrics
and
traces,
or
you
know
separate
ways
of
turning
on
and
off
a
signal
like.
B
Do
we
want
to
use
the
same
instrumentation
module
as
the
current
kafka
instrumentation,
or
do
we
want
to
have
a
separate
ones
so
that,
for
example,
you
might
want
to
turn
on
kafka
tracing
by
kind
of
metrics
or
the
other
way?
If
you
don't
want
kafka
tracing
it,
because
it's
crappy
and
you
want
to
implement
it
yourself,
but
you
do
want
to
have
the
agent
export
the
metrics.
A
Yeah,
so
I
think
there's
a
couple
of
a
couple
of
things
there,
one
the
if
exporter
is
none,
I
think
they
were
discussing
like
that,
could
be
handled
in
the
auto
configure
itself
and
no
op
the
the
whole
metrics
sdk.
C
A
And
then
right,
you
wouldn't
get
those
warnings
you
would.
It
would
be
essentially
more
or
less
the
same
as
if
we
turned
off
that
instrumentation.
B
B
I
mean
I
kind
of
understand
the
reasoning
behind
that,
but
it
still
might
be
unexpected
that
your
your
no
op
metrics
api
is
not
really
know
what.
A
A
A
B
I
I
will
check
the
spec.
I
I
open
it
right
now,
but
it's
kind
of
huge
and
it's
hard
to
parse
it
like
in
in
two
seconds.
So
there
is
some
instrument
naming
your
paragraph
in
the
api
doc,
but
I'm
not
sure
if
you
know
it
says
that
api
should
validate
or
the
implementation,
so
yeah.
A
So
yeah
and
it's
okay,
if
the
api
validates,
I
guess,
but
if
there-
and
maybe
that's
a
general
thing
with
no
op
sdk,
because
what
the
generally,
what
the
s
the
api
will
do
right.
If,
if
it's
invalid,
they
don't
throw
exceptions,
so
they'll
return
a
no
op,
timer
builder
or
something
anyway.
A
So
in
this
case,
since
it's
a
no
op
sdk,
they
were
going
to
return
that
anyway.
So
it's
the
point
of
validate
validating
or
logging
that
validation.
C
A
But
that
doesn't,
but
you
were
asking
a
more
general
question
also
about
with
people.
B
Yeah
that
was
just
a
pretext.
I
mean
the
yeah
for
the
for
the
more
general
question
like
do.
We
want
to
have
a
way
to
like
disable,
select
or
all
matrix
instrumentations,
because
yeah
I
mean,
even
if
the
sdk
stand
of
the
instrumentation
might
have
some
side
effects
like
even
injecting
the
meter
register
into
spring
may
make
it
behave
slightly
differently,
because
there's
a
complete
material
just
printed
now
and
so
on.
A
Wouldn't
we
that
one
we
would
disable.
I
mean
like
the
metrics
registry
kind
of
a
thing.
Like
so
say
kafka
I
mean
as
far
as
turning
off
metrics.
Turning
on
and
off
metrics.
A
I
thought
that
the
way
the
the
ideal
way
to
do
that
would
be
through
views
and
or
metrics
filters,
or
something
like
that
where
people
are
because
people
are
going
to
definitely
want
to
tune
what
metrics
get
emitted
a
lot.
A
A
Sorry,
I'm
super
stingy
on
configuration
option,
adding
configuration
knobs.
B
Yeah,
I
know
and
we're
I
mean
I
kind
of
dived
into
a
new
territory
here,
because
we
weren't
really
even
thinking
of
like
splitting
limitations
by
signal
before
so.
C
A
A
See
how
long
we
can
and
fix
other
things
where
we
can.
B
B
Well,
I
I've
had
one
more
metrics
related
topic,
but
it's
more
towards
the
sdk
people.
B
We
we
are
trying
out
the
alternate
elementary
metrics,
that
produced
by
the
agent,
and
we
found
out
that
the
all
the
metric
data
gets
a
resource
attached
to
them
and
that
resource
contains
the
same
things
that
the
span
does.
So
this
is,
if
you've
been
following
this
spec,
there
is
a
yeah.
If
you
use
me
prometheus
resource
issue
there
that
really
talks
about
this.
B
The
same
thing
and
there
is
currently,
if
you're,
using
autoconfigure
there
is
you
you're,
just
forced
to
basically
use
the
same
resource
for
all
three
signals
and
the
only
way
to
customize
or
to
modify
metrics
resources
to
completely
override
it
and
yeah.
So
that
was
I.
I
basically
have
a
question.
A
B
A
B
Same
the
other,
auto
configure
sets
the
same
resource
on
tracer
provider,
lock,
provider
and
provider,
and
this
is
the
resource
that
contains
things
like
process,
dot,
command
line.
A
Yeah
now
honorable
seemed
to
think,
because
we
talked
about
this
a
little
bit
one
of
the
recent
weeks
honorable
seemed
to
be
fairly
convinced
that
the
s,
the
none
of
the
resources
basically
should
get
added
to
well
at
least
prefer
prometheus
by
default.
Only
like
it
should
just
be
like.
If
there's
a
couple
that
have
mappings,
then
those
should
go
but
yeah.
Otherwise
everything
should
be
ignored.
A
I
see
so
you
yeah
you
might
not
want.
You
might
actually
want
some
of
the
other
resource
resources
on
your
metrics
yeah
for
sure
we
could
either
you
know
in
the
agent
either.
C
B
This
is
something
that
we
would
need
on
this
through
level,
but
I
think
that
it
might
end
up
being
a
more
generic
area.
People
would
want
to
set
this
do
this
thing,
even
if
they
they're
not
using
any
java
agent
like,
for
example,
the
spring.
A
A
A
There
was
oh
yeah
laurie
had
pinged
me
about.
A
Yeah
so
the.
C
A
Thing
I
just
wanted
to
check
with
both
of
you
was
like,
so
we
were,
you
know
declaring
this
alpha,
some
moved
it
to
some
semcom.
A
Are
we
comfortable
than
dropping
it
and
breaking
people
without
them
in
the
java
agent
kind
of
just
thinking
of
like
the
server
span
scenario,
where
you
know
like
the
java
agent
likes
to
upgrade
the
java
agent,
but
not
like
it
makes
sense,
dropping
stuff
from
the
instrument
or
api
because
you
go
in
you,
try
to
compile
you're
like
oh,
that
doesn't
work,
but
for
the
java
agent,
it's
a
little
less
friendly
when
you
upgrade
and
it
just
stops.
A
B
And
yeah
cyberspan
is
considered
considerably
easier
to
instrument
anyway,
because
I
mean
you,
you
don't
really
have
to
keep
the
internal
implementation
and
representing
instrumental
and
so
on,
but
yeah.
I
let's
wait
for
laurie
to
answer
that.
I
like
very
vaguely
aware
of
the
use
case
that
he
brought
up
here,
so
he
might
have
just
more
info
about
this
yeah.
A
Yeah,
I'm
I'm
basically
I'm
I'm
okay
with
merging
it
as
long
as
you
know,
we're
all
kind
of
aligned
that
we
would
with
some
deprecation
cycle
that
this
is
going
to
get
dropped
at
some
point.
C
A
I
owe
lord
to
I
also
a
review
on
this
one
this
week,
so
I
just
postponed
it
until
I
don't
know
I
won't
release
without
them.
I
promised
him
that
I
sent
this.
A
It's
basically
for
session,
aware
message:
listener.
There's.
C
A
Do
it,
I
tried
it
with
the
you
can
write
a
jms
listener
that
accepts
a
session,
but
even
that
was
getting
picked
up
by
our
normal
jms
instrumentation.
But
of
course
interesting.
I
have
a
user
that
is
doing
it
a
different
way.
A
Yeah,
so
this
one
yeah,
so
what's
really
interesting
is
so
this
spring.
What
they
do
is
they
are.
They
have
their
code,
that's
polling,
reading
from
the
queue
and
then
right
when
they
send
it
down
to
the
annotated
class.
A
It
goes
through
an
adapter
class
which
happens
which
just
so
happens,
to
implement
the
jms
listener
interface.
Oh.
A
Yeah
yeah
yeah
they're,
not
using
real
yeah
jms
on
listener,
right,
great,
so
yeah.
I
think
the
main
question
I
have
with
this
is-
and
I
think
as
I
was
writing
it-
it
probably
answered
my
question,
but
I
copy
pasted
a
bunch
of
stuff
over
and
I
moved
all
the
jms
all
the
jms
tests
that
were
spring
tests
really
over
into
this
new
module,
but
the
underlying
instrumentation
itself.
A
I
could
I
copy
pasted
and
then
stripped
out
things
that
weren't
needed,
but
I
could
also
make
this
depend
on
this
and
use
those
classes.
B
I'm
fine
yeah,
I'm
fine
with
copy
pasting
or,
alternatively,
we
could
make
a
like
joining
us
common
java
agent
module.
That
would
be
fine
too.
A
B
Oh
yeah,
I
I
know
what
yeah
I
was
like
instantly
instinctively
avoiding
depending
on
the
other
instrumentations,
and
I
will
remember
why
it's
because
of
muzzle
it.
If
it
sees
two
instrumentation
modules,
then
it
might
cause
some
weird
things
to
happen.
A
A
Because
we
definitely
had
that
problem
yeah
because
remember
I
added
a
attribute
for
muzzle
of
which
instrumentation
yeah
yeah.
C
A
Yeah,
okay,
I'll
probably
do
that,
because
there's
just
a
little
bit
too
much
copy
pay
a
little
bit
too
much
like
logic
here.
That
is
well
not
this
one.
A
A
So
it's
the
basic
idea
from
as
an
experimental
property
or
it's
not
it's
not
even
a
property.
It's
there's
an
bootstrap,
a
snippet
holder
in
the
boot
in
a
boost,
trap,
module
that
a
distro
can
set
their
snippet
into
that.
A
And
if
the
servlet
advice
finds
that
snippet,
then
it
will
go
about
injecting
that.
B
I
was
just
wondering,
if
does
an
iraq
want
to
like
continue
joining
these
tuesday
meetings
or
since
he's
unavailable
today,.
A
A
Also,
if
I
yeah
we'll
find
out.
B
Oh
no,
I
hold
on
a
second,
I
had
a
very
old
topic
in
my
notes.
I
just
stand
out.
Do
you
remember
the
we
had
the
bark
related
sort
of
related
to
the
time
extractor
and
the
metrics
and
spans
having
different
durations.
B
A
So
that
the
sdk
folks
said
that
you
know
there
were
you
know,
exposing
the
clock
was
is
something
that
made
sense
to
them,
exposing
it
from
the
sdk
side
or
the
api
side,
but
they
wanted,
and
that
was
my.
The
action
item
that
was
on
me,
was
to
open
a
spec
issue
to
discuss,
because
they
thought
that
that
was
probably
a
very
general
purpose
problem
that
other
languages
would
have
also.
A
Otherwise,
just
ping
me
about
it
again
and
I
will.
B
I
will
yeah,
I
think,
yeah.
I
think
that
it
makes
sense
to
clean
this
up
and
to
make
sure
that
these
metrics,
metrics
and
tracers
get
consistent
about
their
timings.
But
I
haven't
like
been
feeling
that
it's
that
important,
that
it's
like
the
first
priority
thing
we
have
so
many
other
things
to
fix
here
that
this
is
like.
This
can
wait.
A
I
I
agree,
but
I
do
think
that,
like
exposing
the
clock
makes
a
lot
of
sense
because,
especially
even
with
I
mean,
since
the
api
takes
a
manual
time,
then
I
mean
like,
what's
the
point
of
that
api,
if
you
can't
capture
it
in
sync,
with
the.
C
A
C
A
B
Yeah,
I
think
that
I'm
not
really
worried
about
strawberries,
because
I
I
haven't
in
my
own
apartment
anyway,
I
have
like
two
plant
boxes
of
strawberry.
A
B
B
In
september
so
yeah,
but
my
parents
have
a
couple
of
raspberry
bashes,
so
I
suppose
I
might
have
to
gather
the
whole
bucket
of
them.
A
Nice
yeah,
my
cousin,
just
dropped
by
last
week,
should
gun
raspberry
and
strawberry,
picking
here
just
and
dropped
by
a
couple
of
a
couple
bins
so
yeah.
I
polished
off
the
raspberries,
the
strawberries,
the
strawberries.
We
really
need
to
eat
fast,
they're
gonna
go
yep.
A
Cool
well
have
a
good
one,
and
I
will
see
you
thursday,.