►
From YouTube: 2022-01-06 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
I
I'm
not
hearing
diego,
but
I
don't
know
if
it's
me
or
someone
else.
B
D
C
All
right,
okay,
well,
welcome
everybody
to
another.
C
E
E
C
All
right,
so
I
guess
we
can
start
now
right
all
right.
So,
let's
see
if
I
can.
C
I
guess
well
last
year
ended
with
progress
with
the
metrics.
B
No,
I
I
was
also,
but
I'm
I'm
pretty
excited
about
getting
some
of
the
the
pr's
that
I
have
reviewed
and
get
them
moving
forward.
I
I
started
working
on
the
otlp
tricks
exporter
and
also
tried
to
bring
back
the
prometheus
exporter.
B
I
think
I'm
hoping
to
get
at
least
the
kind
of
the
skeleton
pr
that
I
have
for
the
otlp
exporter
in
so
that
I
can
start
filling
in
the
details,
but
then
yeah,
I
guess,
there's
probably
going
to
be
a
probably
another
week
or
so
of
effort
to
try
and
get
the
details
in.
C
All
right,
great
srikant,
I
think
you
were
active
during
this
few
weeks.
Is
there
any
topic
you
would
like
to
mention.
A
There
wasn't
much
that
that
has
happened
over
the
past
few
weeks.
I
I
was
fairly
active,
looking
at
the
issues
and
prs,
but
yeah
there's
nothing
really
much
to
talk
about.
C
All
right,
thank
you
very
great.
Well,
we
I
think
we
can
move
to
the
next
topic
that
says:
metrics
work,
progress,
just
curious,
whether
this
typical
list.
C
All
right:
well,
I'm
back
with
metrics
I
I
have
a
still
several
github
notifications.
I
need
to
take
a
look
but
yeah
pretty
much
focusing
on
that.
C
I
found
an
issue
that
aaron
opened
about
not
using
a
linear
search
for
the
histogram,
which
is
a
great
idea.
C
Working
a
little
bit
that
hopefully
I
can
have
a
small
pr
open
today
after
that,
I
should
pretty
much
continue
with
looking
into
all
the
issues
and
focusing
especially
on
the
metrics
ones.
C
B
B
I
think
it's
refactoring
aggregations.
I
forget
the
the
number
of.
C
C
I
really
can't
find
it
okay.
Yes,
we
have
all
right,
let's
see
what
you're
saying
I
don't
know
instagram.
C
C
So
I
think
that
this
pr
has
well
a
bunch
of
stuff
that
can
go
in
right
now,
but
aaron
has
raised
several
important
points.
The
need
to
be
at
rest.
Maybe
this
pr
can
be
splitted.
Maybe,
but
I
don't
know,
I
don't
know
what
do
you?
What
do
you
think?
Do
you
think
this
pr
can
be
splitted
and
the
pending
topics
be
addressed
later?
F
Sure
that
sounds
fine.
We
should
try
to
try
to
get
merged
all
right.
I
have
to
go
over
the
comments,
because
I
don't.
C
Great,
yes
sure
so
I
can.
C
In
fact
this
will
be
the
first
vr
that
I
that
I
go
back
to
once.
I'm
done
with
the
stuff
that
I'm
doing
with
the
histogram,
and
I
can
probably
work
on
splitting
this
a
little
bit
so
that
the
pending
stuff
can
be
addressed
later,
but
yeah
that
that
that
should
be
the
status
of
these
erls.
C
B
Okay,
cool
yeah-
I
I
was
mostly
just
curious
of
what's
what's
left
on
it
and
if
there,
if
there
are
issues
we
can
always
open
issues
and
and
fix
them
after
the
fact
like
we
don't,
we
don't
have
to
have
it
perfect
on
the
first
try
here.
C
All
right,
great,
any
other
comments.
Someone
wants
to
add
regard
metrics.
E
This,
let
me
ask
yeah
hi,
so
I
added.
E
G
So
this
is,
like
google,
basically
donated
this
sql
commenter
library
last
year
or
during
september.
So
initial
discussion
like
we
started
migrating
the
pack
renaming
the
packages,
but
our
first
milestone
is
basically
releasing
it
from
open,
telemetry
repositories.
So
currently
the
code
is
present
in
two
repositories.
One
is
in
google
cloud.
One
is
an
open
telemetry
because
we
haven't
completed
the
migration
like
there
is
no
release
versus
open
telemetry.
G
So
what
you
want
to
do
is
like
create
a
release
version
for
sql
commenter
from
open,
telemetry
and
depict
google
google
cloud
like
repository.
Then
there
might
be
discussions
on
how
is
it
like
feasible
to
integrate
with
open,
telemetry
python
this
libraries
or
like
that
will
be
like
a
next
level
discussion.
C
Yeah,
so
I'm
not
that
familiar
with
sql
commenter.
Can
you
give
us
a
little
bit
more
questions.
G
So
it's
more
like
a
library
to
instrument
the
sql
queries,
so
what
we
do
is
like
customer
have
orms
like
they
can
use
django
or
flask
as
frameworks
and
their
queries
would
pass
through
either
the
rm
libraries
mostly
and
what
happens
is
like
they
really
don't
know.
What
is
the
query
really
generated?
G
They
would
be
just
using
the
oral
vm
functionalities.
So
let
me
say
the
links
I
think.
C
All
right
great,
I
don't
know,
if
is
this
the
first
time
you
joined
this
meeting.
G
C
Okay,
I
don't
know
if
you're
already
familiar
with
these
repo
pendulum
three
python
controller.
C
Okay,
if,
if
what
you're
trying
to
do
can
be
done
with
with
an
instrumentation
plugin,
then
what
you're
trying
to
do
should
be
added
into
this
repo
via
pr
and
the
normal
process.
So
here
in
this
repo,
we
have
all
the
components
that
integrate
the
third-party
components
that
integrate
with
the
core
consulate,
python
components
like
the
api
and
sdk
and
so
on.
So,
for
example,
we
have
some
instrumentations
here
for
the
different
frameworks,
class
jungle,
salary
and.
C
Maybe
what
you're
trying
to
do
can
be
done
like
pretty
much
everything
else.
That
is.
G
Mean
this
is
the
plan
generally
to
add
it
into
country
libraries,
but
the
challenges
here
is
like
so
this
it
contains
a
specs
because
it's
like
database
instrumentation,
which
is
adding
information
like
what
are
the
roots
of
what
other,
like
controllers
and
all
these
acts
and
layers.
All
these
things
into
sql
query.
So
the
instrument-
and
it
contains
four
languages-
python,
java,
ruby
and
node.js,
and
so
before
directly
adding
it
to
the
concretes.
G
My
understanding
was:
we
have
to
decide
on
the
specs
first,
like
all
the
language
or,
basically,
all
the
language
owners.
They
have
to
agree
on
the
specs
open,
telemetry
specs
team
also
has
straggly
on
the
specs
that
this
is
fine
and
then
I
thought
like
we
could
move
it
to
each
of
these.
Individual
countries
like
that
was
my
understanding.
So.
C
Okay,
yeah,
I'm
not
totally
sure
about
the
that
or
those
challenges.
Maybe
what
can
be
done
is
to
open
up
an
issue
here.
You
can
open
up
an
issue
here
and
discuss
all
the
challenges
that
you
think
you're
finding
now.
B
G
That
is
the
one
which
needs
discussion
so
as
of
now,
what
we
are
thinking
is
like,
let's
release
it
from
the
current
open,
telemetry
repo
like
there
is
a
single
repo
currently
for
a
sequel,
commenter,
let's
start
release
from
there,
and
so
I
posted
a
link.
There
is
it.
Oh
sorry,.
G
Yes,
so
yeah
all
the
four
languages
from
here
at
the
start,
deplete
the
google
cloud
one
cloud
repository
so
that,
like
people
want
to
contribute,
they
will
actually
start
contributing
in
this
one
which
is
going
to
be
in
the
like
moving
the
future
one
future
repository.
G
A
Thing
is
whether
or
not
do
we
want
to.
You
know
migrate
away
like
all
this
code
into
the
country,
people,
that's
a
that
that
will
be
decided
later.
What
what
he
is
trying
to
you
know
do
right
now
is
if,
if
he
can
get
it
tokens
for
the
pipeline,
he
can
release
the.
As
is
like
this
with
the
just
the
naming
change
in
the
open
telemetry,
you
can
release,
as
is,
and
if
you
want
to
you
know,
move
this
code
to
the
contributing
for
each
language.
A
That's
the
next
discussion,
so
he
is
basically
asking
for
the
help.
In
you
know,
new
tokens
under
the
open
telemetry
are
likely
token.
A
C
I'm
not
gonna
be
here
with
five
but
yeah
yeah.
Sorry.
B
I
I
guess
the
best
thing
to
do
would
probably
be
to
open
an
issue
if
there
isn't
31
in
the
open,
telemetry
contrib
repo
to
get
get
a
set
of
tokens,
because
this
will
require
some
work
because
with
pi
pi
you
have
to
publish
a
package
first
before
it
shows
up
as
a
project
that
you
can
manage.
So
we
would
have
to
publish
a
package
first
and
and
then
create
a
separate
token
that
can
only
be
used
for
that
project
to
be
able
to
to
share
it
with
the
sql
commenter
repo.
B
Yeah
and
then
someone
will
just
someone
who
still
has
access
to
the
account
will
just
have
to
publish
the
initial
package,
and
then
we
can
create
a
token
that
is
scoped
to
the
sql
commenter
package,
and
then
you
can
use
that
until
the
until
the
package
just
moved
into
the
contrib
repo.
Does
that
does
that
work.
C
Great
all
right,
moving
on
the
next
section
pr,
there
are
no
pr's
issues.
B
Think
sorry,
I
think
they
didn't
said
that
we
can
leave
his
his
issues
until
next
next
meeting
since
he's
not
around.
C
All
right,
do
you
see
sure
in
the
next
one
yeah
all
right?
Well,
I
guess
we're
done
for
today.
Someone
else
has
any
questions
or
comments.
C
No,
if
not
we'll
see
you
all
next
week,
hopefully.