►
From YouTube: 2023-08-22 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
A
All
right.
Can
everyone
see
cool
getting
some
thumbs
up
so
first,
the
Jenna
item
is
to
review
the
bullet
board.
I'll
start
with
the
open
issues,
the
planning
issue
we
can
probably
skip.
B
This
really
hasn't
become
necessary
until
we
get
first
get
out
to
customers.
This
is
a
control
specifically,
so
so
to
clarify
the
experiment,
features
list,
I
guess
does
align
with
the
experiment
label,
but
we're
hoping
to
use
this
as
kind
of
an
opt-in
for
beta.
So
it's
really
not
until
we
get
past
the
first
external
customer
phase,
where
we're
out
to
a
couple
like
select
customers
where
we
want
people
to
have
an
opt-in
mechanism,
so
I,
don't
think
it's
something
that
we
can.
B
It's
not
been
ready
for
development,
but
I
think
it's
worth
looking
at
in
terms
of
validating
solution
in
terms
of
how
we
currently
use
it,
and
the
bulk
of
the
controls
for
this
is
for
AI
assist
features.
But
that's
an
issue
to
call
out
as
far
as
like
refining
is
all
out
there.
C
A
B
B
But
if
there's
a
conversation
worth
having
with
the
you
know,
people
currently
kind
of
maintaining
that
area
or
the
I
guess
the
the
code
owners,
it
might
be
worth
to
actually
start
doing.
Some
of
that
work
now
to
be
like
hey.
This
is
very
AI
feature
specific,
but
we'd
like
to
start
using
this
for
other
features
that
are
just
wanting
to
use
experiment
label.
What
do
we
like
I,
guess
I'm
kind
of
fine
leaving
it
in
the
current
Milestone
because
it
seems
like
there
is
work
that
could
be
done
there.
A
A
I
think
that
sounds
good
to
me.
I
guess
we
can
follow
up
and
see
like
if
someone
hasn't
picked
this
up,
then
we
can
maybe
just
assign
this
to
at
least
have
a
dri.
A
A
Moving
on,
we
have
move
group
and
admin
and
lose
settings
to
a
dedicated
page.
This
is
in
solution,
validation,
so
I
think
just
just
need
some
eyes
on.
It
doesn't
currently
have
a
dri,
but
I
looked
at
it
and
makes
sense
so
yeah.
Hopefully
we
can
just
move
that
along
moving
on,
we
have
removed
product
analytics,
clickhouse
connection
string
field.
This
currently
does
not
have
any
workflow
labels.
Anyone
know
anything
about
this.
B
Yeah,
so
this
was
created
by
someone
else.
I
I
also
caught
this
in
my
testing
last
week.
This
was
a
field
that
we
used
to
configure
clickhouse
when
we're
using
Jitsu,
that's
no
longer
required,
because
the
configurator
for
snowplow
has
that
settings
built
into
its
cluster
configuration.
So
this
is
a
field.
This
is
a
database
field,
that's
no
longer
used,
and
so
we
should
definitely
just
remove
it.
I,
don't
even
think
we
have
to
wait
for
a
major
breaking
change
since
the
feature
itself
never
made
it
out
to
ga.
B
A
You
and
then
we
have
a
docs
analyzing
lab
usage.
This
is
signed
to
Lorena
anyone
if
something
sad
seem
like
it.
Moving
on,
we
have
projects
cannot
reset
a
product
analytics
at
the
project
level,
if
they've
already
on
board
it-
and
this
is
also
in
solution,
validation,.
D
B
I,
haven't
read
your
response
on
that.
Do
you
want
to
chat
about
it
really
quickly.
D
Yeah,
it's
it's
fine
to
basically
I
agree
with
you.
We
should
re,
add
resetting
when
you
reset
the
config
yeah.
B
I,
just
don't
want
to
I
mean
I,
guess
you
can
you
we
can
debate
like
what
the
follow-up
or
not,
but
so
such
for
context.
For
the
group
like
if
you
set
up
product
analytics
for
your
project
when
there's
an
instance
level
cluster
configure,
but
then
you
say,
for
example,
you
want
to
connect
one
to
your
like
to
a
private
cluster,
because
we're
using
the
same
ID
gitlab
itself
doesn't
know
to
like
reset
that
or
that
you
you
want
to
do
something
different.
So
this
discussion
was
about.
B
How
do
we
want
to
handle
that
in
terms
of
do
we
want
a
separate
column
for
a
project
level,
ID
or
not,
and
so
I
hadn't
read
albums
I'm,
trying
to
read
it
now
very
quickly,
but
basically
like
what
I
was
proposing
is
like
when
you
enable
product
analytics
at
the
project
level,
it
either
wipes
that
field,
so
they
can
get
a
new
one
so
that
you
can
re-initiate
that
onboarding
process,
because
what
happens
is
you'll
get
stuck
in
a
this
Loop
of
waiting
for
events
or
you'll,
see
your
old,
dashboard
or
you'll,
see
nothing.
B
Sorry
I
think
you'll
see
nothing
or
waiting
for
events,
but
then
there's
no
way
to
actually
initiate
the
onboarding
process,
because
your
project
level
cluster
doesn't
actually
have
sorry.
Okay,
well
things
that
has
an
ID,
but
it
actually
needs
a
new
one
from
the
project
model
cluster.
So
this
is
trying
to
figure
out
like
how
to
how
to
handle
that.
B
So
in
that
case,
you're,
okay,
with
yeah
yeah,
yeah
yeah
you're,
it's
best
to
clear
it.
So
I'm
I'm
happy
with
that.
If
you
are
but
I'm,
not
being
okay
Curious
to
hear
what
other
people
think
about
it
as
well,
if
they
have
any
thoughts,
but
basically
you
know
whenever
you
enable
or
disable
product
analytics
the
project
level,
what
we're
proposing
here,
Alan
and
our
to
clear
out
the
application
ID
so
that
can
re-initiate
the
onboarding
process.
This
basically
allows
the
user,
you
know.
B
Maybe
they
were
trying
out
instance,
level
or
the
shared
environment.
They
want
to
go
to
the
private,
and
then
they
wanted
to
go
back
like
it
just
allows
that
Mobility
in
configuration,
especially
if
we
go
beyond
that
with
the
group
level
or
anything
like
that.
So.
C
My
only
comment
would
be
that
we'd
need
some
way
of
clearing
up
the
old
data
at
some
point,
so
we
don't
end
up
with
lots
of
dead
clickhouse
databases,
because
people
have
jumped,
from
instance,
to
projects
on
at
least.com,
so
I
guess
initial
Step,
At
least
step
one
would
be
just
in
the
old
documentation,
documentation
suggesting
people
export
their
Data
before,
because
there's
no
guarantee
that
it
will
be
there
later
on
after
you've
moved.
Does
that
make
sense.
B
B
If
you
had
data
somewhere
else,
do
you
want
to
bring
that
with
you,
or
do
we
I
just
plan
on
saying
like
if
you,
if
you
change
this
export
it
because
if
we're
not
going
to
be
able
to
you're
not
going
to
be
able
to
bring
it
over,
but
that
that
brings
up
a
lot
of
different
questions
that
we
should
definitely
be
asking
so
I'll
I'll
create
a
follow-up
issue
with
kind
of
like
those
when
you're
in
questions.
B
A
So
it's
like
a
good
discussion.
Yeah
I
think
it
makes
sense
and
ropes,
collect
yeah,
good
collapse,
yeah
cool
moving
on.
We
have
the
brainstorm
ideas
for
customer
interviews
that
it
has
its
own
agenda
items,
so
I'll
skip
that
and
I'll
be
awesome.
Video
moving
on
to
ready
for
development.
A
We
have
the
improved
analytics
settings,
UI
text
and
the
new
custom
dashboard
flow
NPC,
specifically
the
available
visualization
sidebar
I'm
planning
on
picking
this
up
after
I
work
on
the
dashboard.
But
if
anyone
else
has
capacity
feel
free
to
work
on
this,
like
it's
not
blocked
by
the
work
I'm
doing,
and
it
can
happen
in
parallel
and
this
one
I
just
moved
from
open,
but.
B
A
Yeah
he's
not
on
the
call
I
think
this
is
still
like
he's
still
working
on
the
Mr.
So
don't
know
if
anyone
has
anything
to
add,
does
it
seem
like
it
then.
B
Sorry
in
the
maybe.
A
A
Check
maybe
yeah
I
I
just
previously
check
the
issue
and
I.
B
A
B
Yeah
I
can,
from
a
general
point
of
view,
I
think
we're
all
aware
it
needs
an
issue.
It's
I
know
we
do.
We
do
have
one
sorry,
but
this
is
just
all
the
infrastructure
topics
related
to
that.
What
I
can
say
is
that
I'm
working
with
another
SRE
to
hopefully
get
this
over
the
Finish
Line
this
week
and
then
I'm
also
rounding
out
the
work
in
terms
of
fully
enabling
clickhouse
Cloud
support,
which
I
can
speak
to
a
little
further
down
the
column
later.
A
Oh,
you
have
the
next
to
for
the
missing
break
run
and
then
also
the
big
Upstream,
keep
change
anything
to
add.
C
Yeah
breadcrumb
I,
haven't
touched
since
coming
back
from
Roi
is
definitely
won't,
be
I'll,
see
if
I
can
get
to
it
by
the
end
of
Milestone
is
just
one
of
the
lowest
priority
items
on
the
list.
Out
of
all
the
other
tasks
that
I
need
to
focus
on
for
our
goals,
with
the
with
feel
I
finally
got
the
integration
test
completed
just
before
this
call,
so
all
unit
test
or
integration
tests
are
now
done.
C
C
So
if
anyone,
if
we
need
to
make
further
changes
to
cube
in
future
or
anyone
wants
to
have
a
play,
they'll
know
exactly
how
you
can
get
it
working,
because
I
spent
far
too
long
trying
to
figure
that
out
where
I'd
like
to
document
it
somewhere
and
then
I'll
be
requesting
some
input
from
either
elwin
or
your
selfie
on
just
to
look
over
the
code,
make
sure
you're
generally
happy
with
it.
Obviously,
within
the
context,
it's
not
our
repo
and
then
I'll
be
putting
out
a
PR.
A
B
Yeah,
so
I
don't
think
this
issue
even
has
a
good
description.
I
might
it
might
have
literally
just
been
those
six
words
I'll,
surprise
myself.
If
there
is
okay
well
there,
there
are
a
little
bit
more
words
for
that.
So
basically,
but
not
many
I
I,
think
we're
generally
aware.
I
can
share
my
screen
a
little
bit
in
terms
of
what's
happening
with
the
stack,
but.
B
Thank
you
just
to
give
everyone
a
little
more
visibility
into.
What's
going
on,
one
thing
is
I've
updated
these
4700
word
Readiness
review
if
anyone
would
like
some
reading
for
some
for
bedtime
reading,
but
if
not,
we've
had
to
make
some
architectural
differences
that
are
changes
to
to
support
clickhouse
cloud,
and
this
is
publicly
available.
So
there's
nothing
super
crazy
here.
B
B
So
now
this
the
focus
for-
and
this
is
all
in
the
context
of
gitlab.com
or
SAS
right-
is
that
the
cluster
Demand
only
has
to
worry
about
data
in
transit
and
making
sure
that's
encrypted,
and
we've
already
made
all
those
changes
in
the
past
months
to
make
sure
everything
is
encrypted
in
transit.
B
Just
trying
to
make
this
a
little
bit
bigger.
So
in
order
to
support
clickhouse,
Cloud
I've
had
to
add
another
piece
into
the
stack
called
Vector,
which
is
eventually
is
essentially
just
event
delivery.
It's
a
full-blown
event
pipeline.
Basically,
it
pulls
events
from
Kafka
and
pushes
them
over
to
clickhouse
Cloud.
B
This
is
because
clickhouse
Cloud
itself
or
for
people
who
weren't
aware
click
house
in
the
cluster
actually
connected
directly
to
Kafka
and
pulled
events
from
Kafka,
which
is
a
really
cool
feature.
Clickhouse
clickhouse
has
but
is
not
supported
in
clickhouse
Cloud.
So
you
can
see
where
I'm
going
with
this,
where
there's
another
piece
that
had
to
be
added
to
actually
support
the
delivery
of
events
from
Kafka
once
they're
enriched
by
snowplow
to
push
that
over
to
clickhouse
Cloud.
B
That
part
was
working,
that's
what
I
showed
last
week,
but
and
so
that
that's
all
proven
not
to
work.
But
what
needs
to
change
now
is
the
interactions
between
Cube
and
configurator,
so
that
configurator
needs
to
be
able
to
handle
and
create
different
database
table
types
for
clickhouse
cloud
as
well.
As
you
know,
Cube
should
be
just
a
configuration
thing
of
being
able
to
say
hey.
Instead
of
connecting
to
an
end
cluster
clickhouse,
hostname
I
think
we
can
just
already
in
their
values.
B
Yaml
file
just
be
able
to
say,
hey
connect
to
this
click.
Clickhouse
Cloud
instance
share
the
credentials
and
you're
good
to
go.
So
that's
so.
To
summarize,
we
got
event
delivery
to
clickhouse
Cloud
going,
but
we
need
to
update
the
configuring
Cube
to
be
able
to
actually
one
set
up
the
projects
and
then
be
able
to
query
the
data
from
that.
But
everything
else
is
working
as
expected.
So
I
should
be
able
to
get
that
wrapped
up
this
week.
B
A
A
Rob
has
very
graciously
given
me
a
lot
of
his
brain
and
time
to
help
figure
out
like
a
different
approach
like
a
new
layout,
for
that
is
compatible
with
all
the
requirements
that
we
want
for
this
MVC,
but
using
existing
pajamas
components
without
adding
any
like
fancy
pseudo
panel
or
the
stepper,
which
I
don't
think.
A
We
need
right
now,
because
I'm
not
even
sure
we're
gonna
introduce
the
concept
of
user,
selecting
a
data
source
since
that
doesn't
necessarily
make
sense
on
our
dashboards,
because
that's
something
that's
tied
to
visualization,
that's
tied
to
a
dashboard.
A
So
yeah
I've
made
some
mock-ups
here
to
prove
that
this
is
actually
a
lot
more
straightforward,
and
this
is
already
working
and
it's
something
I
can
demo
and
that's
something
I'll
do
in
the
weekly
PM
ux
call
tomorrow.
So
if
anyone's
interested,
please
show
me
that
call,
and
we
can
discuss
this
further,
then
in
review.
We
have
two
issues
from
Alvin,
which
is
update
the
product,
analytics
string
and
improve
analyzing
start
mode,
I
believe
all
the
Android
stream
changes
have
just
gotten
merged
robe.
A
Seeing
your
head
shake
so
I'm
going
to
move
this
to
verification,
and
then
the
dark
mode
is
in
maintain
a
review
with
me
and
then
and
then
you
have
extend
service
ping
for
more
tracking.
D
A
Okay,
great
yeah,
I
think
those
last
comments
were
probably
from
me,
but
the
change
itself
looked
good,
so
I
think
we
can.
We
should
be
able
to
get
that
much
soon.
D
A
D
Want
to
address
the
instrumentation
instructions,
comment
thing
that
you
pointed
out,
because
that
is
not
intended.
So
I
want
to
get
that
sorted.
A
Okay,
cool
yeah.
Let
me
know
if
you
need
any
help
or
like
you,
need
a
patch
or
anything
like
that
happy
to
have
to
jump
in
then
yeah
verification
issues.
We
have
one
from
Hill,
which
is
confidential,
so
I'm
not
going
to
touch
that
then,
in
terms
of
bookmarks
I
check
that
we
don't
have
a
bookmark
for
at
the
previous
week
or
the
week
before
that
so
I'm
gonna
skip
it.
A
A
Stuff,
too,
that
was
like
completed
this
week
unless
anyone
knows
or
thinks
that
we
have
to
go
like
back
a
month,
basically
in
terms
of
changes
all
right,
let's
just
go
back
a
week,
so
Khalil
works
on
this
change.
A
He
also
wrote
a
comment
here
saying
that
the
single
dashboard
page
will
rather,
the
dashboard
list
will
no
longer
throw
a
500
error
when
a
dashboard
references,
a
visualization
that
doesn't
exist,
so
the
user
is
just
made
like
a
typo
or
something
in
their
configuration,
and
instead
this
error
will
be
shown
on
the
new
fancy
panel
error
display
on
the
single
dashboard
page.
A
A
I
can
maybe
demo
this.
By
going
to
the
Mr,
it
looks
pretty
sweet,
so
yeah
here
is
our
before
this
is
our
after.
It's
simplifying
a
bit,
maybe
in
terms
of
contrast,
it's
getting
a
bit
too
simplified
for
my
taste,
but
it's
something
we
can
iterate
on
and
overall,
it's
getting
much
closer
to
matching.
What
are,
in
this
end,
like
design,
vision
and
goal
is
then
I
have
the
next
one
for
create
a
new
custom
dashboard
flow.
Oh,
this
is
just
an
issue
that
I
closed.
A
That
was
essentially
promoted
to
an
epic,
but
there
is
already
an
epic.
So
there's
no
point
promoting
this,
so
it
was
just
closed
because
I
created
several
implementation
issues
for
this
and
the
Milestone
issue.
We
don't
need
to
talk
about
right.
James
has
the
next
agenda
item
which
I'll
read
out.
He
opened
up
a
issue
to
brainstorm,
how
to
get
feedback
from
our
customers
during
the
beta
and
early
GA
of
product
analytics
and
as
for
input
from
everyone.
A
I
just
asked
the
general
question
if
this
has
been
done
before,
and
maybe
we
can
also
like
the
wider
gitlab
team
on
Slack,
if
this
has
been
done
and
for
ideas
just
off
the
top
of
mind,
I
remembered
something
from
coast,
suggestions
and
I
saw
that
they
have
an
alert
on
their
documentation,
asking
for
feedback
and
yeah
any
other
ideas
or
feedback
from
from
the
team
on
this
feedback
issue.
Please
add
it
to
the
issue,
then,
as
you
have.
B
Yeah
I
was
I,
wasn't
sure
how
much
time
we'd
have
in
the
meeting
yeah
we
can.
We
can
discuss
it
if
we
like,
with
the
people
that
are
here
and
then
move
to
async
since
stuff
to
get
everyone's
in
call
anyways.
B
But
basically
one
of
my
first
points
was
about
the
billboard
making
sure
people
still
feel
like
they're
getting
value
out
of
that
Rob
share
that
he
still
feels
like
is
useful.
I
find
it
useful
and
Al
and
I
were
able
to
make
a
decision
very
quickly
on
that.
So
I
think
you
know.
Having
rotating
time
zones
is
still
able
to
accommodate
everyone
get
everyone
into
a
sync
meeting
at
some
point
and
then
for
whatever
else
we
can
do
at
async.
B
But
those
are
just
Rob's
mind
thoughts
I'd
be
curious.
If
anyone
else
has
anything
they'd
like
to
share
about
the
billboard
here,.
A
B
A
B
Yeah
I
think,
and
so
maybe
I
guess
it
really
should
start
with
an
issue,
because
what
I'm
thinking
is
like,
maybe
there's
some
points
of
improvement
we
can
make-
and
this
is
all
timely,
of
course,
with
mid-years
and
things
like
that,
but
basically
like
a
lot
of
times
when
we,
because
especially
because
we
have
alternating
time
zones
too,
we
we
don't.
We
rarely
if
ever
have
the
entire
team
available
for
those
that
aren't
available
on
the
call.
B
It
can
be
hard
if
we
don't
actually
have
direct
contact
with
those
issues
to
be
able
to
actually
provide
context
with
what
needs
to
be
done
there.
So
I
don't
know
if
that's
something
we
can
provide
like
async
like
that's.
Why
we
check
comments
on
that,
but
I
guess
maybe
it's
just
like
you
know
again
not
to
provide
updates
for
the
sake
of
providing
updates.
If
there's
nothing
to
share,
then
that's
also
fine
as
well,
but
I.
Think.
B
Maybe
one
thing
worth
reiterating
to
people
is
that
yeah,
if
you're
not
going
to
be
there
for
time
zone
reasons
or
otherwise
make
sure
the
issues
you
have
on
the
billboard,
at
least
if
they?
B
If
there
are
questions
to
ask
that
you
ask
them
but
I
think
we
already
kind
of
do
that
async
anyways,
so
they
just
kind
of
get
resolved
outside
of
the
group
sync,
but
just
something
to
think
about
just
as
I
kind
of
go
through
the
issues
and
I
don't
see
an
update
and
I
guess
part
of
that's,
because
I
don't
have
a
lot
of
contact
with
a
lot
of
the
the
day-to-day
issues
at
the
moment
I'd
like
to
but
yeah.
B
But
anyways
I
can
I
can
follow
up
with
an
issue
to
get
more
thoughts
and
get
suggestions
as
well.
If
you
think
there
are
improvements
to
make
to
that,
I
definitely
agree
like
going
over
the
same.
You
know
issues
that
are
in
the
Milestone,
but
they're
not
ready
for
development,
but
they're,
not
in
solution
validation
either
it
can
be
a
little
tedious
unless
you've
gone
through
the
these
issues.
In
the
number
of
times
you
don't
know
really
to
skip
them
and
we
end
up
repeating
them
multiple
times.
B
B
We
had
that
make
product
analytics
and
experiment
feature
added
to
the
experiment,
features
list
like
I
guess
in
reality,
that
is
solution,
validation
but,
like
I'm
glad
we
discussed
it
this
time,
but
we
hadn't
we
kind
of
at
least
in
the
past
kind
of
skipped
over
it,
but
like
that,
helped
like
that
providing
that
Clarity
in
terms
of
like
what
we're
trying
to
do
there
is
useful
but
I,
guess
if
anything,
maybe
that
means
that
there
shouldn't
be
any
issues
in
the
open
board
because
they
need
workflow
labels.
A
Yeah
sounds
good.
Did
you
want
to
discuss
any
of
the
other
read-only
points?
I
think
we
have
one
minute
left
if
you
want
to
call
anything
out,
yeah.
B
In
a
minute,
probably
not
so
I'll
I'll
create
an
issue,
but
definitely
take
a
look
at
it
offer
some
amazing
thoughts
if
you
like,
yeah
I'll
transfer
them
over
to
the
issue,
and
we
can
go
from
there.
It's
yeah
I'll
try
to
get
those
done
this
week.