►
From YouTube: 2021-08-10 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
I
heard
something
but
not
clear.
Could
you
repeat.
A
B
B
So
that's
why
I'm
joining
right
now,
it's
also
so
basically,
I
I
know
also
paul
law,
also
from
spike,
which
is
who
is
based
in
singapore,
was
also
mentioning
this
one.
So
basically
we
are
working.
We
are
trying
to
work
on
this
issue,
which
is
about
implementing
the
environment
variables
which
are
in
the
specification
because
we
are
working
on
the
auto
instrumentation
and
we
want
basically
to
you
know
we
prefer
to
do
it
on
the
dotnet
sdk
instead
of
auto
instrumentation
source
code.
B
I'm
just
so
I'm
just
wanted
to
make
sure,
because
there
are
some
pr's
and
there's
some
things
which,
which
I
have
questions,
I'm
not
sure
if
it's
better
to
discuss
here
or
in
dprs,
because
some
some
that's
one
thing
and
also,
if
there's
anything
that
I
can
do
to
basically
make
the
work
faster.
A
Yeah
can
you
like,
because
I
think,
like
I
I
was
on
vacation
last
week,
so
I
I
don't
know
like
whether
anything,
okay.
A
B
A
Yeah
I
mean
I
remember
like
merging
something
like
earlier
today,
but
yeah.
This
is
something
which
I
haven't
had
a
chance
to
look
at.
So
do
you
have
like
something
in
specific
about
this
pr
which
you
want
to
bring
discuss
now
or
yes,
you're,
just
okay
yeah.
Can
you
okay.
B
The
one
the
one
important
thing
which
I
want
to
discuss
you
can
even
see
the
conversation
is
about.
Basically,
I
don't
know
the
design
guidelines
this
one.
This
one
is
not
that
important.
I
think
this
one
can
be-
or
maybe
this
was
this
one
yeah.
B
B
So
he
made
a
very
good
point
that
this
class,
which
is
named
batch
export
processor
options,
looks
like
something
generic
for
all
the
or
the
signals,
meaning
traces,
probably
metrics,
and
locks
right
or
not.
Is
it
intentional.
A
Correct
it
is
intentional,
it
is
common
for
traces
and
loads.
We
don't
know
yet
whether
it
will
be
applicable
for
matrix
or
not,
because
matrix
does
not
really
have
the
same
notion,
so
it
may
not
be,
but
at
least
it
is
applicable
to
both
traces
and
logs
as
of
now
and
potentially
in
the
matrix.
We
just
don't
know
it.
B
So
right
now
it
is
even
used
in
the
metrics.
It
is
used
in
the
otlp
metrics
exporter,
but,
however,
some
of
the
stuff
is
in
reality
not
used,
and
basically
here
I
have
some
questions
regarding
how
to
follow
up.
I'm
not
sure.
Personally,
you
know
I
I'm
just
getting
into
this
source
code,
I'm
not
sure
if
it's
a
good,
a
good
good
thing
that
we
want
to
reuse
the
same
options
for
all
the
signals.
B
This
is
one
of
the
problem,
and
second
problem
is
that,
even
if
we
want
to
reuse
it,
I'm
not
sure
how
to
follow
up.
I
see
three
options
and
I
described
in
dpr,
but
I
think
we
it
will
be
better
just
if
you
look
at
it
offline,
but
basically
I
think
it's
one
of
of
kind
of
things
that
it's
not
easy,
and
maybe
you
know
some
time
and
nights
to
think
about.
A
Okay
got
it
yeah,
I
think.
Like
I
mean
I
mean
from
what
what
I
see
here
like
this
particular
class
is
generic,
but
I
think,
even
in
like
some
of
the
exporters,
we
did
like
make
sure
that
we
have
like
a
one
which
implements
with
t
equal
to
activity
and
one
with
equal
to
log
record,
but
not
necessarily
for
this
one.
A
So
like
I
I
have
to
like
look
at
like
what
was
the
like
point
where
we
have
like
this
discussion,
I
had
haven't,
had
the
chance
to
look
at
it.
Okay,
so
I
can
take
a
read
and
post
back
my
thoughts
on
this,
but
the
matrix
part
is
like
just
a
like
potential
thing.
We
haven't
confirmed
whether
we
will
need
it
or
not
for
metrics
it's
possible
that
we
won't
need
it
in
metrics.
A
We
may
go
for
like
something
else,
but
that
is
still
to
be
decided,
but
like
does
the
spec
defines
this
as
something
which
is
specific
to
tracing,
or
is
it
more
like
generic.
B
A
B
Correct
and
one
of
the
findings
which
may
also
maybe
I
would
prefer
to
ask,
because
it
may
also
help
in
future.
Maybe
if
I
do
some
code
reviews
is
that,
right
now
the
otlp
metrics
exporter
uses
it's
mine
comment
from
yesterday,
like
I
noticed
that
otop
exporter
uses
otlp
exporter,
which
has
batch
export
processor
options
from
activity
which
feels
pretty
wrong.
That's
from
activity.
A
Yeah,
I
think
it's
probably
like
a
two
early
stage
because
and
ellen
is
working
on
the
otp
sport
he's
trying
to
reuse
whatever
available.
But
if
it
doesn't
make
sense,
then
we
can
refactor
it
out.
Yeah,
okay,.
A
B
C
A
B
Okay,
okay,
so
thanks
for
your
time
and
attention,
so
the
the
bad
news
is
that
the
next
two
weeks
I'll
be
on
pto
but
I'll.
Ask
my
colleague
from
splunk
that
he
can
take
it
over.
So
I
will
make
sure
that
it
will
just
move
forward
and
also
a
question,
because
I
feel
that
you
know
I'm
just
making
prs.
Do
you
need
any
part?
Do
you
need
any
code
reduce?
Is
there
anything
important
that
you
need
to
help
on
or
is
it
okay?
We
just
contribute
here.
A
A
Should
be,
I
mean
if
you
see
like
any
issues
where
you
can
contribute,
go
for
it,
but
I
don't
have
anything
in
particular
right
now
to
go
and
assign
to
people.
A
Like
michael,
did
you
have
any
comment
on
this
thing
I
saw
like
you
had
some
reviewed
already,
but
like
is
there
anything
michael?
You
want
to
discuss
now
about
this
one.
C
C
I
think
that's
the
better
way
to
do
it,
but
I
don't
know
if
we
can
do
that
without
breaking
the
trace
side
of
it.
So
we
could
have
a
different
pattern
for
metrics,
but
that
feels
kind
of
weird
too,
like
I
like
that,
it's
all
the
same
right
now
and
we
should
try
to
keep
it
that
way.
So
I
don't
I
don't
know.
I.
A
A
C
B
Scroll
down
a
little,
if
you
scroll
down
here,
I
made
a
proposal
for
the
for
like
for
the
inheritance
way,
so
this
is
here
just
maybe.
Instead
of
this,
I
just
made
a
bug
that
it
should
not
be
the
generic
glass
one
on
the
right
side,
just
making
some
from
export
processor
options,
but
I
it
will
be
kind
of
a
breaking
change
in
my
opinion,
but
I.
B
Not
explicit
because
you
will
don't
do
only
in
the
setter,
so
it
will
not
be.
You
know
exposed
so
here
in
the
api,
the
getter.
It
will
be
the
same
type,
we'll
just
replace
it
in
the
like.
You
know
with
the
constructor,
so
it
so
it
will
be
only
not
compatible
if,
for
example,
someone
would
use
generics
or
stuff
like
not
generics.
I
want
to
say.
A
Yeah
got
it
yeah
I'll,
take
a
detailed
look
later
today
and
see
if
I
have
anything
better
or
maybe
like
we'll,
be
able
to
stick
with
this,
and
we
won't
be
able
to
like
use
a
different
immune
variable
than
this
one,
because
this
is
spec
mandated.
Even
though
the
term
s
doesn't
seem
correct
for
activity,
but
I
think
that's
something
which
we
have
to
deal
with:
okay,
yeah
I'll,
look
at
the
pr
and
leave
any
other
comments
here.
A
Okay,
yeah,
okay,
so
you
have
like
more
upcoming
right.
That's
what
you
mean
by
like
the
from
open
and
what
are
coming.
Okay,.
A
Yeah
you
can
like
it
will
be
much
easier
for
us
to
like
like
comment
if
you
have
like
some
pr
or
even
describe
this,
maybe
like
like
this
is
a
specific
issue
which
you
want
to
discuss
right.
A
You
have
an
enrollment
variable
which
determines
which
export
to
be
loaded
or
which
exporters
to
be
loaded
and
because
okay
yeah,
I
I
haven't
thought
about
this
thing,
but
we
cannot
do
this
in
the
sdk
alone,
because
the
sdk
doesn't
have
a
dependency
on
the
zip
code,
so
it
cannot
just
loads
again.
So
it
has
to
be
like
something
else
like
some
other
component,
which
knows
about
exactly
all
these
exporters
right,
wow.
B
B
A
Yeah
this
is
like
very
tricky
part
because,
like
for
example,
if
someone
says
their
exporter
is
like
jager-
and
we
cannot
like
do
anything
until
that
jager
that
nuget
package
itself
is
loaded,
so
the
sdk
cannot
do
it.
So
we
need
to
invent
something
to
make
sure
that,
like
if
reger
is
available,
go
and
use
it
yeah.
Otherwise,
okay,.
B
A
A
So,
michael,
do
you
have
any
thoughts
on
this
because,
like
we
did
discuss
something
like
this
in
the
past
about
like
adding
a
like
a
convenience
nougat
package
which
kind
of
take
dependency
on
the
sdk
and
all
the
exporters
and
all
the
instrumentations
and
like
since
it
knows
about
all
these
packages?
It
is
something
which
can
react
to
this
environment
variable
and
load
the
right
one.
A
C
We
talked
about
doing
like
a
made-up
package
that
doesn't
have
any
content.
It
just
pulls
in
like
if
you're
doing,
net
core
it
gives
you
the
hosting
and
the
xdk
and
like
the
basic
stuff.
I
don't
know
how
else
you
could
do
this
without
something
similar
like
a
package
that
references
all
the
exporters
that
the
auto
instrumentation
could
consume
and
then
has
a
method
that
it
calls.
You
know
on
the
tracer
provider
that
looks
at
the
environment
variables
and
then
registers
the
specific
exporter.
A
Yeah,
I
think,
like
I
mean
it,
won't
be
like
a
just
a
meta
package.
It
would
be
like
a
package
which
contains
code,
and
it
also
refers
to
all
other
package
yeah.
A
Yeah,
I'm
thinking
like
just
to
confirm,
like
it
would
contain
code
like
something
like
this
right.
Exactly
okay
got
it
and
it
looks
like
instead
of
looking
for
this
configuration,
it
will
just
look
for
it
in
the
informal
variable
and
based
on
that
it
decides
to
add,
and
it
can
add,
because
it
has
dependency
on
jaeger,
zipkin
and
all
the
exporters.
A
Okay.
That
sounds
like
a
good
approach.
Yeah,
if
you
can
like
create
a
like
separate
issue,
just
making
it
more
clear
like
why
are
we
going
with
that
option?
That
rubric
I
mean,
I
vaguely
remember
like
this
comment,
but
I
never
got
time
to
respond
to
it.
Glad
that
you
brought
it
up.
Can
you
just
like
create
a
separate
issue
just
for
this
one
proposal
make
a
proposal
about
introducing
a
new
package
which
can,
which
is
where
we
can
have
this
project.
B
B
To
create
some,
you
know
something
that
can
be
used
even
without
a
snippet
package.
Just
to
not,
you
know,
lock
the
users
just
if
they
want
to
use
this
functionality
that
they
have
to.
You
know,
use
some
hard
coded.
You
know
code,
I
prefer
to
create
something
that
then
can
be.
You
know,
I
think
you
know
what
I'm
sorry
it's
pretty
late
for
me
and
I
have
probably
I
have
problems
just
me.
What
I'm
thinking
about,
but.
A
Got
it
yeah
and
happy
to
review
them
as
soon
as
they
come
yeah
in
case
you
don't
see
like
q
correction,
you
can
just
just
ping
on
the
slack
because
sometimes
like
in
the
front
of
peers,
we
may
like
miss
some
of
them
so
like,
if
you
see
anything
which
requires
our
gender
attention.
Just
like
being
us
right,
we'll
respond.
A
Okay,
yeah
just
an
update
on
the
next
one.
It's
basically
just
fia.
We
discussed
this
last
week
saying
about
like
migrating
the
espana
elementary
module
to
the
open
elementary
repo.
So
it's
pro
progressing
so
michael
like
is
there
anything
which
you
want
to
like
discuss?
I
just
put
it
as
an
agenda
as
an
there
is
no
action
item
but
michael
like
is
there
anything
which
you
want
to
discuss
about
this.
C
A
Yeah,
would
you
consider
like
moving
entirely
from
the
legacy
way
to
activity
source
pay.
C
I
have
many
thoughts
about
it.
I
was
going
to
ping
you
later
and
just
run
some
by
you
and
kind
of
see
what
what
you're
thinking.
A
A
C
The
diagnostic
source
diagnostic
listener
and
go
all
activity
source
and
then
let's
come
along,
maybe
do
the
metrics.
A
C
What
I
kind
of
like
to
do
is
give
so
we
have
the
asp.net
instrumentation,
that's
basically
getting
the
activity
that
was
created
and
then
it
needs
to
do
post-processing
to
say.
Okay
was
this,
you
know
trace
context
and
it
really
should
be
b3
and
then
we're
going
to
create
a
new
activity.
I'd
like
to
kind
of
put
some
options,
some
way
to
get
at
the
module
through
the
sdk
and
then
register
whatever
propagator
the
sdk
has.
So
we
can
kind
of
cut
out
that
extra
activity
all
that
processing.
C
A
A
C
C
A
I'm
pretty
sure
like
we
did
like
there
is
an
activity,
dot,
custom
property
which
can
be
used
to
store
the
exception,
but
that
would
be.
I
don't
think
there
is
a
chart
activity
api
which
can
take
anything
custom
property
so
well.
It
depends.
C
How
open
telemetry
compliant
we
want
to
make
the
module.
So
if
we
move
some
of
our
tag
stuff
into
the
module,
then
you
know
like
the
standard
http
stuff,
like
the
the
semantic
conventions.
If
we
do
run
into
an
exception,
there
is
the
exception
part
of
the
spec.
We
could
just
build
the
activity
event.
You
know
instead
of
passing
the
exception
to
the
instrumentation,
so
it
can
decompose
it
into
tags.
We
could
just
do
that
in
the
module,
so
an
exception
event
is
really
not
an
event.
C
A
Makes
sense
only
thing
is
the
thing
if
you
compare
that
with
sp
net
core,
we
have
the
enrich
where
we
allow
the
user
to
get
a
hold
of
the
actual
exception.
So
if
we
convert
that
exception
into
an
activity,
even
we
would
no
longer
be
able
to
do
that,
but
that's
probably
the
right
way,
because
open
elementary
does
not
like
recommend
anything
else
for
exception.
So
probably
that
should
be
enough
like
if
that's
the
case,
what
you're
saying
is
we'll
like
do
activity,
source,
dot,
start,
stop
and
dot?
C
A
That
makes
sense
here:
okay,
yeah,
like
we,
we
have
the
luxury
of
like
breaking
so
feel
free
to
go
ahead
and
break
things
to
make
things
better,
but
we
didn't
have
that
luxury
when
it
was
in
the
hp
network.
So
cool.
C
C
C
A
It
is
indeed
used
because
we
have
other
packages
which
has
like
very
few
downloads
so
compared
to
that
this
is
very
high,
but
it's
not
like
really
as
because
the
actual
open
elementary
itself
is
crossed,
like
2
million,
so
yeah,
but
like
I
think
I
agree
with
what
you
said
like
when
people
upgrade
from
the
current
version
to
the
new
one.
This
would
be
a
breaking
thing,
but
we
can
my
opinion
is.
We
can
just
understand
the
change
log.
We
don't
need
to
write
anything
more.
A
A
Let's
see
like
how
that
look
like
when
you
like,
add
that
into
the
change
look.
If
it
is
like
really
a
breaking
thing,
then
we
can
put
a
note
here
somewhere
in
there.
It
missing
that.
Okay,
if
you
are
coming
from
rc7-
and
you
are
upgrading
to
the
new
version-
please
pay
special
attention
to
the
web.config,
because
we
made
some
breaking
changes
in
between.
A
So
we
can
find
a
balance
which
one
is
better:
either
change
log
entry
or
like
something
in
this
readme
itself,
but
that,
aside,
like
there
shouldn't,
be
any
change
for
the
industry
like
they
still
do
like
this
one
liner
and
it
should
just
work.
C
A
Okay
and
yeah
I
mean,
depending
I
don't
I
mean
also
we
don't
intend
to
break
this
one
either
like
we
would
still
be
having
this
enriched
functionality.
Even
though
we
are
not
firing
the
diagnostic
source,
we
still
be
able
to
offer
this
opportunity
for
users
to
enrich
themselves.
This
should
still
work
and
we
never
offered
exception
in
the
first
place.
So
that
should
not
be
an
issue,
but
we
will
still
be
recording
exception
assigned
event:
okay,
okay,
yeah.
I
think
it's
going
very
nicely.
A
Okay,
yeah
look
for
look
forward
to
see
something
as
to
that.
Okay,
yeah
last
topic
is
about
metric,
so
I
did
fine.
Okay
is.
A
The
issue
which
I've
been
asking
people
to
make
the
api
oh
come
on.
I
cannot
copy
paste
to
be
a
location
free,
so
the
dotnet
design
team
had
a
different
feedback.
This
like
this,
was
just
literally
like
half
an
hour
ago.
So
please
take
a
look
at
this.
This
is
quite
likely
based
on
what
I
see
in
the
design
meeting.
A
This
looks
like
everyone
has
his
favor
in
this
approach,
as
opposed
to
adding
like
overloads
taking
four
five
six,
seven,
eight
there
is
recording
available
in
case
anyone
wants,
but
this
looks
like
the
likely
candidate
to
solve
this
problem
and
I'm
still
hoping
that
this
will
be
part
of
the
dot
net.
Six,
so
just
sharing
an
update,
yeah.
I
do
have
like
some
refactorings.
I
did
not
do
anything
like
last
week,
partially
out
of
office
last
week,
so
back
to
work
this
week.
A
So
I'll
be
doing
these
changes
and
alain
added
a
new
instrumentation
library
for
http
line
which
builds
the
histogram
which
was
merged
last
week.
So
when
we
release
the
next
one,
we
should
have
histogram
support
as
well
and
along
with
the
perfect
refactoring
and
depending
on
how
much
time
we
have
left.
A
After
all,
this
refactoring,
we
might
have
the
asynchronous
instruments
as
well
and
potentially
the
mini
view
or
like
subset
of
you
as
well,
but
I
just
don't
know
like
how
much
time
we'll
have
in
the
next
three
days
to
finish
so
try
to
do
as
much
as
possible
and
anything
which
don't
make
the
cut
for
this
week's
release.
We'll
do
a
release
next
week.
So
I'm
happy
to
do
like
as
many
releases
whenever
we
are
having
features.
So
even
if
it
means
doing
a
release
every
week
or
every
other
week.
A
Okay,
any
other
topics.
I
think
there
are
few
issues
which
were
like
relatively
new.
Okay,
I
think.
Oh,
this
is
brand
new
yeah,
but
if
anyone
has
like
time,
please
look
at
open
issues
and
if
you
can't
respond,
that
would
be
great.