►
From YouTube: 2021-07-01 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
Okay,
no
problem
yeah.
I
I
really
like
your
your
pr
cool.
B
Yeah,
I
was
I
I
added
that
the
the
config
file
for
the
exporter
and
then
I
I
realized
that
the
exporter
that
I
was
creating
it
just
was
like
very
like
it
took
up
a
lot
of
space
and
I
was
just
putting
a
lot
of
defaults
in
so
I
was
like
I'm
going
to
make
a
builder
for
these
things.
B
Yeah
I
I
accepted
your
your
change
suggestion.
I
was
trying
to
keep
it
like
more
generic,
but
I
guess
it
doesn't
really
really
matter
since
it's
in
the
sdk.
A
Yeah
I
mean
yeah
as
it
was
in
the
sdk.
Yes
provide
the
directly
the
sdk
one
could
avoid.
Maybe
some
casting
after
that.
Yes,
just
for
that.
B
A
A
C
A
A
A
Feel
bad
any
in
all
meetings
yeah,
I
I
I
I
did
other
thing
on
the
project,
but
I
will
talk
later.
The
mobile
carrier
info.
B
We've
got
three
approvals
on
the
change.
It's
been,
we've
been
iterating
on
it
quite
a
bit,
but
it's
it's
almost
done.
I
think
the
who
is
it.
The
the
the
spec
owner
is
waiting
for
some
reapprovals
based
off
of
some
some
recent
changes
that
were
made
before
getting
it
merged,
but
yeah
see
here
we
decided
to
move
away
from
using
3g
4g
5g
as
like
categories
for
carrier
types
and
just
use
the
raw
raw.
E
Values
thought
that
was
the
the
quality
of
the
network.
Right,
isn't
that
what
that
metric
was.
B
Yeah,
but
it's
they
they're
categorized
by
by
the
cell
technology
like
like
generation,
and
so
it's
more
information,
not
less
information.
So
you
know,
if
it
switches
from
like
lte
to
edge.
E
No,
I
was
actually
you
know
when
you
first
mentioned
it
in
the
way
I
read
it
was
if,
if
you're
in
the
middle
of
processing
and
if
your
network
changes
right,
I
mean
that
could
be
the
case
specifically
for
mobile,
not
for
others
right.
You
could
be
getting
off
from
wi-fi
to
sell
data
and
the
seller
data
itself.
Might
you
know
kind
of.
B
I
think
that
would
be
that
might
be
hard
to
detect,
but
I
would
I
would
I
don't
know
necessarily
if
it
would
be
set
as
a
as
a
attribute
on
on
a
trace,
necessarily
because
the
way
that
I
envision
this
is
that
as
the
trace
gets
started
it
would.
It
would
query
what
cell
technology
is
or
what.
What
network
it's
trying
to
run,
and
it
would
add
that
to
the
attributes
and.
B
I
mean
I
I
don't
know
if
you
can
describe
that
necessarily
in
the
spec,
but
that's
totally
that's
totally
a
possibility.
This
spec
doesn't
like
you
know,
preempt
that
you
know.
E
B
E
That
is
exactly
what
the
distributor
is
supposed
to
tell
you
why
why
it
is
slow
right,
yeah
exactly,
and
I
think
also
I
read
through
the
device
type
versus
host
type.
The
the
host
type
should
give
you
the
will
tell
you
right
if
it
is
a
device
or
a
server,
it's
similar
to
the
span
kind.
I
guess,
but
in
a
much.
B
Yeah,
I
I
that
that
needs
more.
That
ticket
needs
a
lot
more
thinking
through.
I
think,
because
yeah,
it's
it's
weird
and
it's
and
it's
yeah
confusing
because
it
doesn't
line
up
with
it's
not
like
mobile,
compatible.
E
B
E
B
A
Great
okay
and
the
yeah
and
distribution
mode
for
users.
A
I
was
doing
some
research
here
trying
to
have
just
one
target
in
the
package,
but
it
could
be
built,
but
the
problem
was
what
that
you
could
you
could
only
you
could
link
only
with
that
library,
but
it
failed,
but
you
couldn't
do
import.
A
A
A
So
you
had
to
import
open
elements:
api
in
port-o-pen,
telemetry,
sdk,
blah
blah
blah
blah
blah
in
its
code
source
code
that
had
to
use
any
of
them
and
you
couldn't
import
only
open
telemetry
in
the
code.
So
I
decided
not
to
move
not
to
continue
with
that,
because
it
will
add.
We
wanted
to
be
easier
for
the
users,
but
it
would
end
up
being
worse.
A
A
So
if
there
was
no
a
library
for
the
modules,
it
was
no
sense
to
have
a
a
binary
framework,
but
thinking
about
that
also
could
give
some
problems.
If
you
were
going
to
use
another
third-party
exporter,
for
example,
that
it's
not
used
in
the
binary,
because
we
we
could
have
double
double
symbols,
one
from
the
xc
framework
and
one
with
with
the
another
exporter,
for
example.
That
should
link
a
open,
telemetry
api,
so
yeah
that
that
was
even
if
we
could
have
make
just
one
target.
B
So
nacho
on
on
that
note,
though,
if,
if
we
had
this
xt
framework,
the
intention
is
to
make
it
easier
for,
like
I
guess,
introductory
users
to
use
it,
so
they
necessarily
be
linking
in
third
party
exporters.
B
A
A
He
will
use
a
xc
framework
and
also
the
splunk
library
that
will
link
with
the
other,
and
if
now
you
can
fix
that,
just
using
all
the
static
libraries
in
your
project,
wherever
they
come,
it
will
be
a
problem
if
the
symbols
are
solved
with
the
exit
framework
on
one
side
and
all
the
other
chain
of
symbol.
Symbols
in
the
third-party
library.
C
C
A
Will
have
the
affirmative
importance
of
the
modules
independently
when
you
use
any
of
them.
E
A
Yeah,
an
xc
framework
is
a
binary
distribution
for
swift
libraries.
B
So,
like
you
know,
multiple
platform
binaries,
so
you
can
get
you
know:
mac
os
and
ios
and
tv
os
all
in
one
package
to
make
life
easier.
Okay,
okay,.
E
So
yeah
so
based
on
whatever
platform
it'll
drop
that
when
you
imported
you,
you
get
that
specific.
A
Yeah,
okay
and
also
supports
linking
with
different
swift
versions.
That
is
also
another
point
of
pain
in
the
street
development.
When
you
have
frameworks
built
with
one
version
of
the
of
swift
and
another
is
not
compatible
so
so
using
xc
framework
with
a
pair
of
variables
or
configurations
more,
it
allows
you
to
do
that
also.
A
Finally,
I
was
able
to
find
a
way
to
create
the
exe
framework
that
I
thought
that
it
was
a
ci
problem,
because
you
have
to
build
all
before
changing
the
checksum.
I
I
found
that
solution,
because
I
I
use
that
now
for
my
project,
but
that
the
solution
is
building
first
via
indeed
have
actions,
for
example,
with
a
release,
action
and
move
the
tag
after
that.
So
you
build
your
framework,
you
change
the
package.
Swift
file
with
a
new
checksum,
commit
that
inside
the
action
and
move
the
tab.
A
A
B
C
A
But
you
can,
you
know:
mark
is
a
as
a
pre-release
before
moving
the
tar,
so
only
the
braves
would
take
it
or
something
like
that,
so
yeah,
but
yeah.
There
are
other
problems
with
with
that
that
I
think
that
are
not
good
for
open
telemetry
as
a
framework
itself.
It's
better
to
have
that
in
the
in.
A
If,
for
example,
you
use
that
or,
for
example,
splunk
uses
open
telemetry,
it's
better
that
they
pack
their
library
with
open
telemetry
in
their
splunk
framework,
for
example,
and
provide
that
to
the
user,
it's
better
than
having
open
telemetry
itself
as
an
xc
framework,
because
there
can
be
providers
of
frameworks
that
will
provide
pain.
Telemetry
in
between
probably
you
also
in
elastic,
are
planning
to
release
some
kind
of
framework
to
users,
and
I
think
it's
better
for
that.
A
E
A
E
When
you
use
the
library
you
have
to
select
the
so
open
the
limiter
api,
sdk,
all
the
static
libraries
and
also
the
exporters
right,
the
ones
that
you
want
to
use.
A
A
You
cannot
import
the
exporter,
but
you
can
link
only
with
the
exporter,
because
exporter
has
all
the
dependencies
on
top
okay.
The
problem
is
that
if
you
use
the
dynamic
library
of
your
exporter
with
a
dynamic
library
of
other,
for
example,
url
instrumentation,
you
have
the
problem
that
both
generate
the
dynamic
library,
including
the
library,
the
open,
telemetry
libraries
inside
them.
A
So
when
you
link
that
it
will
give
you
an
error
that
you
have
the
symbols
in
two
places,
so
that's
a
problem
of
having
a
dynamic
library
as
a
target,
except
if
you
just
have
one
I
I
we
would
even
avoid
distributing
the
dynamic
library.
What
do
you
think
about
that?
Should
we
avoid
yeah?
It
is
confusing.
B
B
That's
like
why
they're
made
is
to
to
be
able
to
share
a
library,
but
that's
not
how
it's
working
right
now,
so
we
probably
should
like.
I
would
argue
that
dynamic
libraries
are
just
broken
in
ios
at
this
point
like
they're,
not
usable.
B
A
That,
with
other
I
mean,
for
example,
you
cannot
weak
link
with
spm.
You
cannot
say
this
framework
or
this
library
weak
links
with
this
other,
because
you
cannot
configure
that
you
have
to
build
a
framework
yourself
with
xcode
and
with
the
standard
xcode
configuration
to
to
provide
a
weak
linking
to
that
framework,
for
example,
yeah.
A
B
A
Make
clear
somehow
that
you
should
only
use
a
static,
yeah.
C
B
B
A
Yeah,
that's
right:
yeah
yeah!
It's
it's!
I
can
imagine
all
the
users
thinking
that
it's
broken
something
and
yes
yeah.
We
had
the
one
user
that
said
that
it
was
not
working
so.
A
A
Probably
will
just
take
all
the
libraries
make
them
static
instead
of
dynamic,
so
we
have
the
same
library
in
with
two
names
we
have,
so
it
doesn't
break
any
user
currently,
but
we
can
say
that
it's
going
to
be
the.
E
A
A
A
If
they
use
a
dynamic
library,
just
one,
it
will
work,
but
if
they
try
to
use
two
or
more
it
won't
because
its
dynamic
library
is
solved
completely
with
all
the
dependencies
that
it
takes.
Statically
all
the
dependencies
are
linked
inside
the
dynamic
library.
That's
the
point:
okay,
yeah,
so
yeah.
I
will
change
that
for
the
next
person
and,
let's
see,
if
anyone
prays,
I
don't
think
so.
A
Okay,
any
other
topic,
you
think
about.
B
B
A
A
E
E
Gonna
ask
so
you
have
to
use
the
url
session
instrumentation
right,
import
it
and
then.
E
You
know
how
do
you
you
know
for
a
user
from
a
user
perspective,
how
would
they
use
this
instrumentation?
They
have
to
replace
their.
A
C
A
Initialize,
the
instrumentation
I
just
create
the
class
just
with
that
it
will
instrument
everything.
B
B
A
Yeah
yeah,
that's
right,
I
mean,
whenever
you
initialize,
that
it
will
capture
everything
that
happens
after
so
let
me
search.
Let
me
see
everything
here.
This
is
the
network
sample,
for
example,
and
here
this
is
a
code
that
it
just
creates.
The
spam
processor
adds
it
and
initialize
the
session
instrumentation.
A
So
it's
just
this
creating
the
exporter
that
is
a
std
out
exporter,
just
to
print
all
that
happens
on
the
site,
call
the
thresher
provider
and
in
the
processor
with
this
you
you
have
your
open
telemetry
just
running,
so
you
could
start
creating
expanse
and
all
you
want
here
just
initializing
this
with
the
default
configuration.
A
No,
we
could
provide
that
default
configuration
also,
but
so
we
we
could
avoid
calling
it
here,
but
just
creating
with
the
default
configuration
like
this.
You
just
that
will
capture
everything.
A
A
Yeah
when
it
takes-
and
here
these
are
just
two
network-
calls.
A
One
very
simple
example:
it
calls
here
with
this
request
and
print
what
it
returns
and
the
other
with
another
method
that
just
has
a
delegate,
but
it's
more
the
same
code
just
in
two
different
ways.
So
here
you
create
your
processor
initialize,
open
delimiter
with
that
processor,
and
just
this
line
is
the
one
that
will
make
everything
worked
so
just
creating
this
and
now
we'll
work,
the
network
and
captures
it.
A
Okay,
and
so
the
network
calls
are
happening
here,
if
you
just
comment
this
out,
it
does
does
nothing.
A
E
And
then
what
are
the
other
instrumentation?
There
is
sdk
resource
extension
and
sign
post.
E
A
We
have
this:
is
this
one
that
is
a
simple
exporter
that
creates
some
expanse
without
network,
and
here
just
configure
the
exporters
currently
under
standard
output.
But
you
can
create
here
right
right.
E
E
So
there
is
what
other
instrumentation
we
have
sdk
resource
extension.
A
Yeah
we
have
the
sync
integration:
that
is
this
one.
This
is,
it
says
it
creates
a
sync
posting
sync
post
for
each
span,
so
you
can
see
that
in
the
in.
Where
is
this
in?
A
Yeah,
so
if
you
are
in
you
are
seeing,
how
is
your
performance
of
your
app?
It
will
appear
there.
It's
it's
it's
nice
to
see
this
and
the
other
is
the
resource
station.
That
just
is
used
to
to
read
the
system,
information
that
you
are
running
right.
E
So
this
is,
it's
almost
like.
Is
this
more
like
a
metric
of
all
the
resources.
B
No,
that
that
gets
applied
to
all
attributes,
they're
all
traces
and
metrics.
I
believe,
but
you
have
to
pass
that
into
the.
B
Yeah
exactly,
but
you
have
to
add
that
as
a
parameter,
when
you
create
a,
I
think,
it's
a
tracer
provider
or
a
meter
provider.
E
E
B
Can
add
any
attribute
yeah
this
isn't
this?
Isn't
it
won't
be
added
automatically
when
you
create
a
standard
like
tracer
provider,
you
have
to
to
pass
this
to
your
provider
when
you
do
it.
Okay,.