►
From YouTube: 2022-03-28 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).
A
A
C
A
A
Yeah,
okay,
let's
I
don't
have
two
two
items
probably
to
talk
about.
One
of
them
is
the
bomb
data
model.
A
This
is
so
that
this
spec
is
stable
for
this,
for
the
data
model,
so
so
the
data
model
is
currently
defined,
which
would
be
used
by
open
telemetry,
which
should
be
used
for
all
the
open,
telemetry
sdks
implementations.
A
A
Logging
is
part
of
most
of
the
languages
today
they
have
their
own
structure
of
logging
out,
but
what
all
attributes,
what
all
data
fields
would
be
there,
which
is
supported
by
the
language
so
just
to
unify
and
from
open
telemetry
perspective,
we
have
defined
a
log
model
which
would
be
so
all
all
the
language.
Specific
logging
framework
should
be
able
to
convert
to
this
data
model,
and
then
this
should
be
used
to
export
or
convert
to
some
other
model
less
than
when
you
want.
A
So
this
is
more
of
a
unified
model
which
is
used
so
so
most
of
the
most
of
the
log
framework
should
should
be
able
to
should
be
able
to
map
to
this
model.
So
that's
that's,
and
this
is
stable
and
for
c
plus
it's
bit
different.
We
don't
have
logging
as
part
of
these
place
language
specification,
so
we
are
ideally
the
best
way
would
be
to
use
the
same
data
model
which
is
defined
by
open,
telemetry
and
use
that
in
our
apis
and
and
eventually
in
the
sdks.
A
C
C
A
A
A
A
C
A
A
Still
under
I
mean
they're
still
not
stable,
so
we
were
expecting
the
breaking
changes
in
this
so
yeah,
but
for
your
question,
you're
saying
that,
should
we
be
upgrading
should
we
be
upgrading
the
proto
files
regularly
yeah.
A
A
A
A
A
A
A
A
A
A
Along
with
the
current
program-
and
I
mean
there
will
be
multiple
information
which
hotel
cpp
version-
they
are
using
to
build
their
own,
their
components.
A
So
yeah,
I
think
that
probably
we
can
create
one
table
in
the
redmi
5
and,
let's
let
them
let
them
update
populate
those
tables,
though
that
table
and
so
again
this
this
first
other
thing,
which
probably
we
have
to
do
it
I
can.
I
can
create
the
table
for
that.
A
A
Start
for
number
of
downloads,
I
don't
think
it
is
provided.
I
did
try
out
to
see
if
github
provides
it
and
just
checking
some
of
the
styles
this
video
provides.
I
don't
think
it
is
available
readily
without
adding
something
without
adding
some
other
tools
exclusively
to
do
that.
C
A
A
A
Yeah,
so
so
how
to
get
the
exact
usability,
which
is
something
either.
It
could
be
that
so
I
mean
it
could
be
either
directly
downloading
these
releases,
but
if
somebody's
using
it
as
a
submodule
can't
really
track
that,
even
I
mean,
even
if
we
use
some
tool
or
some
bit
of
action
to
really
provide
and
provide
us
this
information
of
number
of
release
downloads,
but
that
won't
give
us
information
of
the.
A
B
A
A
A
C
So
since
on
average,
one
user
cloned
or
ripple
for
ten
times.
A
A
So
then,
then
this
unique
is
not
unique,
is
not
representing
the
ci
pipeline
right
then
it
would
be.
I.
A
Which
is
I'm
not
sure
if
we
go
to
other?
I
think
I
know
that
is
way
way
ahead
from
us.
I
think
it's
1.7k.
A
Number
but
yeah
still
so
good.
This
is
increasing.
I
know
it
was
when
I
started
it
was
around
50
or
60,
or
something
very
early
enough.
I
think
when
we
started
working
on
this
project,
so
I
think
it's
still
good
from
again
from
perspective.
A
I
mean
from
last
week
I
have
been
asked
and
I'm
telling
that
I'll
review
it,
but
somehow
I'm
not
getting
time.
So
this
is
the
only
problem.
Right
now
is
that
this
is
adding
a
concurrent
request
going
from
from
processor
to
exporter.
So
that's
probably
the
the
export
interface
is
we're
making
it
as
async-
and
this
is
this-
this
pr
is
invoking
multiple
async
requests
from
processor
to
exporter.
A
A
Somebody
doing
the
default
grid
should
not
get
this
functionality,
but
somebody
who
want
who
want
more
performance,
they
can
always
enable
the
future
flag
and
start
using
that.
A
A
B
Yeah
the
title
in
the
title:
it
fixes
fixes
issues:
12,
6,
36,
12,
35,.
A
Probably
I
may
have
copied
it
from
the
comments
from
some
java
where
it
was,
I
don't
know
I'll
change
it
here.
C
A
Yeah
told
me
that
I'm
talking
to
some
of
them
yeah,
I
didn't
raise
another
pr,
the
periodic
exporting.
Probably
this
is
a
smaller
field.
It's
not
a
big
change.
This
is
going
to
this.
This
is
going
to
basically
create
the
metric
reader
which
periodically
it
is
going
to
do
a
collection
we
define.
C
A
A
A
A
A
A
B
A
Okay
and
always
not
there,
but
I
don't
probably
I
think
we
can
discuss
in
next
meeting
if
we
want
to
do
anything.
A
A
So
curl
is
including
the
kernel
headers
they
are,
they
are
using
some
other
color.
I
mean
they
have
their
own
proprietary
color,
which
they
are
using.
The
linux
color
and
it's
different.
The
headers
are
different
from
what
comes
with
the
default
planet.
Color,
it's
not
coming
from
that.
They
have
their
own
custom.
Changes
in
these
files
and
curl
is
going
curl
is
including
these
headers,
and
so
once
they
include
this
header,
they
they
their
expectation.
A
A
Getting
booted
so
all
the
headers
which
are
defining
these
files
are
not
getting
included
as
part
of
tcp
knowledge
inclusion,
so
normally
let
them
work
with
their
maintainers
of
their
kernel
and
fix
it
under
center.
You
have
some
other
thought,
because
you
also
commented
on
this
but
feel
free
to
check
it
once.
B
A
A
Yeah,
but
there
may
be
a
case
where
say
application
a
is
going
to
send,
so
it's
going
to
send
a
request
to
application
b
and
it
as
part
of
sending
a
request.
It
creates
a
spam,
but
it
won't
also
want
to
add
some
more
spans
which
it
may
have
created
while
sending
a
request
to
say
application
c
or
application
d,
and
it.
A
That
information
also
should
be
there
in
the
expand
context,
or
it
should
be
there
in
the
span
not
spam
context,
but
it
should
be
part
of
that
span.
So
as
part
of
dashboard,
it
should
be
able
to
link.
So
if
I
want
to
see
in
that
board,
I
see
a
given
span.
Click
on
the
other
span,
which
are
linked,
and
I
should
be
able
to
see
the
information
about
those
fans,
although
those
were
getting
used.
A
A
We
can
add
all
these
pans,
which
we
want
to
relate
it
with
the
given
span,
but
we
cannot
add
it
after
we
create
a
span
and
the
reason
why
we
cannot
do
is
because,
when
we
create
a
span
at
that
time,
we
also
so
probably-
I
think
it
should
be
well
explained
here.
A
B
A
So
the
problem
could
be
when,
when,
when
this,
this
pan,
which
we
are
creating,
that
is
getting
so
a
scenario
where
this
span
the
span
which
we
are
creating.
That
is
some
that
is
getting
sampled.
A
The
related
spans
are
not
getting
sampled
or
the
other
way.
It
can
happen
that
the
related
spans
are
getting
sampled
out
or
they
are
not
they're,
they're
they're
being
removed
for
sending,
but
this
span
is
getting
it's
not
sampled
outside,
so
we
may
have
seen
the
dashboard
we
may
see
this
span,
but
the
related
spans
may
not.
If
you
click
on
the
related
span,
you
may
not
be
able
to
see
it
because
it
will
already
get
centered
so
better
to
have
all
the
information
up
front
and
let
sampling
take
a
decision.
A
A
B
A
A
I
mean
I
I'm
not
very
concerned,
even
if
we're
not
reviewing
it
very
thoroughly,
I
think,
as
part
of
release
candidates
that
says,
if
we
can
have
an
end
to
end
which
totally
fine,
I
think
we
can
always
optimize
even
the
scenarios.
If
you
feel
that
your
change
is
going
to
be
it's
it's
it's
it's
going
to
take
lots
of
time,
at
least,
to
support
asynchronous
collection
from
the
same
instrument
with
the
multiple
collections,
the
part
of
views,
which
is
that
configurable
from
mean
that's
totally
fine.
A
I
mean,
if
we
at
least
deliver
something
else,
and
then
we
can
always
always
do
these
changes.
At
top
I
mean
once
we
have
our
increase
connected
before
doing
a
ga.
We
can
always
do
lots
of
changes.
I
mean
right
now,
java
also
they
have
all
I
mean.
Ideally,
they
have
delivered
release
candidate
six
months
back,
but
they
are
doing
awesome
changes
still
yeah,
so
yeah,
it's
good
good
for
us.
A
A
A
Next
week
also,
so
I
think
that's
fine,
I
think
probably
we
can
discuss
next
week
right.
I
had
some
travel
plans
next
month,
okay,
so
because
of
that
I
wanted
if
we
can
change
the
for
next,
probably
next,
at
least
three
weeks
in
april,
if
we
change
one
of
the
schedule
like
this,
this
meeting,
which
we
have
at
one
pm
in
redmond
time,
if
we
can
change
it
to
the
same
time
as
we
have
the
vendor
meeting.