►
From YouTube: 2022-04-11 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
B
All
right,
it's
four
minutes
after
let's
get
started
and
if
you
have
items
to
fill
in,
please
continue
following
them.
So
first
updates
from
the
specification
sig
the
instruments:
instrumentation
stability
document
has
been
merged
and
some
semantic
conventions
are
being
extended
and
revised
metrics.
I
imagine
there's
no
updates,
because
we
had
the
big
merge
and
everything
else
over
the
last
week
or
two.
Oh
okay,
we've
got
an
update
here,
open
this
up,
dropping
histogram,
aggregation
and
defaulting
to
explicit
bucket
histograms.
B
Okay,
we'll
just
keep
going
logs
log
collection,
repo
has
been
deprecated
and
merged
into
collector
contrib.
That's
really
cool,
that's
great!
So,
to
your
end,
just
to
clarify
for
this
this.
This
is
by
the
log
collection
repo.
This
is
like
the
sort
of
standalone
stanza
repo
that's
been
merged
in
that's
correct,
very
cool.
Okay,
that's
actually
really
important
news
for
everyone,
so
that
yeah,
that
just
furthers
our
journey
of
just
more
natively
making
the
logging
experience
part
of
the
hotel,
collector
php
point.
0.0.9
release
was
completed
java.
B
We
had
1.13.0
release
completed,
which
is
the
metrics
sdkrc,
fantastic
that
we
talked
about
that
last
week
for
javascript
resolved
some
dependency
conflict
issues
which
held
up
metrics.
The
metrics
will
be
longer
than
expected
working
on
final
cleanup
for
the
metrics
alpha
release.
Okay
and
daniel.
Do
you
still
think
that
we're
on
track
for
js
for,
like
a
ga
or
at
least
an
rc
by
kubecon?
I
assume?
Yes,
I
just
want
to
clarify
yes,
okay,
great
cool
dot
net,
expecting
our
last
rc
in
the
next
two
days
to
be
followed
by
a
stable
another.
B
Two
days
very
cool
go
1.6.2
and
1.6.3
have
been
shipped
to
address,
otlp
version,
0.15
and
other
global
provider
issues
respectively.
Okay
c
plus
version
1.3.0
is
planned
for
this
week,
which
includes,
trace,
bug,
fixes
and
build
improvements.
Metrics
sdk
work
is
in
progress,
async,
aggregation
and
prometheus
exporter.
Alpha
release
is
planned
for
the
end
of
april.
Okay,
ruby
metrics
work
is
on
go
good.
B
C
Yeah
sure,
hey
everyone,
just
a
quick
update,
so
we
have
a
proposal
on
a
shared
community
demo
application
we're
still
looking
for
a
couple
contributors.
I
think.
C
Know
the
running
dock:
now
you
can
see
everyone's
commenting
on
it.
We
could
also
use
potentially
per
language
support
for
things
like
adding
support
for
ruby,
rust,
swift
and
php
and
then
also
just
general,
some
architectural
help
as
well.
So
if
you
have
any
interest,
please,
you
know
just
hit
the
link.
Start,
writing
some
comments
or
feel
free
to
reach
out
to
me
as
well.
B
And
then
carter,
just
going
forward
like
once
you
get
some
more
contributions
on
the
dock.
What's
your
plan
for
next
steps,
like
typically
a
no-tell?
What
we've
done
for
similar
processes
or
projects
like
this
is
we've
gone
and
then
created
like
a
one-hour
call
or
something
like?
Is
that
your
intent
for
the
next
step,
or
or
do
you
want
to
keep
things
on
the
dock
for
now
like?
What?
How
do
you
want
to
take
this
forward
over
the
next
few
weeks
or
months.
C
Yeah
great
question,
so
I
was
thinking
for
at
least
the
next
two
weeks,
maybe
keeping
it
more
in
the
dock
itself,
just
kind
of
identify
identifying,
more
control
contributor
is
kind
of
going
a
little
broader
on
the
feedback
and
then,
after
that,
yeah
doing
a
dedicated
call.
You
know,
ideally
by
the
end
of
april,
we
have
some
sort
of
you
know.
Cadence.
B
B
All
right
second
topic:
metrics
announcement
blog
post
at
kubecon,
so
I
have
a
draft
that
I
need
to
put
the
link
in
for
for
the
otell
sort
of
community
metrics
announcements
for
our
status
for
metrics.
We
were
thinking
we
talked
about
this
on
the
gc.
So
when
I
say
we
that's
who
I'm
just
describing
we're
thinking
of
making
publishing
this
announcement.
Rather
while
we're
at
cubecon
and
there's
some
as
everybody
knows,
we
have
some
rooms
and
talks
and
other
events
taking
place
there.
B
So
it
seemed
like
an
appropriate
time
to
make
that
announcement,
because
we'll
be
there
and
also
because
by
then
we'll
have
a
few
of
the
ga
releases
already
out,
which
will
be
great,
so
we're
gonna
do
the
same
thing
we've
done
in
the
past,
where
we
will
have
the
community
draft
one
that
I
as
soon
as
I
stop
talking
I'll,
go,
get
the
link
and
paste
it
here.
B
We'll
have
the
community
draft
blog
post
that
people
can
review
that'll
get
published
at
a
set
time,
we'll
figure
out
the
time
in
the
coming
weeks
and
then
any
people
or
organizations
or
others
who
want
to
participate
in
this.
Can
cross
post
it
at
the
exact
same
time
and
this
you
know
they
can
write
their
own
intro
paragraphs
and
things
and
then
just
the
the
goal
is
that
they
also
include
the
body
of
the
blog
and
a
link
to
the
main
one.
B
B
So
that's
the
plan.
I
will
link
the
draft
here.
We
still
have
to
figure
out
the
exact
timing
during
kubecon,
we'll
do
that
in
the
coming
weeks.
Time
is
on
our
side
for
this
we're
a
bit
ahead
of
things,
which
is
good
and
we
will
go
from
there
and
if
you
have
any
questions
or
anything
about
it,
please
reach
out
to
me
or
just
put
a
comment
on
the
draft,
the
link
for
which
I'm
going
to
paste.
As
soon
as
I
shut
up.
B
All
right
sounds,
like
things
are
still
looking
pretty
good
for
the
metrics,
rc
and
ga
releases.
Obviously,
if
you
have
maintainers,
if
you
have
any
questions
or
concerns
or
or
you've
had
to
change
your
schedule
like
please
please
raise
that.
I
particularly
raise
it
raise
it
during
this
call
and
also
on
on
slack,
but
things
at
the
moment
actually
appear
to
be
going
really
smoothly,
which
is
great,
I
think,
after
cube
or
at
and
then
after
kubecon
will
be
a
great
opportunity
for
us
to
sit
down
as
community
and
talk
about.
B
What's
next
right,
everybody
who's
been
so
focused
on
metrics
over
the
last
year,
or
so.
We
now
have
an
opportunity
to
to
breathe
a
bit
and
think
about
our
next
moves.
Obviously,
there's
a
lot
to
that.
We
all
want
to
build
to
continue
our
metric
support
and
more
integrations
and
things,
but
I
suspect,
like
other
topics
like
logging
and
others
will
be,
a
big
focus
of
the
community,
for
the
remainder
of
their
will
become
more
of
a
focus,
at
least
for
the
community,
for
through
the
remainder
of
the
year.
D
I
have
one
thing
I
want
to
point
out.
The
one
1.6.2
release
that
we
mentioned
was
required,
because
users
had
been
updating
otlp,
the
otp
proto
go
to
one
0.15
prior
to
the
changes
that
we
had
made
to
use
the
instrumentation
scope
fields
instead
of
the
instrumentation
library
fields,
and
this
should
work
when
used
with
the
collector
048.
D
The
most
recent
release
that
has
rewriting
for
taking
those
the
the
old
field
names
in
their
new
positions
and
putting
them
back
in
into
place
where
they
should
be
used
that
wasn't
working
and
users
were
seeing,
dropped,
traces
and,
and
so
we
we
had
to
release
that
to
ensure
that
we
were
putting
the
fields
back
in
the
place
where
they
would
be
the
same.
On
wire.
A
D
Yeah,
let
me
find
the
link
to
the
comment
where
I
described.
What
I
went
through,
but
basically
161
with
0.121
worked
fine
161
with
point
15
did
not
162
with
point
15
did
so
the
change
to
ensure
that
instrumentation
library
scope
appears
in
the
same
place
on
the
wire
as
instrumentation
or
sorry.
Instrumentation
scope
appears
in
the
same
place
on
the
wires
interpretation
library
functions,
because
I
was
able
to
use
162
and
point
15
with
an
older
collector
that
had
no
concept
of
instrumentation
scope.
So
that's
working.
It's.
A
A
B
Perfect
all
right
anthony,
thank
you
for
calling
out
that's
the
exact
kind
of
topic
we
have
this
meeting
for
so
it's
perfect
any
other
topics.