►
From YouTube: Telemetry: Snowplow Debugging w/ Roman & Jerome
Description
Issue: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30516
Key Takeaways:
- Use Snowplow Chrome Extensions in Incognito to clear caching of Snowplow events.
- Continue standardizing Snowplow Tracking and which Frontend events to use https://gitlab.com/gitlab-org/gitlab/-/issues/207930
A
Let
me
try
to
get
everything
in
order
here,
so
kind
of
also
makes
sense
on
the
video.
How
do
I
just
start
often
end
up
rambling
about
things,
so
you
know
it's
the
question.
We're
gonna
put
this
page,
so
yeah
in
general,
I
started
Claire
watch
the
video
you
recently
did
right
and
I
kind
of
tried
to
follow
it
as
much
as
I
could
or
so
to
go
through
everything
and
I
kind
of
like
try
to
follow
the
documentation.
We
have
a
bill
for
snow
plow
and
what
I
notice
is
it?
A
Can
we
use
this
tracking
event
very
off
more?
It
is
tracking
element
or
cell
from
tracking,
yes,
which
kind
of
like
encapsulates
I
love,
snow
plow.
So
most
of
the
things
that
the
snow
plow
documentation
has
that
we
refer
to
does
not
seem
to
work.
So
there's
kind
of
like
a
little
bit
of
a
disconnect
for
me.
Yeah
I
might
be
doing
something
wrong.
I'm,
not
true.
I.
B
Just
sent
you
a
link,
I'm,
not
sure
which
documentation
link
you're
looking
at,
but
this
link
that
I've
added
here
is
one
which
is
in
the
process
of
being
merged
in
I,
wrote
everything
up
in
a
wiki
and
then
mm-hmm,
it's
just
much
easier
to
use,
wiki's
and
and
then
I'm,
throwing
it
all
into
an
M
R,
and
then
it
should
land
on
the
actual
docs.
Don't
get
lab
comm
pages,
I
love.
B
A
A
Cool,
so
that's
kind
of
me
trying
to
kind
of
keep
notes
of
a
few
of
the
things
that
were
mentioned
in
the
video
and
for
me
to
kind
of
go
through
all
the
documentation,
so
I
think
I
stumbled
over
their
wiki
telemetry.
Did
you
just
link
to
me
I
think
that
was
helpful
regarding,
like
the
implementation
and
some
parts
yeah,
there
was
the
event
exploration
part
where
they
ended
up
in
the
trekking
guide
right.
That's
the
other
one.
I
I
tried
to
follow.
A
Right,
okay,
maybe
I
took
it
from
here,
actually
right
so,
and
the
interesting
part
is
here.
What
I
found
was
this
like
this
tracking
element
that
we're
using
for
many
things
and
I
look
at
trekking
chess,
and
this
is
like
just
a
small
wrapper
or
a
few
things
like
event
and
this
kind
of
things.
So
there
was
one
thing:
I
was
looking
into.
Was
this
page
view?
A
A
That
was
what
I'm
trying
to
go
for,
but
it
didn't
find
anything
in
our
dogs
to
be
able
to
use
it,
and
they
also
didn't
find
that
a
way
for
us
like
to
be
supposedly
kind
of
how
this
should
work
or
so
so
what
I
ended
up
doing
is
okay,
I
tried
to
hunt
this
down
eventually,
I
went
to
tracking
chess
and
right.
We
have
this,
this
tracking
class
somewhere
event
and
learn
right.
A
The
tracking
class,
where
we
allow
okay
to
call
custom
events
and
that's
what
the
our
documentation
is
referring
to
and
there's
a
bunch
of
other
things
and
then
I
found
the
only
way
where
we
actually
called
it
as
the
last
no
cloud
--trackpageview
so
can
I
call
this
directly
because
I
don't
seem
that
access
to
the
snow,
plow
event
or
so
on
my
pages
for
some
reason.
So
what
I
try
to
do
is
like
put
in
just
a
static
method
in
here.
A
A
B
A
That's
the
customer
and
we're
called
like
the
custody.
Then
I
give
it
our
name
that
I
now
having
the
constants,
which
is
like
this
project
issues,
design
what
our
documentation
recommends
to
I
took
it
from
rails
for
the
generates
yeah
and
gave
it
this
name
design,
viewed
and
for
the
label,
because
I
don't
know
which
one
is
used
afterwards
in
periscope,
but
that
one
yeah
I
think
like
the
snowplow.
Debugger
is
kind
of
like
buggy,
just
certain
agree,
because
it
does
not
give
me
like
consistently
events
or
so.
A
If
it's
working
or
not,
sometimes
see
popping
up,
then
I
see
like
super
old
events
popping
up.
So
it's
kind
of
weird,
and
so
my
question
I
guess
is
it's
just
a
right
left
in
it
cause,
like
otherwise
tracking
the
page
view
just
not
seem
to
work
properly
and
if
that's
like
just
a
wrong
usage
of
it
in
general,.
A
So
that's
the
page
in
this
design
tab
on
an
issue:
okay,
I
uploaded
two
images
very
much
upload
is
kind
of
like
broken
and
the
local
development,
for
whatever
reason-
and
what
should
happen
is
so
used
to
snowplow
debugger
here
and
then
and
what
should
happen
when
I
click
on
it,
it
should
fire
the
custom
event
now.
So
what
you
see
it's
like
just
populating
was
a
ton
of
events.
A
A
B
A
A
B
A
A
So
I'm
updating,
recompiling
one
second
I
theory
loads,
automatically,
okay
cool!
So
now,
when
I
click
on
it,
it
should
show
tracking
or
track,
and
if
I
click
on
this
one,
it
should
throw
show
track
again,
which
it
that's,
not.
Okay,
that
might
be
a
mistake,
but
yeah
I
still
don't
see.
Mycustomevent
popping
up
anymore
yeah.
A
And
one
thing
I
feel
like
snowplow,
you,
like
you
say
you
click
on
clear
bends,
but
it
like
always
keeps
the
one
stored
like
from
days
ago
as
well
and
wearing
your
cache
of
the
browser
mm-hmm
and
then
just
like
reload
time.
Once
you
do
get
a
new
event.
It
like
gives
you
all
the
old
events
again
yeah.
A
A
B
B
A
B
A
B
A
A
A
A
A
B
A
B
B
Write
write
our
own
Chrome
extension
well,
I
mean
I.
Think
what
you've
done
here.
If
you
close
this
a
kognito
tab,
it
clears
the
cache
right
and
then
you
can
open
it
again
and
then
see
the
most
recent
events.
So
it
could
be
that
we
need
to
just
enable
this
Chrome
extension
inside
incognito
and
work
off
of
a
fresh
window
every
time
or
a
fresh
browser.
Every
time.
A
A
That's
true,
that's
that's
true
and
I.
Wonder
like
I
do
mind
doing
this.
How
it's
just
like
cause
Donald,
told
me:
hey,
you
could
use
like
a
pageview
vent.
Okay,
it
maybe
make
sense
to
trigger
page
view
and
I
will
just
check
in
the
next
one
or
so
how
do
kind
of
trigger
than
a
page
switch
as
well,
but
does
it
make
sense
to
use
like
page
view
over
custom,
or
do
we
say
no?
B
If
it's
all
calling
the
same
tracking
Jay
s
and
it's
all
being
loaded,
that's
something
that
telemetry
team
is
looking
into
inside
a
13-point,
oh
just
to
get
some
consistency
there,
especially
within
view,
for
instance,
having
things
loading
on
different
event.
Hooks
is,
is
difficult,
but
I
guess
to
answer
your
question
here
or
to
talk
about
your
next
steps
here
of.
Do
you
even
care
for
having
a
page
view
event,
or
can
you
just
use
a
custom
event?
Hey.
A
Yeah
I'm
totally
fine
with
using
the
custom
one.
For
me,
the
important
part
is
I
afterwards,
when
I
have
like
data
that
I
can't
wreck
in
periscope
and
when
I
have
a
table,
they
just
gives
them
a
number
to
say:
okay,
like
how
many
page
views
or
how
many
kind
of
people
call
and
looked
at
a
design
and
fullscreen.
Basically,
that's
what
I'm
trying
to
get
it
if
I
used
a
custom
event.
A
That's
for
me,
like
super
fine,
because
I
want
to
use
like
custom
events
and
more
things
like
where
say
like
who
clicked
on
kind
of
closing
comment,
resolving
a
comment.
These
kind
of
things
like
a
lot
of
things
that
how
people
interact
with
in
the
UI
that
it
cannot
get
out
of
the
rails,
back-end
data
or
usage
ping
right
now.
This
is
the
valuable
information
we
care
for
so
the
custom
events
seem
like
the
right
thing
and
we
can
try
to
create
a
nomenclature.
A
B
B
B
If
pageview,
it's
I
think
for
the
use
case
that
you
described
where
someone's
clicking
on
an
image
and
that
image
generates
a
new
URL
which
is
loaded
in
the
browser.
If
page
new
event
works,
fine,
then
I
think
page
view
would
track
that
right
because
you
just
be
able
to
to
basically
write
a
regex
when
you're
trying
to
build
a
funnel
or
you
just
have
regex
by
urls
right.
B
I,
if
you
want
to
track
clicks
like,
for
instance,
who
closes
a
modal,
that's
where
a
custom
event
or
maybe
a
click
event
might
make
more
sense,
yeah,
but
yeah.
We
I
think
you
pointed
out
that
we
need
to
standardize
it
so
I'll
link
over
to
that
issue,
and
maybe
you
can
follow
it
and
provide
some
of
your
feedback
as
well
as
we
start
to
standardize
it
because
I
think
what
you've
shown
today
is
a
really
good
sort
of
case,
or
example,
of
this.
A
A
Would
say
so
yeah
I
would
say
so
like
I
now
know,
okay,
I
learned
something
about
the
debugger
I
know
I'm,
not
crazy.
Okay,
it's
like
really
nice
kind
of
odd
nice
idea.
The
thing
is,
we
regard
the
events
or
so
that
kind
of
makes
sense
this
way.
But
if
you're
working
on
the
docks
and
everything
there's
a
I
think
that's
that's
super
awesome
and
please
feel
free
to
pull
me
in
on
anything
because
I'm
super
excited
about
more
tracking
capabilities
and
how
we
can
make
it
all
work
in
our
code
and
so
that.
B
A
B
Well,
what
gets
really
interesting
is
when,
when
we
can
leverage
snowplow
on
self-managed
instances,
I'm
not
sure
if
you
saw
that
diagram
in
in
the
slides,
but
we're
trying
to
put
a
snow
plow
collector
inside
a
self-managed
instance
so
front
end.
Events
get
sent
back
into
the
instance
gets
written
into
Postgres,
and
then
we
can
surface
it
via
usage
ping
right.
That's
our
big
challenge
for
q2
yeah.
A
Yeah
yeah
wonderful
is
like
also
in
wäôre,
so
that
users
could
just
say
similar
to
say
like
do.
You
want
to
opt
in
and
kind
of
helping
get
like
making
a
better
product,
and
they
say
yes,
and
in
this
case
snowplow
data
will
just
like
go
to
their
own
warehouse,
but
it
also
goes
like
to
the
kid
loved
one
as
well.
It.
A
B
The
the
only
issue
is
well,
the
one
would
be
just
dealing
with
with
firewalls
if
the
events
are
being
fired
from
the
backend,
because
we
have
snow
cloud
Ruby
on
the
backend.
It
still
needs
to
find
a
way
to
get
out
of
there.
Vpc
front
end
is
fine,
though
most
browsers,
you
should
be
able
to
unless
you're
on
some
sort
of
intranet
that
restricts
it,
and
then
the
other
one
is
just
sensitivity
of
what's
being
tracked.