►
From YouTube: 2023-03-29 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
A
B
A
B
Yes,
like
both
Fabian
and
Richie,
have
the
most
context
and
Richie's
traveling
and
Fabian
has
like
a
meet-up
that
he's
organizing,
so
they
can't
make
it.
However,
I
can
like
you
know
we
are.
We
are
basically
putting
a
dock
together
that
we
will
share
pretty
soon.
The
answer
is
I
mean
just
to
give
you
a
little
context,
it's
very
inconsistent.
B
What
open
metrics
is
what
Prometheus
is
and
what
Prometheus
implements
and
things
like
that-
and
this
is
from
a
deliberate
decision
at
the
last
Dev
Summit-
that
there
are
things
that
Prometheus
wants
to
do,
that
open,
Telemetry,
open
metrics
prevents,
but
instead
of
updating,
open,
metrics
and
then
implementing
it
in
Prometheus,
we
will
implement
the
changes
in
Prometheus,
see
how
they
work
and
then
update
the
open,
metrics
spec.
B
A
B
Yes
again,
Richie
and
Fabian
have
the
most
context,
and
one
of
the
things
that
we
decided,
also
at
the
last
Dev
submit,
is
we're
going
to
fold
open
metrics
into
Prometheus,
so
that
it's
just
one
thing
and
updates
are
quicker
rather
than
having
two
separate
projects.
B
A
Okay,
yeah
I
know
that
that's
a
question
that
had
been
asked
a
few
times
over
the
last
year,
so
I
think
I'm.
Certainly
in
support
of
that,
if
it
makes
things
easier
to
keep
them
reconciled
between
Prometheus
and
open
metrics,
I
just
need
to
figure
out
how
to
make
sure
we
keep
things
reconciled
between
Prometheus
and
up
and
telemetry.
B
Yep
again,
we
should
have
that
follow-up
call
with
Richie
and
Fabian,
but
this
is
the
most
context.
I
have
there's
a
working
progress.
Talk
I,
don't
want
to
share
it
yet,
but
it
just
shows
that
it's
super
inconsistent
everywhere
and
we
need
to
figure
out
how
to
work
with
that.
B
I
mean
I
guess
we
can
get
started
on
the
other
point
as
well,
which
is
whatever
so
I
was
surprised
that
I
have
to
enable
the
metric
name,
normalization
with
a
special
CLI
feature
flag
and
it's
state
Alpha.
However,
the
last
meaningful
code
change
for
metric
name,
normalization
was
September
2022.
So
that's
like
six,
no
six
months,
yeah,
that's
six
months
since
the
last
code
change
so
should
we
make
it
beta
and
should
we
kind
of
try
to
find
a
path
towards
making
it
on
by
default?.
A
Yeah
I
think
that
would
be
probably
appropriate
at
this
time.
The
the
offer
stage
is
typically
for
Gathering
feedback
from
early
adopters,
make
sure
that
it
functions
as
expected
and
giving
us
a
chance
to
communicate
the
change.
If
it's
a
change
that
really
needs
to
be
communicated,
but
I
think
we're
probably
okay
to
to
make
that
change.
B
A
That's
that's
the
process
it
has
to
follow.
It
has
to
go
to
enabled
by
default,
but
still
able
to
disable
okay
for
a
while
and
and
then
it
will
be
permanently
enabled
and
the
gate
can
be
actually
I.
Think
we're
talking
about
changing
how
we
do
that.
We're
not
going
to
remove
the
gates,
but
we're
going
to
put
them
into
a
state
where
they're
stable
and
can
no
longer
be
disabled.
A
All
right
well,
thanks
for
providing
the
additional
context
on
the
exemplars
issue
and
I'll
look
forward
to
that
doc
when
you
guys
have
it
ready,
yep
cool,
oh
hey!
It's
Morgan!.
A
Gotham
and
I
were
just
talking
about
the
couple
issues
that
are
on
the
agenda.
We
were
just
wrapping
up,
I
think
we've
covered
it,
but
Gotham.
If
you
want
I,
don't
know
Morgan.
Are
you.
C
B
So
tldr
is
in
the
Prometheus
world,
we
do
implementation
first
and
once
the
implementation
is
stable
and
people
are
adopting
it,
then
we
convert
it
to
spec.
B
Like
things
like
exponential
histograms
how
to
expose
this
and
things
like
that,
we
don't
want
to
wait
for
open
metrics.
So
we
will.
We
decided
in
the
last
step,
submit
that
we
will
Implement
everything
we
want
in
Prometheus
and
once
we
are
confident
and
it's
stable,
then
that
will
go
into
open
metrics.
C
I
see
so
for
otel
I
take
it.
We
should
still
wait
for
open
metrics
to
spec.
It
then
before
taking
dependencies
on
it.
So.
B
And
the
second
decision
we
made
is,
we
will
merge
the
open,
Telemetry,
open,
metrics
and
Prometheus
like
we'll
fold
open
metrics
into
Prometheus.
It
won't
be
separate
projects
anymore,
right,
I,.
B
The
idea
was
to
create
a
standard
that
you
know.
Other
projects
can
adopt,
but
I
think
that's
becoming
open,
Telemetry,
metrics,
okay,
so
cool
again,
so
we
like,
we
decided,
you
know,
you
know
what
let's
just
merge
it
into
Prometheus
and
make
it
like
the
standard
of
Prometheus
uses.
Yeah
products
can
adopt
it.
C
B
Of
them
cannot
be
here,
but
we
are
trying
to
like
we're
writing
a
doc
with
the
current
state
and
the
doc
says
everything
is
inconsistent,
so
we'll
we'll
finish,
the
dock
share
it,
and
then
we
can
have
a
sync
call
to
see
how
we
can
proceed.
B
A
Cool
yeah,
I
think
overall,
emerging
permutation,
open
metrics
will
be
a
good
change.
The
only
real
concern
I
have
with
the
Prometheus
approach
of
implement
first
specify
second,
is
that
open
Telemetry
relies
on
Prometheus
code
a
lot,
so
you
know
our
Prometheus
receiver.
If
we
don't
have
controls
over
saying,
please
don't
use
this
new
functionality
that
may
cause
us
to
to
have
issues
where
we're
getting
ahead
of
where
open
Telemetry
is
specified,
agreed.