►
From YouTube: 2021-02-17 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
A
So,
like
I
said,
cjo's
not
here
today,
so
he
just
asked
me
to
kick
this
off.
Take
any
notes.
He
said
that
if
there's
any
there's
anything
that
comes
up
that
requires
his
response.
You
can
check
in
afterwards
or
later
this
evening,
but
it
looks
like
victor
is
that
you
typing.
C
C
Sure
I
guess.
C
Sure
so
I
think
this
first
issue
is
a
naming,
so
I
think,
that's
probably
a
more
of
a
of
a
spec
issue
per
se,
but
the
general
question
is:
how
do
we.
C
When
we
create
a
instrument
or
or
what
have
you,
what
is
its
unique
name
and
how
do
we
merge
unique
names
together,
based
on
you
know
the
type
of
instruments
or
the
int
versus
double
or
versus
you
know
the
different
counter
types
and-
and
I
don't
know
that,
how
else
to
make
traction
on
it?
I've
been
pushing
different
areas
but
different
cigs,
but.
C
A
A
Well,
as
you
may
know,
the
the
the
metrics
in
in
dotnet,
specifically,
I
said,
you've
kind
of
been
shopping,
this
around
all
the
six
dot
net,
where
we've
got
a
older
version
of
the
spec
implemented
in
kind
of
a
prototype
state,
and
so
it's
it
we're
basically
waiting
for
the
spec
to
settle
down.
C
So
the
second
issue
relates
to
separation
of
api
versus
sdk
and
again
this
is
more
metric
specific.
I
don't
know
how
to
get.
I
don't
know
how
to
keep
those
two
separate
while
still
treating
them
separate.
More
specifically,
you
need
to
get
just
like
in
trace.
You
need
to
get
a
trace
provider
in
this
case,
get
a
metric
provider,
but
if
you
are
a
third
party
library,
you
cannot
get
a
metric
provider
unless
it's
the
default.
C
All
right,
so
so
the
the
question
I
think
cjo
probably
is
best
to
answer
this,
because
cjo
has
already
provided
some
input
on.
This
is
how
do
I
do
this
and
the
reason
I
want
to
address
metrics
from
instrument
a
versus
instrument
b
is
perhaps
I
want
to
send
the
metrics
from
instrument
a
to
a
different
exporter
than
instrument
from
library
b
and
so
forth.
D
A
Yeah,
I
imagine
so
and
yeah.
I
know
that
cjo
has
been
attending
the
metrics
meetings
and
has
been
staying
apprised
of
that
stuff,
so
yeah.
I
would
poke
him
with
these,
and
I
can
do
that
too.
You
know.
C
Okay,
like
I
said
I
I
didn't
know
if
this
was
the
right
sig
to
bring
it
to
so
I'm
just
hitting
every
one
that
I
can
find
so.
B
Yeah,
I
I
was
kind
of
like
hoping,
cj
or
probably
sergey
would
be
here
because
they
have
some
context.
So
this
is
like
a
long-standing
pr
for
the
aws,
sdk,
client,
instrumentation
and
yeah.
If
you
scroll
down,
there
was
a
point
of
discussion
just
a
little
bit
more
a
bit
more.
B
A
bit
more
yeah,
so
I
think
that
the
long
thread
of
discussion,
if
you
scroll
up
about
using
the
propagator
within
the
instrumentation,
just
look
for
cjo's
comment,
which.
B
Please
yeah
this
one,
so
I
think
yeah
as
a
general
guidance.
I
would
like
to
get
some
idea
on
this
that
so
we
have
two
components:
one
is
the
aws
x-ray
trace
id
generator
and
propagator
that's
in
a
separate
project.
We
call
it
extensions
and
then,
in
this
pr,
I'm
adding
a
new
project
for
the
aws
client
instrumentation.
B
B
C
A
A
A
A
So
yeah,
then
then,
technically
you're
saying
it's
it's
it's
taking
the
dependency
on
the
sdk.
It
would
be
it's
it's
feasible.
So
basically
you're
just
asking
is
this:
this
is
like
a
violation
of
some
sort
of
best
practice
or
something
right.
A
Interesting,
yeah
yeah,
as
you
suspected
cj,
is
probably
a
good
one.
To
comment
on
that.
So
I
think
this
use
case
is
super
interesting.
A
I
don't
know
that
looks
like
there's
been
a
lot
of
people
involved
on
this,
dr,
but
I
don't
know
that
we
have
anybody
on
the
call
today.
A
B
Yeah
yeah
yeah,
my
I
like
my
reason
for
kind
of
expediting
this
is
that
we
have
an
upcoming
release
on
aws
side.
So
I
just
wanted
to
like
understand
if
this
would
float
or
if
there's
a
better
practice,
that
we
can
implement
real,
quick.
B
And
my
other
point
was
about
so
I
I
was
working
on
kind
of
getting
the
contra
repo
to
us
to
a
shape
where
we
can
have
separate
projects
released
separately.
B
I
added
the
github
workflow
for
releasing
to
my
git,
but
couldn't
test
it
because
all
the
maintainers
can
push
the
tag
and
kick
off
the
workflow,
so
I
was
hoping
either
to
get
added
as
a
maintainer.
I
don't
know
if
cj
discussed
this
in
in
the
sake
or
not
or
either
like
have
a
maintainer
work
with
a
maintainer
to
test
out
the
workflow
and
have
the
projects
built
to
make
it
and
then
eventually
to
nougat.
A
Yeah
yeah
again,
I
think
that
cj's
best
to
speak
to
that,
but
yeah
no,
this
is
super
cool
to
see
it
moving.
Is
this
the
work
that
you
did,
the
setting
of
the
package.
B
So
a
different
built-in
release
workflow
for
different
tag.
Prefixes.
A
B
Yeah
so
sorted
out,
the
menuer
attack
prefixing
to
separate
projects
so
that
all
the
projects
can
have
different
versions
and
also
target
different
versions
of
the
open,
telemetry
sdk.
B
Yeah,
I
think
the
one
step
that
needs
to
be
added
is
publishing
to
nougat,
because
I
believe
cj
mentioned
that
it's
being
done
manually
right
now,.
A
B
So
if
you're
looking
at
the
extensions
x-ray
yeah,
so
what
I
would
ideally
want
that
since
it
targets
the
1.0
rc
4
right
now,
I
would
try
it
out
with
a
1.2
rc4
same
version
for
the
extensions
and
then,
if
everything
works
out,
fine
then
cut
a
tag
of
1.0
and
have
that
released.
B
Right
now
that
exists,
that's
a
pretty
old
one!
That's
so!
I
tested
this
out
on
my
personal
fork
and
seemed
to
be
working.
Fine.
B
But
yet
the
release
to
my
get
was
not
executed,
because
I
didn't
have
the
my
get
account
set
up.
A
Okay,
so
yeah,
theoretically,
based
on
that
workflow
somebody
created
a
new
tag
here,
is
that
workflow
triggered
yeah
cool
yeah.
I
guess
we'll
yeah
again
get
sutra's
eyes
nice,
and
maybe
you
can
test
that
out.
Just
need
them
to
create
a
tag
basically
and
see
if
it
does
the
thing.
A
B
A
Okay,
yeah
I'll
try
to
grab
his
attention.
B
A
But
I
don't
have
anything
necessarily,
I
guess
the
big
announcements
you
probably
are
all
aware
of
is
we've
got
a
slack
channel
now.
So,
if
you're
not
already,
if
you
haven't
already
joined
in
join
in
there
and
other
than
that,
I
think
have
a
good
day.