►
From YouTube: 2021-06-02 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
C
C
C
It
was
expected,
but
confirmation
is
always
good.
Another
thing
we,
we
are
doing
these
experiments
now
with
always
loading
the
sdk
in
the
start,
even
if
there
is
no
instrumentation
to
be
loaded,
which
I
think
zach
mentioned
also
is
the
direction
that
datadog
is
going
anyway.
So
we
is
a
small
validation,
but
we
are
also
doing
our
tests
with
the
plc.
A
You
mean
always
letting
the
open
source
skate,
we're
always
loading
the
the
profiler
stuff.
C
Our
is
loading
the
sdk
via
the
profiler,
so
even
if
there
is
no
instrumentation
to
be
suppose,
even
if
the
integrations
json
was
not,
there
didn't
match
anything
it
loads.
The
the
sdk
via
the
profiler
got
it.
You
know
and
rasmus
have
has
a
pr.
It's
quite
large
because
needs
to
bring
a
bunch
of
components,
doing
the
instrumentation
with
activity
source,
but
still
using
the
scope
interfaces
and
all
of
that
right.
Erasmus.
D
C
I
see
so,
I
think
the
that's
the
the
next
step,
and
then
we
should
do
kind
of
this
will
be
instrumentation.
C
C
I
don't
think
it's
going
to
work
for
the
legacy
stuff
that
used
to
work
on
the
ripple,
but
the
sdk
offers
that
and
then
we
should
wrap
the
results,
kind
of
with
sample
applications,
using
old
versions
of
the
system,
diagnostic
diagnostic
source
and
then
kind
of
what
users
in
using
those
combinations
should
do
in
case
they
want
to
try
the
the
the
this
plc,
then
I
think
the
next
step,
if
all
goes
well-
and
we
have
a
kind
of
a
view
that
this
is
a
viable
path.
C
We
should
then
kind
of
start
to
discuss
a
plan
for
that.
You
know,
but
let's
first
wrap
up
with
this
kind
of
basically,
what
what
I
want
is
a
table
kind
of.
We
have
dot-net
framework
with
some
application
that
has
a
new
get
package
using
our
old
version.
C
What's
the
path
that
the
user
has,
we
think
that,
via
the
redirect
bindings
is,
is
viable.
Our
initial
tests
show
that,
but
I
think
we
should
see
that
table
so
then
we
can
make
the
the
decision
and
then
decide
if
you
are
going
to
take
that
path
and
how
we
do
this
migration.
C
This
is
one
thing
that
actually
dave
is
not
here
today.
I
finally
had
a
question
for
dave,
but
just
wonder
if
any
of
you
know
about,
I
was
looking
at
because
we
are
doing
now
this
thing
about
loading
the
sdk
at
the
start.
I
was
looking
at
some
other
random
profilers
that
I
found
on
github
and
a
few
of
them
had
the
it's
a
type
for
what
they
call
tiny
method.
I
that
I
was
just
searching
here,
can
you
guys
see
here
in
my
screen?
C
So
yes-
and
I
didn't
find
documentation
about
that-
and
I
was
wondering
what's
that?
Okay,
I
get
by
the
name,
it's
something
small.
But
what
are
the
implications
of
that
do?
Do
they
need
to
generate
code
different?
Because
of
that
you
know.
So
I
was
kind
of
curious
about
that
and
wondering
if
you
any
of
you
have
heard
about
that.
A
I'm
vaguely
aware
that
when
you're
generating
aisle
you
can
have
like,
I
knew
there
was
like
a
fat
io
or
basically
had
more
information
and,
like
maybe
the
tiny
is
just
the
smaller
representation
where
you
can
use
that
to
save
space,
but
there's
some
requirements
about
how
much
your
stack
size
is
and
maybe
instruction
count.
I
don't
remember.
A
Yeah
yeah
so,
like
general
case,
you'd,
probably
just
use
the
fat
method,
but
within
restrictions
you
could
use
the
tiny
one
and
that
would
save
on
some
space.
I
assume
I
don't.
I
don't
remember
exactly
why
it's
it's
been
a
while,
since
I've
been
deep
inside
that
profiler
code.
C
Yeah-
and
I
didn't
note
this
on
on
the
ripple,
so
I
I
noticed-
I
found
that
when
looking
at
the
other
ripple,
so
it
seems
that
in
our
case
doesn't
matter,
but
in
this
case
that
I
saw
I
and
I
have
to
dig-
I
was
just
searching
this
morning,
so
I
and
then
I
was
like
oh,
but
they
take
a
different
code
path
if
it's
tiny
and
a
different
code
path.
C
If
it's
not
tiny-
and
I
was
like-
oh
I-
I
didn't
see
this
before
no
so
yeah,
so
I
I'll
try
to
investigate
that
a
little
bit.
I
I
I
will
not
give
a
high
priority
of
this,
because
I
think
we
know
that
it's
probably
one
of
those
things.
That's
just
not
the
documentation
is
not
there,
but
it
doesn't
seem
important.
C
I
also
saw
a
bunch
of
profilers
that
don't
even
ever
mention
that
so,
okay
and
somebody
put
here
to
review
the
project
board,
which
is
always
a
good
idea,
and
I
am
not
good
at
doing
that.
E
E
C
Yeah,
so
the
last
I
think
robert
had
asked.
I
think
it
was
having
to
do
the
c
plus
plus
he
in
the
end
he's
separated.
C
E
C
We
can
just
sort
it
are.
I
are
you,
are
you
ask
this
because
we
have
this,
we
are
not
releasing
immediately.
So
this
is
a
good
question.
If
you
need
this
4g
a
or
beta
open
telemetry,
you
know.
D
C
By
the
way
we
in
in
the
in
the
poc,
we
are
using
call
target
as
the
default
not
test
in
the
order,
and
I
I
I
think
datadog
is
actually
switching
to
to
call
target
very
soon.
A
Yeah
the
last
couple
integrations
we've
done
are
only
call
targets,
so
we're
gonna
be
switching
sometime
soon.
A
Yeah,
we
already
got
pretty
good
results
so
far.
I
don't
have
any
particular
numbers,
but
a
couple
of
customers
who
have
complaints
about
like
performance,
we've
encouraged
them
to
try
call
target
and
they've
seen
pretty
good
results
there.
So
yeah
good
news
on
that
front.
C
Cool
very
cool,
so
I
think
we
covered
this
and
that
we
had
the
this
is
older
one
right
so.
B
C
C
E
So,
based
on
the
the
prototyping
you
all
been
doing,
it
sounds
like
things
are
looking
quite
promising
for
being
able
to
leverage
the
hotel
sdk
for
the
most.
C
Part,
yes,
I
think
a
fair
assessment
will
be
the
following.
We
didn't
counter
the
problems
that
we
expected
to
encounter,
but
it
seems
that
the
proposed
workarounds
are
reasonable
are
acceptable.
You
know
they
will
not
assuming
let's
talk
about.
Perhaps
the
limitations
no.net
core
2.1,
because
the
sdk
doesn't
support
that
and
we
it
will
not
be
possible
to
work
with
people
that
have
the
code,
but
don't
build
their
their
application.
C
You
know
because
we
they
walk
around
around
the
box.
Oh
change,
your
nougat
package
version
to
request
this
use
binding
redirects
to
force
the
load
of
the
version
of
the
diagnostic
source
that
we
need.
So
this
kind
of
work
around
excludes
people
that
are
just
running
their
code.
So
perhaps
there
is
some
devops
scenario
that
will
not
be
covered
because
perhaps
they
just
received
the
application,
but
I
have
I'll
my
tendencies.
You
think
that
for
open,
telemetry
project
that
is
starting,
I
think,
that's
acceptable.
You
know
yeah.
E
C
C
Yeah,
if
you
could,
if
you
have
some
kind
of
information
about
that
scenario,
because
then
we
can
try
to
see
if
it's
possible
at
all
to
do
some
kind
of
binding
redirect
or
not.
You
know.
E
C
Yeah
yeah,
so
one
thing
that
when
we
get
to
the
binding
redirects
to
dive
more
into
them
that
I
think
we
should
be
looking
at
how
easy,
because
I
think
the
there
is
a
easy
case.
That
is
the
case
that
you
just
because
there
are
two
properties
on
the
cs
project
that
can
take
care
of
that
for
you,
but
I'm
not
sure
if
everyone
is
going
to
be
able
to
use
those
simple
ways
of
doing
and
may
have
to
go
to
the
app.config,
add
to
the
app.config
and
then
build
you
know.
C
So
that's
why
I
I
get
to
that
thing
that
I
mentioned
in
the
beginning.
I
want
to
kind
of
collect
the
case
and
collect
the
workarounds
to
see.
Perhaps
should
we
build
some
tooling
to
help
with
that?
You
know.
C
Makes
sense
yeah
so
so
chris,
if
you
have
any,
because
I
I,
but
if
you
have
something
about
this
sharepoint
scenario,
that
you
can
send
me,
I
I
can
perhaps
try
to
take
a
look
and
see
how
how
we
can.
E
D
Yeah,
I
think
the
solution
for
sharepoint
should
be
a
little
bit
different.
For
example,
using
these
large
frameworks
they
usually
include
plugins
or
add-ons
framework.
Also,
so
you
can
build
a
separate
plugin
for
sharepoint
applications.
E
Right
yeah-
and
this
is
kind
of
a
specific
case
of
a
lot
of
content
management
systems
and
so
yeah.
It's
just
one
example.
Those.
C
A
Hello,
one
thing
you
might
consider
and
like
the
workarounds
as
just
an
idea
that
could
be
supported
later,
is
maybe
having
like
a
reference
kind
of
nuget
package
that
you
know
we
wouldn't
kind
of
introduce
any
code
ourselves,
but
at
least
it
could
maybe
add
a
nuget
package
dependency
to
the
required
system.
Diagnostic
source
that
way,
dotnet
framework
builds
would
automatically
do
the
binding
readers
and
other
projects
would
kind
of
do
the
nuget
resolution
and
unify
on
one.
C
C
I
see
that
dave
joined,
and
today
I
actually
had
a
question
for
dave
yep,
I'm
here
now
I
I
was
looking
because
we
are
always
now
we
are
always
loading
the
sdk,
the
open
telemetry
sdk
via
the
profiler,
and
I
was
looking
random
other
profilers
and
I
found
a
few
of
them
with
this
tiny
and
I
didn't
find
documentation
for
the
the
tiny
method.
Do
you
have
some
information
that
about
that.
B
Not
off
the
top
of
my
head,
so
the
I
kind
of
vaguely
remember
what
it
is.
There's
you
know
different
ways
that
we
encode
method,
headers
and
there's
the
yeah
il
method,
tiny
and
I'll
have
to
look
it
up.
I
don't
remember
enough
to
tell
you
off
top
my
head,
but
I
can
find
out.
C
I
I
thought
that
was
something
kind
of
obscure
because
I
didn't
see
many
profilers
using,
but
I
did
the
same
one
example
using
and
it
was
kind
of
I
was
puzzled
because
I
didn't
remember
what
was
you
know,
so
I
just
tried
to
understand
why
that
profile.
I
think
it's
important
enough,
because
most
of
profilers
that
I
see
doing
io
rewrite
didn't
bother
with
that.
B
C
Yeah,
I
I
I
if
you
want,
I
can't
try
to
find
the
example
that
I
I
saw
but
th.
This
is
not
to
be
fair.
This
is
more
trying
to
learn
everything
around
the
the
sample
that
I
was
looking
to
understand
why
they
are.
They
are
doing
that
yeah.
B
I
think
it's
something
to
do
with
the
way
we
store
the
actual
il
itself
and
if
it's
small
enough,
then
we
have
to
use
this
special.
So
normally
you
get
the
I
o
header
by
decompressing.
It
there's
all
those
methods,
it's
like
core
decompress
method,
signature
or
something
like
that,
and
I
think
this
is
just
an
alternate
format.
Format
for
that.
If
I
remember
right
because
there's
the
yeah
okay,
I'm
searching
now
so
there's
the
il
method,
fat
and
then
the
il
method
tiny.
B
So
it's,
I
think
it's
just
an
alternate
way
of
encoding
the
the
method
information
when
it
when
it's
a
small
enough
method.
That's
what
I
think,
but
let
me
look.
C
Yeah,
I
know,
and
if
you
prefer
just
send
later
as
a
message,
if
you,
if
you
find
something
short
that
you
can,
it
is
more
for
us
to
kind
of
keeping
our
knowledge
on
top.
You
know
kind
of
understand
the
stuff.
That's
there.
C
Yeah
so
I
think
they've
joining
time
for
us
to
answer
us
one
question
and
then
we
are
ready
to
end
the
meeting
unless
somebody
says
something.
D
A
E
Yeah,
if
you
want
some
example,
instrumentation
for
outbound
wcf
instrumentation
new
relic
has
some.
I
mean
the
instrumentation
works
differently,
but
it's
the
same
idea.
C
Yeah,
so
if
you
want
to
look
at
the
new
reality,
one
it's
on
github
and.
C
A
Another
thing
I
had
really
quick
was
regarding
the
current
upstream
to
the
hotel
repo.
Like
last
week,
we
merged
apr
and
datadog
to
add
copyright
headers
to
all
of
our
c
sharp
files.
A
So
that's
currently
included
in
the
upstream
poll,
and
so
I
commented
on
that
pr,
but
it'd
probably
be
good
to
take
it,
but
also
on
that
pr
also
just
kind
of
modify
that
for
whatever
headers
you
want
for
open
timesheet.
Whatever
the
specs
says
is
the
appropriate
message.
C
On
that
note,
because
it's
a
pr
that
robert
opened
it's
a
holiday
in
poland
tomorrow
and
I
think
friday
and
a
lot
of
people
took
the
the
week.
So
I
I
think
that's
why
robert
and
david
are
not
here
today.