►
From YouTube: 2022-08-16 meeting
Description
Instrumentation: Messaging
B
A
Yeah,
I
know
I
think
the
first
two
are
actually
I
think
you
and
I
can
discuss
okay.
It
only
takes
a
few
minutes,
but
maybe
let's
give
another
couple
minutes
just
in
case
never
joins
sure.
C
A
Let's
get
started
and,
like
I
said
we
can
end.
Oh
he's
he's
replied
he's
saying,
won't
be
able
to
attend
a
priority.
She
just
occurred
that
I
need
to
address.
Yeah
sounds
good,
so
we'll
proceed.
B
Which?
Which
symbol
tick
mark.
A
A
C
A
Okay,
so
the
the
third
topic
that
I
have
is
is
is
is
for
nav,
so
we
can,
you
know,
do
that.
You
know
tomorrow
we
I
yeah,
I
I
I
want
to
talk
to
you
too
about
it
briefly,
but
yeah
we
can
dig
into
it
later.
Okay,
so
basically
the
first
topic,
70
conventions.
A
Remember
there
used
to
be,
or
there
is
a
an
attribute
called
component
yeah
in
in
all
the
spans.
You
know
that
refers
to
fetch
xhr
document
load.
You
know
something
like
those
yeah
yeah,
so
that
component,
you
know
it
doesn't
have
a
namespace.
A
Introduce
some
name
space
for
it,
but
then
t2t2
right
his
name,
so
he
replied
in
another
nervous
document
that
it
should
actually
be
an
instrumentation
scope,
name
yeah.
So
so
my
question
is
now
we
can
do
that.
I
think
that
seems
to
be
the
right
thing,
but
in
our
current
you
know
spans
that
are
emitted.
A
C
B
A
Because
the
timing
doesn't
work
for
me
and
you
know
we
don't
want
to
wait
sure
yeah
yeah,
but,
like
you
said
first,
I
want
to
see.
B
B
You
know
it
may
be.
It
may
be
that
I
see
I
see
that
it's
been
renamed
inside
the
code
and
it's
yeah
and
it's
like
for
metrics
there's
a
scope
metrics
in
the
payload.
B
A
No,
so
could
you
do
me,
you
had
an
example
right
to
emit
a
trace.
Could
you
check
what
exactly
we're
emitting,
because
the
example
that
I
have
you
know
shows
me.
I
don't
have
a
running
example.
I
just
have
some
sample
json.
B
B
B
A
Let
me
know
okay,
so
we're
good
we're
good
with
that.
If
it
is
instrumentation
scope.
A
For
the
http
referral,
the
next
one
is
http
referrer
for
http.
Referrer
reason
I
wanted.
I
forgot.
I
think
the
reason
I
wanted
is
yeah,
I
think
for
iframes
like
like.
If
you
see
you
know
this
link.
A
You
know
yeah,
you
should
fill
this
too
if
you
haven't
already
so
I
filled
only
like
partially
not
complete,
but
in
our
page
view
event
we
call
it
as
base
page.
A
We
also
have
an
attribute
to
indicate
that
it's
an
iframe
right
so
and
for
iframes.
We
we
want
to
define
what
is
the
page
that
embeds
this
hazard
frame.
B
A
So
so
the
parent-
I'm
guessing,
you
know
you,
you
could
refer
it
from
the
referral
url,
because
it's
usually
the
parent
that
refers
you
right
and
http
referrer,
you
know
is
generally
useful
too.
So,
instead
of
introducing
another
in
a
parent.page.url
or
should
page
that
you
are
alive,
I
thought
it's
just
simple:
to
use.
Http
referrals.
C
Hi,
stefan,
I
can
say
hello,
rejoined
sorry
for
being
late
yeah.
I
know
it
is.
C
A
A
Yeah,
okay,
okay,
so
he
he's
so
he
and
his
manager
ram.
They
have
asked.
A
You
know
us
to
fill.
You
know
this
document
with
the
events
that
we
have
today
for
india
for
our
vendor
implementations
in
the
legacy
products.
You
know
so
that
we
can
come
up
with
a
consolidated.
You
know
common
structure
right,
I
think
we
spoke
about
it.
I
think
you
all
you
had
already.
You
know
one
version
of
this.
You
know
you
had
started
yeah
so
so
this
is
another
attempt,
and
you
know
this
time.
I
think
I
have
put
something
microsoft.
A
C
I'm
already
working
on
it,
it's
a
bit
more
complicated
to
get
the
fields
from
our
existing
events.
I
think
so.
A
Maybe
you
could
start
by
at
least
putting
the
the
names
of
the
events,
the
actual
detailed
fields
you
could
leave
out
and
then
put
whatever
you
know
a
few
yeah.
You
think
you
can
and
then
you
know,
yeah,
it's
okay,
if
it's
incomplete,
in
fact
mine
is
incomplete.
So
even
I
don't
know.
A
Yeah,
so
so
going
back
in
our
case,
what
I
was
saying
is
in
this
base
page.
We
do
want
to
indicate
that
you
know
this
page
refers
to
an
iframe.
A
A
B
B
B
C
A
C
C
Matter,
what's
your
referral
policy
referral.
C
A
Okay,
so
there
is
a
referrer
whereas,
whereas
if
I
go
to
let's
say.
C
Why
is
it
not
showing
you're,
not
the
first
page
url.
C
Is
this
the
first
page?
What
is
the.
A
Yeah,
so
so
for
yeah,
it
is
showing
the
referrer
event
for
this
page,
which
is
fine,
so
just
because,
as
a
referrer
doesn't
definitely
it
doesn't
mean
that
it's
an
iframe.
So
we
still
need
one
more
attribute
to
indicate
that
it's
an
iframe,
so
the
referral
is
only
going
to
be
used
to
to
get
the
parent
page
that
that's
what
we
said
here
right.
A
So
we
still
need
another
attribute
to
indicate
that
it
is
an
iframe
and-
and
you
know-
and
I
I
that
was
actually
my
third-
you
know
item
here
that
how
do
we
indicate
I
frame
something
to
represent
iframes.
C
B
You
know,
like,
I
think
that
you
know
in
in
the
browser
the
w3
specification
is
probably
is
there's
like
a
parent
parent
api,
like
in
the
browser
which
is
different.
B
A
A
So
like
for
me,
you
know,
since
I'm
not
coming
from
a
javascript,
you
know
background
the
node
background.
I
don't
know
what
you
know.
These
different
folders
mean
there
is
a
packages
there's
an
experimental
packages.
Then
there
is
a
country
packages.
Then
there
is
some
meta
packages
and
then
there
are
plugins
right.
So
so
what
is
the
difference?
A
So
looks
like
the
contrib
refers
to
third
party
and
not
the
main
code
base
right
when
it
is
instrumentation
for
third-party
libraries,
like
exporters
for
gcp
aws.
In
that
case,
the
document
load.
A
I
don't
think
so,
but
let's
confirm
one
second
see:
there's
an
instrumentation
fetch
why
the.
B
Yeah,
it's
it's
yeah,
because
those
are
like
part
of
the
you
know.
I
think
I
think
the
http
instrumentations
are
considered
core
because
they,
you
know
they're
like
key
for
tracing
okay,.
B
B
I
think
you
know
part
of
that
is
also.
You
know
the
the
maintainers
of
this
core
sdk
have
to
decide
like
if
they're
able
to
maintain
it
like
if
they're
not
able
to,
then
you
know,
I
think
in
the
contrib
is
that's
maintained
by
the
community.
A
Yeah,
so
I
am,
I
don't
have
a
problem
leaving
it
in
contrib
just
wanted
to
be
sure.
You
know
what
you
know
each
of
those
means
because
yeah
you
know
as
more
and
more
folks
begin
to
work
on
this.
It's
you
know.
You
know.
If,
if
these
are
not,
you
know
clear
it.
It's
going
to
be
confusing
yeah.
B
A
A
And
also
the
other
thing
you
know:
when
do
you
move
from
experimental
to
with
the
non-experimental
like?
Is
there
a
criteria.
A
Well,
I
don't
think
that
is
a
valid
reason
like,
for
example,
these
are
instrumentation
instrumentation.
The
specification
doesn't
talk
about
instruments,
oh
yeah.
B
Yeah
yeah,
I
don't
know.
A
Well,
things
could
always,
you
know,
evolve
right.
I
think
I
would
put
experimental
only
until
like
there
is
some
sufficient
usage
and
confirmation,
and
I
think
one
way
to
do
it
is.
If
you
go
to
the
npm
repository.
A
A
Okay,
I
think
this,
I
think
it
makes
sense
to
discuss
in
the
you
know,
hotel
js
meeting,
because
I
already
asked
here-
and
I
haven't
heard
a
response.
B
A
So
yeah,
no,
no!
No,
I
think
it's
it's
a
little
early.
I
think
we
need
to
see
you
know
what
they
say
tomorrow.
Basically,
my
ask
is
that
you
know
somebody
start
working
on.
A
You
know
moving
the
android
sdk
from
splunk
report
to
open
telemetry
project
okay,
so
I
was
going
to
ask
them
if
they
can
help
with
that.
After,
after
that,
you
know,
each
of
us
can
can
help
control,
but
I
think
sirat's
concern
was
they
need.
You
know
some
more
maintenance
on
that
right,
right,
yeah,
right
and
then
maintainer
has
certain
requirements,
and
so
I
think
that's
what
we're
going
to
discuss
tomorrow.
B
Yeah
I
mean,
I
don't
think
it's
up
to
me.
I
think
we
can
bring
it
up
and
see
if
the
maintainers
are
open
to
it.
B
I
think
it's
basically,
I
think
the
guidelines
for
adding
something
to
the
contrib
are
more
loose.
You
know,
I
think,
it's
easier
to
add
things
to
the
contrib
than
is
the
core.
So.
C
B
Yeah
I
mean
like
I
said
I
think
it
might
have
to
do
with
also
having
enough
people
like
in
in
the
maintainers
group
to
maintain
those
those
those
packages
that
they
might
be
hesitant
to
add
new
things
if
they
ca,
if
they
can,
if
they
can't
support
it,.
A
A
On
issues,
so
let's
let's
hear
it
out,
I
think,
because
I'm
also
feeling
that
you
know
you,
you
have
to
look
at
the
number
of
issues
for
each
of
the
packages
like,
for
example,
no,
not
here.
A
C
A
Okay,
let
me,
where
is
the
meeting
noise
for
tomorrow
I'll.
C
C
Let
me
try
okay.
A
Yeah,
okay,
that's
all
I
had
with
respect
to
the
nested
attributes
or
tip.
I
think
this
is
for
nev
I'll
bring
it
up
with
him,
but
I
was
writing
up.
You
know
tip,
for
you
know.
A
A
B
A
So
so,
at
the
end,
I
think
you
know
this
is
what
I
think
we'll
end
up
using
like,
for
example,
I
I
seriously
think
that
we
should
move
away
from
the
events
for
the
performance
timing.
A
Like
you
know
this,
but
if
we
can't
use
a
map
data
structure,
you
know
we
could
basically
put
it
all
in
a
json
one
object
as
a
map,
but
but
then
do
a
json
stringify
and
then
attach
it
to
an
attribute.
You
know
like
this.
B
A
B
A
Discuss
this,
you
know,
along
with
nev,
okay,
yeah
yeah
go
through
this
and
think
about
it,
and
I
also
feel
that
you
know
we
could
discuss
offline
okay,
just
three
of
us
or
if
anybody
else
is
interested.
C
B
Okay,
yeah,
I
I
have
a
quick
question.
How's
is
the
api,
the
logs
api?
Pr
that
you
that
you
have
in
specification
is
that
waiting
for
something.
A
No,
I
think,
tomorrow's
meeting
I'll
I'll
get
it
emerged.
A
A
A
So
I
don't
mind
you
know,
and
at
this
point
only
the
android
sorry
only
the
javascript
browser
is
progressing.
A
And
then
that's
the
topic.
I
want
to
bring
up
in
the
with
the
android
folks
tomorrow
that
you
know
they
should
start
thinking
about
even
the
standalone
events
and
and
then
contribute
in
the
spec,
if
even
if
they
don't
actually
implement
those
things.
A
No,
no
so
remember
it
is.
It
is
experimental
at
this
stage,
so
we
should
expect
changes
to
it,
but
I
don't
think
the
changes
will
be
drastic.
You
know
so
so
we
should
go
ahead.
You
know
continue,
you
know
our
events,
implementation.
Basically,
whatever
new
events
we
are
going
to
build.
You
know
we
should
start
implementing
using
the
the
log
data
model
using
your
api
sure,
yeah.
B
A
So
you
should
get
your
api
merged.
Your
sdk
log,
sdk
merged.
B
A
A
So
so
I'm
I
think,
let's,
let's
ask
regret
tomorrow.
I
think
he
might
be
okay
merging
it.
I
will
tell
him
that
you
know
we
were
on
the
javascript
side.
We
were
ready
to
merge
it
so
that
we
could
start
implementing
a
few
examples,
and,
given
that
it's
experimental
will,
we
can
always
come
back
and
make
changes
to
it.
A
Yeah,
I
could
propose
that
way.
B
Yes,
I
don't
have
anything
else,
so
I'll
talk
to
you
tomorrow,
then
yeah.
C
I
try
to
so
just
some
minor
updates
from
my
side.
I
had
a
discussion
today
with
the
android
team
and
already
told
them
that
they
can
join
if
they
want.
So
we
have
one
person
for
20,
that's
the
maximum
that
I
could
get
out
at
the
moment,
but.
A
Yeah,
I
think
that
might
be
enough.
You
know,
I
think,
like
I
said
at
this
point,
we
we
are
gonna.
Think
of
it
as
we
are
in
a
design
stage,
so
we
want
to
do
more.
You
know,
reading
the
specification
you
know,
reading
the
code
that
splunk
has
and
then
identifying.
You
know
what
to
you
know
how,
to
you
know,
move
it
to
open
telemetry
project.
So
so
it's
an
existing
repo
that
you
know
we
want
to
move.
C
I
know
the
signal
fx
repository,
there's
one
interesting
concept
that
I
anyway
wanted
to
discuss,
and
it's
good
that
the
splunk
gears
are
joining
tomorrow.
Okay,
because
in
mobile
you
have
kind
of
an
offline
capability
which
you
usually
don't
use
in
any
other
open,
telemetry,
instrumentation
or
in
any
other
technology,
except
for
mobile.
C
Basically,
it
would
be
possible
that
you're
offline,
so
your
doing
some
interaction
in
an
application,
but
you're
going
through
a
tunnel
or
whatever,
and
you
still
want
to
capture
all
the
offline
information
you
know
so
something
like
you're.
Writing
it
to
the
disk
and
flashing
it
out
later,
and
that
concept
is
nowhere
else
used,
except
for
mobile.
A
Yeah
makes
sense
so,
let's
so
that
is
where
you
know
the
you
know
the
community
contributions
help
right.
So
so
we
there
has
to
be.
You
know
a
sig
sig,
for
you
know
mobile.
There
is
one
for
ios
already,
so
we
could
combine
them
and
we
should
develop
a
common.
You
know
design.
A
It's
a
swift
actually,
but
we
could.
You
know
they're
they're,
ready
to
you,
know,
work
on
ios
as
well.
A
Like
I
said
the,
that
is
where
I'm
asking
more
people
to
contribute
right,
the
implementation
is
the
last
part.
A
Agreeing
to
you
know
what
to
implement
is
is
is
going
to
take
more
time,
so
we
should
that's
why
I'm
stressing
that
we
should,
you
know,
get
started
discussing
and
creating
tickets
and
we
mark
them
help
wanted.
I
think
there
will
be
youngsters,
you
know
eventually
that
will
join
I'm
every
each
of
us.
You
know
we.