►
From YouTube: PostHog Walk Through
A
A
So
post
hog
is
a
product
instrumentation,
open-source
product,
instrumentation
piece
of
software.
The
website
so
therefore
providing
analytics
into
the
what
the
users
of
your
application
are
doing
and
what
their
behavior
is
seems
pretty
cool.
It's
got
like
funnel
and
graphing
capabilities,
apparently
pretty
easy
to
integrate.
I'll
share
that
I'm
just
running
this
pipeline
to
revert
the
fact
that
I
previously
instrumented
this
applet
I'm
going
to
show
you
how
instrument
so
I
know
it
works.
I
know
it
was
pretty
simple,
but
I
wanted
to
get
a
recording
of
it.
A
So,
okay,
let's
start
with
post
doc,
I
will
already
create
an
account.
Well,
I'll
give
you
a
story:
I'm
gonna
start
with
post
I
like
that
app
I'm
gonna
instrument.
Is
this
one?
It's
a
toy
app
that
I
use
simple
ruby
on
rails
app
that
has
different
kind
of
crud
actions
on
the
subject
called
artisans
I
can
see
all
of
them.
I
can
add
comments
to
some
of
them.
I
can
remove
them
and
I
can.
A
Let
me
do
one
thing:
real,
quick,
there's
a
feature
flag
for
a
random
that
I
might
turn
on,
can
also
choose
a
random
one.
So
I
can
create
a
new
one.
I
will
instrument
this
with
JavaScript
and
then
we'll
see
how
easy
that
is,
and
then
perhaps
instrumented
we're
in
Ruby
with
there's
some
instructions
for
implementing
it
in
Ruby.
So
you
can
create
your
own
instrumentation
rather
than
just
the
generic
web-based
orientation
you
get.
So,
let's
get
started
post
hug.
The
wall
get
my
screen
over
here,
so
I'm
looking
a
little
bit
more
straightforward.
Okay,.
A
So,
as
you
can
see,
I
had
already
instrumented
this,
but
there's
no
instrumentation
in
place
at
the
moment
post
hog
gave
me
I
think
it.
This
was
not
here,
so
I'll
delete
this
panel,
I
added
it
myself.
So
when
I
get
started,
actually
you
know
what
I'm
just
gonna
start
a
new
account
I
noticed
in
post
hog
that
there
is
no
quick
way
to
log
out,
but
I
found
that
URL
worked.
So
let's
just
create
a
new
one.
This
way
we
get
a
full
view.
A
A
A
A
A
B
A
A
A
A
A
A
A
B
A
A
A
A
A
A
A
I'm
not
sure
what,
if
that
one
is
coming
from
this
is
the
Auto
DevOps
domain,
but
I've
been
navigating
through
here.
Oh
I,
wonder
if
this
is
the
production
performance
test,
yeah,
that's
interesting!
So
in
my
get
that
pipeline,
when
I
was
deploying
to
production,
it
has
this
performance
test
that
ran
and
hit
traffic
on
that
other
URL.
This
one,
let's
add
some
eight
requests,
essentially
I'm
wondering
where
that,
where
that
count
is
only
three
I
guess:
okay,
so
we
have
this
breakdown.
This
is
what
I
had
added
to
the
dashboard.
A
A
A
A
B
A
A
B
B
A
B
B
A
A
A
A
B
B
B
A
B
A
A
That's
possible
fresh
names.
Yes,
we
could
play
around
with
post
hog
to
get
a
sense
of
what
specifically
we
can
track,
but
maybe
I'll
stop
at
instrumentation
and
have
another
video
for
utilizing.
That
there
were
plenty
looks
like
there
were
plenty
of
tutorials
that
post
dogs
already
created
I'm.
Okay.
What
I
do
want
to
do
is.
A
A
A
B
A
A
A
B
B
A
A
A
A
A
A
A
A
A
B
B
B
B
A
B
B
B
A
I'm
gonna
pause,
my
according
figure,
this
out
I
think
up.
I
can
see
once
we
have
it
figured
out.
Okay,
I
think
I
got
it.
This
is
just
do
a
bunch
of
trial
and
error
on
my
part
that
I
mentioned
any
repeat,
developer
would
have
known
him
pretty
quickly.
Had
this
capture
event
here,
I
think
what
worked
for
me
was
just
adding
this
Ruby
file
that
defines
a
new.
A
A
Locally,
look
at
the
show,
one
specifically,
which
is
what
I
instrumented
here
you
can
see:
I
instrumented,
just
the
show
man
its
renders
correctly
and
tells
me
that
it
got
a
few
hundred
response
from
somebody,
the
post
hoc
so
way
that
worked.
I'm
gonna
pause
while
I
run
some
submit
this
commit
this
change
and
then
let's
the
pipeline
run
and
see
am
production.
A
Okay,
I'm
back
I
a
pipeline
successfully
ran
so
this
change
of
instrumenting
it
with
Ruby
got
added.
It
took
me
a
little
while
to
figure
out
how
I
then
accessed
those
events
in
post
talk,
but
I
found
them
out.
You
have
to
create
a
new
action,
so
I'm
gonna
go
to
actions.
The
section
is
going
to
be
for
artisan
display.
I
have
this
custom
events
that
I
am
adding
through
my
custom,
instrumentation
called
artisan
displayed.
I'll
show
you:
where
did
that,
so
that
was
to
find
here,
I
called
this
event.
A
Artisan
displayed,
so
I
can
add
that
actually
I'd
already
tell
me
that
there
are
18
events
from
viewing
this
since
I.
Add
the
instrumentation.
Ok!
So
then,
here
it
is
I've
got
all
these
person
I
just
added
this
distinct
idea
of
a
user
ID
in
this
app,
so
I
think
now
I
can
not
look
at
page
views,
but
instead
look
at
artisan
displayed.
So
there's
that
and
one
of
the
things
I
added
in
association
was
the
name
and
ID
as
artists,
and
that
was
split.
A
So
if
I
wanted
to
see
like
how
many
times
are
people
looking
at
specific
artisans,
I
should
be
able
to
then
break
this
down
by
was
a
name
cool.
That's
all
I
mean
of
all
the
people
are
looking
at
artisans.
Here's,
the
name
of
that
person
and
again
this
is
something
I
wouldn't
have
gotten
through
JavaScript,
because
this
instrumentation
is
not
just
get
getting
the
URL.
It's
also
getting
me.
I
can
add
custom
properties
from
my
application
code
to
further
slice
and
dice.
A
So
you
could
add
the
same
instrumentation
to
things
like
creating
new
and
CA.
Often
you
create
new
ones
like
this
poison.
You
could
also
do
from
JavaScript,
but
there
are
probably
some
places
where
you
could
look
at
which
random,
when,
when
random
artisan
is
added,
which
art
is
in
one
of
random,
artisan
is
shown
which
artisan
is
being
shown.
So
it's
an
example
of
how
we
and
by
instrumenting
it
with
the
so
kind
of
like
in
app
code,
you
can
get
more
depth
into
your
user
behavior,
so
cool
I
am
going
to
stopped.
A
A
So
in
monitor,
we
talk
specifically
about
gaining
insight
seamlessly
in
completing
the
loop
first,
and
that
is
really
that
in
today's
world
we
typically
think
about
DevOps,
as
stopping
at
the
in
this
monitor
section,
as
primarily
about
your
applications,
performance
and
availability.
So
how
are
we
making
sure
your
application
stays
performant
and
availability,
but
not
about
how
available,
but
not
about
how
you
get
feedback
from
your
live
application
to
support
what
you
should
build
next
into
it?
A
That's
really
about
user
behavior
and
product
in
products
telemetry
and
analytics,
and
so
I,
really
like
the
idea
of
some
integration
between
get
lab
and
post
hog.
One
of
the
things
that
I
was
adding
in
the
background,
while
waiting
for
these
pipelines
to
run
was
that
we
could
do
an
MVC
of
adding
post
hog
as
I
get
labs,
get
that
managed
app
and
so
when
I
follow.
Ups
is
also
contact.
The
post
hog
team
about
to
discuss
if
they'd
be
interested
in
contributing
to
them.
A
So
with
that
I'm
gonna
end
this
video
I
hope
this
was
informative.
I
know
it
took
a
little
while
of
pauses
in
order
to
wait
for
pipelines
to
run,
but
in
all
the
experience
of
instrumenting
post
hog
was
really
straightforward
for
the
JavaScript
and
I
think
in
the
Ruby
case
it
was
more
just
my
lack
of
knowledge
about
Ruby,
more
than
anything,
but
otherwise
super
straightforward,
I'm
using
post
hog
I
mean
we
gave
me
some
value
in
quickly
instrumenting
and
showing
information
about
my
user
behavior
Thanks.