►
From YouTube: 2023-06-20 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
Hey
everyone
welcome
to
the
July
20th
product,
analytics
group
sync,
since
we're
a
little
bit
low
in
attendance
today.
We
think
we're
just
going
to
kind
of
go
around
and
just
kind
of
share
what
we've
been
focused
on:
James
and
James
Allen
and
myself,
and
we
can
go
from
there
and
then
just
work
through
the
agenda.
A
I'm
happy
to
start
so
Focus
remains
on
infrastructure.
As
we
saw
last
Friday,
we
launched
snowplow
support
for
production,
so
existing
projects
have
to
re-initiate
the
onboarding
process,
but
any
events
collected
now
and
all
the
and
the
enrichment
and
all
the
schemas
running
off
of
production
are
now
using
snowplows.
That's
exciting,
I
think
we're
still
kind
of
catching
some
possible
bugs
to
look
into
so
any
support.
A
There
would
be
much
appreciated
as
far
as
what
I'm
looking
at
next
I'm
continuing
to
work
on
click
house,
hardening
and
also
working
with
analytics
instrumentation
and
we'll
just
call
it
three
different
names
there,
but
working
with
their
group
as
well
to
kind
of
secure
the
front
end
part
of
our
stack,
so
snowplow
Kafka
and
the
events
getting
into
click
house
just
to
make
sure
we
have
everything
buttoned
up
as
far
as
security
is
concerned,
so
we
can
make
sure
we
get
official
approval
to
to
launching
the
the
actual
production
environment.
A
At
the
same
time,
you
know
Helio
and
I
are
kind
of
focused
on
how
we
can
separate
click
house
from
the
rest
of
the
cluster
and
how
we're
going
to
scale
that
and
that'll,
hopefully
give
be
good
preparation
for
us
to
instrument.com,
which
I
think
we
already
at
this
point
have
legal
approval
to
move
forward
with.
So
it's
really
just
a
matter
of
analytics
instrumentation
now
this
is
just
kind
of
sharing
what's
going
on,
but
analytics
instrumentation
in
terms
of
the
unified
interface
to
be
able
to
send
us
events.
A
In
addition
to
all,
there
are
other
ways
of
collecting
events
and
then
making
sure
that
we
have
a
separate
cluster
to
connect,
specifically
the
gitlab
project
too,
which
will
help
us
not
only
test
bring
your
own
cluster,
but
also
make
sure
that
we
isolate
that
level
of
traffic
when
we
are
still
figuring
out,
load,
testing
and
things
like
that
from
you
know,
external
customers,
which
we
hope
to
onboard
soon
and
then
it'll
also
be
a
great
way
for
us
to
one
get
better
at
scaling
the
services,
as
well
as
doing
cost
modeling
and
thing
things
like
weight
limiting
and
such
and
go
from
there
so
exciting
stuff
coming
up
in
the
next
few
Milestones
I.
A
Think
but
yeah.
Definitely
that's
what
my
focus
is
for
as
far
as
the
infrastructure
stuff
concerned.
Who
wants
to
go
next.
B
B
In
review,
I've
been.
B
B
Is
the
dedicated
analytics
settings
page,
which
is
mostly
all
there
I'm,
just
stuck
on
a
couple
of
things
which
I'm
catching
up
with
Helen,
hopefully
today
to
help
me
through
those
so
yeah?
That's
progressing
well
as
well.
B
C
Cool
on
my
side,
yeah
working
with
internal
stakeholders
or
employer
users
to
try
to
get
things
launched
and
onboarded,
and
thank
you
for
helping
on
pajama's
site,
exciting
to
see
progress.
There
I've
got
a
check-in
scheduled
with
those
folks,
a
couple
of
them
between
now
and
the
end
of
our
experimental
days
and
then
continuing
to
try
to
engage
with
field
team
and
with
a
couple
of
customer
customers
who
have
expressed
interest
to
get
them
on,
boarded
I.
C
A
Awesome
that
was
exciting
and
then,
as
far
as
agenda
points,
James
you've
got
the
next
one.
C
So
I
wanted
to
talk
just
a
little
bit
about
what's
next
after
the
experiment
and
some
of
the
goals
of
work
of
the
Beta
release,
which
I'm
going
to
share
my
screen
just
so
I'm,
not
blabbering
as
much
so
goals
for
beta.
The
purpose
of
the
beta
is
to
identify
potential
issues
bugs
or
edge
cases
with
their
features.
That
would
prevent
us
from
being
ready
for
production
grade
usage
and
probably
opening
up
for
the
ga,
so
we're
going
to
exit
criteria.
C
I
need
to
put
a
date
on
that,
but
we're
gonna
do
the
same
thing
that
we're
doing
with
experiment
of
six
weeks
after
we
onboard
we're
going
to
kind
of
close
it
off
and
say:
hey
the
beta
part
is
done.
We're
not
onboarding
anybody
new,
specifically
and
get
ready
for
GA.
Take
a
look,
learn,
math
and
move
forward.
C
As
far
as
the
actual
user
stuff
goes,
we're
pretty
much
where
we're
at
with
our
default
dashboards,
Kevin
and
I
will
continue
to
work
to
validate
the
custom,
dashboard
creation,
the
visualization
Designer
work,
that's
more
admin,
Aegis
or
opportunistic
that
we
would
add
in,
but
really
the
focus
is
on
getting
those
first
sdks
out
getting
this
available
for
users
and
doing
the
Strat
testing
through
the
beta.
So
that's
really
the
focus
and
what
we're
looking
at
next
click.
The
stop
share.
C
So
then,
beyond
that,
some
of
the
validation
work
that
we're
doing
now,
Kevin
and
I
did
some
interviews
last
week
moderated
interviews
with
internal
stakeholders
on
the
hack
of
creating
a
custom
dashboard
users
walking
through
that
hello,
that
great
feedback
from
them,
which
we
would
expect
from
moderated
even
in
an
Earl
moderated
panel
or
discussion
rather,
and
then
we're
going
to
unmoderate
it
this
week
using
user
typing.
C
So
we're
excited
to
see
what
the
the
feedback
is
there
as
well,
as
can
they
complete
the
task
and
if
they
do
we're
going
to
move
forward
with
that
feature,
we're
going
to
look
to
scope
it
down
or
continue
to
try
to
scope
it
down
so
that
we
can
get
it
done
pretty
quickly
and
get
it
out
there
and
available
and
then,
after
that,
I'm
going
to
be
looking
at
the
product
analytics
visualization
designer
and
getting
users
through
that
blow
making
sure
that
the
ux
is
really
nice
and
tight,
and
the
process
that
we're
going
through
is
a
pretty
exciting
one
of
trying
to
very
rapidly
iterate
through
these
prototypes
and
use
user
feedback
really
quickly.
C
It'll,
look
to
get
engineered
more
involved
in
that
process
as
well.
It
shouldn't
be
just
product
and
design
or
just
design
or
just
product
it'd,
be
great
to
have
kind
of
a
trio
of
sorts,
and
so
we'll
continue
to
share
the
devtep
recording.
But
I'll
try
to
be
more
proactive
about
letting
the
group
know
when
we
have
moderated
discussions,
we're
putting
together
an
asynchronous
or
synchronous
kind
of
discussion
around.
What
did
we
learn?
What
were
the
insights?
How
could
we
iterate
next
and
get
through
those
Cycles
really
quickly
with
all
of
us
weighing
in.
A
No
that'll
be
good,
especially
since
you
know
these
are
already
partial
pieces.
We've
built
and
really
there's
already
some
functional
ux
around
it
and
it'll
be
good
to
get
Engineers
input
in
terms
of
you
know,
potential
technical
constraints
or
just
things
that
we
need
to
consider.
You
know
with
what's
built
and
what
we
want
to
steer
it
towards
as
well
based
on
the
feedback,
absolutely
cool.
A
So
I
mean,
of
course,
I
think
every
week
I've
been
telling
everybody
we're
almost
there
we're
almost
there
we're
trying
to
get
our
external
customers
there
and
obviously
there's
steps
still
that
we
trying
to
buy
enough.
So
we
can
stay
with
confidence
that
you
know
we're
customers,
customers
data
is
safe
things
like
that,
but
at
the
same
time
I
think
there
are
opportunities
for
us
to
just
continue.
James
you
and
I
have
been
having
conversations
I've
been
talking
to
busty
as
well,
and
you
know
just
anyone.
A
Basically
I
can,
on
my
little
world
European
tour
of
gitlab
team
members,
I'm
also
trying
to
spread
the
word
and
get
generate
some
excitement
there
and
so
getting
pajamas.
You
know
out
of
the
co-working
day
yesterday
and
I
think
the
Memoir
hopefully
should
be
merged.
Yet
it's
not
officially
being
instrumented,
but
we
got
it
done.
It
was
great
to
actually
just
sit
down
and
you
know
have
IPS
I
just
told
them
go
to
this:
go
to
go
to
analytics
and
dashboards
and
then
just
follow
the
flow
and
see
what
happens.
A
So.
It
was
also
just
good
to
see
you
know
in
my
own
way,
just
like
how
that
flow
works
and
how
well
it
does
at
the
same
time,
I
think,
there's
a
you
know
more
opportunities
for
us
to
instrument
internally
and
just
really
use
a
lot
of
you
know:
production
like
and
once
weget.com
and
really
iacl
production
environment
applications
to
really
help
us
validate
and
figure
out.
I'm
already
thinking
like
you
know,
obviously
we're
in
the
beta
phase.
We
want
to
polish
things
that
I
can
already
see.
A
A
But
you
always
see
just
one
single
day
point
for
the
for
the
one
day
that
you
collected
data
so,
like
you
know,
I
think
having
that
abundance
of
existing
projects
to
like
really
balance
the
stuff
towards
will
be
exciting,
but
also
help
us
focus
on,
like
things,
topics
that
we
haven't
really
explored
yet
in
terms
of
like
making
sure
that
we're
happy
with
the
taxonomy,
with
all
the
different
sdks
that
we're
able
to
collect
events
from
as
well
as
just
making
sure
that
we
can
focus
on
event
tracking
and
actually
have
that
workflow
out
like
Define
in
terms
of
what
are
we
looking
to
provide
to
users
as
part
of
the
shared
environment?
A
Or
what
is
the
appeal
for
people
who
want
to
run
their
self-managed
cluster
to
be
able
to
pull
whatever
they
want
out
of
custom
events?
Obviously,
if
you've
used
mix
panel
or
amplitude,
where
you
have
you
know,
collect
every
all
the
data,
but
then
you
can
clear
everything,
but
you
go.
You
know
a
small
typo
can
just
make
it
a
huge
mess
like
we
have
to
find
where,
where
is
the
where's?
The
line
that
we're
drawing
for
that?
A
But
you
know
just
calling
out
a
few
of
the
other
things
we
want
to
potentially
not
potentially
but
like
plan
to
instrument
for
things
like
the
external
handbook
version
have
metrics
dictionary
from
that
analytics.
Instrumentation
re-instrument,
the
internal
handbook.
The
Mr
is
already
there,
but
it's
just
waiting
for
review.
A
Those
already
have
a
pretty
good
like
sizable
amount
of
traffic,
and
then
we
start
getting
into
like
the
documentation
website,
which
I
think
is
another
like
200
000
events
a
day
or
something
like
that.
Pajamas
is
pending
soon
and
obviously
we're
very
focused
on
trying
to
figure
out
how
to
get.com
going
in
a
way
that
is
scalable,
and
you
know,
Boston
and
I
have
been
having
conversations
about
that
as
well.
A
In
terms
of
yeah,
we
want
to
be
able
to
take
all
the
pageviews
from.com
and
eventually
the
back
end
data,
and
and
do
it
in
a
way
where
we
can
just
slowly
be
able
to
ingest
all
that
data
at
once,
because
we're
talking
I
think
a
total
of
70
million
events
a
day
which
will
be
tricky
to
scale
to
be
able
to
do
that.
But
I
think
it's
also
I.
A
A
While
we
will
have
that
kind
of
feature,
flag
percentage,
gate
that
shouldn't
stop
us
from
using
another
flag
to
be
able
to
just
say:
hey
whatever
AI
enablements
building
a
bunch
of
stuff
was
talking
to
someone
who's
close
to
like
pipeline
execution,
and
they
want
to
attract
things
like
merge
trains,
and
things
like
that,
like,
hopefully,
generating
excitement
to
kind
of
show
people
how
they
can
track.
A
Events
with
product
analytics
get
them
excited
start
to
show
them
that
you
know,
there's
no
there's
an
alternative
into
as
in
addition
to
what
we
already
used
to
track
metrics.
So
all
that
to
say
is:
we've
got
a
lot
more
coming,
not
just
internal
handbook
and
at
the
same
time
we
still
are
very
keen
to
get
customers
on
board,
but
I
think
there's
a
lot
to
look
forward
to,
even
with
just
the
amount
of
dog
food
that
we're
able
to
do
so.
A
C
A
And
it
all
kind
of
just
feeds
each
other,
like
you
know,
I
think
when
we
start
to
have
the
cut
like
get
in
front
of
customers
or
get
in
front
of,
like
you
know,
people
out
in
the
field
and
want
to
like
prove
that
we
can
handle
it.
It's
like
well
we're
running
it
on.com
and
we're
able
to
ingest
this
much
data,
at
least
so
I
think,
there's
a
lot
of
credibility
that
we
can
use
to
establish
by
just
the
amount
of
diet
food
in
that
we
could
do
yeah
for
sure
same.
A
So
that's
all
I
got
anyone
else
have
anything
they
want
to
share
or
we
can
give
everyone
15
minutes
back
all
right.
Well,
it's
good.
A
B
A
A
good
rest
of
your
Tuesday
have
a
good
rest
of
your
weekend,
as
always,
if
there's
something
that
I
haven't
looked
at
or
to
do
that,
you've
pinged
me
on
a
week
ago
and
please
feel
free
to
send
it
my
way.
Otherwise
have
a
good
rest
of
your
day
and
take
care
all.