►
From YouTube: 2023-07-11 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
All
right,
hello,
everybody
Welcome
to
the
July
11th
edition
of
the
product
analytics
group
snake,
we'll
start
to
share
my
screen
airport
internet,
permitting
we
go
ahead
and
do
the
Board
review
I'm
just
going
to
go
ahead
and
get
the
story
for
logging
is
still
the
same,
something
we
want
to
pursue,
but
until
we
have
a
clear
path
forward
in
terms
of
what
infrastructure
wants
out
of
our
logging
solution,
we're
going
to
just
hold
on
that.
A
My
focus
is
still
remaining
on
getting
out
to
production
or
at
least
being
able
to
handle
customer
data.
So
at
this
point,
I'm
going
to
be
escalating
and
making
working
to
getting
an
exemption
to
be
able
to
launch
and
host
run
data.
In
the
meantime,
both
product
analytics
and
analytics
instrumentation
continue
to
work
to
do
security,
hardening
I,
think
in
terms
of
improving
management
of
environment.
Specific
configurations-
I
might
have
said
this
before,
but
I
think
we've
already
wrapped
that
up.
A
So
all
the
other
issues
apart
from
documentation,
are
unassigned
I,
don't
believe
the
rings
on
the
call
so
I'll
just
move
on
to
what
is
assigned
James.
Is
there
anything
you
wanted
to
discuss
with
regards
to
the
user
screen
map?
Apart
from
the
agenda
point
I
think
regarding
this?
No.
B
A
You
sure
that
is
the
in
progress
or
the
equivalent
of
just
that
works
for
you,
cool
and
we've
got
a
follow-up
for
dismissing
the
analytics
panel,
but
I,
not
it's
not
like
not
on
the
call.
So
I
think
we
can
go
ahead,
move
on
Kevin's
also
on
the
call.
So
unless
there's
an
update
that
anyone
else
can
cover
as
far
as
the
right
prototypes
are
concerned,.
B
We
did
another
round
of
interviews
unmoderated
on
Thursday
and
Friday
last
week,
I
tagged
those
interviews.
Yesterday,
Kevin
wants
to
do
one
more
round
combining
two
of
the
steps
to
see
how
that
plays
out,
and
then
we
should
be
getting
close
to
being
wrapped
up
and
being
able
to
move
into
implementation
on
the
custom.
Dashboard
flow
I
think.
A
A
We
have
nothing
in
blocked,
so
we'll
just
move
on
to
ready
for
development.
We
have
an
issue
I,
think
that
was
built
in
recently
for
hiding
analytics
dashboards
for
users
without
access
the
context.
Here.
A
Being
that
the
idea
is
that
eventually
the
shared
dashboard
listing,
will
you
know
house
multiple
dashboards
not
only
for
product
analytics,
optimize
and
observability,
but
also
the
other
dashboards
that
exist
in
the
product
which,
if
we
remember
back
to
the
original
conversation
with
the
left
menu
sidebar
was
part
of
the
reason
why
we
came
up
with
the
concept
for
the
share
dashboard
listing.
But
until
then
we
want
to
make
sure
that
if
you
don't
have
access
to
anything,
that's
going
to
be
there
that
you
don't
see
it.
A
So
that's
ready
for
assignment
as
well.
We've
also
got
a
follow-up
for
adding
missing
trailing
breadcrumbs
for
analytics
dashboard.
Pages
rathers
or
anything
you
want
to
call
out
here.
C
Something
I'm
gonna
pick
up
after
the
issue
I'm
working
on
if
anyone
comes
along
and
has
nothing
to
do,
feel
free
to
take
that
off
me,
it's
a
very
simple
basic
weight
of
one
task,
just
for
some
tidy
up
they're
refactoring
on
the
book.
We
just
did.
A
C
Very
fiddly
not
highly
ideal
I
have
created
a
follow-up
issue
after
talking
with
Max
and
Dennis,
when
we
were
in
London
the
other
day
to
Upstream
this
to
cubes
click
house
driver,
but
for
now,
as
a
sort
of
patch
I'm
implement
I'm
implementing
a
transformer
in
the
cube
proxy
level
to
add
those
that
data
to
zero
values
for
for
the
entire
date
range,
not
just
the
parts
for
the
data.
We
actually
have.
C
It's
medium
review.
I
have
one
more
spec
to
finish
off,
so
hopefully
I
should
have
that
done
at
the
end
of
the
day,
depending
on
how
the
kids
go.
If
not
it'll
be
first
thing
in
the
morning.
A
Okay,
cool
and
then
Helen's
got
an
issue
for
creating
a
configuration
screen
for
configuring
product
analytics,
post
initial
setup.
We're
moving
this
one
back
to
Dev
to
address
some
structural
changes
we
need
to
make.
So
that
is
the
last
state
that
we
had
looks
like
there
are
so.
C
I
need
to
so
it
went
to
Jan
from
antenna
review
yesterday,
but
we
both
me
and
you
both
agreed
that
it'd
probably
be
better
to
split
it
up,
because
by
that
point,
you'd
hit
just
over
800
lines
of
code
just
because
of
the
various
changes
that
have
taken
place
throughout
the
Mr
review
process.
So
I
wouldn't
have
split
it
into
two
separate
Mrs,
so
I
need
to
actually
review
the
second
Mr
and
pass
it
back
to
Young
for
final
approval.
So
it's
still
going
on
very.
A
D
B
D
I
think
I
think
we
don't
need
because,
like
it
is
for
the
clickhouse
cluster,
which
is
not
in
production
Yeah,
so
basically
I'm
working
on
the.
D
I
was
working
on
limiting
the
requests
to
clickhouse
Cluster
yeah
I.
Did
it
I
actually
have
a
branch
which
working
solution,
but
I
I'm
still
looking
for
a
base.
Maybe
we
can
do
it
in
a
better
way
because
I'm
now
hard-coding
the
not
IPS
from
another
cluster,
the
first
cluster.
So
that's
like
in
protest,
yeah,
gotcha.
A
All
right,
and
then
we
have
an
issue
in
Dev
without
the
signee
or
exception,
is
not
being
properly
handled
in
this
product,
analytics
worker,
not
sure
if
I've
created
the
issue
but
he's
oh
okay,
Alan
I,
think
you're
working
on
this
one
yeah.
A
It
I'll
assign
myself
now
no
worries
anything
that
you'd
like
to
share
regarding
this.
This
issue.
A
D
Yes,
folks,
so
I
already
merge
another
Mr
yesterday,
but
I
think
there
will
be
two
Mrs
to
just
like
make
the
review
a
bit
easier.
So
it
will
be
during
the
next
days
merged.
A
Sounds
good
and
then
we
have
the
encryptor
displaying
encrypted
Fields
as
password
fields
or
in
the
admin
settings
which
is
in
review
broad
I.
Suppose
you
don't
I'm,
not
sure
if
you
were
reviewing
this
one
or
not.
Do
you
know
anything
about
this.
C
I
have
been
involved
in
all
of
Owens
and
Miles
I
believe
in
regards
to
all
of
them.
They
are
very
close-
the
dehydrated
one,
for
instance,
to
say,
dehydrated
dashboard
drift
I
am
doing
the
retainer
review,
so
they
are
nearly
there
there's
nothing
in
particular
to
say
about
them.
Other
than
they've
been
a
bit
fiddly
taking
a
bit
of
time
to
get
through.
The
various
review
processes
got.
A
It
cool
and
then
we
have
nothing
in
verification.
I
will
quickly
check
the
bookmark.
It's
reflection.
Custom
Dash,
massage
from
the
mtvo.
C
Story
with
in
the
what
I
didn't
attend
or
did
no
one
attend
that
once.
A
Okay,
fetching
customers,
okay,
wow
yeah.
We've
got
quite
a
number
of
issues
completed
since
our
our
last
sync,
then
live
clusters
and
snowplow
support
should
bring
your
own
cluster
I'll,
just
okay,
so
Alan
is
there
anything
you'd
like
to
I
feel
like
we've
covered
these
issues
before
yeah
we've
covered
these
last
time,
yeah
so
I
apologize
I
have
the
wrong
bookmark
yeah.
A
Old
yeah,
the
switchover
is
already
done
so
that
looks
way
out
of
date.
All
right,
so
we've
got
a
couple
for
front-end
improvements
for
The
Bachelor
designer.
C
A
Okay,
then,
let's
just
start
from
from
these
top
three,
then
you've
already
kind
of
follow-up
for
this.
But
this
was
there
anything
you
wanted
to
call
out
for
the
Missing
backgrounds.
C
Yeah
the
solution
isn't
ideal,
we're
injecting
onto
the
Hamel
bread
crumbs
is
the
way
we're
doing
it
right
now.
We're
waiting
on
foundation's
work
with
coding
in
broken
view,
Ruby
view
component
and
various
other
gitlab
UI
tasks,
in
the
hopes
that
we
can
move
this
away
from
that
injection
approach
into
a
more
stable
approach,
hopefully
using
a
shared
view
component
or
some
other
derivative,
but.
B
A
Does
work
yeah
yeah
we're
doing
what
we
can
to
get
it
done
so
yeah,
some
some
long-term
solutions
for
sure
in
store,
and
then
we've
got
two
issues
from
Jan
for
analytics
dashboards
alerts
were
made
after
the
user
leaves
the
page
and
the
being
able
to
search
available
visualizations
from
the
back
end
of
the
dashboard
designer.
A
So
we're
gonna
see
those
get
completed
but
yeah.
If,
unless
anyone
has
anything
they'd
like
to
add
for
those
I
think
that
about
concludes.
B
I
just
wanted
to
create
some
time
and
space
if
anybody
had
questions
or
wanted
to
talk
synchronously
about
the
direction
update
that
I
mentioned
yesterday
in
the
section
call
just
better
connecting
that
longer
term
vision
of
you
know
gitlab
as
an
analytics
platform
or
a
really
usage
platform,
understanding
what
users
are
doing
and
how
effective
the
code
for
shipping
in
his
back
to
what
we're
doing
today,
which
is
really
quantitative
analysis
on
events
of
age,
use
things
like
that.
C
A
Thanks
for
doing
that,
again,
Jess
yeah
I
think
it's
great
update
for
the
for
the
where
we're
at
this
thus
far
awesome.
B
I'll
be
looking
to
get
that
merch
in
the
next
day
or
so,
but
I'll
leave.
You
know
another
24
hours.
If
there's
any
other
sponsor
comments
on
Mr
and
leave
them
there,
that's
going
to
be
the
best
way
to
get
my
attention
cool.
Moving
on
to
number
three,
the
user
story,
map
for
usage.
So
thank
you.
Everybody
who
drops
tasks
in
to
do
that.
That
was
really
helpful
in
kind
of
some
expansive
thinking
about
what
are
the
tasks
that
a
user
would
have
in
understanding
what
their
usage
is.
B
It
also
opened
up
a
lot
more
questions
for
me
and
I
think
Kevin
to
explore
in
talking
with
our
friends
and
fulfillment
about
how
is
the
user
gonna
kind
of
understand?
They
need
to
go.
Look
at
usage.
What's
going
to
trigger
that,
because
I
think
it's
a
different
use
case
from
what
I'm
used
to
seeing
for
someone
who's
going
to
look
at
usage
quota.
I
can't
start
a
pipeline
because
I'm
out
of
the
I
minutes,
I
need
to
figure
out.
B
What's
going
on
that's
kind
of
the
first
step
that
I'm
used
to
that's
not
probably
going
to
be
the
case
for
product
analytics.
Instead,
it
will
be
a
you
know.
You've
used
all
of
this
over
the
course
of
the
month.
Here's
potentially
a
bill
now
they're
going
to
go,
look
and
see
whoa,
what's
going
on
here,
so
just
a
different
approach
to
the
use
case,
but
definitely
lifting
out
all
those
tasks
to
help
expose
that
assumptions
that
we
need
to
go
validate.
B
We
go
to
start
building
some
of
that
with
fulfillment,
so
that's
been
really
great
but
wanted
to
get
some
feedback
from
the
team
or
answer
any
questions
about
the
flow
so
far,
I
updated
it
a
little
more
yesterday.
I'll
continue
to
do
so
today
to
kind
of
break
things
out
towards
First
Slice,
with
a
learning
goal,
and
that
might
be
research
that
might
be
build
and
then
we'll
go
route,
creating
the
issues
to
build.
B
B
That's
the
terminology
that
I've
been
using
for
the
the
clickhouse
cluster,
everything
that
stood
up
today.
Everyone
will
be
using
that
until
we
get
to
bring
your
own
cluster,
so
the
way
that
we're
approaching
the
billing
is
probably
going
to
be
in
this
is
still
TBD
that
you
pay
if
you're
using
that
event
cluster
for
us
to
process.
The
events,
that's
very
in
line
with
what
the
rest
of
the
industry
is
doing.
A
All
right,
sorry,
so
you
you
find
a
change,
how
we
refer
to
it
or
you
want
us
to
change
the
analytics
stack,
Amy.
A
B
Happen
with
your
one
name:
I'll,
just
I'll
change
my
verbiage
to
analytics
stack
so
that
we're
all
using
the
same
language
and
as
we
get
closer
to
GA.
If
that
needs
to
change,
then
we
can
make
a
holistic
change,
but
I'll
I'll
make
a
switch
to
use
the
wording
that
we've
already
been
using
to
call
it.
The
product
empathic
stack.
A
Okay,
I'm
not
opposed
to
event.
Cluster
I
mean
it
does
make
a
lot
of
sense.
I
just
think
we
need
to
make
sure
that,
like
in
terms
of
Performing,
like
queries
and
reading
from
it
from
the
cubesata,
that
is
what
we're
happy
with,
but
anyways
I'm,
not
again
I'm,
not
super
I.
Don't
care
either
way.
I
just
want
to
make
sure
that
yeah
we're
going
to
refer
to
it,
and
it's
just
it's
about
one
thing.
So,
yeah
thanks
rob
you
had
something.
C
Firstly,
I
appreciate
James
you
setting
up
that
moral
user
story
map
and
giving
clear
Direction
and
instruction
to
what
we
needed
to
do
with
it.
That
was
very
helpful.
My
in
terms
of
moral
usage
works
fine
feels
like
a
really
nice
tool
for
getting
out
of
faults
just
dumped
onto
a
page.
The
one
downside
I
have
is
I,
think
product
and
design
get
more
neural
accounts,
but
engineering
doesn't
so
I,
don't
get
any
notifications
or
any
kind
of
indication
that
changes
happen.
C
So
I'm
very
much
looking
to
you
and
Kevin
to
tell
us
tell
me
or
us
more
broadly,
this
has
changed.
We
need
you
to
do
this
by
then.
This
is
what
you
need
to
do,
because
otherwise
I'm
not
going
to
remember
to
constantly
go
back
and
keep
an
eye
on
it
and
look
at
it,
because
I
I,
don't
remember
much
normally
so
yeah
I
think
I
more
broadly
I'm.
Looking
at
waiting
to
hear
what
the
next
steps
are.
C
B
Okay,
let's
get
feedback
I'll
I'll,
add
to
my
process
more
pings,
because
yeah
I
know
that
not
everyone
has
an
account
in
there.
That's
going
to
notify
them.
If
there's
a
comment
or
a
question
or
a
change
to
make
sure
it
check-ins
and
I'll
try
to
do
some
better
readouts
async
for
the
team
through
or
quick
unfiltered
videos.
So
you
can
get
an
update
that
way
as
well.
C
Yeah,
thank
you.
Do
we
want
to
start
for
those
without
an
account?
Do
we
want
to
start
tagging
the
responses
we
give
with
our
names
like
we're
doing
in
the
Google
Doc
just
to
allow
I?
Guess
we
don't
need
an
immunity?
C
Once
we've
got
that
now,
we've
got
the
all
the
dumb
ideas
and
good
ideas
and
all
the
other
ideas
on
the
page
we
can
I
guess
we
should
start
making
it
easier
to
see
who's
conversing
and
what
they're
saying
yeah,
maybe.
B
B
Cool
it
looks
like
Dennis,
you
have
0.3
C.
A
Yeah,
so
I
was
just
curious,
like
we're
working
on
the
user
story,
mapping
and
you
were
saying
like
we're,
trying
to
figure
out
what
to
research
or
build
I,
believe
I,
assume
or
I
believe
you've
already
started
talking
with
the
filament,
but
I
guess
like
at
what
point
do
we
kind
of
like
present
to
like
them
all
right
like
here's?
What
we
want
and
you
know
what
can
fulfillment
provide,
or
you
know
what
or
and
then
what
do
we
have
to
do
to
kind
of
help
like
meet
them
in
the
middle.
B
So
two
fronts
there
one
is
this
usage,
part
and
I,
don't
know.
What's
going
to
live
in
customers,
dot,
I,
don't
know.
B
What's
going
to
look
exactly
in
gitlab
I
started
the
conversation
in
the
Fulfillment
slack
Channel
today,
I'm
gonna
have
a
coffee
chat
with
product
manager
and
then
I'll
start
an
issue
outlying
outlining
some
of
the
work
that
we
need
to
do
so
that's
kind
of
one
side
of
things
on
the
other
side
is
then
the
billing
and
the
pricing
side,
where
we're
at
in
that
process
is
that
I've
pretty
much
got
a
pricing
proposal,
wrap
yeah
kind
of
review
with
Sam
and
Justin
next
and
then
we'll
review
with
pricing
team
so
that
we
can
move
forward.
B
Then
another
round
of
conversations
with
lymphoma
then
happens
at
that
point
of
how
do
we
work
within
to
get
that
building
done?
What
do
we
need
to
do
on
the
product
analytics
backside
to
count
those
widgets
that
were
charging
based
on.
A
B
A
For
sure,
and
and
as
we
touched
on
before,
with
with
beta
that'll,
be
the
set
at
the
same
time,
we're
doing
load,
testing
and
really
trying
to
understand
the
costs
and
having
real
figures
behind
that
so
it'll.
It
should
dovetail
nicely
once
we
start
to
build
some
of
that
functionality
and
then
make
it
make
it
available
to
as
we
prep
for
GA
that
we
yeah.
We
have
all
those
questions
answered,
but
yes,
definitely
great
to
hear
we're
already,
starting
the
conversation
with
fulfillment,
but
yeah
I'm
sure
we'll
be
touching
base
with
them.
B
Cool
that
wraps
up
my
agenda
items.
Does
anyone
have
any
show
and
tell
or
anything
else,
they'd
like
to
share.
A
All
right,
then,
that
wraps
things
up,
it's
good
to
see
everybody
happy
Tuesday
another
it's
morning
afternoon
or
evening
for
you
and
hope
to
see
everyone
again
soon.