►
From YouTube: 2023-03-20 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
B
Okay,
let's
get
started
so
no
updates
on
spec
for
logs.
We
discussed
that
in
depth
last
week.
If
you
didn't
attend
last
week,
we
have
all
the
notes
here,
but
the
plan
for
stabilizing
the
logs
Bridge,
API
and
SDK
and
our
long-term
thinking
there,
and
we
had
a
good
discussion
about
that.
Moving
on
PHP
Java,
no
major
updates
there
for
JavaScript.
We
have
exponential
histograms
arriving
the
next
release,
that's
great
for
python.
There
are
no
updates
for
net.
B
1.19.0
semantic
convention
is
still
blocked
by
a
spec
issue,
so
I
imagine
we'll
be
looking
at
that
tomorrow
morning
in
the
specsig
moving
on
for
rust,
we
have
more
contributors
joining
us
today
in
the
next
one
to
two
weeks.
That's
great
so
we've
CJ
Thomas
from
hotel.net
and
Lali
Kumar
from
Motel,
C,
plus
plus
it's
wonderful
and
no
major,
updates.
Further
down
looks
like
Ted's,
adding
an
issue
about
using
stack,
Overflow
I'm,
actually
going
to
put
one
above
that
that
pops
into
my
my
mind,
while.
B
Okay,
Ted
yep,
yep
yep
and
that's
this
is
really
for
people
to
work
on
metrics
I
saw
last
week
an
issue
on
openmetrics
slash
Prometheus
from
some
of
the
open,
metrics
maintainers
I
think
was,
might
have
been
like
Brian
Brazil,
claiming
that
open
metrics
is
no
longer
compatible
with
Prometheus,
which
seems
bad
and
I'm.
Just
wondering
how
that
impacts.
Us
like
is
our
compatibility
in
hotel.
Is
it
with
open
metrics
or
is
it
wow
it
got
signed
up
or
is
it
with
Prometheus.
C
We're
in
a
little
bit
of
a
weird
spot,
I
think
at
least
with
respect
to
the
collector,
so
Prometheus
is
no
longer
compatible
with
open.
Metrics
Prometheus
has
changed
they.
They
are
now
accepting
exemplars
on
any
metric.
C
For
the
most
part,
that's
not
really
an
issue
for
us,
I
think
other
than
the
fact
that
it
causes
some
compatibility
tests
that
we
have
in
the
collector's
Prometheus
receiver
to
fail,
because
that
is
using
open
metrics
as
the
the
ground
truth.
There
is
testing
Goblin
metrics
parsing,
using
the
Prometheus
scrape
manager
code,
where
we
may
have
specification
issues,
but
at
least
as
far
as
I've
discovered,
thus
far
I
just
started.
C
Looking
at
this
on
Friday,
so
I'm
kind
of
new
to
this,
but
at
the
very
least
Prometheus
will
now
be
supporting
exemplars
on
summaries
and
the
otlp
summary
definition
does
not
include
a
field
for
exemplars,
so
we
will
not
be
able
to
round
trip
summaries.
C
B
Yeah,
it's
weird
yeah
yeah
I
I'm
not
involved
in
those
communities,
but
it
does
seem
strange
to
me
Anthony
to
the
point
you
were
just
making
that
that
open
metrics,
which
I
we
all
assumed
was
meant
to
be.
The
thing
we
should
be
compatible
with
is
now
not
compatible
as
Prometheus
Anthony
or
anyone
else.
Who's
been
working
on
metrics,
second
sort
of
follow-up
question
like
if
those
two
specs
continue
to
diverge
I.
C
C
But
most
users
are
going
to
be
using
Prometheus
and
Prometheus.
What
it
does
is,
and
it
affects
the
de
facto
standard
yeah.
B
C
A
D
Is
there
an
issue,
something
I
think
we
still
need
to
do.
Work
on
on
our
end
is
exemplars
as
far
as
like
our
own
specification
is
concerned.
I
wonder:
are
there
issues
anyone
who
knows
that
part
of
the
spec
being
able
to
kind
of
like
keep
up
or
keep
compatible
with
Prometheus
here.
E
The
only
issue
that
I
know
we
have
that
is
really
tracking
a
lot
of
the
Exemplar
work
is
opened
by
Jack
Burke
and
that's
more
about
like
how
we
set
it
up
in
the
SDK
I.
Don't
know
if
there's
going
to
be
a
compatibility
issue
with
the
open
metrics
side,
because
I
think
we
already
have
exemplars
pretty
much
everywhere
in
the
data
model,
except
for
summaries.
B
Just
because
I
saw
the
comments
in
the
chat.
Does
anyone
like
what
is
open
metrics
if
it's
not
Prometheus
compatible
like
I
I
I
had
always
just
treated
it
as
basically
the
spec
for
Prometheus?
If
it's
no
longer
compatible
with
it,
it's
open,
metrics,
actually
plugged
into
anything
else,
Beyond
open
telemetry.
B
Okay,
interesting,
okay,
well,
I!
Imagine
well!
This
will
be
a
topic
of
discussion
going
forward
as
well.
If,
if
they
continue
to
diverge,
okay,
I'll
add
the
notes
from
the
conversation
while
I
mute
myself
Ted,
you
want
you're
the
next
topic.
Organ.
E
B
E
Thing
I
wanted
to
add.
There
is
don't
we
have
like
a
community
sync
with
Prometheus
every
week
or
is
it
every
other
week
or
something
like
that?
That.
B
E
Yeah
it's
next
week
at
8,
A.M
on
Wednesday
looks
like
so
maybe
it
might
be
worthwhile
if
you
wanted
it
or
one
of
the
gcftc
check
in
with
them.
There.
B
Yeah
I'm
also
curious
and
I'm
also
curious
what
this
means
for
openmetrics
as
Daniel
and
others
were
putting
in
the
chat.
B
D
Yeah
yeah,
so
I,
don't
know
how
much
this
was
covered.
Last
week
with
like
the
kind
of
feedback
about
the
gctc
Summit,
it
was
good
a
lot
of
actionable
stuff
coming
out
of
that.
D
But
one
thing
that
was
relevant
to
maintainers
that
one
of
y'all's
input
on
was
we
were
discussing
making
better
use
of
stack
Overflow.
The
reason
for
this
is
we
get
a
lot
of
questions
coming
in
to
open
Telemetry,
usually
through
slack
either
through
one
of
the
open,
Telemetry,
slack
channels
or
DMS
or
just
various
other
places,
and
we
type
out
answers
to
those
questions
there
and
that
helps
that
one
person,
but
but
it
also
just
kind
of
dies
there,
because
slack
really
isn't
indexable
or
useful
on
the
internet.
D
Also,
it's
a
bit
of
a
barrier
for
some
people
to
ask
questions
having
to
make
a
cncf
slack
account,
and
so
we
were
thinking
that
a
better
solution
to
this.
Obviously
we're
going
to
keep
answering
questions
on
slack
or
anywhere.
We
get
them
but
to
make
sure
that
we're
actually,
then
just
cop,
be
pasting
the
question
and
answer
onto
somewhere.
That
is
popular
in
search
indexable,
like
stack
overflow
and
in
General,
trying
to
maybe
push
the
community
towards
stack
Overflow
as
the
place
to
to
ask
questions.
D
There's
two
ways:
if
we
decide
to
go
that
route
that
would
affect
maintainer,
so
I
guess
three
ways:
one
is,
you
know:
we're
gonna
work
out
something
with
the
comsig
to
make
it
easy.
If
you
do
end
up
answering
a
question
either
to
post
it
on
stack,
Overflow
or
ping,
somebody
to
post
it
for
you.
The
second
is,
if
we
as
a
community,
don't
kind
of
monitor,
stack,
Overflow
to
some
degree,
it'll
be
a
little
sad
and
three.
D
We
currently
have
GitHub
discussions,
kind
of
turned
on
here
and
there
and
in
one
or
two
places
it's
it's,
it's
had
a
positive
response
and
in
a
lot
of
places
it
seems
like
it
hasn't
in
the
debate
between
stack,
Overflow
and
GitHub
discussions.
The
main
thing
that
came
up
was
stack.
Overflow
seems
to
have
much
better
SEO,
think
GitHub
discussions.
D
No
one
we've
been
talking
to
is
in
general,
been
noticing
like
when
they
search
for
stuff
on
the
internet.
They
get
GitHub
discussions
as
search
results,
which
is
one
of
the
main
things
we're
looking
for,
and
it
seems
like
having
both
GitHub
discussions
and
stack.
Overflow
is
like
just
like
too
many
places
to
to
keep
track
of,
but
this
is
a
hundred
percent
of
maintainer.
You
know
domain
thing.
We
don't
want
to
try
to
start
moving
the
community
in
some
direction
if
the
maintainers
don't
want
to
go
there.
D
So
I
wanted
to
raise
the
discussion
here
in
this
group
and
get
people's
feedback
what
they
would
like
to
see
how
they
think
github's
discussions
have
been
working
and
if
they
have.
D
F
F
Add
a
comment
on
GitHub
discussions:
I
I
do
worry
that
currently,
because
we
have
so
many
repositories.
Some
discussions
Maybe
opened
in
the
wrong
repository,
which
often
happens
in
The
Collector
or
The
Collector
slack
Channel,
even
whereas
the
having
the
answers
in
stack
Overflow
may
be
a
little
bit
more
centralized
and.
D
To
clarify
yeah
stack,
Overflow,
there's
an
open,
Telemetry
tag
and
people
can
apply
open,
Telemetry
plus
like
a
language
tag
or
collector,
or
something
if
they
want
to
subdivide
it
but
yeah.
If
they
they
screw
up.
Or
you
know
someone
who's
not
in
one
Community
happens
to
know
the
answer.
It
does
seem
a
lot
easier
to
just
find
all
of
the
questions
and
traffic
happening
around
hope
and
Telemetry
over
there.
D
G
One
thing
one
thing:
I'm
wondering
about
with
stack
Overflow
is
there's
kind
of
semi,
is
strict
Community
guidelines
about
how
to
structure
a
question
and
answer
and.
G
You
know
this
idea:
I,
don't
know
how
literally
you
meant
this
when
you
said
earlier,
you
know
when
a
question
is
asked
asked
and
slack
that
you
can
copy
the
question
and
the
answer
into
stack,
Overflow
but
I,
don't
know,
I,
think
that
would
violate
I.
Don't
know
stack
overflows
super
well,
but
I
think
that
that
would
violate
the
community
guidelines.
H
So
this
may
be
different.
Now
it's
been
a
while,
since
I've
been
active
on
stack
Overflow,
but
as
far
as
I
know
as
long
as
you're,
not
doing
it
to
just
like
Farm
reputation.
If
you're
not
duplicating
existing
questions,
they
don't
discourage
answering
your
own
question
as
far
as
formatting.
Yes,
that
is
something
that
it
can't
be
literally
just
copied
word
for
word
out
of
a
chat.
H
I
think
that
would
be
definitely
discouraged,
but
that's
something
that
if
the
comms
say
we're
going
to
handle
this
as
a
task,
part
of
that
task
would
be
formatting
it
properly,
or
maybe
we
have
section
in
our
own
documentation
where
we
put
these
sorts
of
questions
and
answers
instead
of
stack
Overflow
but
I
think
stack.
H
Overflow
has
a
huge
advantage
in
in
several
ways:
one
it's
where
a
lot
of
our
end
user
Community
is
most
of
the
people
interacting
with
the
GitHub,
are
developing
open,
Telemetry
and
not
using
it,
and
most
people
already
have
stack
Overflow
accounts.
Making
them
sign
up
for
for
GitHub
is
not
as
easily
discoverable
for
them.
H
H
G
Yeah
I
think
stack.
Overflow
is
a
much
better
option.
So
let
me
I
guess
just
express
my
support
for
this
I'm,
just
kind
of
wondering
if
about
you,
know
a
bit
of
an
implementation
detail,
but
can
we
put
the
onus
on
the
on
the
the
question
asker
in
in
slack
to
post
the
question
in
stack
Overflow
so
that
we
don't
need
maintainers
or
folks
from
the
com6
to
Bear
the
burden
of
properly
formatting?
The
question
like.
A
G
Ask
it
and
you
know
it's
your
burden
to
conform.
The
question
to
the
community
guidelines.
H
Yeah
I
think
so.
This
came
up
in
the
the
gctc
meeting
and
I
believe
it
was
de
Rossi
who
said
something
along
the
lines
of.
If
somebody
asks
me
a
question
in
slack
I'm
going
to
answer
it,
I'm
not
going
to
push
them
to
some
other
like
stack,
Overflow
or
anything
like
that
and
I.
H
Think
that
that's
true
in
a
lot
of
cases
like
the
the
answer
is
just
like
one
line,
or
you
know
very
quick
and
if
somebody
asks
a
question
in
slack
like
you're,
not
going
to
not
answer
it
a
lot
of
the
time.
Sometimes
you
might,
if
you're
asking
for
clarification
or
something
like
that,
you
may
ask
them
to
put
a
more
fully
formed
version
on
stack,
Overflow
or
something
like
that.
But
I
think
a
lot
of
that
is
is
sort
of
implementation
details
right
now.
H
The
reason
people
ask
and
user
questions
on
slack
is
because
that's
where
we've
told
them
to
go
I
think
once
there
is
more
community
supported
interaction
around
stack,
Overflow,
we'll
get
less
end
users
on
the
slack,
which
will
in
turn
make
slack
more
useful
for
developers,
because
right
now,
I
don't
know
about
the
other
shakes,
but
at
least
to
JS.
The
slack
channel
has
become
more
of
a
community
support
Channel
than
a
development
Channel,
and
we
have
separate
private
channels
for
development,
because
the
main
Channel
became
I
don't
want
to
call
it
useless.
H
But
this.
H
Doesn't
fit
the
intent
purpose
and
as
a
result
of
that,
the
maintainers
and
approvers
and
whoever
are
not
looking
at
that
channel
anymore,
because
they're
not
going
to
slack
to
answer
support
questions
they're
going
to
select
to
participate
in
JS
development
so
that
become
like
the
JS
Channel
at
least
became
not
a
dead
Channel,
but
not
the
it
doesn't
fulfill
its
original
purpose
anymore.
A
H
D
Yeah,
which
is
exactly
my
question
like,
though
it's
part
of
why
I
think
it's
been
working
and
we
seem
to
be
a
responsive.
Community
is
it's.
D
It's
almost
cross
purposes
like
Daniel
said
because
we
are
trying
to
use
slack
to
communicate
with
each
other
when
end
users
wander
in
there
and
ask
questions
we're
kind
of
already
looking
at
it
and
you
know
have
a
tendency
to
answer
them,
and
so
my
one
worry
would
be
if
we
don't
agree
as
a
community
to
develop
some
kind
of
practice
of,
like
you
know,
paying
attention
to
slack
stack,
Overflow
we're
not
going
to
be
using
stack
Overflow
for
development
purposes.
So
that's
that
would
be
my
only
concern
with
this
I
think.
F
D
Work,
if
we're
willing
to
to
actually
pay
attention
to
it
and
one
yeah
yeah
there
we
go
essential,
O'reilly
documentation,
right
copy.
D
But
like
so,
for
example,
here,
here's
like
one
practical
example
of
this.
What
do
maintainers
think
about
like
cordoning
off
like
five
minutes
or
so
of
their
weekly
Sig
meeting
to
just
scanning
stack
Overflow,
to
see
if
there
are
any
new
relevant
questions.
That
would
be
like
one
way
that
we
developed
practice
of
paying
attention
to
it.
Does
that
seem
reasonable
to
people.
D
Who
are
like
I'm,
not
gonna,
do
this?
It's
fine
to
say
it.
I
just
want
to
want
to
know
what
you
know
whether
there's
anyone
who's
just
like
doesn't
feel
like
they
got
it
in
them
to
to
bother
with
this.
E
D
I
D
They
used
to
have
a
thing
called
teams
which
was
like
a
private
stack
Overflow
that
cost
money
and
didn't
really
seem
appropriate
for
open
Telemetry,
but
their
new
communities
feature
might
be
something
we
could
either
get
the
cncf
to
pay
for,
or
maybe
they'll
make
it
free
for
an
open
source
project,
but
at
at
any
rate
it
it's.
A
D
Totally
clear
what
we
get
with
that,
but
one
thing
we
might
get
is
is
mod
tools
which
might
help
with
the
the
community
issue
or.
D
B
They're
comments
about
the
toxicity,
Community
I
assume
at
least
my
experience
there
is
that
I
agree.
You
can
get
some
very
strong
opinions
about
how
questions
are
phrased.
No
questions
are
asked
positives
and
negatives
I
mean
the
negative
is
sometimes
the
cross
comes
across
this
very
root.
Sometimes
it
is
very
root.
The
positive
is
certainly
stack.
Overflow
aggressively
tries
to
get
like
one
canonical
question
for
for
sort
of
every
possible
question.
Instead
of
dupes,
there
are
positive
outcomes
that
come
out
of
that,
and,
and
certainly
being
on.
B
D
And
people
can
give
dumb
answers.
I
have
definitely
looked
for
things
on
stack,
Overflow
found
the
answer
that
was
voted
up
and
been
like
that's
dumber
than
what
I
thought
of
so
yeah,
but
us
being
there
would
probably
solve
the
latter
thing.
Hopefully,.
A
G
Would
I'd
be
fine
answering,
but
looking
for
new
questions
and
answering
them
on
stack
Overflow
but
I'm
not
interested
in
moderating
stack
overflow.
B
Agreed-
and
that
would
be
probably
one
of
the
benefits
of
staying
on
the
main
instance
as
opposed
to
getting
our
own,
because
if
we
get
our
own
instance,
that
onus
like
believe
the
way
it
works
is
on
us,
the
main
one
we
take
advantage
of
the
standard
stack,
Overflow
mods.
We
just
have
a
tag
that
we're
monitoring
basically.
D
That's
also
why
we
kind
of
passed
out
the
idea
of
using
discus
or
something
that
we
would
have
to
manage
ourselves
like
we
wouldn't
get
a
lot
of
juice.
Frankly,
it's
also
something
I
see
on
GitHub
discussions,
for
whatever
reason
people
tend
to
I
mean
people
end
users
can
be
kind
of
high-handed
when
they
have
a
problem.
You
know
at
the
best
of
times,
but
for
whatever
reason
in
the
various
GitHub
communities,
I'm
on
people
tend
to
be
act
more
like
jackasses.
D
In
the
discussion
session
than
the
issues
section
I,
don't
know
why
it
is,
but
people
because
it
seems,
is
framed
as
being
more
casual.
People
are
more
willing
to
kind
of
like
toss
some
invective
in
there,
along
with
their
question
or
their
answer,
and
if
it's
on
GitHub,
we
we
have
to
then
we're
policing
that
and
that
doesn't
doesn't
seem
fun.
D
Anyways
cool,
okay,
I'm,
not
hearing
anyone
really
like
scream
they
would.
They
would
hate
this
and
wouldn't
participate.
So
we'll
we'll
try
to
we'll
try
to
make
this
happen
and
come
up
with
a
process
for
kind
of
moving
the
Q,
a
part
of
a
hotel
over
to
stack
Overflow
and
hopefully,
clearing
up
our
slack
channels
in
the
process.
D
B
D
B
I
think
there'll
be
yeah,
so
first
off
maintainers
are
not
expected
to
be
months
period.
The
benefit
like
please
chime
in.
If
you
disagree,
this
isn't
an
edict
or
something,
but
the
way
at
least
I
perceive
it
I
think
the
way
Ted
does
is
is
the
benefit
of
using
something
stack.
Overflow
is
there's
mods
or
already
on
the
platform.
We
will
do
most
this
for
us
all
right,
GitHub
discussions,
even
slack
means
that
the
onus
is
on
us,
either
explicitly
or
implicitly
so,
I
think
I.
B
If
you're,
a
maintainer
on
like
JS
or
or
like,
like
yourself,
Daniel
or
anything
else
like
yeah,
no,
if
you're
or
yes
as
Armin,
mentioned
the
hotel,
Community
managers
like
Austin
I,
would
expect
them
to
be
doing
anything.
Moderation
related.
If
you
know
our
ask
here
really
is-
is
for
the
sigs.
As
we
start
moving
things
over
to
stack
Overflow
is
take
like
five
ten
minutes
out
of
every
Sig
meeting
or
every
other
Sig
meeting
and
just
reviews
things
with
these.
The
open
Telemetry
tags
see
if
there's
any
questions
relevant
to
your
Sig.
B
D
D
You're
like
that's
confusing
as
hell
and
I
have
talked
to
the
comms
team
about
this,
and
because
we're
getting
so
little
feedback
about
our
docs
right
now,
they
are
willing
to
accept
very
low
grade
low
effort
issues
being
opened
as
a
form
of
feedback,
so
just
a
thing
to
know
as
maintainers
and
people
in
the
community
or
you
yourself,
if
you're
trying
to
use
a
portion
that
you
don't
maintain.
D
Just
that
copy
and
pasted
into
an
issue
on
the
the
doc
GitHub
repo.
The
the
comms
team
would
welcome
that
kind
of
feedback
from
the
end
user
community,
so
it
doesn't
have
to
be
like
an
actual
PR
or
like
even
well-formed
feedback.
We
just
want
to
know
just
any
kind
of
feedback
from
the
community
about
what
areas
where
docs
need
Improvement,
so
just
throwing
that
out
there
as
well
for
stuff
that
does
seem
like
it
should
be
in
the
dock
and
not
just
on
stack
Overflow.