►
From YouTube: 2022-03-23 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
A
C
B
So
so
you
just
you,
came
back
to
this
nice
weather.
D
C
No,
it's
just
job
took
us
away
from
took
us
to
la,
but
we
were
able
to
find
a
way
back
to
seattle,
which
is
great
because
I
mean
I
moved
up
here
from
microsoft.
Yeah.
We
absolutely
love
seattle,
so.
B
Yeah,
I
I
love
here,
but
to
be
fair,
I
I
also
like
la
a
lot.
You
know,
especially
that
if
you
go
a
bit
to
the
south
in
between
l.a
and
san
diego,
there
are
some.
E
B
Places
there
you
know
all
right,
let's
get
started.
Welcome
back
to
seattle,.
B
Okay,
we
have
just
one
pull
request
open,
but
let's
discuss
that
later,
I
think
rasmus
has
some
interesting
stuff
that
he
mentioned
on
slack
that
we
we
should
look
at
that
in
more
detail.
E
This
one
I
created
yesterday,
so
I
was
trying
to
I'm
trying
to
check
how
we
can
get
the
metric
export.
I'm
just
doing
the
base
work
on
this.
So
during
that
point
in
time
I
found
there
are
several
like
generic
names.
We
have
from
an
environment,
variable
standpoint
and
also
from
the
file
standpoint.
E
A
simple
example
would
be.
We
have
an
instrumentation.cs
like
that
can
be
named
renamed
to
a
tracer
instrumentation.cs.
E
Similarly,
we
can
have
a
metric
instrumentation,
because
logs
traces
and
metrics
are
all
three
different
signals,
so
we
should
have
a
control
to
enable
or
disable
one
of
the
signals
in
that
the
I'm
slowly
going
to
do
those
three
names,
and
even
our
samples
are
all
in
one
folder,
maybe
like
organizing
it
with
the
traces
will
leave
us
a
way
to
get
it
started
on
the
other
metrics
or
the
logs
work.
So,
as
a
prep
of
this,
I
found
these
environment
variables
it's
better
to
get
it
fixed
before
the
beta
release.
E
B
So
but
but
we
could
imagine
in
the
scenario
that
in
the
future
we
say
kind
of
measure
use
a
measure
to
get
latency
for
a
method.
So
people
couldn't
give
that
so.
B
Since
you
are
brainstormed
before
you
kind
of
go
and
and
do
anything
I
I
was
thinking
just
just
for
brainstorm-
I'm
not
saying
this
is
good.
I
also
is
starting
from
a
position
that
I
actually
think
what
I'm
going
to
say
down,
probably
is
not
good,
but
we
could
do
things,
for
instance,
a
console
exporter.
We
could
put
trace
metrics
logs
in
the
value
you
know,
but
I'm
I
I
tend
to
think
that
it's
simpler
if
you
do
with
the
environment
variables,
so
the
question
will
be
on
the
other
way
around.
B
F
E
Yeah,
I
also
spoke
to
the
sdk
folks
internally
here,
so
now
they
create
all
these
three
signals
as
different
and
at
some
point
in
time
there
will
have
some
combined
like
a
wrapper
or
something
which
will
enable
the
user
to
do
like
call
one.
Instead
of
using
a
tracer
provider
and
metric
meter
provider
and
everyone,
they
will
have
only
one
thing
which
can
enable
all
three
of
them.
A
Yeah,
okay,
so
I
think
we
we
can
have
some
discussion
on
the
issue
itself.
I
think
what
pilate
mentioned
is
also
reasonable.
So
add.
B
Those
there
and
then
when
you
have
a
chance,
it
starts
to
work
on
those,
because
I
also
think
it
it's
a
beta.
We
can
change,
you
know,
but
if
you
want
to
do
that
before
the
beta,
it
seems
reasonable.
You
know
kind
of
people
already
start
with
what
we
are
going.
So
these.
E
Are
kind
of
between
the
betas
a
bigger
like
change
when
they
upgrade
also
so
if
we,
if
these
are
taken
care,
this
is
these
are,
according
to
me,
a
very
big
change,
so
it
will
be
easier
for
the
users
who
uses
it.
B
Okay,
so
let's
not
put
this
on
beta,
but
one
thing
that
I'm
I'm
I'm
thinking
here.
B
Do
you
have
a
way
we
have,
of
course,
but
this
is
a
major
implementation,
but
this
is
something
that
perhaps
we
want
to
bring
with
the
sdk
folks.
This
kind
of
I
think
they
have
some
common
code
for
getting
environment
variables
this
thing,
but
could
we
do
the
code
in
a
way
that
everything
that
uses
the
sdk
to
implement
the
the
the
instrumentation
kind
of
automatically
conforms
to
the
kind
of
environment
variable
that
we
need?
B
Let's
say
there
is
some
instrumentation
that
has
some
environment
variable
okay,
so
they
could
do
a
a
way
that
they
add
an
attribute
and
we
can
do
ideally
nowadays
we
can
do
even
before
they
ship,
but
at
build
time
generate
code
that
includes
environment
variable.
If
I
stand,
their
name
includes
the
method
to
configure
and
then
everything
we.
We
know
that
all
those
contributes
that
come
from
the
open,
telemetry
itself
will
be
kind
of
following
the
standard
for
environment
variables.
B
I
I
I
I'm
being
ambitious
here.
I
think
this
is
not
something
that
I
think
for
us
to
take
here
in
this
week,
but
I
think
this
is
a
conversation
that
we
want
to
have
with
the
sdk.
So
then
we
ensure
that
whatever
instrumentation
the
the
configuration
is
always
kind
of
work
with
the
environment
variables
and
the
methods
that
perhaps
we
need
to
inject
the
instrumentation.
E
So
you
are
saying
everything
in
the
country:
repo
every
project
should
have
a
special
environment
variables
for
itself
too.
B
B
Can
I
put
some
here
that
automates
and
ensures
that
these
things
are
consistent?
You
know
all
of
them
have
environment
variables.
All
of
them
have
the
method
that
follows
the
pattern
for
the
builder
everything
you
know.
As
I
said,
I'd
be
ambitious,
but
I
I
think
that
makes
our
case
easier
and
users
easier.
You
know,
so
I
think
it's
worth
kind
of
perhaps
reaching
back
to
the
sdk
and
try
to
have
a
conversation
around.
That
is
not
something
immediately,
but
for
the
future.
B
And
this
there
was
some
updates
or.
A
B
So
I'm
I'm
still
working
on
cleaning
up
the
samples,
I'm
unifying
the
sample
for
a
startup
hook
and
asp.net
core
that
we
have,
because
they
are
basically
the
same.
I
just
gonna
put
one
and
put
in
the
script
a
way
to
launch
in
both
ways
you
choose
I
am
about
to
probably
later
today.
I
still
have
to
do
kind
of
three
things
before
I
can
submit
the
the
pr,
but
I
will
have
a
pr
that
improves
a
little
bit
more.
B
The
samples
after
that,
I
have
the
thing
that
I
want
to
discuss
regarding
the
the
name
of
the
sample
project,
but
I
want
to
do
that
afterwards,
so
we
should
expect
trupiaz
to
complete
this
item
333,
the
one
that
I
should
open
today
after
I
fix
the
remaining
things
and
the
follow-up
after
our
discussion
for
rename,
and
then
we
should
be
good
to
complete
this
one.
E
One
question
there
apollo,
so
you
said
the
rename
right
it
is
like
aligning
the
namespaces
right
yesterday
when
I
was
looking
at
that
part,
every
sample
has
its
own
namespace.
So
are
we
going
to
group
it
together,
like.
D
B
Our
all
the
other
projects
have
prefixes
that
make
sense
and
just
to
kind
of,
let
me
change
the
share
here.
B
I
was
just
so,
for
instance,
here
if
I
come
to.
B
Configuration
manage
that
so
you
see
here,
everything
has
a
nice
prefix,
so
you
can
kind
of
find
the
stuff
that's
related
and
you
can
deal
with
them,
but,
for
instance,
this
is
a
sample
application
used
in
tests.
This
is
a
actual
sample
application
and
the
other
ones
are
all
kind
of
all
over
the
place.
So
I
want
to
organize
this
in
a
way
that
kind
of
makes
sense
you
know,
and
then
the
namespaces
we
should
change
accordingly.
B
You
know
so
I
I
kind
of
anticipated
a
bit
what
I
wanted
to
discuss
on
that
topic,
but
we
get
back
and
kind
of.
Let's
try
before
I
do.
Let's
try
to
settle
on
the
pa
pattern
that
we're
gonna
use
for
that.
B
Okay,
so
chris
is
not
around
so
no
progress
on
that
vacation,
which
is
good
robert's,
not
here
today,
rasmus
any
chance
did
you
have
any.
G
Chance
to
touch
on
those
or
are
you
blocked
by
something
I
think
actually
the
asp.net
test
can
be.
B
By
the
way,
regarding
additional
depths
just
to
mention,
because
when
I
did
the
first
change
with
the
samples
I
have
to
remove
the
additional
samples,
because
I
was
having
trouble
to
launch
the
server
application
with
that
setting,
I
can't
wrap
up
that
anymore,
so
I'm
enable
again,
but
I
I
think
we
really
should
investigate
additional
depth.
B
What's
going
on,
I
I
open
you,
erasmus
during
the
week
to
try
to
figure
out
that
you
know
if
anyone
knows
what's
happening
there,
please
let
me
know
I
I'm
kind
of
puzzled
and
I
hate
when
I
had
something
happening.
It
stops
happening
and
I
don't
know
why
it's
very
frustrating.
B
Okay,
I
will
try.
I
will
try
that
I
I'll
clean
up
the
new
get
cash.
This
is
a
good
point
because
I
think
perhaps
I
didn't
do
any
get
clean.
Usually
I
do
perhaps
when
I
started
the
other
time
I
did
the
clean.
Thank
you
for
that
raj.
I
think
that
maybe
has
a
potential
there.
Thank
you
all
right
and
okay,
just
before
starting
going
to
the
samples
project
discussion
here.
Does
anybody
want
to
add
any
topic?
E
I
initiated
a
conversation
internally
last
week,
thursday,
like
I
had
a
meet
with
noah,
so
he
is
driving
a
conversation
internally
on
this,
so
it's
going
on
there,
it's
all
on
the
they
are
driving
a
conversation
with
jana
itself,
so
he
is
the
one
who
is
responding
to
us
in
the
runtime
repo
also,
so
we
might
need
to
wait
like
if,
if
possible,
I
will
try
to
get
nova
itself
here
to
provide
an
update.
B
Yeah
so
since
the
meeting
is
on
record,
I'm
gonna
put
on
the
notes
that
there
is
an
internal
conversation
on
microsoft
going
on
and
we
are
gonna
wait
on
that
yeah.
I
think
these
matches
also,
if
I
think
that
I
I
was
thinking
about
that,
is
that
we've
been
initially
we
treated
that
scenario
as
kind
of
not
our
high
priority.
Our
high
priority
was
kind
of
people
that
can
change
the
build
so
for
now
I
think
the
sig
itself
keeps
focus
on
that
scenario.
B
Build
I
mean
changes
in
the
build
and
let's
see
what
comes
up
and
then,
let's
see
how
we
can
collaborate
or
or
work
on
that
yeah.
E
It
is
like,
as
jan
explained
in
the
run
time,
it
seems
like
it's
a
little
tricky
to
get
that
enabled.
So
that's
why
it's
like
they
are
discussing,
whether
it
should
be
that
way
or
like
one
of
the
work
around
what
have
been
proposed
earlier.
D
E
B
Okay,
so
we
I
I
think,
when
we
have
some
concrete
there,
perhaps
if
they
wanna,
we
can
schedule
something
for
them
to
come
and.
E
Yes,
probably
like,
when
we
are
ready,
I
wanted
to
get
know
where
they
or
someone
some
pms
from
that
or
to
join
us
and
provide
us
an
update
there,
because
the
update
is
common
for
and
even
I
work
on
that
internally,
the
update
is
common
for
all
of
us,
so
we
should
get
it.
The
update
here.
B
Okay
sounds
good,
sounds
good
to
me
so
related
to
that
kind
of
a
follow-up
to
that.
You'll,
be
that,
since
we
are
focusing
on
the
kind
of
build
scenario
that
builds
anatomy,
that
people
can
run
the
build
to
get
proper,
auto
instrumentation,
so
we
are
kind
of
going
for
no
source
chains
but
build
chains.
It's
a
scenario
that
we're
kind
of
going
at
first
until
we
have
this
kind
of
more
concrete
answer.
B
Regarding
the
other
scenario,
I
think
we
should
bump
it
up,
because
there
is
already
a
issue
to
create
a
new
get
package.
We
should
bump
it
up
that
for
the
beta.
You
know,
because
I
think
that
will
be
the
way
for
kind
of
having
successful
runs
of
the
application.
You
know
so.
E
Like
I
always
have
a
thought
followed
here
like
if
you
are
providing
a
new
gate
and
also
asking
them
to
like
change
their
cs
project,
how
it
is
different
from
sdk,
because
sdk
is
also
a
new
gate,
they
can
add
like
two
lines
of
code
to
their
cs
pro.
That's
the
promise.
They
also
do.
B
Yeah,
but
I
think
I
think
the
difference
in
this
case
is
that
there
are
still
at
this
moment
there
are
still
places
that
require
il
instrumentation.
B
You
know,
otherwise
they
require
is
not
only
the
sdk
bootstrap,
so
I
think
rasmus
pr
show
a
small
piece
of
code
is
a
small
piece
of
code,
but
for
that
one
to
work
with
the
sdk
somebody
has
to
change
that
code.
What
we
are
proposing
is
that
with
the
ire
right,
we
will
do
such
a
thing.
You
know,
so
we
do
the
bootstrap,
but
the
bootstrap
is
more
because
we
need
to
do
the
the
il.
So
I,
the
future,
that
I
see,
is
kind
of
long-term.
B
Il
kind
of
rewrite
reduces
the
need,
because,
let's
say
either
people
adopt
achieved,
source
or
us
kind
of
not
us,
but
open
telemetry
via
the
contrib
and
and
those
stuff
create
the
packages
that
kind
of
hook
up
with
whatever
the
application
library
provides,
and
if
that
doesn't
need
any
il
change
to
kind
of
be
in
place,
then
there
is
no
need
to
do
ill
rewrite,
but
right
now
we
do
need
that.
B
You
know
okay,
so
so
once
more
and
this
could
be
a
bias
of
the
customers
would
be
a
lot
of
thing,
but
I
think
we
satisfy
a
lot
of
cases.
If
you
just
say,
hey
just
add
this
nuget
package,
don't
touch
anything
else
and
build.
You
know.
I
know
that
adding
the
sdk
by
hand
is
not
that
complicated,
but
the
experience
that
I
have
is
that
there
are
some
people
that
I
know
a
nuget
package
is
fine
but
change
the
code.
B
No,
you
know
so
I
think
I
think,
for
the
time
being,
we
should
focus
on
that
scenario
and
be
sure
that
we
have
the
new
get
package
by
the
time
that
we
do
the
beta.
So.
E
B
Yeah
yeah
so
think,
like
this,
the
sample
that
I'm
working
now
it
shows
this
kind
of
very
easily.
After
you
see
the
pi
and
you
run
there,
you'll
be
our
option
to
just
use
the
startup
hook
without.
D
B
Profiling,
so
what
you're
going
to
see
is
that
you
see
the
server
side
getting
the
expand,
the
request,
but
you
don't
see
the
they
spend
the
clients
spend
for
money
with
the
b
depends
on
that.
You
know.
So
it's
going
to
be
clear
kind
of
what
you
are
losing,
what
you
are
not
losing
you
know,
so
I'm
just
I'm
just
thinking
that
that
was
kind
of
that
is
where
we
can
make
progress
right
now
and
we
are
really
trying
to
get
this
beta.
B
So
I
think
the
new
get
you
facilitate
people
to
try
on
their
own
projects.
You
know
I
it's
a
beta.
I
don't
think
anybody
will
be
deploying
this
to
production
right.
So
just
having
a
way
for
people
to
kind
of
hey.
Let
me
run
my
docker
compose
on
top
of
my
project
and
see
what
I
get.
I
think
the
new
gateway
is
going
to
help
a
lot
with
that,
so
I'll
bump
it
up
after
the
meeting
I'll
bump
it
up
the
nougat
issue
for
us
to
tackle
that
on
the
beta.
B
It
probably
will
have
a
lot
of
tasks
because
we
need
to
do
ci
publication.
All
that
stuff,
you
know,
but
I
think
it's
worth
so
people
can
we
facilitate
people
trying
the
beta.
That
is
the
main
tension
of
the
beta
okay
and
then
we
get
back
to
what
you
are
talking
about
about
the
samples
project
name.
I
would.
B
I
would
like
to
kind
of
have
a
if
possible,
having
a
decision
between
us
about
what
should
be.
You
know,
let
me
just
go
back
here
and
share
the
screen
again.
B
E
B
So
what
what
will
be
your
proposal?
We
put
samples
demo
and
or
if
you
put
samples
here,
then
we
have
to
change
these
ones
should
be.
I
don't
know
test
app
or
something
like
that.
You
know.
B
Yeah,
so
so
you
guys
in
general,
feel
that
prefix
demo
is
the
best
way.
B
B
Okay.
I
I
o
I'll
do
after
I
do
this
pr
that
I'm
already
working
I'll
do
the
rename
and
I
use
the
demo
prefix
I'll-
try
to
rename
the
projects,
but
I'm
most
worried
right
now
about
the
prefix,
the
rename
of
each
project,
individual
project.
Then
it's
kind
of
relatively
is.
I
just
wanted
an
agreement
at
least
for
the
prefix
okay.
B
So
then
they
will
be
outgrouped
here
and
you'll,
be
how
nice,
okay,
that
was
quick.
That
was
good
so
related
to
what
you're
talking
about.
I
think
rasmus
you
can
share
and
show
the
pr
to
us
about
what
you
did
for
mongodb.
D
One
can
you
see
the
mongodb
here
or
okay,
so
basically,
I
took
the
first
community
solution
and
that
is
using
the
diagnostic
source
and
found
out
the
few
issues.
B
So
this
code
will
be
called
that
we
want
to
do
as
ir
rewrite
right.
B
I
I
I
think
we
had
in
the
past-
maybe
maybe
I'm
mistaken
zack.
You
probably
know
this
better.
I
think
we
had
at
least
when
we
had
called
target.
I
think
we
had
something
at
some
interception
at
constructor
right.
C
We
so
we
have
a
hope
to
hook
in
pretty
early
like
when
we
would
invoke
the
like
instrumentation
class
from
native.
So
that
is
one
point
at
which
we
could,
you
know
set
up
a
subscriber.
Is
that
not
work.
E
C
It
might
be
tough
because
if
we
want
to
guarantee
it,
we
might
double
subscribe,
but
yeah
we
do
have
access
to.
We
could
rewrite
the
constructor,
because
that's
the
only
way
that
the
settings
get
used.
E
And
also
like,
I
was
thinking
about
the
reflection
way
like,
even
though
it
has
passed
toward
that
we
have
access
to
that
object,
so
we'll
be
able
to
modify
the
values
or
other
property.
If
we
have
a
property
which
is
holding
that
value
that
diagnostic
source
value
at
the
time
using
a
reflection,
we
might
be
able
to
do
it.
That
might
be
an
easier
solution
than
the
native
one.
So
it's
a
good
to
check
it
out
if
it's
possible
in
that
way,.
C
B
Yeah,
I
I
can
see
the
I
already
write
working,
but
I
I'm
still
kind
of
okay.
If
I
know
the
object
I
can
manipulate
via
reflection,
but
without
some
kind
of
dependency.
Injection
kind
of
that
kind
of
makes
this
injection
via
reflection,
sure
that
these
things
are
going
to
be
created
with
that,
I'm
I'm
I'm
not
sure
how
we
can.
B
There
there
are
ways
yeah,
but
I'm
not
sure
how
we
can
do
that
with
only
reflection.
You
know.
D
D
D
B
B
Oh
so
one
one
question
these
options:
they
are,
they
are
actually
options
from
mongodb.
They
are
not
relate,
they
are
related
to
the
diagnostic
source
of
mongodb.
B
Yeah
so
raj.
E
That
has
a
way
to
listen
to
this
and
do
some
like
based
on
that,
we
need
to
do
some
modifications
already
like
I
did
a
wrapper
or
something
kind
of
beer.
So
I
somehow
believe
the
reason
why
I'm
if
we
can
cover
more
customers
if
we
go
through
the
reflection
week,
so
I
I'll
explore
this
little
more
and
see
if
it's
possible.
B
Okay,
okay,
so
yeah!
I
I
that's
how
I
was
gonna
say
we
we
had
that
pr
that
you,
you
did
the
stuff
for
the
activity
source
yeah,
and
I
understand
that
for
the
activity
source,
but
I
I
I'm
not
sure
how
you
do
the
same
for
this
kind
of
thing,
without
with
touching
the
source
code
for
without
changing
the
code,
in
fact,
either
via
il
or
at
build
time
to
get
this
to
work.
E
Definitely
like
I
have
the
sample
in
my
repo
already
so
this
will
be.
I
need
to
build
on
top
of
it.
It's
my
in
my
public
with
every
boom,
my
sample,
so
I'll
just
try
to
see
if
we
can
build
on
top
of
that
and
see
if
it
comes
up.
E
But
we
should
not
block
this
peer
for
that
work.
We
should
review
and
like
move
this,
because
that's
a
different
implementation.
B
Yeah,
but
but
we
should
block
this
pr
until
we
have
the
stuff
that
zach
talked
about
yeah,
not
necessarily
block
the
pr,
but
at
least
have
a
plan.
We
don't
wanna,
we
we
could
create
the
other
stuff,
but
we
need
to
have
a
plan
to
be
able
to
remove
that
snippet.
That
now
is
not
on
the
screen,
but
from
the
sample
app.
You
know
we
need
to
be
able
to
remove
that
snippet.
We
we
don't
want
to
touch
the
source
at
all.
You
know.
B
If
we
had
to
touch
the
source,
then
raj
then
you'll
be
kind
of
what's
the
difference
from
the
sdk.
Yes,
so
we
really
don't
want
that.
D
Yeah
and
at
the
same
time,
we
need
to
be
careful
with
package
version,
engage.
B
A
D
A
B
Yeah,
so
so
can
we
come
up
with
a
plan
to
kind
of
fix
that
part
of
the
program?
I
don't
know
if
you
have
cycles
to
go
into
that,
erasmus,
if
you
don't,
perhaps
we.
B
Postpone
for
now
we
look
at
the
pr,
but
then
we
are
not
going
to
be
able
to
merge
it.
You
know,
because,
ideally
we
wanted
this
kind
of
to
be
the
the
case
that
we
are
going
to
the
future.
We
remove
an
il
instrumentation
and
add
this
that
just
inject
some
instrumentation
that
somebody
wrote.
You
know.
D
Yep
and
just
also
looking
at
this
package
from
the
stickers
they
they
have
a
different
package
just
doing
this
one
adding
they
have
one
one
extension
only
and
this
package
is
the
reference
in
the
auto
sdk.
So
if
user
is
bringing
in
the
sdk,
then
it's
going
to
overwrite
what
we
are
bringing
in.
D
So
it's
back
in
the
runtime
mission.
B
B
Yeah
so
one
more
reason,
kind
of
it
reinforces
what
we
are
talking
about
about
us
having
the
nougat.
Perhaps
it's
going
to
be
a
big
new
get,
but
we
can
also
break
down,
but
at
first
I
think
not
trying
to
do
anything
fans
just
make
a
new
get
off
all
the
instrumentation
that
we
support.
You
know,
then,
later
we
can
train
him
or
perhaps
have
some
way
for
the
user
to
dream.
B
Yeah,
I
I
would
say
just
I
think
I
I
don't
know
if
of
course,
I
don't
have
any
idea
if
it's
like
zach
has
any
cycles,
but
because
he
has
more
experience
with
this.
If
you
find
the
issues,
perhaps
ping
via
slack
or
something
so
you
don't
get
stuck
with
stuff.
You
know
yep.
A
All
right,
I
think,
from
my
part,
these
were
these.
The
topics
that
I
wanted
to
to
bring
it
up.
A
All
right,
the
silence
of
hey
nice
to
see
you
guys
see
you
guys
next
week
and
let's
do
some
stuff
and
get
this
bit
out.