►
From YouTube: 2023-05-16 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
product
analytics
weekly
sync.
It
is
the
16th
of
May
and
I'll.
Kick
us
off
by
reviewing
the
billboard.
The
first
open
issue
we
have
here
is
designer
outputs,
incorrect,
visualization
definition.
Rob
I
see
your
sign
on
the
as
the
dri
on
this
we're
also
missing
a
workflow
label.
You
know
what
the
stats
is.
B
A
This
is
yeah
the
title
input.
A
Oh,
that's
not
a
worry,
I
think
this
is
also
related
to
one
of
Tim's
Mrs
that
we've
taken
over
about
saving
the
visualization,
because
once
we
have
that
figured
out
it's,
this
is
also
probably
going
to
be
solved.
B
A
Cool
then
the
16th
Milestone
Milestone
planning
for
program
analysts.
We
probably
don't
need
to
talk
about,
but
right
now
we
have
update
user
facing
product
analytics
docs
for
first
external
user
phase.
Anything.
You
would
like
to
note.
C
Yeah
I
think
that's
pretty
much
done.
I
have
one
Mr,
that's
waiting
verific
by
Dennis,
So
He
suggests
making
some
changes
to
a
diagram
and
with
that
I
think
it's
a
little
bit.
Okay,.
D
A
Yeah,
it's
it's
probably
going
to
be
that
when
we
implement
the
saving
of
the
visualization,
we'll
just
fix
this,
while
we're
doing
that.
Okay,.
D
A
It's
also
potentially
going
to
slip
because
that
other
issue
doesn't
have
anyone
I
think
working
on
it
right
now.
In
that
case,
we'll
just
slip
to
the
next.
A
Cool
and
planning
breakdown
Dennis,
you
have
upgrade
live
clusters
with
snow
plower,
Kafka
analytics
stack,
yeah.
D
So
this
is
unblocked.
I
am
currently
in
the
process
of
creating
different
infrastructure
issues
to
actually
update
Dev
dot,
staging
Dot
and
gitlab.com
to
connect
to
these
clusters
or
add
new
information
for
the
instance
of
production,
for
example,
it's
already
connected
using
the
existing
credentials.
We
just
need
to
add
the
snowplow
configurator
details
so
that
when
we
do
actually
switch
things
over
new
projects
will
be
able
to
go
through
that
onboarding
flow
and
use
the
snowplow
tracking.
D
F
Yes,
actually,
it
is
not
in
the
planning
breakdown,
there
were
multiple
options
for
implementation,
so
I
actually
had
the
talk
and
like
we
decided
to
in
in
development
now
I'm
working
on
it
yeah.
So
we
decided
to
use
the
Affinity
speakers
operator.
I
am
creating
some
Mr
for
it.
A
A
Dennis,
you
have
the
next
one
connective
and
staging
Club
environments
to
their
respective
clusters.
Yeah.
D
So
that's
related
to
the
one
issue
right.
We
just
went
over
so
I've
just
moved
that
into
in
Dev,
but
like
I
mentioned
we
just
have
to
now
that
we
have
the
clusters
for
each
environment.
We
just
need
to
connect
the
two
so
that
we
can
start.
You
know,
testing
things
out
in
Dev,
staging
and
stuff
like
that.
So
yeah.
B
Yeah
I'm,
so
damn
close
I
keep
getting
a
cracker.
Last
few
days
have
been
a
crop
dealing
with
snowplow
related
issues
as
I've
worked,
my
for
it
I've
noticed
little
bugs
and
little
problems
with
our
implementation,
which
yarn
and
Max
have
been
very
kindly
helping
me
verify
and
in
Max's
case
fixing.
So
I
appreciate
that
for
the
quick
turnaround
so
I'm
now
on
to
the
very
final
test
file
and
it's
going
to
be
out
for
review,
hopefully
in
an
hour
or
so
fingers
crossed.
A
Very
cool
max:
you
have
improved
management
of
Secrets
within
the
stack,
any
updates.
E
So
no
major
updates
from
last
week,
where
we
kind
of
proved
that
it
can
be
done
most
of
the
work
now
is
finding
the
right
people
to
get
us
our
own
OCTA
group
and
get
us
added
to
the
production.
Vault
I
had
some
movement
overnight
from
it,
but
I
need
to
ping
some
other
people
in
infra
to
get
an
approval
somewhere,
which
I've
done
so.
Hopefully,
progress
is
being
made,
but
slowly.
A
All
right
does
anyone
know
of
the
status
of
this
removed
just
related
front-end
code.
B
A
Gotcha
or
if
this
would
be
a
better
represented
block
then,
but
since
you
say
it's
also
kind
of
working
on
it,
I
guess
ndf
is
fine.
A
A
mixed
bag
Dennis,
you
have
the
next
one
connecting
Devon
staging.
D
A
Just
oh
yeah,
oh
yeah,
that
is,
that
is
the
one.
We
talked
about
sorry
about
that
and
then
this
is
also
the
one
that
we
already
talked
about.
Well,
the
first
two
interview
items
are
mine
at
say
visualization
as
panels
through
dashboard.
So
this
is
in
the
final
review
with
our
very
own
Rob
here,
thanks
so
much
for
your
feedback,
yeah.
A
If
Rob
is
happy
with
the
what
I
just
committed,
then
hopefully
this
gets
merged.
This
allows
us
to
it
provides
a
panel
with
a
list
of
all
the
available
visualizations,
both
built-in
and
custom,
and
allows
users
to
just
with
one
click
those
to
a
dashboard,
and
it
adds
it
in
a
new
panel,
very
quick
and
easy
and
then
with
a
recent
Mr.
Also
that
you
can
then
save
that
the
next
one
is
to
put
an
entry
point
to
the
dashboard
and
the
visualization
designer
behind
a
feature
flag.
A
So
what
this
is
doing
is
fighting
all
of
the
edits
and
creating
of
dashboards
and
visualizations
behind
a
feature
flag,
because
we
don't
want
to
ship
that
as
part
of
the
first
customer
preview
release.
A
B
No
I
told
everyone
that
I'm
doing
one
Mr
review
today,
I'm
working
on
my
own
Mr
for
once,
because
yesterday
was
entirely
Mr.
Reverse
I
will
be
dealing
with
these
tomorrow.
No.
A
G
A
Very
cool
we've
covered
this
one
yeah
we've
covered
this
one
thanks,
Dennis
and
then
we've
covered
this
one
as
well
verification
quite
a
lot
in
verification.
Alan.
You
have
three
issues
any
any
that
you
want
to
call
out.
G
All
of
these
are
waiting
for
snowplow
to
be
enabled
on
staging.
So
once
yeah,
once
we've
got,
snowplow
turned
on
everywhere
then
go
through
and
verify.
D
G
D
That's
related
to
the
change
requests
so
I
need
to
get
through,
but
then
we
can
verify
the
new
staging
so
I'm
effectively
blocking
these.
E
So
tracking
is
well
they're.
All
in
verification
now
just
went
from
this
merge
vote.
To
be
honest,
I
might
just
close
the
issues
anyway,
because
we
can't
verify
that
they're
working
until
the
next
service
thing
runs
anyway,
but
they've
been
tested
locally
and
doing
as
expected,
and
then
the
one
below
there
I
think
there
might
even
be
another
one
below
that
I
didn't
create
the
issue,
that's
why?
E
But
this
basically
we're
just
adding
into
the
dashboard
type
graphql
a
user-defined
field
so
that
the
front
end
can
see
whether
or
not
a
dashboard
is
custom
or
not,
and
additionally,
we've
added
the
slug
attribute
as
well.
So
you
can
see
the
slug
for
a
dashboard,
but
I
haven't
created
an
issue
for
that
they're,
both
verification
and
being
deployed.
As
we
speak
right,
that's.
A
Good
news
cool
moving
on
to
close,
let
me
get
the
bookmark
Groove
values
in
the
yaml
hey.
We
have
two
issues
this
one
already
covered.
As
I
said
you
can
now
add-in
dashboard,
but
it's
going
to
be
hidden
behind
the
feature
flag.
So
unless
you
have
that
enabled
you
can
see
this
one,
then
we
have
an
unassigned
issue
which
is
update,
project
analysis,
settings
to
match
the
latest
design
and
copy.
A
D
Yeah
so
sorry,
I'm,
just
like
in
the
middle
of
putting
this
plan
together,
yeah
I,
just
kind
of
wanted
to
I
posted
yesterday
on
slack
kind
of
where
we're
at
with
the
snowplow
switchover
so
effectively.
D
The
Clusters
are
snowplunk
capable
today
I'm
going
to
verify
that
they
are
receiving
events,
this
no
black,
collector
and
based
on
the
review
of
the
remaining
issues.
It
looks
like
we're
we're
once
we're
able
to
fetch
the
dashboard
from
the
back
end.
We
should
be
theoretically
able
to
enable
snowplow
support,
so
it's
good
we're
catching
all
these
issues
with
snowplow.
Now
so
that's
great
since
I'll
be
out.
D
As
I
mentioned,
we
still
need
to
wait
for
infrastructure
to
connect
gitlab
to
these
clusters,
but
I've
just
started
drafting
basically
the
plan
for
everyone
to
understand
like
what
needs
to
happen
so
that
we
can
turn
this
on
and
also
get
your
feedback
to
make
sure
I'm
not
missing
anything
but
I.
Think
at
this
point
we
are
able
to
start
at
least
having
project
manager,
project
owners
of
projects
that
are
currently
instrument
that
should
see
to
prepare
merge,
requests
to
start
using
the
new
version
of
the
SDK
which
sends
us
to
snowplow.
D
We
won't
have
the
app
IDs
yet,
though
I
might
be
able
to
prepare
that
ahead
of
time,
but
basically
the
plan
right
now
that
I've
spoken
to
Boston
over
analytics
instrumentation
about
is
we
will
have
to
shut
off
Jitsu
because
it
interferes
with
the
setup
process
for
snowplow
and
then
flip
the
snowplow
support
flag
on
run.
The
setup
project
flow
for
actually
I
was
just
thinking.
D
Part
of
the
plan
was
to
drop
all
the
databases,
but
then
you
know
like
rubber
ducking
with
with
the
seven
other
people,
but
basically
we
may
not
have
to
drop
all
the
databases,
because
if
we
drop
it
and
scale
down
Jitsu,
then
everyone
in
every
project
owner
could
just
go
through
the
onboarding
flow
again
and
get
an
app
ID
and
update
their
merge
requests.
That
might
be
easier.
D
So
thanks,
everybody
I
appreciate
your
feedback
on
that.
But
if
I
got
it
wrong,
then
please
let
me
know,
but
my
original
thought
process
was
a
lot.
A
lot
more
manual
in
terms
of
basically
Jitsu
creates
a
database
every
time
it
receives
an
event.
So
that's
why
we
need
to
scale
it
down
and
then
we
would
need
to
run
the
setup
project,
but
since
the
onboarding
flow
is
connected
to
that,
then
project
owners
can
do
that
themselves.
So
for
context,
that's
that
was
my
thought
process
anyways.
D
What
I've
detailed
is
the
general
plan
and
I'll
update
that
for
that
on
what
I
just
covered,
but
long
story
short
as
we're
able
to
start
enabling
snowplow
support,
but
there
will
be
a
cut
off
because
the
snow
snowplow
support
flag
is
not
is,
is
an
All
or
Nothing
thing.
D
So
when
we
start
when
we,
when
we
execute
this,
we
will
stop
collecting
events
from
Jitsu
and
then
we
will
have
to
project
owners
will
have
to
go
through
the
onboarding
step
again
to
reinstrument
their
applications,
so
yeah
be
sure
to
check
out
the
slack
message
if
you
haven't
yet
in
terms
of
just
the
context
of
what's
been
going
on
with
the
Clusters
here's
and
then
I'll
refine
this
plan
in
terms
of
how
we'll
actually
be
able
to
enable
it
from
the
sounds
of
things.
D
This
could
happen
while
I'm
out,
if
anyone
would
like
to
we,
can
coordinate
if
anyone
would
like
to
try
to
implement
this
outside.
Otherwise
we
can
try
to
implement
it
next
week
when
I'm
back,
but
we're
very
close
to
at
least
enabling
snowball
support.
So
that's
exciting
I
have
the
next
Point
as
well.
Please
check
out
the
16-1
planning
issue.
I
will
be
as
a
side
note.
D
I
will
be
out
of
office
starting
Thursday,
but
if
there
are
any
questions
regarding
any
engineering
related
issues
on
the
61
planning
issue,
please
let
me
know
I'd
love
to
clarify
that
before
right
now
and
that's
all
I've
got.
B
B
Just
one
there's
one
issue
which
I
think
is
assigned
to
Alan
at
the
minute,
but
it's
scheduled
for
16-1
that
is
currently
a
technically
a
blocker
for
front
end
to
be
fully
functional
because
it
prevents
the
implementation
flow
from
working
right
now.
D
B
It's
not
a
blocker
for
like
the
work
I'm
doing,
because
you
know
I
could
just
run
a
patch
and
what
not,
but
to
actually
fully
test
this
full
fly.
We'll
need
that
fixed
to
make
back-end
fully
feature
complete.
D
Yeah
that
makes
sense.
Alan.
Is
this
something
you
can
prioritize
like
I
guess
we
could
pull
it
into
160,
but
it'll
just
go
back
to
16-1,
but
since
it's
already
in
Dev
like,
can
you
make
sure
that
this
is
something
we
can
prioritize,
yeah
sure
about
the
others?
Awesome
yeah!
That's
thanks
for
calling
that
out.
Rob,
basically
I
just
wanted
to
make
sure
yeah
everything.
Soundcloud
support
was
ready
before
we
flipped
the
feature
flag
on
so
yeah.
This
is
a.
B
D
The
Focus
right
now
is
pre-built
dashboards,
anyways
and,
of
course,
this
still
doesn't
get
us
to
customers
so
like
basically
just
as
a
near-term
overview.
Once
we
get
snows
out
like
main
priorities,
gets
no
plus
support
running
in
production
and
then
second
is
what
we
need
to
do
to
get
out
to
customers
which
I'll
be
meeting
up
with
nulls,
and
if
he
has
any
questions,
please
be
feel
free
to
answer
those
but
yeah
small
steps.