►
From YouTube: 2021-07-14 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
B
C
D
D
D
D
So,
first
welcome
andrei
how
how
should
I
pronounce
your
name?
I
do
it
andre.
B
D
I
I
I
was
thinking
in
start
with
rasmus
pr,
because
it's
a
a
bit
larger
and
adding
a
lot
of
the
tests
to
the
poc
branch,
and
I
I
would
like
to
understand,
if
kind
of
it,
this
is
falling
the
same
line
of
what
we
have
in
maine
or
if
it's
kind
of
trying
to
change
some
of
the
implementations
or
ways
to
test
that
we
have
there.
D
Do
you
want
to
present
it?
Erasmus.
E
E
Yeah,
okay,
then
it's
the
right
screen,
so
I
think
the
most
of
it
is
from
the
data
talk.
E
D
So
so
this
is
basically
the
same
set
of
tests
that
we
have
in
maine
or
is
a
a
different
set
of
tests.
What
I
mean
is
is
the
same
set
of
tests
with
a
slightly
different
organization
targets
or
is
the
same.
It's
a
different
set
of
tests.
D
D
Okay,
so
let.
C
D
Just
take
a
because
I
I
I
see
the
the
huge
number
of
files
so
then
it's
basically
bringing
those
files
right.
E
D
A
F
E
F
Datadog
repo-
I
don't
know
if
how
far
back
the
hotel
main
branch
is,
but
we
have
instructions
in
our
datadog
one.
So
not
sure
if
those
made
it
over.
E
C
E
We
should
look
what's
there
and
then
maybe
even
bring
these
ones
or
write.
Another
set.
D
Okay,
so
it
it
seems
very
reasonable
by
what
you
described
and
what
I'm
seeing
here
so
yeah.
We
should
look
at
the
instructions
that
zach
mentioned
and.
E
C
A
E
Is
a
little
bit
tricky
so
when
I
implemented
nuke,
then
one
helper,
this
is
helper
is
behaving
like
little
bit
differently
and
adding
a
few
extra
good
parts
there.
Let's
see.
E
E
E
C
E
Easier
to
see
from
the
comment.
D
But
by
the
way
they
do
test
this
on
both
mac
and
more
linux
and
windows.
But.
D
F
Yeah,
I
wouldn't
be
too
concerned
about
that.
That
test
is
just
looking
to
make
sure
that
we're
able
to
scan
for
typedefs
just
querying
core
profiler
okay,
so
it
must
have
just
leaked
in
from
I
don't
I
don't
know
a
recent
commit
or
something
recent
changes.
E
E
G
A
E
E
E
You
mean
like
in
this
project
or.
G
There
is
a
tool
nuke
that
that
controls
the
running.
I
wonder
what
it
stands
for,
doesn't
matter
just
curious,
yeah.
E
D
D
All
right,
so
I
I
think
we
we
have
insight
in
in
this
pr
and
we
can
do
the
review
and
close
on
that.
I
actually
you
you
take
out
the
branch
and
run
on
my
machine
too.
D
I
think
I
I
still
have
to
recover
here,
but
I
think
the
next
topic
was
about
the
instrumentation
for
service
fabric
right.
D
That's,
that's
me,
that's
my
topic.
So
are
you
looking
for
a
bite,
cold,
instrumentation
or
actually
I'm
not
familiar
with
service
fabric?
I
don't
know
if
service
fabric
has
diagnostic
source
or
other
hooks
for.
B
We
already
use
open,
telemetry
collector
for
traces,
and
sometimes
a
customer
will
ask
well
will
a
customer
come
along
that
have
some
code
in
service
fabric
and
then
the
question
is:
can
you
instrument
that,
and
apparently
the
only
way
we
could
find
was
that
this
piece
of
code
that
data
dock
is
contributed
that
this
sig
is
about
right
and
the
original
code
used
to
use
a
profiler
from
what
I
was
able
to
understand
until
now,
because
I
am
pretty
near
to
this
all
this
still,
and
so
we
are
trying
to
figure
out
what
would
need
to
be
done
to
be
able
to
support
customers
with
the
instrumentation
of
service
fabric
code,
and
one
way
is
to
probably
just
try
to
make
that
original
data
doc
code
send
data
to
an
arbitrary
location
like
sumo
logic
or
anything
else,
open,
telemetry,
collector
and
but
that
would
require
putting
up
a
profiler,
putting
a
provider
next
to
the
application.
B
B
What
would
need
to
be
done
for
to
be
able
to
support
service.
D
Fabric
instrumentation,
so
so
a
quick
description
where
we
are
on
the
main
branch.
We
have
basically
the
tracer
that
came
from
datadog
and
we
do
have
exporters
there.
We
have
the
jaeger
exporter
and
the
zip
exporter.
D
I
think
we
just
have
the
zip
king
and
the
jaeger,
so
we
never
did
a
kind
of
awful
release
of
that,
but
that,
in
a
sense,
since
the
service
fabric
instrumentation
is
there
already,
it
should
be
able
to
export
that
for
via
zip,
king
and
jaeger,
but
to
be
fair
recently
we
have
been
concentrating
more
of
the
work
on
the
poc
branch
that
you
are
trying
to
use
the
sdk
and
on
that
branch
we
essentially
start
as
a
plc.
D
We
we
brought
very
minimal
code
from
main,
so
we
didn't
bring
the
instrumentation
for
service
fabric
to
this
poc
branch.
Where
we
have
worked
more,
you
know,
but
in
principle
there
is
nothing
that
blocks
that
same
instrumentation
to
be
brought
to
the
poc
branch.
D
The
only
thing
that
I
would
say
is
that
on
the
plc
branch
we
just
enable
call
targets,
there
are
two
types
of
instrumentation.
We
can
go
into
details
later,
but
there
is
call
cycling
called
target.
We
just
enable
call
target
on
the
plc
branch
so
far.
D
So
if
the
instrumentation
is
called
target,
it
should
be
relatively
easy
to
be
to
the
poc
branch,
but
I
I
I'm
I'm
not
sure
about
that
specific
instrumentation,
but
as
long
as
in
the
ripple,
we
you
have
these
two
paths
to
get
that
to
work.
But
that
said,
we
didn't
do
a
release.
Yet
on
this
thing
you
know
there
is
no
official
release
from
the
sig.
Yet.
F
Can
jump
in
with
a
little
bit
more
knowledge
on
the
surface
fabric
instrumentation.
So
this
one
is
one
of
the
two,
the
other
one
being
asp.net
core
that
we
actually
use.
F
F
So
this
one
specifically
doesn't
require
a
profiler,
but
you
would
have
to
get
access
to
the
types,
and
so
we
we
use
a
profiler
to
hook
in
early
and
just
use
reflection
to
get
the
tights
and
register
the
event
handler.
But
you
don't
necessarily
need
to
do
that.
D
Right
yeah,
so
so
zach,
so
since
this
is
the
kind
of
traditional
thing
for
diagnostic
listener,
potentially
this
can
be
implemented.
This
instrumentation
can
be
implemented
on
the
dotnet
contrib
from
telemetry
using
alicia.
That's
what
they
do
for
asp.net.
F
D
F
I
haven't
looked
at
which
versions
or
if
service
fabric
actually
uses
diagnostic
source.
I
I
wasn't
the
one
that
implemented
this,
so
I
don't
know
if
they
have
dynamic
source,
we
did
use
event
handler,
but
if
later
versions
of
their
various
like
remoting
libraries
actually
use
diagnostic
source,
then
that
can
definitely
just
be
using
diagnostic
source
instead.
But
yes,
this
would
be
a
good
candidate
for
just
a
contrib
sort
of
yeah.
D
No,
I
I
kind
of
just
just
thinking
about
the
pattern
about
being
diagnosed
source,
but
whatever
you
listen
and
you
can
generate
the
expense,
then
it's
something
that
and
doesn't
need
the
profiler
you
in
interior,
you
can
implement
in
the
country
before.net
and
then
just
use
the
sdk
without
the
profiler.
B
Okay,
that
makes
sense
yeah
because
yeah
I
looked
at
the
code
and
I
was
wondering
why
the
providers
even
need
it
if
it's
just
hooking
into
the
methods
which
reflect
in
the
to
the
events
with
the
reflection
right.
Okay,
so
so
it
seems
that
I
should
be
able
to
do
the
same
thing
with
regular,
open,
telemetry
instrumentation.
Instead
right,
I
didn't
didn't
see
anything
like
that
in
the
open,
telemetry.net
repo.
But
I
didn't
look
at
the
country,
repo
and
you're,
saying
that
the
asp.net
is
done
in
similar.
D
Way
the
asp.net
they
do
with
the
diagnostic
source,
but
the
idea
is.
C
The
same
you
are.
D
Gonna
have
something:
that's
gonna,
listen
capture,
you're,
gonna,
use,
reflection
to
assess
properties
and
types
whatever
you
need,
and
then
you,
you,
publish
the
expands
using
the
open,
telemetry
api.
So.
B
Yeah:
okay;
okay,
so
it
doesn't
seem
that
difficult,
so
either
service
fabric
already
supports
diagnostic
source,
which
is
even
easier,
and
if
it
doesn't,
maybe
I
could
just
hook
into
those
events,
as
this
code
already
does.
Does
that
make
sense?
Okay,
okay!
Thank
you
very
much
for
your
explanations.
That
explains
a
lot.
I
think.
B
D
B
D
I
I
I
think
both
us
from
ultra
instrumentation
and
the
dot
net
slack
channel
itself
are
good
things
for
good
places.
For
these
questions.
You
know,
I
think,
service
fabric,
you
it's
a
relatively
popular
library,
so
I
don't
see
any
issues
for
you
to
add
one
to
the
contributor.
You
know.
D
And
for
folks
there
haven't
been
active,
especially
aws
folks
had
been
very
active
on
the
contrib,
so
the
only
thing
that
I
would
say
is
that
they
just
had
a
release
and
they
are
just
planning
another
official
release
later
for
november,
and
if
you
need
any
features
in
your
instrumentation
for
a
service
fabric
that
are
not
there
in
this
version,
then
you
are
gonna,
have
to
build
and
run
against
a
provisional
release
from
the
from
the
sdk
package.
D
All
right,
I
I
unfortunately
was
bullied-
should
do
some
other
stuff
and
they
will
wrap
up
that.
I
wanted
to
do
on
the
poc.
I
I
still
didn't
have
time
to
finish
that,
but
it's
something
that
I
really
want
to
do
as
soon
as
possible.
So
we
we
take
the
the
lessons
learned
there
and
what
we
collected
there
and
move
ahead
and
start
to
really
do
the
implementation
for
using
the.
D
Sdk
all
right
anything
else
that
you
guys
want
to
bring
it.