►
From YouTube: 2022-10-12 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
B
B
B
A
Okay,
Martin
said
he'll
be
15
minutes
late,
so
we
can
start
once
Nev
joins.
C
Thank
you.
Let
me
see
nav
actually,
I
don't
have
said.
C
Okay,
I
guess
you
know
we
did
finish
exception
yesterday.
I
think
you
can
start
with
the
reduction.
I
believe
is
that
what
the
computer
numbers
do
where
we
stopped
yesterday,
I
think.
C
Okay
how's,
my
audio
now
is
it
okay,
yeah.
C
I
was
I
was
definitely
bumbling.
Man,
sorry,
so
I
think
we
finished
up
to
exception.
Certainly,
we've
fully
administered.
Yesterday
we
get
started
user
action.
A
Yeah
I
I
see
there
is
a
agenda
item
on
user
action.
Last.
C
Night
we
were
chatting
about
it.
It
came
up
in
an
internal,
yes,.
C
Were
looking
at
it
just
came
up:
okay,
I
realized,
user
interaction
doesn't
seem
to
be
there.
I
thought
I've
seen
it
in
somebody's
schema.
We
couldn't
find
it
thought
we
would
discuss
that.
It'll
be
a
good
idea
to
talk
about
it.
C
And
impressionally
semantic
convention-
I,
don't
know
who
added
this.
A
I
I
added
it,
we
discussed
it
yesterday,
RAM
and
I.
Think
T2
has
some
comments,
so
I
I
want
to
go
over
it
with
him,
got.
C
It
got
it
okay,
cool
hey
now
morning
and
then
is
ready
for
the
view.
Yeah.
B
That
one's
super
quick,
it's
just
letting
folks
know
that
it's
it's
up
for
review,
so
I
think
it's
tagged
like
the
JavaScript
approvers,
so
yeah,
there's
just
hopefully
there'll
be
some
movement
on
that
soon.
B
I
would
say
it's
more
just
like
if
you
want
to
look
if
you're
able
to
look
at
it
at
any
point,
it
doesn't
have
to
be
right
now:
okay,
yeah,
so
if
you
someone
can
review
that
that'd
be
very
helpful.
Yeah.
A
I
I
think
you
might
want
to
let
folks
in
the
jsig
also
know
yep.
C
Perfect
all
right,
so,
okay,
we
can
start
with
the
the
preach
interaction
schema.
We
would
actually
take
interaction.
That's
Gmail,
okay,
I,
don't
think
you're
capturing
anything.
But
AWS
did
we
not
have
any
different
videos.
C
Yeah,
okay,
so.
A
B
C
B
Derive
it,
but
generally
it's
it's
one
of
the
metrics
it
gets
captured
for
browser.
B
View
we
don't
capture
it,
but
there
are.
There
are
other
people
that.
C
B
C
Think
that's
yeah!
That's
what
I
thought
too
and
that's
why
I
wanted
to
bring
it
up
see
if
anybody
catches
anything
Martin
might
have
some
item.
They
they're
the
big
on
caption.
Are
these
timing
type
stuff,
so
you
might
have
something
you
get
probably
table
it
until
he
joins
and
then
we
will
discuss
that
also
the
time
to
interaction
that.
A
I
think
it's
not
a
big
deal,
I.
Think
one
question
related
to
that
is:
do
you
expect
it
to
be
present
in
all
the
other
interaction?
Events
are
only
when
it's
present
only
when
it
only
for
the
first
interaction
event.
You
you
add
it,
in
which
case
you
think
it's
okay.
C
I
see
yeah
I
think
that's
a
good
point.
Okay,
we
can.
You
know
I'd
like
to
table
this,
for
you
know
we
can
close
on
that.
C
Oh
Martin.
A
D
C
B
Yes,
things
like
that:
we're
looking
at
there
like
the
first
contentful
layout
and
all
the
rest,
that's
around
the
same
thing
in
terms
of
the
interaction
like
I'm,
getting
a
lot
of
people
talking
about
web
vitals,
and
they
want
us
to
capture
it.
So
this
is
like
that's
becoming
the
the
new
standard
for
data,
which
is
really
like
the
stuff
derived
from
the
performance
timings.
B
So
it
might
be
a
case
of
we
either.
Add
this
to
the
page
view
performance
or
we
have
a
specific
one
called
web
vitals
or
something
like
that.
C
So
I
think
I
lost
you
a
little
bit.
I
was
not
just
switching
headset
lab.
Are
you
done
generally
about
user
action
or
a
particular
field.
B
B
I've
just
pasted
a
link
into
the
Google
web
vitals
definition,
which
more
and
more
people
are
wanting
to
capture
that's
a
standard
thing,
which
is
the
last
contextual
paint,
though
there's
a
whole
bunch
of
stuff.
There.
C
B
C
I
guess
we
would
talk
about
it
when
we
talk
about
this
timing,
stuff
right
yeah,
but
the
the
basically
performance
equivalent
okay.
So
let's
just
deal
with
this
guy
first
go
through
so
AWS
doesn't
have
anything,
that's
good!
What
about
your
guys's
stuff?
Sometimes
don't
have
anything
equivalent
to
user
action.
C
Okay,
all
right
and
same
with
the
honeycomb
also
were
we
yeah.
B
At
the
moment,
in
terms
of
like
user
interaction,
we're
very
interested
in
how
I
guess
Hotel
will
handle
this
stuff
and
we'll
just
kind
of
like
like
we're
interested
in
it,
but
yeah,
we
don't
do
anything
specific
around
it.
C
Okay,
all
right
so
looks
like
Hotel
currently
does
that
using
so
I'm,
not
too
sure
about
you
know
what
we
do
do
we
capture
all
the
inputs,
and
you
know,
set
a
span.
Is
that
what
we
do
today.
C
All
right
the
same
deal
here
for
us
also
Nev,
can
probably
take
that
I
can
time
it
also
how
we
capture
things.
B
C
Okay,
this
is
also
for
mostly
for
what
type
of
analysis
is
what
I'm
thinking?
It's
not
you
know
any
performance
or
you
know,
APM
specific
things
or
whatever
yeah
click.
Click,
analysis,
yeah,
the.
C
Correct
the
what
parts
of
the
page
is
actually
being
useful,
you
know,
and-
and
things
like
that-
please
improvements
is
what
they
use
it
for
a
lot
of
marketing
teams
use
use
that
as
well.
They
do
a
campaign
or
whatever
it
is,
they
put
a
link
somewhere
and
they
want
to
see
how
many
people
actually
click
on
that
link
from
you
know,
page
a
versus
page
B,
which
is
Click
C
or
whatever
those
type
of
analysis.
It's
a
pretty
useful
thing,
I
believe
Google
also
does
this
tagging.
C
This
is
where
tagging
content
comes
into
picture.
On
a
page
apart
from
the
HTML
attributes,
IDs
and
other
you
know,
attributes
you
can
throw
in
there.
People
can
also
add
custom
attributes,
data
data,
Dash
attributes
those
could
be
all
marketing
information.
C
C
I
guess
the
first
okay,
the
I
I,
want
to
make
sure
that,
because
you
know
you
get,
you
know
the
others
don't
seem
to
have
equal
and
things
and
stuff.
First,
you
know
this
is
a
useful
thing.
I
think
right
now,
we
believe
from
Microsoft.
It's
useful
I
think
currently,
Splunk
is
also
using
that
we
believe
it's
useful
for
hotel
any
thoughts
from
Santosh
purvi.
A
And
I
think
we
agree
yeah.
We
are
looking
forward
to
having
this
feature
yeah.
C
Cool
so
we'll
we'll
just
go
through
the
you
know
things,
then
it
should
be
pretty
straightforward
thing,
I
think
event,
name
and
timestamp.
You
know
we
know
these
are
standard
stuff.
The
URL
comes
from
common
event,
stuff
element.
C
The
the
particular
element
that
we
clicked
on
we
need
to
talk
about,
you
know,
are
we
capturing
the
name
or
the
ID
or
any
other
custom
attribute,
or
anything
like
that?
So
that's
always
been
it
yeah.
B
That's
a
that's
an
interesting
one.
That's
something
I've
been
thinking
about
a
little
bit
but
yeah
I.
Think
they're,
like
it's
not
simple
to
just
just
have
the
name
of
the
element
or
like
the
tag
or
the
ID
because
like
you're,
not
if
the
only
thing
you're
guaranteed
is
like
what
kind
of
an
element
it
is,
but
then,
if
you
don't
have
any
more
information,
it's
it
could
just
become
very
noisy.
C
Yes,
I,
agree,
I
think
you
know
if
we
start
capturing
type,
the
input
type
equals
you
know,
I'm
just
taking
a
simple
example:
input
type
equals
button
name
equals
the
submit.
Id
equals
one
two
three
four
five,
something
like
that
and
then
other
stuff
right.
So
when
we
start
capturing
these
things,
there's
an
order
of
Precedence.
You
know
I'm
again
talking
from
you
know,
memory
like
five
years
ago
or
something
when
I
when
we
implemented
this
internally
yeah.
C
So
there's
an
order
of
Precedence.
We
typically
look
for
the
main,
because
name
is
the
one:
that's
guaranteed
to
be
unique
for
that
input
thing
at
least
not
guaranteed.
You
know
the
it's
up
to
the
users.
You
can
call
everything
sub
it.
So
that's
the
thing
I
believe
our
order.
Precedents.
Never
correct
me
if
you're
wrong
is
a
special
data.
Dash
attribute
for
this.
If
that
is
available,
we'll
take
that
if
it's
not
available
then
go
for
the
ID.
C
If
the
ID
is
not
available,
then
come
to
the
name.
Id
is
guaranteed
to
be
unique,
at
least
as
per
the
HTML
spec
yeah.
You
know
if
you
have
the
you
could
throw
in
the
same
ID
you
guys.
You
know.
We
all
know
that
throwing
the
same
idea
across
the
board
it'll
be
considered,
not
a
compliant
HTML,
but
browsers
will
still
render
yeah
but
anyway,
so.
A
So
the
row
9
expat,
is
guaranteed
to
be
unique
right
for
every
element.
C
The
path
that
leads
to
that
element,
I
think
and
then
in
the
same
expat
you
can
I
believe
I,
don't
know
where
this
came
from
yeah
the.
B
Is
there
a
discussion
here
about
whether
we
want
to
have
something
like
introduce
something
like
data
open
like
like
a
data
field
specific
to
Hotel?
There.
C
This
is
this:
is
data
Dash,
so
in
the
in
the
actual
you
know
HTML
attribute
for
that.
C
So
this
is
the
magic
thing
you
know
for
us
internally
in
Microsoft,
it's
data,
Dash,
bi,
okay,
that's
a
tag,
but
data
Dash
is
important.
You're
allowed
to
add
any
attribute
with
data
Dash
that
is
not
defined
in
HTML
standards.
B
C
So
so
that
way,
customers
can
give
you
know
a
human
readable,
unique
ID
for
the
page
or
for
the
whole
website
or
whatever
they
feel
like
right.
The
content,
Management
systems
do
come
up
with
these
kind
of
things.
You
know
they.
They
have
a
big
database
full
of
input
elements.
They
know
which
input
element
shows
up
on
which
page,
which
instance,
and
what
else
and
whatnot
so.
A
Because
I'm
I'm
thinking
these
can
be
together
like,
for
example,
the
the
element
that
you
clicked
on.
A
If
that
happens,
to
have
the
data
attribute
the
data
tags
then,
and
then
that
that's
what
you
will
include
here
right
and.
A
No
in
in
the
in
the
event,
so
so
let's
say
a
given
page
can
have
you
know
these
data
attributes
on
on
multiple
different
elements
yeah.
But
in
this
event
that
you
generate
here,
you
will
include
only
those
data
attributes
present
on
the
element
that
you
clicked
on.
That.
C
Is
correct?
That
is
correct,
but
the
question
is
one
of
those
attributes.
You
know
this
could
be.
You
know
one
at
one
value
or
100
values.
C
Need
to
include
all
of
them,
the
you
know
when
we
get
to
it.
We
can
talk
about
in
our
recapturing
all
of
the
like
key
value
pairs.
Also,
we
need
to
know
what
what
maps
to
what
right
I
can
talk
about,
how
we
handle
it.
Some
you
know
in
a
second,
but
this
I
think
is
a
special.
You
know.
One
of
the
one
of
the
attributes
is
a
special
attribute.
We
need
to
figure
out
a
thing,
I
believe
it's
probably
an
ID
data,
Dash
Hotel,
Dash
ID.
C
We
fish
out
that
special
attribute
value
and
then
stick
it
here
in
element,
so
that
becomes
the
easy
thing
to
Simply.
You
know
the
querying
and
things
as
opposed
to
you
having
to
look
through
a
collection
which
is
just
free
for
all
that
you
know
the
data
Dash
your
special
attribute
may
or
may
not
be
there.
C
C
A
So,
when
you
say
order
of
Precedence,
did
you
mean
only
whichever
is
available
in
that
order?
Correct.
C
It's
in
my
opinion,
they're
useless
once
once
you've
found
the
most
unique
thing
identifying
an
element
you
don't
need.
Other
things
is
what
I
think
I
like
to
hear
thoughts.
It's
it's
usually
garbage
at
that
point,
because
the
ID
becomes
a
unique
ID.
Only
for
that
page
data,
Hotel
ID
is
even
more
unique
in
a
bigger
space.
B
I
think
we
should
capture
like
all
of
them,
because
there
might
be
a
situation
in
which
people
want
to
filter
by
something
different,
whereas
the
the
data
Hotel
ID,
might
actually
just
be
what
we
use
in
the
name
of
that
event.
C
I
see
nav.
If
you
have
experience
dealing
with
our
you
know,
bi
folks,
you
know
please
chime
in
what
I've
seen
is
that
I?
Can
you
know
on
this
section
here
tags
we
have
a
concept
called
content:
blog
I
can
have
a
you
know.
I
can
find
a
link
to
it
immediately
whenever,
if
you
can
find
it,
if
you
can,
you
close
it
it'll
be
great,
but
internal,
but
anyway
it's
it's
a
blob
field.
C
We
call
it
the
content
blob,
which
is
pretty
well
curated
from
the
client
side,
and
then
we
don't
send
garbage,
because
the
thing
is,
if
you,
if
you
think
about
it,
the
contact
blob,
there's
gonna,
be
so
much
the
usefulness
of
that
over
time
we
figured,
and
if
you
send
so
much
data,
it
just
becomes
less
useful,
so
we
curate
it
and
then
across
the
board.
We
send
only
the
things
that
we
believe
is
useful.
C
The
use
cases
so
I'm
just
talking
from
the
the
current
use
cases
that
we
have
internally.
People
are
fine
with
sending
getting
only
one
of
them.
I'm
not
opposed
to
sending
it.
But
you
know:
I
I
can
tell
it'll
just
be
a
lot
of
noise
or
Garbage
data.
C
If
we
send
all
three,
how
do
you
guys
propose?
We
send
it?
You
know
into
the
same
field
or
different
fields.
C
Yeah,
it's
just
an
increasing
the
the
the
payload
stuff,
I
think
yeah
I'm,
okay
with
it.
We
can
throw
it
in
there.
The
usefulness
of
that
I
really
question
because
ID,
if
you
take
ID
and
isolation
right,
ID
number,
seven,
multiple
Pages
could
have
the
same.
Seven
number
ID
number
seven
for
different
elements.
Just
you
need
to
then
look
at
which
page,
which
ID
a
big
database
of
something
needs
to
tell
you
this
page.
This
ID
means
this
and
stuff.
It's
typically
the
content.
C
A
So
what
do
we
send
today?
82
I
think
there
is
an
implementation
already
right
currently.
B
A
C
A
I
also
feel
like
if
we
capture
the
the
HTML
tag
like
AR
div
span,
and
then
you
know
list
all
the
attributes,
so
ID
name
are
also
attributes
on
that
tag.
Right
on
that
HTML
element,
so
so
line
23
instead
of
tags.
You
know,
if
you
call
it
attributes,
then
it
will
include
pretty
much
everything.
That's
on
that
tag
as
attributes.
C
Know
it'll
be
so
nice
I,
really
question
the
value
of
you
know
capturing
that
you
know
at
that
point.
We're
basically
saying
the
whole
HTML
page
I
want
to.
You
know
I'll
end
up
capturing
or
something
like
that,
but
you
know
it's
only
for
the
clip
that
we're
talking
about.
If
we
go
down
this
path,
the
next
thing
might
be
we
you
know
we
haven't
gotten
to
that.
Yet
there
is
a
another
event
called
contact
view.
Yeah
we
haven't
talked
about
here.
It's
it's
super
specific.
C
You
know
that
starts
describing
the
whole
page,
so
people
can
do
analysis
on
hard
parts
of
the
page
and
you
know
what's
useful:
what's
not
useful
and
so
on
and
so
forth.
Another
level
that
content
thing
would
start
being
influenced
by
how
we
capture
these
tags
and
stuff
and
that
will
become
a
there'll,
be
like
an
event
for
the
entire
HTML
page
HTML
right
that'll
be
I,
I,
yeah,
so
I
really
question
the
usefulness
of
capturing
all
the
HTML
attributes.
D
Another
issue
is
that
currently
in
the
hotel,
it
takes
what
the
event
Target
as
the
element.
It's
it's
captured
so
exciting,
for
example,
in
this
HTML
G.
If
you
have
a
quick
comment,
listen
on
the
button
here
then,
but
you
click
on
like
either
the
icon
of
the
save
text.
Then
it
would
say
that
it
takes
a
click
on
the
save
or
icon,
but
they
will
show
up
as
two
different
things.
Kinda.
C
B
So
if
you
click
on
Save
and
it
didn't
have
the
data
Hotel
tags
where
you
would
actually
go
to
the
parents,
so
the
parent
ID
is
actually
the
button
in
this
particular
case,
looking
at
the
click
analytics
because
Christian
you
and
Hector
worked
on
it,
it's
it's
really
is
the
the
idea
is
the
is
the
ID
there's
also
a
thing
called
content,
name
which
I
wasn't
familiar
with,
which
we
pull
out
as
well,
and
we
include
somewhere
and
the
ID
can
default
the
content
name.
C
C
Yeah,
it's
it's
coming
back,
I!
Think
the
the
content
blog
that
I
talked
about.
That's
that's
the
one
that
will
contain
all
of
the
data
Dash
stuff
yeah.
C
B
C
Yeah,
those
are
two
separate
things.
If
I,
if
my
memory
says
me
correctly,
content,
content
and
Page
tags
are
two
separate
things.
Content
contains
data,
Dash,
bi
values,
yeah
collected
with
specific
order,
presidents
and
stuff
and
Page
tags
is
the
metadata
meta
tag
on
the
page.
You
collect
everything.
C
We
can
probably
table
The
Meta
stuff
for
a
second,
that's
at
least
from
input
user
action
type.
We
don't
care
about
it.
B
No,
so
on
line
10,
the
the
hotel,
ex-path
I
think
is
the
the
X
path
to
the
field.
So
the
thing
you
clicked
on
yeah,
where,
for
us
we
have
an
ID
and
then
we
have
the
parent
ID.
B
So
we
don't
capture
the
full
path,
so
I
think
XPath
covers
both
that's
effectively.
What
I'm
saying.
C
Okay,
I
think
I'm,
fine
with
that
any
any
thoughts
from
others.
On
on
that,
we
can
talk
about
the
data
Dash
Hotel,
how
we
capture
it
next.
A
Yeah
I
I
think
somebody
needs
to
carefully
write
detailed
description
with
examples.
Yeah.
C
So
just
to
element,
XPath
is
what
we're
going
to
capture
element
is
not
needed.
The
I
don't
believe
we
need
this
separate
thing
here.
C
B
C
Yeah
I
think
this
is
probably
where
you
know
the
hard
analytics
guys
would
have
a
good
input.
I
think
that
they
are
the
users
of
this
data,
I'll,
try
and
see
if
we
can
reinvite
them
and
there's
an
internal
team
in
Microsoft
that
that
has
a
lot
of
data
scientists
and
stuff
they
created
a
they.
You
know
we
worked
with
them
to
create
this
plugin
for
them
the
click
analytics
plugin.
C
C
I
think
we
can
move
on.
Can
we
jump
to
this
tags
since
we
started
talking
about
it
and
then
come
back
here
to
other
things?
Sure,
okay,
so
I
think
there's
you
know
we
talked
about
two
things.
The
page
tags
is
not
the
same
as
tags.
I
think
you
know.
We
just
understand
that
now,
after
Peter
described.
C
B
C
C
All
right
so
for
for
this
one
here,
then,
what
we're
saying
is
that
the
ID,
the
the
attributes,
aren't
that
clicked
HTML
element
is
what
we
want
to
capture
as
part
of
this
tags.
Correct.
C
C
C
Okay,
all
right,
switching
back
here,
I'm
going
to
remove
this
from
here.
Then
it's
not
equivalent
just
put
it
down
here.
C
This
I
believe
is
content.
That's
this
guy,
the
equal.
In
this
content.
We
currently
capture
content
with
in
a
structured
format.
That's
what
I
want
us
to
chat
about,
there's,
probably
going
to
be
n
number
of
attributes
that
we
would
come
up
with
from
the
tax
collection
right.
C
How
is
it
sent
currently
travel?
Do
you
know.
C
Oh
got
it
support
for
some
way
to
define
user
interaction.
Name
is
attribute.
Okay,
it's
a
it's.
You
know
my
thinking
is
you
know
we
do
this
with
the
content
blog
that
I've
been
talking
about
it's
it's
a
Json
blob,
essentially
Json
blog.
It
just
doesn't
make
sense,
but
you
get
get
that
idea.
It's
a
Json
string.
The
object
is
essentially
a
you
know.
The
tag
name
value
tag,
name
rally,
kvp,
that's
it.
The
type
name
does
not
contain
data
Dash
or
tell,
or
what
Dash
or
whatever
it
will
simply
say.
C
Xyz
its
value
is
one.
You
know
some
Fubar
values
do
so
on
and
so
forth.
C
Is
that
agreeable,
or
do
we
need
to
do
something
else?
What's
the
format
of
capturing
this.
D
B
A
size
perspective
that
that
would
be
painful,
a
nested
object
would
be
better
than
separate
attributes.
A
At
this
one
level
I
think
he
means
if,
if
and
when
we
have
support
for
object
objects
as
the
value
of
an
attribute,
then
we
can
just
put
them
all
in
in
one
dictionary
and
assign
it
yeah.
B
B
It's
not
good,
whereas
the
Json
blob
at
least
you're,
not
repeating
the
x
dot
y
multiple
times,
because
if
you've
got
like,
you
know,
50
tags
that
have
them
an
additional
50
attributes
is
just
painful
to
create
and
populate.
D
B
D
Yeah
but
we'll
we'll
do
all
of
those
values
have
any
sort
of
prefix
or
would
they
all
be
different,
because
if
they
aren't
different,
then
it
doesn't
matter
if
it's
all
one
object
or
what.
D
B
B
No
so
effectively
I
I,
my
preference
would
be
the
Json
coded
string,
but
the
Json
coded
string
would
just
have
the
x
dot
y
and
then
the
value
and
then
the
ABC
and
then
the
value
and
the
def
and
then
the
value.
Because
yeah,
as
as
Peter
said,
we
cut
we'd
cut
off
the
data.
Dash
Hotel.
C
If
you
have
something
like
that,
you
know
what
what
we're
saying
is:
whatever
that
field
is,
but
if
we
call
it
tags
right,
tags,
I
think
the
proposals
are
something
like
this.
C
C
Okay,
that's
good
now
we're
all
on
the
same
page
about
what
each
each
of
us
are
saying
and
stuff.
Okay.
C
So
if
you
know
there
is
a
we
have
seen
like
data
Dash
Hotel
like
28
attributes
in
single
element
and
stuff,
so
this
would
be
all
of
a
sudden
that
particular
event
has
20
fields
and
another
event
has
this
one
field
and
so
on,
and
so.
B
B
That's
it's
the
repeating
nature
of
that
prefix.
That
I'm
saying
is
wasteful
yeah
I
agree
because
the
the
third
option
is
instead
of
being
adjacent
string,
it's
actually
nested
attributes,
but
unless,
when
they
converted
to
Jason
they're
a
bit
painful
as
well
yeah.
D
C
Yeah,
so
this
is
where
the
what
we
have
done
in
the
past,
you
know
before
Nev
joined
our
team
and
stuff.
So
is
we
took
special
attributes
that
across
the
board,
the
content
analytics
guys
used
and
we
created
a
special
thing
called
content.
So
you
know
you
would
have
something
like
this
content
again.
I'm
typing
it
for
memory,
so
maybe
may
or
may
not
be
correct.
So
the
special
things
are
I'm
gonna.
C
Just
you
know
forego
the
quotes
and
stuff,
not
a
valid
Json
ID
colon
one
name,
Colin
save
or
something
like
that,
and
then
slot.
C
I
think
there's
I
was
just
trying
to
look
for
the
options
by
the
way.
Let's
say
this
is
the
top
level
things
that
we
worry
about.
This
is
this
is
what
the
content
is
and
then
the
rest
of
the
stuff
would
be
free
for
you
know
whatever
else
we
find
we'll
just
throw
them
all
there.
So
everything
goes
here,
so
the
analytics
guys
will
always
look
for
Content
dot,
ID,
content.name
and
content
dot
slot
slot
is
the
idea.
Is
that
let's
say
you,
you
created
this
as
a
slot.
C
C
It's
it's
typical
in
the
cartoon
analytics
space
as
far
as
I
know
so,
special
meaning,
special
meaning
assigned
field,
attribute
names
and
then
free
for
all,
so
the
analysis
guys
will
always
be
looking
at
the
four
or
five
key
things
that
they
care
about,
and
everything
else
is
just
in.
You
know
in
the
blog.
C
That's
why
I
tend
to
like
this
tags
thing
where
we
stick
everything
into
a
field.
Nested
would
be
awesome,
but
at
the
moment,
if
it's
not
available,
it
could
be
a
string.
Stringify
Json,
that's
good.
B
Yeah,
so
so
to
get
back,
so
that's
why
we
send
them
as
nested
objects
so
that
the
back
end
when
serializes
it
it
doesn't
have
to
pull
it
apart.
So
if
we
sent
it
as
a
Json
encoded
string,
you
could
say
that
the
back
end
systems
can
go
and
decode
them
and
pull
them
back
out
again.
That's
where
the
nest
attribute
idea
is
just
happens.
B
B
C
So
we
we
go
with
you
know
which,
which
one
we
go
with
and
I
think
this.
This
definitely
has
it's
just
you
know
a
teacher.
This
was
your
proposal.
Do
you
see
the
problems
that
have
highlighted
with
this
one.
D
B
C
No
I
think
the
problem
that
I've
never
highlighted
was
that
if
you
go
with
the
top
level
Fields
you
have
to
prefix
them.
You
know
what
what
are
we
prefixing
as
that's?
That's
that
becomes
another
another
thing
right.
You
prefix
the
page
ID
or
something
like
that,
because
in
the
back
end
and
everything
is
collected,
a
could
be
coming
from
100
different
pages.
It's
just
become
less
just
less
useful.
B
But
it's
more
a
case
of
clashing,
so
if,
for
example,
there
was
a
data
dash,
hotel-event
dot,
name,
you'd
end
up
having
a
second
event.name
attribute
added.
If
it
wasn't
didn't,
have
a
prefix
saying
it
was
retail
tags.net
or
in
this
case.
C
B
Of
the
size
that
it
gets,
I
think
included
onto
the.
C
So
so
the
fields
are
going
to
be
like
this
tags,
that
my
field
and
so
on
so
tags
is
just
repeated
several
times.
That's
what
Nev's
talking
about
the
same
argument
for
nested
or
not
so
I
guess
we
all
agree
that
we
need
to
capture
this
tags
from
data
Dash,
it's
the
it's.
The
format
would
would
the
the
nested
attribute
conversation
help
drive
this
to
completion
now.
B
Yeah,
if
we
had
it
as
a
nest,
accurate
I'm
just
trying
to
find
my
browser
so
I
can
click
that.
That's
that
one
so
I
could
document
an
example
would
help
because
effectively,
you
would
say
attribute,
would
be
tags
and
then
the
elements
inside
of
that
would
be
your
a
in
your
my
field
and
yeah
yeah.
B
A
We
can
table
this
discussion
too.
I
think
there
are
other
situations
that
require
National
attributes
to
yeah
and
I.
Think
when
we
get
to
implementing
this-
and
you
know
we
don't
have
the
Institute
attribute
support
yet
so
we
well.
B
We
do
have
it
for
logs
we're
primarily
talking
about
logarithms
here,
okay,
if
we
don't
get
nested
attributes
support
for
span
events,
then,
when
we
come
to
the
discussion
of
how
do
we
represent
a
log
event
as
a
span
event?
That's
when
we
hit
that
roadblock
right.
C
C
Okay
and
then
the
page
name.
Didn't
we
talk
about
page
name
already
here
the.
C
Sorry,
apologies.
B
D
B
I'm
thinking,
page
width
and
height
I,
don't
actually
know.
Let
me
go,
have
a
look.
B
A
B
C
Oh,
this
is
what
it
is
sorry
I
was
getting
distracted
with
how
detailed
Drew
on
the
thing
and
annotate
it's
pretty
neat.
B
So
yeah
so
I
found
the
code.
It
is
as
I
thought
it.
Just
like
yeah
the
x
coordinate
with
an
X
and
then
the
Y
coordinates.
There's
a
string,
How
We
Do.
B
C
Okay,
so
what
I
wrote
was
a
script
writer
and
something
somebody
something
like
this
21
X
400,
something
like
that:
yeah.
Okay!
So
do
some!
You
know
here,
okay,
moving
on
so
this
one
here,
these
guys
the
peace,
medium
Target,
URI
refueri.
A
Actually,
we
have
only
five
minutes
left.
Do
you
want
to
talk
about
this,
or
do
you
want
to
talk
about
other
things
on
the
agenda.
C
Okay,
so
this
is
good
I
think
yeah
I
can
yeah
and
back
let's
go
back
to
that.
Okay,
it's
running
on
schema
time.
Actually
we
need
to
talk
about
this
later
impression:
ID
yeah,.
A
I
I
want
to
talk
quickly,
so
I
have
a
question
a
tattoo,
so
the
page
URL
for
single
page
applications
every
time
the
route
changes.
You
would
capture
that
as
a
as
a
separate
page,
URL
right
it
will.
It
will
change
the
resource
attribute.
A
Yes,
now
for
impression,
do
you
want
a
separate
impression
every
time
the
page
changes
within
the
single
page
application.
D
Well,
personally,
I
would
use
the
ID
to
group
all
of
the
data
that
happens
on
one
page
load.
So,
for
example,
if
you
load
a
page
but
the
script
doesn't
load
and
then
two
clicks
later,
you
try
to
do
something
that
script
is
needed
for
the
only
way
to
know
this
cost.
That
tissue
is
to
look
back
or,
if
anything
that
happened
during
this
document
instance.
A
But
here
we're
talking
about
the
impression
ID
and
this
is
for
the
purpose
of
Analytics.
A
So
if,
if
you
want
to
show
that
hey,
your
application
has
500
impressions
for
a
single
page
application.
If,
if
you
are
keeping
only
one
impression,
ID.
D
Well,
this
depends
how
people
consider
different
Different
Page
views
in
a
single
page
step,
for
example,
you
could
also
consider
if
the
URL
changes.
You
also
send
an
event
that
the
URL
has
changed
at
English
count
to
those
URL
change
events.
As
how
many
times
a
base
has
been
loaded.
B
D
C
So
the
the
service,
this
service,
ID
right,
I,
think
the
service
instance
ID.
Will
that
change?
You
know
first
pass
when
a
logical
page
view
happens
no.
A
C
A
We
can
call
it
service
instance
ID,
but
to
you
RAM.
So
do
you
want
the
impression
ID
to
to
change
within
a
single
page
application
when
the
user
navigates
to
a
different
route,
correct.
C
It's
it's
ideal.
Yes,
it's
a
logical
page
view
right,
so
it
should
change
every
time
the
the
application
developer
or
the
application
owner
feels
like.
Oh,
this
is
a
new
page
and
hence
a
new
impression.
A
Okay,
so
today,
if
that
is
your
understanding
too,
then
then,
within
a
given
single
page
application,
the
service.name
and
service.version
refers
to
the
to
the
entire
application
and,
and
then
the
service
does
instance.id
is
now
referring
to
the
individual
routes.
D
No,
it
would
refer
to
that
document.
You
hope
the
document
that
has
the
single
reception.
D
A
Yeah,
no,
what
I'm
saying
is
the
service
namespace,
you
know
is
referring
to
the
the
entire
application,
your
single
page
application,
whereas
the
service.instance.id
is
referring
to
a
particular
route.
C
So
I'm
gonna
look,
look
here,
I
think
we
did
do
page
view
service.id
or
something
like
that
for
the
app
name.
D
N't
in
this
document-
okay,
it's
your
PIN
yeah,
basically
in
this
here,
gotcha,
okay,
sorry.
B
I
was
just
gonna
say
that
if
we,
if
we're
gonna,
use,
impression
or
Define
impression,
ID
as
route
change,
even
in
a
single
page
application
I
would
not
use
the
service
instance
ID.
For
that
then,
so
it
seems
to
me,
like
the
servants
is
service.
Instance.
Id
should
be
generated
once
once
when
the
SDK
initializes
and
then
the
impression
ID
like.
If
you
want
to
change
that,
then
you
know
there's
going
to
be
probably
a
different
plugin,
for
you
know
for
route
changes
or
something
like
that.
B
That
will
generate
a
new
ID
every
time
the
route
change
is
detected,
but
the
service
namespace,
in
my
opinion,
should
be
independent
of
that.
B
Hey
folks,
one
one
thing
just
before
we
wrap
up
changing
topics
slightly.
If
you
go
back
to
the
agenda,
the
hotel
governance
committee
election
is
next
week,
just
chiming
in
here,
just
because
I've
participated
in
this
sig,
but
also
because
I
think
a
lot
of
people
on
the
Sig
have.
B
The
metric,
the
the
thing
used
to
decide
whether
you
can
vote
or
not.
So
if
you
click
on
that
link,
it
goes
to
the
blog
post,
that
I
think
lives
or
how
Lila
wrote
describing
how
the
election
works.
If
you
want
to
vote
double
check
that
you're
on
the
voter
roll,
if
you
are
not,
there
are
details
on
how
to
get
yourself
on
it
by
saying:
hey,
I'm
part
of
the
rum
Sig.
Here
are
my
contributions
that
are
in
docs
and
not
GitHub.
D
C
Great,
so
you
know
we
are
at
time
or
a
little
bit
over
I
think
we
need
to
pick
up
this
topic
next
week.
I'll,
try
and
summarize
some
of
these
things,
but
or
do
we
want
to
do
this
offline,
we're
pretty
close,
I
think
the
service
in
society,
impressionality,
stuff.
C
Okay,
all
right
we'll
pick
up
from
there
next
week,
then
right,
yeah
I've,
heard
arguments
about
capturing
all
three
essentially
yeah:
okay,
okay,
cool
thanks
all
appreciate
it.