►
From YouTube: 2022-10-18 Product Analytics Sync
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
hello,
everybody
Welcome
to
the
October
18th
edition
of
the
product
analytics
sync,
a
couple
of
read-only
topic:
not
a
couple
there's
only
one
read-only
topic
there
for
family
and
friends
day.
So
please
be
please
check
that
out.
A
But,
more
importantly,
we
have
a
new
face,
a
familiar
face,
but
a
new
face
to
the
product
analytics
team
Jan.
Welcome
to
officially
it's
your
first
day
as
a
product
analytics
engineer.
Is
there
anything
you
would
like
to
say
as
far
as
intros
are
concerned,.
B
Thanks
for
the
welcome
just
want
to
say,
super
excited
to
be
here:
yeah,
it's
a
lot
of
us
already
know
each
other,
but
really
had
a
coffee
chat
with
Axel
and
I'll
set
one
up
also
with
Lorena
and
yeah.
It's
it's
good
to
be
back
in
the
team.
I
guess.
A
Well,
welcome
welcome
back,
however,
we
want
to
characterize
it,
but
it's
good
to
see
you
and
it's
good
to
have
you
on
the
team.
I
would
say
that
rounds
out
the
front
engineering
side,
as
I
mentioned
before.
We
are
definitely
looking
for
two
more
back-end
Engineers
Max
has
already
put
fourth
a
referral,
so
it
would
be
I'm
excited
about
that
as
well,
but
yeah
welcome
you
on
to
the
team.
A
As
far
as
additional
topics,
I
wanted
to
kind
of
bring
something
that
we
were
doing
in
the
compliance
group
over
here,
which
was
reviewing
the
billboard
I
think,
as
we
are
kind
of
moving
away
from
just
a
huge
list
of
epics
and
issues
and
we've
got
this
board
set
up
to
track
and
organize
Things
based
on
our
workflow
labels
and
Milestones
it'd,
be
good
for
us
to
kind
of
get
into
the
habit
of
reviewing
that
to
make
sure
that
the
things
we're
working
on
are
actually
being
tracked.
A
So
I
can
go
ahead
and
share
my
screen,
and
then
we
can
kind
of
just
go
through
and
see.
If
there's
any
any
updates,
we
want
to
share
about
that.
I
did
just
update
my
resolution,
so
it's
not
going
to
be
super
microscopic.
A
If
it
is
please,
let
me
know,
I'm
happy
to
share
the
screen
directly.
All
right,
so
we've
got
create
any
necessary
sorry
create
any
necessary,
reusable
UI
components
and
services
ready
for
production
for
production,
ready
dashboards,
wait.
This
is
this,
is
blocked
and
not
assigned
to
anyone
until
we
get
actually.
C
Interesting
I
always
assumed
that
that
was
sort
of
the
issue
to
do
with
creating
the
actual
widgets
themselves,
which
is
technically
blocked
until
my
Mr
gets
merged,
had
merge,
set
that
I'm
getting
pipeline
failures
which
are
unrelated
Joys,
so
not
entirely
sure.
What's
going
on
with
that
one,
okay,
I'd
say
we
could
probably
start
working
it
well,
we
could
definitely
start
working
it
by
the
end
of
the
day.
A
Right
this
is
the
one
I
created
I
think
when
I
was
just
trying
to
map
out
all
the
different
dashboard
kind
of
you
know
to
work.
I
know
you
have
a
whole
line
of
different
issues
for
actually
building
the
widgets
out,
so
this
might
be
redundant
at
this
point,
but.
C
A
Pardon
window
switches
yeah
because
this
was
when
I
was
just
kind
of
building
out
like
the
dashboard
views
and
using
schemas,
and
things
like
that.
So
at
this
point
I
one
thing
maybe
perhaps
is
you
could
take
a
look
and
see
if
these
are
even
relevant
anymore
or
if
this
already
has
been
separated
out
further.
C
A
D
I
I
have
a
comment
really
like
that:
hello,
guys,
sorry
for
the
boys,
it's
okay,
yeah
I
have
a
I.
I
did
so
this
issue
when,
when
the
initial,
the
link
to
the
board
and
one
of
the
things
I
did
with
the
with
the
review
I
did
on
the
on
rubber
simmer,
was
to
actually
go
ahead
and
create
the
the
chart
and
like
to
see
how
how
how
did
it
feel
to
to
to
use
what
he
implemented
and
I
was
under
the
impression
that
this
issue
could
cover
like
the
first,
the
first
actual
actual.
D
They
first
had
to
charge
that
that
we
could
create.
That's
that's
what
I
thought.
So,
maybe
maybe
we
can
push
that
that
issue
that
way,
but
anyway,
I
can
I
can
still
talk
it
out
with
Rover
afterwards,
but.
A
Cool,
well,
it's
a
sign
about
the
esa.
We
can
figure
out
if
there's
anything,
to
push
for
for
this
side
or
if
it's
been
superseded
by
the
other
issues
as
well,
because
they've
definitely
there's
a
bit
of
a
gap
between
when
they've
been
created
and
how
long
they've
been
updated,
so
cool
yeah.
Thank.
D
A
Yeah
one
thing
I
also
moved
into
this
in
terms
of
our
expected
timing.
Of
course,
this
is
dependent
on
our
conversations
with
infrastructure
and
security,
as
we
integrate
gate
lab.com
with
the
analytics
cluster
to
be
able
to
instrument
staging
and
or
have
the
stacks
service
working
on
staging
and
production
so
that
we
can
instrument
the
internal
handbook.
A
That
was
a
mouthful
I
moved
this
into
the
Milestone,
and
this
one's
already
been
assigned
to
Sam,
so,
basically
just
to
make
sure
that
we
can
track
the
internal
announcement
about
what
we
plan
to
do
for
dog
fooding
and
how
we
plan
to
instrument
the
internal
handbook
to
start
and
then
move
on
from
there
and
kind
of
as
we.
A
This
is
our
first
step
in
terms
of
our
communication
plan
to
just
come,
make
our
way
out
out
externally
in
terms
of
our
plans
for
product
analytics,
so
Sam
I,
don't
think,
there's
anything
to
speak
to
at
this
point
beyond
what
I
just
mentioned,
but.
E
No,
the
the
announcement
is
drafted
and
ready
to
go
if
you'd
like
to
look
at
it,
make
any
edits
or
comments.
It's
linked
in
the
issue,
pretty
much
we're
just
waiting
until
we
have
line
of
sight
when
we
will
push
it
because
the
announcement
says
end
of
October
right
now.
We
can
change
that
if
we
need
to
push
it
and
otherwise
I'm
just
waiting
for
the
yeah.
Let's,
let's
go
ahead
and
publish
it,
so
we
can
give
people
a
week's
worth
of
heads
up
and,
and
then
we'll
make
it.
A
I
was
trying
to
link
it
to
the
infrastructure
issue,
but
I
don't
have
it
handy
I'll,
do
it
later,
okay,
cool
and
then
our
resident
designer
Rob
instrumentation
screen.
Anything
you'd
like
to
mention
here.
C
I
am
terrible
at
design,
it's
going,
things
are
happening,
I
am
making
okay
progress
and
I
am
going
to
contact
a
few
people
from
ux
once
I've
got
a
decent
chunk
to
get
their
suggestions
and
how
I
can
make
things
better
without
necessarily
handing
it
over
to
them,
because,
obviously,
it's
not
their
job
but
I'll,
see
if
I
can
solicit
some
feedback
from
some
people.
Hopefully,
I'll
have
something
that
I'd
be
willing
to
share
in
the
next
day
or
so.
A
A
Anything
we
can
help
you
with
and
prior
to
that,
a.
A
Sure
you
know
we've
got
that
O'reilly
subscription,
so
you
know
then
maybe
we
can
use
that
in.
E
Terms
of
design
resources,
I
am
trying
to
push
to
get
us
an
actual
designer
for
the
group,
we're
likely
to
be
able
to
get
a
head
an
actual
head
count
for
that,
probably
towards
the
beginning
of
next
year,
until
that,
what
we'll
likely
be
able
to
do
is
identify
a
designer
to
help
us
on
Project
based
topics
like
here's,
a
specific
issue,
we
need
design
help
with
do
that,
and
only
that,
so
that
that's
something
I'm
working
on
in
the
background
to
hopefully
have
for
you
all
soon
so
Rob
you
don't
have
to
get
that
design
degree.
C
I
don't
mind
doing
it
and
I'm
sure
Beyond
an
axel
wouldn't
mind
doing
a
bit
of
design
if
they
were
forced
into
it.
C
It's
just
expressed
at
this
point
where
we're
still
at
the
pre,
giving
it
out
to
user
stage,
but
as
soon
as
we
start
actually
selling
this
as
a
viable
product
for
them
to
start
using.
That's
when
I
really
want
someone
with
far
more
ux
experience
to
come
in
and
tell
me
everything.
I've
done
wrong.
A
Yeah
that
that
will
come
in
due
time
and
I
think
it
will
line
up
in
terms
of
as
we
kind
of
get
more
out
to
the
beyond
the
customer
preview
and
how
the
actual
packages
up
to
customers.
In
terms
of
our
like
hiring
plans
for
the
for
the
next
fiscal
year.
We
should
be
able
to
have
some
stable
counterparts
there
to
really
help
us
get
to
that
point.
A
But
until
then
it
seems
like
we
can
get
some
at
least
partial
capacity
to
to
make
sure
you're
not
just
completely
on
your
own
with
this.
But
we
appreciate
your
efforts,
regardless
cool
I
think
this
I'm
sorry
go
again
just.
B
Wanted
to
say
that's
rope,
please
feel
free
to
include
me
of
that
happy
to
help
out.
Also
not
yeah
I,
don't
mind
doing
it
temporarily,
as
long
as
it
does
become
my
full-time
position
but
happy
to
help
out
with
the
design
version.
A
Awesome
so
we've
got
two
resident
designers
for
now,
then
very
cool
I,
think
of
track
usage
with
new
tracker
internal
handbook.
I.
Think
we're
all
aware.
This
is
just
con
dependent
on
the
sorry
infrastructure
production
change,
request.
A
A
Very
cool
I
just
recently
added
this,
because
it's
the
thing
I've
been
doing,
but
it
didn't
have
really
an
issue
with
it,
which,
which
is
the
stack
integration
with
staging
and
production.
This
is
effectively
the
support
issue
for
the
infrastructure
change
issue,
which
is
actually
where
I
have
the
link
for
the
infrastructure
one.
So
I
can
use
that
to
save
that
later,
but
yeah,
as
you
might
have
seen
from
last
week.
We
have
the
production
change
issue
here
and
gotten.
A
Some
feedback
from
I
got
some
questions
from
from
infrastructure,
so
I'm
hoping
to
push
that
topic
as
well,
and
so
hopefully
we
can
get
some
movement
there.
A
C
For
me,
the
widget
Mr,
as
I
said
Tim's
approved
it's
set
to
merge
having
a
few
difficulties
with
pipeline
unrelated
pipeline
issues,
which
I
need
to
look
into
after
this.
So
next
stages,
for
this
is
actually
building
a
widget,
a
proper,
proper
Cube
widget,
which
I
don't
know.
If
it's
going
to
be
me
or
you
or
Axel
or
John
I,
don't
know,
but
somebody
needs
to
build
a
widget.
A
D
Believe
that
that's
the
the
ticket
we
were
talking
before
the
first
one,
we
might
use
that
one
too,
and
one
thing
one
thing
we
need
to
do
is
to
sit
down
with
the
end
and
on
talking
through
life.
All
of
the
the
vision
process
we
made
through
with
the
with
this
Mr
I
was
I
was
I
was
trying
to
do
that
on
our
one-on-one,
but
we
ended
up.
A
Might
also
be
something
worth
recording
too,
as
we
Loop
in
optimize
Engineers
as
well
to
kind
of
lay
out
the
overall
plan
for
for
dashboarding
and
widgets.
That's.
A
Cool
we've
also
got
the
admin
settings
section.
Also
in
Dev
Axel
is
there
anything
you'd
want
to
call.
D
A
D
Yeah,
the
for
the
administration,
the
UI
is
ready.
This
is
still
not
not
actually
hooked
to
the
to
the
back,
and
one
thing
that
I
want
to
do
today
is
to
go
ahead
and
merge
max
Mr
into
my
into
my
branch
and
and
to
actually
hook
it
up,
I.E
and
I'm,
expecting
a
quick
turnaround
time
after
that
us
one
one
good
thing
of
working
on.
D
That
is
that
we
have
like
a
lot
of
examples
and
I
mean
I'm,
not
adding
anything
new
I'm,
just
following
the
conventions
of
the
settings
so
yeah
whenever
that's
whenever
I
I,
that's
actually
working,
then
I
can
move
it
to
review,
hopefully
to.
B
F
Yeah,
so
this
one
should
have
been
simple:
it's
already
been
approved
by
maintainer,
but
I've
been
stuck
in
merge
conflict
hell
for
some
reason,
so
I'm
hoping
that's
going
to
be
resolved,
but
once
it
has
been
resolved
we
can
get
it
merged
straight
away
because
it's
already
got
all
the
required
approvals.
That's
just
the
one
remaining
like
the
main
on
off
switch,
essentially
in
the
admin
panel
that
enables
or
disables
all
of
the
work
we've
been
doing,
got
it
and
the
one
underneath
that
is
just
pushed
my
first
10
Fitness
now.
F
So
that's
just
all
the
work
in
the
back
end.
That's
been
done
so
far
behind
a
license
feature
for
ultimate
to
make
sure
that
that
doesn't
end
up
in
the
free
version
by
accident,
so
yeah
that
should
be
merged
by
the
end
of
this
week,
comfortably.
A
C
Out
here
yeah:
firstly,
the
widgetsmr
just
merged
yeah.
C
C
But
in
doing
so
there's
we've
got
to
wait
for
the
CSS
to
load
which
can
cause
a
bit
of
a
junky
experience,
so
we
should
really
add
some
kind
of
loading
skeleton
loader
type
state
to
the
dashboard.
So
that's
the
follow-up
that
I
need
to
look
at
doing
as
a
nice
to
have
it's
not
a
priority.
I've
got
higher
priority
things
to
do
so
with
yarn
or
axle
you
feel
like
taking
that
on
feel
feel
free
to
take
that
off
me.
A
Very
good
we've
got
a
couple
of
items
as
well:
close
investing
in
scope
of
management
layer
for
the
analytics
stack,
Cube
proxy
doesn't
work
with
cube.js
library,
a
lot
of
investigation
that
we
were
able
to
close
out
so
a
lot
of
good
work.
A
There
I
think
that
would
cover
it
for
the
boardwalk
that
was
great
and
we'll
kind
of
scope
it
in
a
little
bit
more
I
guess
well
everything's
top
priority
right
now,
so
I
guess
it
doesn't
really
make
sure
it
makes
sense
to
separate
it
out
any
further
cool.
What
else
do
we
have
on
the
agenda
demo?
We
could
definitely
do
that,
but
I
want
to
I'm
not
trying
to
avoid
it
honestly,
but
there
is
total.
A
There
is
12
minutes
left
on
the
in
the
meeting,
so
I
want
to
make
sure
we
can
get
to
the
other
topics.
So
I
guess
I
can
just
speak
to
one
thing:
I
wanted
to
call
out
oops.
Sorry,
okay,
just
thought,
I
heard
someone
yeah,
Sam
and
I
are
looking
to
introduce
some
of
our
typical
ceremonies
again
with
Milestone
planning
having
an
actual
issue,
start
to
getting
bringing
a
little
bit
more
structure
into
our
planning
process.
Other
than
take
a
look
at
this
epic
and
see
what
issues
are
available.
A
E
Yeah
so
as
part
of
the
discussion
on
what
we
want
to
do
with
the
left
sidebar
the
conversations
broadening
to
include
other
groups,
which
is
great
so
that
we
have
a
correct
solution
for
git
lab
as
a
whole.
Not
just
for
our
group,
something
I
I
thought
would
be
helpful
to
frame
that
discussion
is
if
we
could
give
other
teams
a
sense
of
how
many
things
we
want
to
add
to
left.
E
Sidebar
there's
going
to
be
a
big
difference
between
if
we
want
to
add
two
new
options
versus
20
new
options
right
now,
I
believe
we
are
trying
to
add
around
five
screens
and
I
just
wanted
to
talk
with
you
all.
If
does
that
seem
like
the
right
amount
of
screens
that
we
would
want
to
be
doing
for
the
first
set
of
releases
for
product
analytics,
or
would
it
be
more
than
that
or
less
than
that.
A
E
Yeah
yeah
and
when
we
get
to
the
point
where
we
need
to
add
even
more
like
I
I
Envision,
the
experimentation
workflows
needing
a
whole
lot
of
different
screens
added
I.
Think
we'll
have
another
left
sidebar
discussion
as
our
group
grows,
but
starting
at
five
will
help
that
initial
discussion
move
forward.
If
we
just
bundle
everything
under
the
existing
analytics
left
sidebar
option
split
it
out,
do
or
do
something
completely
different.
E
A
That's
that's
actually
how
I
would
prefer
to
do
it,
because
then
I
can
actually
speak
to
more
in
depth
of
how
Helm's
going
to
work
and
why
it's
advantageous
in
terms
of
like
updating
and
we're
like
yeah,
changing
installation
and
the
whole
point
of
it.
I
can
start
it
if
we
have
time
but
anyways
I'll,
just
let's
get
to
the
rest
of
these
electronics
and
see
where
we
land
first
tangentially
related
to
to
your
topic.
A
Sam
about
the
the
left
side
bar
we're
using
a
product
analytics
controller
currently,
which
belongs
to
some
work
done
when
product
analytics
was
an
idea
from
the
monitor
stage.
That
code
is
I.
Think
at
this
point
over
two
years
old
that
feature
flag
has
never
been
turned
on
for
more
than
two
private
groups,
so
I
think
it's
safe
to
say
that
we
can
probably
remove
it
entirely
Max
to
answer
your
point
about
cleaning
it
up.
A
It
was
kind
of
news
to
Sam
and
I,
at
least
as
recent
as
I
think
last
month,
when
we
kind
of
discovered
that
this
was
something
that
we
had
attempted
in
a
different
stage,
but
I
think
we
could
just
perhaps
reach
out
to
the
managers
at
monitor
and
see,
if
they're,
okay
with
that.
But
it
seems
like
this
is
something
that
it's
not
being
looked
at
anymore.
A
It's
causing
issues
on
our
end
because
there's
our
there's
existing
feature,
flag
checks
that
are
we're
having
to
dance
around
and
so
I
think
it's
just
good
maintenance
and
hygiene
to
clean
this
stuff
out.
If
it's
not
been
used
for
for
quite
a
long
time,
yeah.
C
It's
not
been
touched
in
two
years
yeah.
We
have
an
issue
for
this
I
can't
remember
where
it
is,
but
we
do
have
an
issue
to
tidy
this
up.
Axel.
F
I
can
take
that
on.
If
you
want.
F
Yes,
I
do
so
sorry
I'm
on
one
screen,
first
of
all,
yeah
at
the
moment,
because
I'm,
the
only
back-end
engineer,
Rob
and
axel,
or
one
or
other
comfortable
taking
initial
reviews.
Obviously
I
can
use
roulette
just
to
pick
a
random
back-end
engineer,
but
considering
domain
knowledge
is
pretty
constrained
within
this
group
of
people
at
the
moment,
while
we're
still
figuring
out
our
Direction,
it
makes
sense
to
keep
it
internal
for
now
and
I
see
Brothers,
gracefully
volunteered.
Is
that
all
right
with
you,
then.
C
F
You
can
be
my
default
initial
reviewer
for
now.
Just
let
me
know
if
you
find
yourself
overwhelmed
and
we
can
find
someone
else.
C
I'm
maxing
myself
out
at
two
reviewers
for
roulette,
so
ignore
that
and
just
go
for
me.
It's
just
so
I've
got
enough
room
for
this
team
cool.
F
F
Our
rest
API
proxy
works
well
and
works
with
existing
products
on
the
market.
I've
had
a
go
with
some
of
the
low
code
tools
and
it
just
kind
of
functions
as
you
would
expect.
The
SQL
API
from
Cube
will
be
considerably
more
complicated
to
expose
from
within
gitlab,
but
have
a
look
in
the
Epic
async
if
you're
interested,
and
we
can
decide
what
to
do
with
that.
Outside
of
this
meeting.
I
think.
A
Cool
then,
it's
demo
time,
if
you
have
to
jump
for
any
reason,
feel
free
to
I'm
just
going
to
record
into
this
and
then
cut
this
out.
It's
just
as
part
of
the
demo,
so
I
can
also
just
see
how
far
it
goes
before
it
fails.
That's
all
I've
done
was
do
or
have
been
for
me
lately,
so
yeah,
let's
check
it
out.
The
point
of
this
is
just
to
kind
of
demonstrate
the
interaction
between
gitlab
as
the
product
and
how
we
would
establish
the
connection
to
an
analytics
stack
service.
A
A
In
terms
of,
however,
they
want
to
collect
analytics
data
and
so
I'll
be
kind
of
going,
giving
a
very,
very
brief
overview
of
how
it's
being
currently
packaged
as
a
Helm
chart
and
then
kind
of
just
showing
what
the
work
that
everyone's
been
working
on
in
terms
of
actually
getting
the
cluster
set
up.
The
clickhouse
database
created
and
things
like
that,
so
without
further
Ado
I
will
share
my
screen.
We
will
see
how
far
I
get
the
stack
is
online.
A
So
that's
a
good
start,
so
we'll
go
from
there
so
to
kind
of
give
a
quick
overview
in
terms
of
how
this
stuff
works.
Sorry
I
have
a
bunch
of
Windows
everywhere.
The
idea
for
the
stack
is
that
basically
there's
a
package
you
can
download
and
and
install
on
your
own
infrastructure.
Hopefully
you
know
we're
testing
this
on
Google
Cloud,
but
hopefully
this
can
extend
to
AWS
as
well
as
Azure.
A
But
if
you
look
at
it,
oh
sorry,
my
zoom
window
is
blocking
it.
As
you
can
see,
it's
it's
still
typically
using
what
you
would
expect
from
a
kubernetes
setup
in
terms
of
setting
up
the
services
and
everything
else.
You
would
need,
as
far
as
the
kubernetes
cluster
goes.
The
only
difference
is
that
eventually
it
packages
up
to
the
point
where
you
can
gzip
or
archive
this
entire
folder
I,
don't
know
what
just
happened
there
and
then
run
a
simple
command.
A
Basically
say:
Helm
install
you
can
name
the
cluster
whatever
you
want
and
then
effectively
it
will
install
it
on
whatever
cluster
you
have
set
up
with
whatever
cloud
provider
you
have.
So
this
is
a
one
way
for
us
to
deploy
it
for
ourselves,
but
also
for
others
to
run
their
own
stack,
and
so
I've
already
got
this
set
up,
because
when
you
install
it
it
takes
time
you
have
to
set
up
Ingress
and
things
like
that.
A
Ingress
is
a
way
for
basically
to
set
up
an
actual
public
entry
way
to
to
access
these
services.
So,
as
I
mentioned
before
the
configurator,
at
least
when
I
tested
it
was
working,
this
is
also
available
on
https
I'm,
not
sure
why
it's
defaulting
to
it.
Otherwise,
but
we'll
just
go
through
the
setup
process
and
just
go
as
far
as
you
can
and
to
end.
A
And
these
credentials
will
change
once
we
actually
get
it
to
the
point
where
we
need
to
integrate
it
with
production,
so
we
already
set
up
Jitsu.
So
this
is
again
what's
going
to
be
collecting
all
the
data
and
submitting
everything
over
to
click
house.
We
won't
set
up
the
destination
right
now
because
we
don't
need
to
at
this
point
in
time,
but
one
thing
I
am
planning
to
do
is
set
up
different
projects
for
different
environments,
so
we'll
have
one
for
staging
one
for
production
once
we
actually
get
this
set
up
with
infrastructure.
C
A
Now,
just
purely
out
of
management,
it's
it's
simpler
and
quicker
right
now
to
have
the
tier
since
we're
not
really
doing
anything,
we're
staging
right
now
in
an
ideal,
State
I
would
say.
Yes,
we
should
have
completely
separate
environments
for
staging
and
production.
That
would
be
the
general
best
practice
there.
A
E
A
Theoretically,
it
should
work
for
any
Cloud
platform
that
the
kind
of
finessing
you
have
to
do
is
making
sure
that
and
and
I
think,
there's
other
tools
that
can
help
with
this,
like
customize,
where
you
can
basically
say
if
I
want
to
install
it
on
a
specific
platform,
there
are
certain
nuances
between
them
in
terms
of
how
you
classify,
for
example,
like
volume
storage
for
your
cluster,
so
you
have
to
point
to
different
types
of
different
IDs
or
different
types
of
storage
classes.
A
So
that's
something
that
once
we
actually
get
to
that
point
where
okay,
we
want
to
offer
this
to
allow
customers
to
set
it
up
on
whatever
they
want
and
Beyond
just
Google
Cloud.
There
will
be
some
testing
that
we'll
have
to
do
which
we
actually
have
environments
for
at
least
for
AWS,
in
addition
to
Google
Cloud,
where
we
can
test
out
to
make
sure
that
it
is
able
to
adapt
and
change
the
configuration
values
based
on
which
platform
you're
going
to
install
it
on
got
it
thanks.
A
Cool
and
I
kind
of
did
Breeze
over
it
too,
but
well.
Actually,
I
just
lost
my
train
of
thought
there,
but
anyways
I'm
gonna
go
ahead
and
connect
it.
A
So
I've
got
a
copy
and
paste
here,
but
basically
I'm
just
going
to
go
in
sorry,
I'm,
jumping
on
the
right
side
and
I'm
just
going
to
change
the
project
key
for
jitsu
and
see
how
far
we
can
get
here
and
then
make
sure
everything
else
is
looking
all
right.
We
have
our
Gypsy
host.
A
We
can
actually
use
https
now
Zoom
Windows,
getting
in
the
way
again
our
clickhouse
conduction
string
again
the
credentials
will
change,
there's
no
issues
there,
plus
you
can't
access
it
outside
of
the
cluster
Network
and
the
Jitsu
credentials
as
well.
So
that's
looking
good,
so
we
will
go
ahead,
update
the
application
settings
and
do
a
Reload,
and
at
this
point
we
can
select
a
project
I'm
going
to
use
a
new
one.
A
A
You
know
it
only
took
four
attempts
of
like
trying
to
demo
this
for
it
to
work
for
me
cool.
So
now
we
have
the
jitsuki.
This
is
what
we
are
going
to
present
to
the
users
and
say:
hey:
you
want
to
start
collecting
data
on
your
application,
congrats.
Let's
do
it
and
the
way
you
would
do
that
is.
You
would
go
to
your
that's,
not
the
right
window.
I'm,
sorry
I'm,
jumping
around
because
I'm
lost
right
now,
so
we
would
go
here
right
now,
I'm
just
going
to
the
GDK,
of
course.
A
For
us
it
would
be
the
internal
handbook,
but
let
me
just
click
this
one.
So
it's
easier
to
see
I'm
just
going
ahead
and
including
the
scripts,
the
sorry
JavaScript
SDK,
as
well
as
a
tag
to
instrument
initialize
it
and
then
use
the
key
as
well
to
start
tracking
data.
So
if
I
go
to
my
GDK.
A
Obviously
this
is
a
little
weird
because
we're
tying
it
to
a
specific
project,
but
now
we're
Gathering
data
on
the
entirety
of
the
ddk,
but
we'll
just
go
to
the
issues
list
go
through
one
more
page
and
then
we'll
just
verify
that
the
events
are
getting
picked
up
from
oops
I.
Don't
know
how
to
fix
that.
The
front
end
where
it's
like
emitting
the
port
number
on
that,
so
the
links
fail
I'm
getting
a
course
policy
thing,
even
though
I've
turned
it
off.
So
that's
cool
I'm,
not
sure,
what's
happening
there.
A
So
if
I
go
back
to
Jitsu,
it's
probably
not
picking
up
the
events
now
or
no
yep.
So
why
am
I
having
a
course
issue?
Well,
I'll
probably
just
have
to
record
the
demo
there.
But
basically,
what's
supposed
to
happen
is
that
you'll
start
seeing
the
events
go
through
here
and
then
we
can
verify
it
on
the
clickhouse
server
Itself
by
just
querying
the
database
directly,
but
that's
as
far
as
we're
going
to
get
with
the
demo.
A
So
far,
but
yeah
I
had
already
turned
off
content
security
policy,
but
I'll
have
to
figure
it
out
later.
That's.
C
A
Yeah,
that's
interesting,
I'm,
not
sure
why
that's
the
case
that
would
be
new
to
me,
so
I'll
have
to
dig
into
Jitsu
server
and
why
that's?
Why
that's
changed,
but
at
any
rate,
I'll
take
a
look
at
that
and
then
I'll
record
Another
demo
just
to
see
if
we
can
get
to
the
end,
but
any
thoughts
so
far.
A
Just
the
at
this
point,
it
just
needs
to
be
able
to
receive
the
events,
but
yeah
it'll
show
up
here.
What
I
was
going
to
do
is
flip
back
to
the
clickhouse
server.
You
could
log
in
and
then
verify
the
events
are
actually
there
as
well.
But
that's
that's.
For
a
later
time.
A
A
C
A
Probably
it
okay,
then
that's
why
the
database
didn't
show
up
cool
well,
I'll
figure
out
the
course
issue
and
see
what
happened
there,
but
I
I
pinned
the
ish,
the
the
version
numbers
so
I
know.
That's
not
not
a
thing
anymore,
but
I'll
dig
into
it.
Well,.
A
A
No
they're
cool-
we
got
pretty
far
there,
so
yeah
nice.
Well,
thanks
for
watching
thanks
for
everyone
for
joining
this
meeting
good
agenda
and
everything
like
that.
So
if
there's
anything
else,
see
you
on
the
slack
channels,
otherwise
see
you
in
the
next
call.