►
From YouTube: Testing Snowplow Events in Gitlab GDK
Description
Testing Snowplow Events in Gitlab GDK
- Snowplow Micro
- Snowplow Analytics Debugger Chrome extension
- Frontend and backend events
The presentation (for Gitlab members): https://docs.google.com/presentation/d/1DuKijFAjJf3VZZuk9ZcWiauTOYySs7OVq0w2zn7V2Bc/edit#slide=id.g29a70c6c35_0_68
A
A
You
are
going
to
point
your
url
in
your
local
instance
to
that
snow,
plow,
meaning
environment.
When
it
comes,
and
then
you
can
also
test,
you
will
be
able
to
test
your
local
events
using
snow,
plow,
meaning
so
to
start
with
solo,
you
have
to
install
snow
plow
micro
on
your
local
test
to
be
able
to
test
bake
and
events
and
also
from
time
to
events
are
testable.
A
You
have
to
go
to
your
local
instance
admin
area
in
the
settings:
integration,
snow,
plow.
You
can
enable
snow
plow
tracking
by
pointing
your
collector
to
your
localhost
and
then
the
ugly
configuration
part
is
that
you
have
to
change
your
application
settings
to
be
able
to
use
part
9090.
You
have
to
update
the
application
settings
in
Postgres
database
console.
A
You
also
need
to
change
two
files
in
your
github
instance,
tracking,
J's
and
tracking
RB,
to
be
able
to
use
your
local
instance
with
an
insecure
non
SSL
URL
in
the
future.
I'm
sure
that
will
change
and
things
will
be
easier
and
finally,
in
this
presentation,
I
put
some
links
for
you
so
that
you
can
read
about
snowplow
micro.
Now,
let's
make
a
small
test
run.
A
First
of
all,
what
is
event
tracking
at
kidnap
context?
If
you
are
curious
or
product
usage
in
the
front-end
and
back-end,
for
example,
you
want
to
use
your
new
zoom
integration
feature
is
used
or
not
by
people
and
get
some
feedback.
You
can
do
it
by
using
the
snow
cloth,
front-end
and
back-end
JavaScript
and
Ruby
trackers.
A
A
You
need
some
special
configuration
for
your
igloo
JSON
for
kid
lab.
You
need
get
lab,
igloo
JSON
configuration
when
you
run
this
docker
instance.
You
can
access
on
your
localhost
snow,
plow
micro,
REST
API,
which
gives
you
a
possibility
to
see
the
good
and
bad
events
to
make
things
easier.
I
have
developed
a
local
repository
for
small
micro
in
the
config
section.
You
have
here
the
configuration
for
get
lab,
which
includes
the
get
lab
igloo
registry
and
official
snowplow
Analytics
registry.
A
A
Expand
the
snow
plow
section
and
you
should
enter
here
localhost
you
see
here
1990.
This
is
impossible
to
put
here
in
the
user
interface
but
I'm
going
to
show
how
you're
going
to
do
this
in
the
database
console
initially
just
put
your
localhost
and
get
lab
and
save
changes
and
enable
smart
or
tracking
check
this
checkbox
after
you
do
that
you
come
to
your
Postgres
database
console
and
iran.
You
update
the
application
settings
and
set
smoke,
electrons
name
to
localhost
9090.
Why
do
we
do
this?
A
Because,
currently
in
the
github
application
settings,
we
are
unable
to
set
port
9090?
That's
the
first
step.
Second
step.
We
have
to
go
and
change
two
files
in
our
github
instance.
One
is
the
app
assets,
JavaScript
tracking
j/s.
Here
we
should
disable
the
force
secure
tracker
by
just
commenting
out
because
we
don't
have
HTTPS
on
our
local
small
micro.
A
Similarly,
for
backends
Ruby,
we
have
to
go
to
the
lip
get
lab
tracking,
that
RB
file
and
in
this
file
we
have
to
add
their
protocol
HTTP
and
port
1990,
which
is
our
local
small,
clone
instance.
In
addition,
we
have
to
come
here
and
in
our
local
local
snowplow
options.
We
have
to
put
here
protocol
HTTP,
you
can
see
the
changes
here
again
here
and
I
also
put
a
link
in
the
presentation
to
the
snow,
applaud.
A
A
One
thing
worth
mentioning
here
is
the
snowblower
Chrome
extension.
If
you
search
for
it,
you
will
see
there
are
two
options:
choose
the
snow,
plow
analytics
debugger
install
this
Chrome
extension
to
your
chrome,
dev
tools
and
when
you
do
that,
you'll
see
personal
analytics
debugger
in
your
Chrome
extensions.
A
And
when
you
open
the
dev
tools,
you'll
see
the
snow
analytics
debugger
section
in
the
dev
tools,
so
I
see
them
two
events.
Let
me
clear
this:
whenever
you
click
on
something
and
if
there's
an
event
in
the
front
end,
you
will
see
that
an
event
is
locked
in
the
snow
polo
analytics
debugger
and
when
you
click
on
the
event,
you'll
see
some
details.
How
this
snowplow
event
is
structured.
A
A
So
when
I
refresh
micro,
all
I
see
that
we
got
total
11
events
and
I
come
here
and
reset
all
the
events
come
back
and
see
you
again:
I
have
0
events,
let's
go
back,
click
star
to
say:
yeah,
refresh
I
got
one
good
event.
Let
me
go
to
micro,
good
URL,
when
I
do
that,
I
will
see
the
same
event.
I'm,
seeing
in
chrome,
dev
tools
in
the
small
analytics,
debugger
I
see
it
on
my
snowplow
micro
REST
API,
which
is
here
here.
You'll,
see
a
field
called
CX
context,
which
is
important.
A
A
A
A
Reset
the
events
I
have
nothing
now
so
in
the
backend.
I
can
use
a
rupee,
a
PID
club,
tracking,
Sanders,
half
describing
event
using
the
page
view
context,
igloo,
schema
and
I
will
put
here
a
page
type
good
type,
with
a
context
need,
let's
see
when
I
do
that.
I
should
have
send
an
event.
Let's
come
back
here.
A
A
Let's
do
another
example
and
let's
send
a
bad
event,
so
now
I
will
see
all
my
events
in
my
snowplow
micro
I
have
one
good
event
and
I'm
gonna
send
a
bad
event
by
putting
here,
let's
say
by
mistyping
the
page
view,
context
and
typing
here
page
view
bad
send
it.
It
goes
to
my
snowplow
micro
refresh
here.
I
have
a
bad
event.
Now
I
can
see
it
here.
That
is
here.