►
From YouTube: 2022-10-11 meeting
Description
Instrumentation: Messaging
B
C
A
B
C
A
C
A
B
A
D
D
A
So
it's
a
super
confusing
the
way
it's
the
terminology
in
open,
telemetry,
the
API
and
SDK
are
not.
They
don't
have
the
standard
meanings
in
open
Telemetry
as
far
as
I
understand,
so
the
API
refers
to
some
of
the
front
facing
components.
So
what
the
end
user
end
user
were
to
create
events
or
spans
or
metrics
now
the
API
is
to
create
that
is.
Is
they
call
it?
An
API.
Sdk
is
also
an
API,
but
it
covers
some
of
the
things
that
happen
next
in
line
like
exporting.
A
You
know
the
span,
processors,
the
processing
pipelines,
but
everything
on
the
client
itself
on
the
agent
itself,
but
things
that
happen
next
in
line
like
after
the
user
submits
the
data.
How
does
it
go
through
processing
pipelines
How?
Does
it
go
through
the
export
exporters
conversion
to
protobuf?
All
that
is
the
concern
of
sdks.
B
Another
way
to
describe
it
is
in
open,
Telemetry
land.
The
API
is
the
API
surface
and
effectively
defines
that
a
note
of
implementations,
so
the
people
could
effectively
code
against
the
API
and
then
you
can
replace
it
with
any
SDK
implementation
of
that
API.
Underneath
the
covers
to
make
it
functional
it's
actually.
One
of
the
things
is
that
with
the
web
and
that
we
don't
really
need
the
not
implementation,
but
it's
there,
yeah.
D
C
A
A
C
So
so
that's
what
I
was
describing
is
that,
like
the
chord
there
has
to
be
like
a
core
module
or
a
core
package
for
the
SDK,
similar
to
like
the
trace
Trace
base.
Sdk,
where
you
have
you
know
you
have.
You
have
some
additional
classes
for
like
for
actual
like
the
pipeline
of
processing
blogs
and
there's
going
to
be
some
some
basic
implementation,
like
console,
console
exporters,
for
example.
C
A
B
A
B
A
A
Yeah
I
I
recommend,
irrespective
of
like
you,
you
should
continue
the
changes
you
have
in
mind,
but
it's
okay
to
open
it
up
for
public
comments.
Okay,
yeah,
I,
I
like
you
can
you
can
add
markers
saying
you
know
this
is
your
plan
in
in
places
where
you
plan
to
make
changes?
Okay,
you
can
just
add
from
to-do
markers
and
then
open
it
up
and
then
seek
feedback.
Okay,.
D
Okay,
perfect,
so
this
one
right,
so
the
okay
yeah,
that's
good!
So
that's
yeah
thanks
for
going
through
that.
Let's,
let's
quickly
go
through
that
and
then
yeah
talk
about,
you
know
since
Martin
Luther
and
everything
you
can
do
a
quick
recap
of
where
we
are
at.
You
know
what
we've
done
and
some
organization
of
how
we
transferred
some
of
the
completed
events
from
Excel
spreadsheet
into
into
this.
A
D
Then
I
Martin's
benefit
also
we've
done
page
here.
Yeah
touch.
Timing
is
the
next
one
and
then
looks
like
we
did
use
action
and
error
right.
Yeah,
okay,
I
was
wondering
and
one
of
the
items
you
know
just
real
quick.
How
do
we
Mark
these
things?
You
know
which
one's
just
done
or
whatever
should
we
just
move
to
the
left
and
then
stuff
or
Twitter
aspects,
or
something
like
that.
D
D
B
B
Yeah
so
for
identity
effect,
I
use
this
so
that
the
it
normalized
the
event
I
I
calculated
on
the
back
end,
which
is
I,
think
what
we
marked
it
as
italic
here,
because
I
can
bite
a
whole
bunch
of
things
so
that
when
I
went
got
the
custo
I
could
do
a
single.
You
know
Group
by
the
stack
hash
rather
than
having
the
group
by
other
individual
things.
So
that's
what
the
hash
is
about.
That's
just
to
try
and
normalize
the
event
without
taking
some
of
the
random
stuff
into
account.
D
So
it
seems
like,
as
long
I
know,
we
we
have
this
as
a
field
at
the
category,
the
whole
entire
trace
and
then
what
I'm
a
little
confused
about
is
it
doesn't
look
like
it's
a
just,
a
simple
husband:
it's
you've
got
to
remove
certain
pieces
and
stuff
and
take
interesting
stuff
and
then
hash
it
right.
Yeah.
B
B
D
C
D
C
I
would
also
say
that,
no,
maybe
you
don't
you,
don't
send
the
stack
Trace,
but
we
do,
but
we
only
do
it
for
like
the
first
error
in
this
session,
so
you
know
so
like
to
optimize
the
the
payload
not
being
as
big,
but
but
every
error
that
has
a
stack
hash.
The
same
stack
hash
in
the
same
session
is,
can
then
be
like
identified
in
the
back
end
and
look.
Those
stack
trays
can
be
looked
up
based
on
the
stack
hash.
B
C
A
Instance,
and
also
the
first
error.
So
if
let's
say
there
are
a
and
error
B
happen
and
error
a
happens
first
and
then
only
for
that
this
parameter
is
true
for
error
B.
If
it
happens
few
seconds
later,
it
is
not
true
because
I
think
the
the
purpose
of
this
attribute
As
I
understood
and,
of
course
it
was
from
from
nav's
explanation.
B
A
C
B
B
It
would
count
up
to
whatever
the
error
number
is
that
it
sends
and
it
sends
all
the
errors
down
and
then,
after
a
period
of
no
errors,
it
would
then
reset
it
back
to
zero
so
that
you
could
actually
group
them
and
only
concentrate
on
the
the
first
error
of
anything
that
that
happened,
and
this
is
because
there
was
a
big
jump
of
a
chunk
of
identity.
That's
like
a
spa
where
the
fact
that
we
have
virtual
page
changes.
B
If
we
changed
it
from
first
air
in
session
to
error
sequence
in
session,
or
something
like
that,
put
it
back
as
a
number
and
then
we
could
say
the
instrumentation
that
sends
this-
can
either
reset
it
or
just
not
do
anything
or
you
configure
it
to
only
ever
sends
the
first
one,
but
from
the
exception
perspective,
we
just
know
that
you
know
this
is
the.
This
is
the
X
number
of
error
that
happened
within
this
user's
session.
D
B
A
B
A
B
B
B
D
D
B
B
D
B
The
Vera
one
so
effectively.
The
first
thing
you
do
is
investigate
what
what
is
error
one,
that's
actually
causing
the
problem
to
concentrate
on
that.
That's
really
what
it
was.
What
what
I
used
it
for
when
I
was
investigating
JavaScript
errors
is
to
say:
well,
you
know,
I
I
got
a
Cascade
of
errors
in
a
very
short
period
of
time.
This
was
always
the
first
one.
B
Let's
go
and
look
at
that
one
and
then
once
I
I
know
what
that
one
is
I
then
looked
at
the
second
one
and
the
second
one
was
the
side
effect
of
the
first
one.
Then
I
would
just
ignore
the
rest,
because
the
rest
are
probably
related
as
well
and
then
just
you
know,
do
a
fix
for
for
zero.
But
if
I
found
that
the
second
one
was
completely,
it
was
another
thing
all
together.
Then
that
would
you
know,
raise
another
bike
and
go
fix
that.
D
Okay,
so
question,
and
then
you
know
if
we,
if
we
go
with
this
definition,
a
couple
of
questions
in
my
mind,
I
think
Santosh
also
asked
the
one,
the
first
editing
session.
Does
this
match
neurolix
implementation?
Do
you
need
one
more
field?
That
is
one
question.
Second
question
is:
if
we
say
that
we're
going
to
the
SDK
has
to
do
something
in
the
timer
to
reset
the
errors
and
whatnot
that
has
to
be
defined
right.
You
know,
how
do
you
define
it?
How
do
we
make
sure
that
this
is
consistent?
D
B
I,
don't
think
we
need
to
define
the
the
period
now
and
it
will
probably
be
different
depending
on
the
application,
because
some
applications,
if
they're
all
automated,
would
probably
want
that
period
to
be
really
small.
But
if
it's
user
interaction,
then
you
know
one
or
two
seconds
is
probably
enough.
Okay,.
D
D
B
B
D
D
So
it
seems
like
this
is
a
sort
of
an
optimization
unless
this
is
this
has
got
something
to
do
with
the
stack
hash
and
then
I
need
to
go
to
this.
You
know
event
with
the
first
ever
in
session
to
look
up
the
stack
hash,
because
nobody
else
is
going
through
that
nobody
else
is
going
to
start
has
a
stack
that
makes
sense.
C
But
yeah
yeah,
so
I
think
this
this
is
just
makes,
makes
makes
the
art
processing
easier,
so
I
think
you
could
easily
like
Implement
well,
not
easily.
You
could
implement
this
a
different
way
like
you
could
on
the
back
end,
you
could
have
some
kind
of
some
kind
of
caching
gotcha
or
some.
You
know
some
kind
of
processing
where
you
look
for
you
look
for
the
first
error
for
for,
like
a
session
or
page
view,
ID
and
then
use
you
generate
the
metric
from
that.
C
But
you
know
because
because
like
we,
so
we
our
ingest
is
more
like
a
stream
base,
so
we
just
generate
events
and
like
we
don't
yeah
so
this
this
allows
like
for
an
easier
query.
So
we
can
select
the
number
of
page
views
or
like
a
number
of
errors,
that
there
are
first
divided
by
Page
views,
gives
you
like
the
percentage
of
pages
with
errors.
Okay,.
D
D
A
C
D
B
D
B
D
D
B
B
D
D
A
A
B
C
B
Depending
on
the
runtime,
so
yeah,
the
line
number
on
the
error
object
itself.
Yeah,
that's
not
supported
everywhere
because,
as
it
says,
it's
non-standard,
but
in
terms
of
the
global
error
Handler
then,
yes,
you
do
get
the
error
and
line
number,
although
with
minified
code
it
tends
to
be
line
number
zero,
which
is
never
fun.
D
D
A
D
A
A
A
B
No
symmetically,
it
is
the
exception.
It's
just
that
in
JavaScript
the
errors,
but
you
know
you'd
still
deal
with
in
this,
try
catch
so
you
still
deal
with
them
as
exceptions.
So
and
in
terms
of
like
your
browser,
not
browser
mobile
runtimes,
then
they're
going
to
be
playing
with
exceptions
like
react,
native
and
stuff
like
that,
so
yeah
I,
think
candy
to
exception
makes
sense
to
me.
B
D
D
C
D
B
Apart
from
that
was
the
only
way
to
figure
out
the
door
would
be
considered
a
handle
exception,
as
opposed
to
a
log
exception
would
be
an
unhandled
one
of
which
we
could
Define
it
here,
I
think
as
part
of
defining
the
fields.
We
then
have
to
look
at
these
fields
and
say:
okay,
do
we
want
to
Define
this
as
its
own
error?
Error
data
object,
or
do
we
want
to
say
this
is
close
enough
to
the
existing
convention?
So
therefore
we
just
conform
to
that
I.
B
A
B
A
A
B
B
B
D
All
right
we
got
another
15
minutes
or
so
I
think
I
was
going
through
this
and
I
tried,
in
my
mind
at
least
trying
to
see
what
the
descriptions
would
be
for
this.
You
know
somebody's
got
to
fill
up
these
descriptions.
This
is
useful
should
be
useful
as
we
go
through
discussions.
You
know
when
you,
when
you
define
these
fields
put
in
some
description,
will
be
used
for
the
algorithm
I
think,
because
that
was
one
of
the
ways
we're
going
to
identify
that
have
we
talked
about
the
field
or
not.
B
D
Maybe
you
know
one
of
you
can
drop
a
link
or
you
know
maybe
take
that
yeah
I
I
can
do
that
yeah,
okay,
thanks,
because
when
we
come
back
to
these
things,
I'm
pretty
sure
we'll
we'll
be
confused
like
now.
How
did
this
come
about?
If
we
talk
about
it
or
not?
So
let's
just
put
some
even
if
it's
a
demo
description
like
you
haven't,
discussed
about
it,
something
like
that.
D
D
Let
me
start
with
say
this
one.
You
know
we
decided,
you
know
we'll
be
we'll
do
common
resources
first,
that
applies
to
every
every
event
and
then
individual
events
go
ahead
and
go
see.
I
believe
this
is
useful.
That's
why,
when
I
put
these
things
out
there
when
bankruptc
implementation-
or
you
know
trying
to
understand
what
the
field
does
or
whatever,
if
the
description
is
not
clear
enough,
this
will
be
useful.
D
A
D
Right
thanks,
I
appreciate
it.
It
will
be
a
collective
thing.
Also,
you
can
just
ask
for
folks
just
come
through
and
then
start
putting
some
values
and
stuff
yeah.
Okay.
So
that
was
that
and
then
so
there
was
a
comment
that
DJ
put
on
this
guy.
The
other
common
resource
impression
I
did,
if
you
guys
are
up
for
it,
then
I
would
like
to
quickly
discuss
about
this
so
just
to
reorient.
D
D
A
D
D
C
Do
kind
of
agree
with
Thabo
here
is
that
the
instance
ID
is
really
it
is
the
same
service
or
you
can
obviously
the
same
app,
but
it
has
so
much.
It
has
like
many
many
different
instances
running.
You
know
in
different
clients,
so
it
makes
the
same
sense
to
me
that
the
instance
ID
would
be
different
in
different
client
sessions.
Yeah.
A
It
comes
close,
but
you
know
consider
for
an
example
how
it's
used
on
the
back
ends
right
on
the
back
ends.
Let's
say
you
know
for
for
scalability
purposes.
You
know
you
run
multiple
instances
of
a
service
where
the
service
name
versions
are
all
the
same,
but
the
instance
ID.
Each
one
will
have
a
different
instance
ID.
Now
each
service
could
be
servicing.
Let's
say
20
different
API
calls
now.
A
C
D
D
D
A
So
so,
actually
sorry
to
interrupt
service
in
this
case
is
a
document.
Let's
look
at
that
sentence
again,
so
a
document
refers
to
a
page
right,
a
physical
page,
yes,
physical
page
now
are
we
using
this
different
service
name
for
each
of
the
pages?
We
are
not
no
so
so
that's
my
that's.
Where
I
see
a
discrepancy.
B
D
Explanations,
we
gave
that
you
know
it's
pretty
distributed
tracing.
You
know
days
right
so
yeah
now
that
we're
able
to
attach
that
to
the
server
that
produced
the
the
spand
and
produced
this
page
and
that
span
should
have
the
service
instance
idle,
and
that's
what
you
know:
that's
how
we
can
get
to
it.
I
think
yeah.
B
And,
like
I,
think
the
service
version
would
be
tied
to
that
because
you
know
generally
it's
because
you've
got
multiple
versions
that
actively
deployed
and
the
instance
sort
of
tells
you,
although
sometimes
we
we
did
have.
You
know
a
faulty
instance
that
would
have
to
go
track
down
and
and
bounce,
but
yeah
yeah,
if
full
distributed
tracing
with
full
mapping,
is
enabled
then
yeah.
You
don't
need
that,
but
I
found
it
useful.
Okay,.
D
B
A
A
D
Yeah,
that's
a
that's
a
good
point.
That's
what
I
was
going
to
go
back
to
also
you
know.
We
already
agreed
that
service.net
is
what
we're
going
to
use
for
the
application
names,
the
client
application,
name,
client,
application
version,
I,
I'm
kind
of
stuck
on
the
second
thing
that
we
talked
about
right
can
have
multiple
open
tabs
at
the
same
time.
D
A
C
A
D
A
D
A
I
I,
we
have
a
browser.page.url
I.
Think
if
you
scroll
down
the
in
the
varying
attributes,
there
is
a
browser.page.url
I
am
thinking
that
we
should
just
call
this
as
a
browser.page.id,
because
this
does
map
to
this
URL
like
for
every
different
page.
You
have
a
different
URL
and
in
the
case
of
single
page
application,
it
includes
the
the
URL
fragment
and
each
time
and
each
instance
of
this
page
for
for
different
users
or
different
tabs.
The
ID
will
be
different,
but
the
the
URL
will
be
the
same.
D
I
see
we
could
do
that
as
one
conclusion.
I
think
in
the
systems
might
be
used
if
I
remember
correctly
internally
in
the
back
ends,
will
generally
take
this
URL
and
then
hash
it
and
create
an
ID
for
querying
purposes
or
something
like
that.
So
that
might
conflict
with
that.
That's
the
only
thing
ma'am
are
you
aware
of
any
you
know
concrete
use
cases
we.
A
B
A
B
B
B
B
D
D
D
A
D
B
Speaking
of
semantic
inventions,
so
the
semantic
invention
working
group
is
actually
going
to
be
kicking
off
next
Monday
next
Monday
yeah
yeah,
and
it's
going
to
be
bi-weekly
at
this
point
that
it
came
up
in
the
respect.
Reading
before
this,
the
the
first
topic
is
going
to
be
around
metrics
there's
a
metric
or
thing,
though
sorry
but
yeah.
Just
your
way.
It's.
It
is
kicking
off
next
Monday
10
to
11
PST
bi-weekly.