►
From YouTube: 2023-03-21 Product Analytics Group 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
Hello,
everyone
and
welcome
to
the
March
21st
product
analytics.
Sync:
let's
go
ahead
and
get
started
with
the
Board
review.
A
A
This
is
something
we've
been
starting
to
work
on,
but
kind
of
need
to
flesh
out
further
I
think
I
kind
of
said
the
same
thing
last
week,
but
Max
anything.
You
want
to
add
to
this.
No.
B
Not
really
at
the
moment,
okay
yeah,
we've
discussed
a
brief,
there's,
not
a
lot
a
lot
to
do
at
the
moment.
Yeah.
A
I
think
the
overall
end
goal
right
now
is
to
figure
out
where
to
collect
all
the
logs,
because
we
would
ideally
want
to
use
something
like
classic
search
Commander
which
we're
using
currently
at
gitlab,
but
right
now,
I
think
we
can
prove
that
out,
perhaps
with
like
clickhouse
and
Q,
perhaps,
but
we'll
probably
want
to
incorporate
the
same
strategy
for
snowplow
and
Kafka.
A
Because,
ideally,
this
can
feed
into
how
we
can
do
counting
of
events,
and
things
like
that.
So
this
could
feed
into
our
overall
like
building
strategy
and
things
like
that.
Yeah
cool
we've
got
the
previous
muscle
planning
issue,
which
I
think
we
probably
just
closed
out
soon,
not
already,
and
then
got
a
couple
open
but
assigned
issues
here,
first
thing
being
designer
outputs,
incorrect,
visualization
definition:
Rob
is
there
anything
you
don't
want
to
call
out
here,
just
need
to
work
for
label.
C
D
A
A
Problem
and
assume
the
same
for
the
design,
audit
or
yeah
yeah,
okay,
cool
we've
got
a
follow-up
from
save
custom
dashboards
to
other
repos
and
dashboard
designer.
So
this
is
a
follow-up.
Let
me
see.
C
This
is
related
to
something
I
raised
where
right,
if
you
are
in
the
UI
and
you
create
a
yaml
definition
that
for
a
dashboard,
it
gets
analyzed
against
a
different
schema.
A
Yeah,
it's
a
back-end
issue
that
requires
problem
validation,
so
see
if
we
can
get
take
a
look
at
that.
We've
got
create
cubes
schemas
to
read
from
the
snowplow
generated
columns
Max.
Anything
to
add
here.
B
Yeah,
oh
sorry,
this
should
be
in
Dev.
It
is
so
I've
written
the
schemas
to
replace
one
for
one.
The
Jitsu
schemas
Tim
quite
rightly
raised
that
we
should
be
making
available
all
of
the
columns
in
snowplow,
but
I'd
suggest
we'll
do
that
as
a
follow-up.
B
So
this
one
will
just
cover
replace
exactly
what
we
have
now,
but
there's
no
plan
there's
an
open
Mr
that
I
think
Rob
is
assigned
to
so
once
he's
got
a
chance
to
look
at
that,
then,
hopefully
get
it
merged
in
the
not
too
distant
future.
We
they
will
exist
side
by
side
with
the
existing
Jitsu
schemers
and
once
we've
got
a
Jitsu,
we
can
get
rid
of
the
old
schemas
and
just
use
these
ones
as
the
default.
But
for
now
we
can
have
both
and
there's
no
reason
not
to.
A
Yep
yeah
we'll
we'll
kind
of
touch
on
that
a
little
bit
more
in
terms
of
the
steps
to
decommission
this,
the
Jitsu
stuff,
but
cool
I'll
go
inside
with
my
for
my
agenda
Point
further
down
the
agenda
cool
that
covers
everything
in
open.
We've
got
a
couple
issues
in
design
here,
Kevin
I
know.
You
just
said
that
you
came
back
from
PTL,
but
is
there
anything
else
in
these
in
this
column?
That
you'd
want
to
call
out.
E
Nope
not
much
I,
just
updated
the
the
one
we
talked
before,
like
the
scorecard
to
design
I
will
probably
start
with
the
scorecard
as
a
P1
yep,
so
yeah.
If
there's
anything
else,
urgent,
also
updates
software
too,
that
you
know.
A
Cool
we
did
call
out
so
then
planning
breakdown.
We
have
a
application
setting
rename
for
Jitsu,
but
it's
it
makes
sense
that
we
shouldn't
actually
work
on
this
since
we're
going
to
see
commission
this.
A
This
is
just
to
separate
the
concept
of
the
configurator,
as
well
as
the
collector
configurator
setting
up
the
project
and
the
service
we
interacted
with
in
the
onboarding
process,
which
we
will
replace
with
the
snowplow
implementation,
but
it
doesn't
make
sense
to
rename
this
is
something
for
Jitsu
when
it's
going
to
be
updated
for
snowplot
later
I'm
gonna
follow
up
for
updating
the
dashboard
scheme
is
to
remove
specific
referrals
to
product
analytics
Ellen.
Has
this
not
sure
if
there's
any
update
here?
A
No,
it
looks
like
we're
still
looking
to
verify
the
implementation
plans.
It's
implying
breakdown.
So
let's
move
right
along
got
a
couple
of
blocked
issues,
fish
dashboard
configurations
for
the
back
end,
which
is
something
we
actually
started.
Picking
up
this
Milestone
as
far
as
the
back
end
is
concerned,
and
then
removing
product
analytics,
specific
dashboard
listing,
which
is
blocked
by.
F
So
that's
blocked
by
the
work
I'm
currently
doing
to
move
the
product
analytics
specific
the
Lost
components
over
to
the
shared
listing
right,
I've
also
just
assigned
the
fetch
the
dashboard
list
from
the
back
end
to
myself.
Okay,
because
I
provisionally
marketed
this
block
just
because
I
think
we
need
to
check
if
the
implementation
plan
is
still
valid
because
it
was
originally
like
four
months
ago
and
I
think
a
bit
has
changed
in
that
endpoint
that
is
available
and
how
we're
saving
dashboards.
Now,
because
it's
not
necessarily
the
same.
A
Yeah
I
think
something
worth
calling
out
someone's
of
the
mind
that
we
would
just
continue,
calling
the
dashboards
from
the
front
end
that
we
have
work
here,
that
Allen's
been
working
on
that
and
Max
has
been
doing
working
on
for
several
months
to
kind
of
have
back
in
as
a
single
source
of
Truth.
A
What
I'd
love
to
understand
if
I'll
ping,
everyone
on
this
but
Tim's,
calling
out
some
blockers
in
terms
of
like
having
a
commit
endpoint
and
some
other
Integrations
to
actually
have
this
working
I'm,
not
quite
clear
on
that.
So
if
we
can
kind
of
dig
into
this,
I'd
appreciate
that
which
this
issue
would
block
or
is,
is
beyond
your
issues
depending
on
that
background.
One.
So.
F
D
A
Cool
then,
as
far
as
ready
for
development
there's
one
issue,
that
is
no
signs,
so
unless
anyone
can
speak
to
that,
we'll
just
move
along
and
then
returning
to
the
issues
called
out.
Alan
you've
been
working
on
this
one
anything
you
want
to
call
out
here,
no
I've
just
been
just
getting
started
on
it.
Really
so
cool
awesome,
all
right
and
then
Lily
you've
got
consulted
in
the
party
analytics
feature
Flags
anything
to
call
out
here.
I
know
you
had
a
slack
comment
earlier:
yeah.
A
Great
I,
don't
believe:
Sam
is
on
the
call
up
so
James
I,
don't
know.
If
there's
anything
you
can
call
out
for
the
internal
preview
blog
post.
A
Kind
of
stuff
we've
got
to
put
an
add
dashboard
button
on
the
analytics
listing
page
I,
don't
believe
Tim's
on
the
call
it
looks
like
we
still
have
a
draft
Mr
there.
So
I
think
that
status
is
accurate.
You've
already
called
this
issue
out.
It's
something
you're
working
on
to
unblock
the
other
blocked
issue.
F
Just
that
this
will
probably
be
several
Mrs,
since
it
is
a
multi-faceted
issue
and
that's
one
on
the
surface,
we're
just
pulling
in
the
product
analytics
stuff
into
the
shared
listing.
The
follow-up
issues
for
this
is
removing
all
the
existing
product
analytics
files,
because
they're
no
longer
needed
with
the
onboarding
moved
over.
That's
the
last
bit
of
functionality.
We
need
the
other.
F
One
is
implementing
a
architecture
where
other
teams
like
optimize,
can
easily
slot
in
their
features
into
that
list
of
like
available
features
dashboard
list,
that's
something
that
I've
struggle
to
figure
out
how
we're
going
to
do
that
for
the
past
few
days,
but
I
think
I.
Finally,
cracked
it
so
yeah.
This
will
be
moving
into
review
shortly.
F
A
Good
I
have
a
more
in-depth
update
here,
but
effectively
bossy
has
been
doing
a
lot
of
work
to
get
Kafka
and
snowplow
integrated
into
our
Helm
chart,
and
so
we're
kind
of
splitting
a
little
bit
up
and
then
I'll
speak
to
more
of
the
overall
strategy
for
the
snowball
implementation.
After
the
Board
review.
A
A
C
Just
reviewed
it
as
a
maintainer,
so
once
we've
had
that
conversation
we'll
get
merged
soon,.
A
Sounds
good
I
have
not
made
any
progress
here.
I've
been
focused
on
the
sunflower
implementation
and
then
I've
got
the
add
product
analytics
application
setting
for
collector
host
hello.
Anything
you
want
to
call
out
of
this
issue.
D
Yeah,
so
basically,
this
was
from
the
late
last
Milestone,
but
there
is
a
change
that
yeah
in
the
previous
my
Approach
there
I
didn't
think
about
the
part
that
some
of
our
types
of
customers
might
be
enabling
this
feature
flag
already.
So
that's
why
we
changed
their
approach
a
bit
and
now
it's
the
new
approach
is
under
review,
but
it's
in
the
initial
review,
so
hopefully,
in
the
next
few
days,
I
think
it
will
be
finished.
Yeah.
A
Sounds
good,
we've
got
add
empty
states
to
panels
which
I
think
Ellen
had
a
agenda
point
to
call
out,
but
we
can
just
take
a
look
at
it.
Real,
quick,
it's
in
review.
It
looks
like
there's
still
some
discussion
as
far
as
requirements
or
consider
Behavior.
So
anything
worth
calling
out
here.
F
F
Yeah
I
think
it
would
be
one
thing
like
there
isn't
agenda
item
for
this,
but
the
question
that
I
have
James
and
your
answers.
You
said
you're
in
favor
of
my
Approach
but
I'm,
not
entirely
sure
which
approach
you're,
referring
to
whether
it's
the
displaying
the
text
or
displaying
the
number
zero
for
single
stats.
G
A
Previously
we
had
strategy
for
rebuilt
dashboards,
so
let's
go
down
here.
Let's
go,
we've
got
about
six
issues
so
back
to
you
on.
You
have
two
issues
here
that
are
enclosed
handling.
If
a
dashboard
is
not
available.
F
A
Sure
and
then
we've
got
initially
being
worked
on
by
lores
and
fixing
spec
violations
for
the
metric
chart
spec.
So
it's
great
to
see
and
then
Alan
you've
been
working
on,
adding
an
API
to
retrieve
the
state
of
the
project,
analytics
stack
anything
worth
calling
out
here.
No,
that's
that's
been
merged.
The
the.
A
We're
there
got
it
yeah,
we
might
have
to
schedule
a
front-end
related
issue
for
that
cool
and
then
we've
got
the
column
chart,
which
is
version.
So
that's
great.
So
hopefully
we
start
using
that
for
your
new
visualizations,
our
new
charts
rather
and
then
Kevin
you've
done
some
work
to
learn
the
product
analytics
domain.
Anything
you
wanted
to
call
out.
E
No,
not
so
much
I'm
I'm,
still
a
bit
confused
with
the
listing
like
the
common
listing
and
and
seeing
all
those
things
so
I'll
need
to
dive
a
bit
deeper
into
that,
but
I
also
expect
to
kind
of
learn
more
as
I
go
into
the
weeds
of
the
different
design
issue.
I
pick
up,
so
that's
also
why
I
close
it.
A
So
then
Ellen
has
a
agenda
item
that
I
vocalize
for
getting
thoughts
on
the
question
for
empty
States
looks
like
we've
got
some
opinions
already
in
terms
of
representing
null
versus
zero.
So
if
anyone
else
has
thoughts
there,
please
chime
in
otherwise
I
have
the
rest
of
the
agenda
so
probably
about
90
more
seconds
of
listening
to
me.
A
I
just
want
to
provide
an
update
of
what's
going
on
with
this
mobile
integration.
Update
I
just
got
out
of
a
working
session
with
busty
who's
been
doing
a
lot
of
work
to
get
snowplow
and
Kafka
integrated
into
our
stack.
There's
a
little
bit
more
work
to
do
there
in
terms
of
making
sure
it's
a
smooth
installation
process.
As
far
as
you
know
how
we
can
manage
it,
how
we'll
install
it
as
well
as
how
other
users
will
be
using
it
as
well?
A
So
hopefully
we
can
make
some
progress
in
the
next
couple
days
and
then
start
to
push
that
out
to
Dev
staging
and
production
and
then
start
to
test
it
out.
So
after
we
get
the
chart
ready
to
go,
we'll
verify
it
by
instrumenting
the
metrics
dictionary
for
those
that
aren't
familiar,
it's
the
metrics
we
collect
through
our
existing
snowplow
implementation.
So
it's
just
another
project
just
to
kind
of
test
it
out
with
something
new.
A
If
that
looks
good,
then
we'll
switch
over
to
the
internal
handbook
and
then
before
we
can
really
move
the
rest
of
the
projects
over
or
as
far
as
like,
not
the
data
but
like
just
sending
events
over
there's
a
ghost
service
that
product
intelligence
is
working
on
to
actually
replace
a
lot
of
the
automation
that
we're
relying
on
Jitsu
to
do
in
terms
of
the
table
set
up
and
all
the
connections
set
up
there,
so
that
we
can
verify
that
we
are
ready
to
receive
events
and
so
that
our
UI
responds
accordingly.
A
So
you
know
if
it
based
on
the
work
that
we
just
kind
of
went
over
in
terms
of
the
cluster
State.
You
know.
If
we're
actually
ready
to
receive
events
and
are
receiving
events,
then
we
can
actually
show
the
dashboard
and
things
like
that.
So
that's
a
big
tie
in
that
or
a
big
dependency
we
need
as
far
as
our
onboarding
flow
is
concerned.
A
After
that,
then
we
can
that
that
effectively
means
that
we're
ready
to
decommission
Jitsu
so
we'll
start
to
remove
the
services,
remove
it
from
our
charts
and
yeah
move
on
from
there
and
then
the
final
point
I
just
wanted
to
signal
boost
this.
You
saw
this
in
the
stock
Channel
already,
but
for
those
that
are
curious
in
terms
of
kind
of
what
happens
with
the
infrastructure
side
of
things,
Rob
and
I
had
a
working
session
to
upgrade
our
Helm
chart
to
do
some
knowledge
during
and
produce
some
documentation.
A
So
that
was
a
lot
of
talking.
Anyone
have
any
other
topics,
they'd
like
to
discuss.
B
A
B
Haven't,
oh
sorry,
one
thing
that
I
haven't
mentioned
in
terms
of
the
switch
from
Jitsu
to
snow
plow.
From
my
point
of
view,
Willow
quiet
sorry,
is
that
the
funnel
generation
requires
all
required
changes
in
a
gitlab
API,
specifically
because
it
generates
SQL.
The
cube
then
runs
so
we'll
have
to
make
sure
that
we
coordinate
that
part.
B
So
while
we
can
have
both
the
snow
plower
and
the
jitsu
Cube
schemas
running
simultaneously,
we
can't
have
the
API
running
simultaneously,
so
we'll
just
have
to
make
sure
we
time
that
right,
I
know
we're
not
really
using
funnel
analysis
all
that
much
right
now.
So
it's
not
a
huge
problem,
but
definitely
something
to
be
aware
of.
When
we
we
do
the
switch.
A
Makes
sense
well
thanks
for
calling
that
out,
even
if,
like
we
do
want
to
get
in
the
funnels
as
soon
as
possible,
so
we
just
want
to
make
sure
we
don't
trip
over
ourselves
as
we
do
this,
whichever
so,
it's
definitely
worth
calling
out
James.
You
have
a
point.
G
Yeah
I
had
mentioned
reactive
users
at
least
half
a
dozen
times,
if
not
more
yesterday,
in
the
deck
I
didn't
see
in
an
issue
for
tracking
and
I,
don't
see.
Anything
in
five
sense
is
that
something
we
think
we
can
fit
into
our
first
external
user.
Epic
it'd
be
great
to
get
account
of
how
many
users
are
editing,
charts
and
how
many
users
are
looking
at
charts.
A
Yeah,
it's
a
good
question:
I
mean
we
can
definitely
use
the
our
conventional.
So
one
thing
I
want
to
accept.
Sorry,
would
love
to
use
assassins
dashboard
and
just
do
the
standard
like
snowplow
instrumentation.
This
gets
confusing
because
we're
using
snowplow,
but
our
exist
like
our
existing
instrumentation
for
actually
how
we
track
feature
usage.
A
One
thing
I
wanted
to
verify:
maybe
we
can
do
both,
but
what
I
was
trying
to
say
is
maybe
like,
since
we're
using
snowplow,
which
is
already
like
users,
are
opting
into
that
instrumentation
I,
wonder
if
we
can
then
start
to
actually
instrument
gitlab
the
project
itself
and
then
be
able
to
actually
dog
food,
our
own
dashboard,
to
see
like
how
our
weekly
active
users
are
looking.
If
we
only
instrument
the
analytics
features,
at
least
to
start
yeah,
but.
G
A
And
we'll
go
from
there
yeah.
So
to
answer
your
question,
we
don't
have
an
issue
yet
so
thanks
for
there
were
issues
previously
with
legal
as
far
as
like
the
non-snopal
uses,
because
that's
another
way
of
we're
collecting
another
host.
But
if
we
are.
B
Yeah
I
think
we
could
probably
do
it
in
a
for
depending
what
we
Define
as
an
active
user.
You
know
we
can
track
things
like
projects
that
have
product
analytics
enabled,
for
example,
we
can.
We
can
instrument
that
in
size
sense.
A
Yeah,
so
we
can
start
with
that,
but
it'd
be
great
if
we
can
really
start
dog
fooding
that
as
well
but
yeah.
The
the
main
point
is
just
making
sure
that
whoever
will
be
captured
in
events
that
we're
okay
to
do
so
so
yeah.