►
From YouTube: 2023-04-04 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
April
4th
analytics
group,
sync
about
analytics
groupsync.
Let's
go
ahead
and
take
a
look
at
the
billboard.
A
Cool,
so
the
environment
connection
for
the
Clusters
is
on
hold
pending
the
snowplow
integration,
which
we'll
talk
about
a
little
bit
more
later.
In
this
meeting,
we've
got
updating
the
schema
to
remove
specific
referrals
product
analytics
on
element,
which
is
wait.
Sorry,
I'm
on
the
wrong
side,
so
logging
is
something
I'm
still
working
on
Kevin's
got
an
open
issue
for
that
I,
don't
think
he's
joined
the
call
and
then
Rob
you've
got
output,
incorrect,
visualization
definition,
nothing
to
say
about
this
still
open
or
anything.
You
want.
B
To
call
it
nothing
to
say,
I've
not
dived
into
it,
just
because
I'm
on
high
priority
items
yeah
at
the
minute.
A
Great
I
just
pulled
this
one
into
the
Milestone,
so
this
is
updating
our
product
analytics
worker
to
integrate
with
the
snowplows
configurator
service
instead
of
Jitsu,
so
making
sure
that
we're
ready
to
receive
events
and
everything
in
the
stack
set
up
to
do
so
so
that
is
I'll
still
shows
his
block.
So
I'll
fix
that,
but
that's
ready
to
pick
up
or
at
least
start
kind
of
putting
together
the
implementation
plan
from
the
back
end
side
of
things
other
than
that
Hey
Kevin,
good
timing.
A
C
No,
no
I
believe
we
have
a
path
forward
that
just
kind
of
need
to
go
to
it,
got
it.
A
Cool,
let's
move
on
then
in
terms
of
locked
issues.
Is
there
anything
we
want
to
call
it
here?
You
know
I,
think
they're.
All
yours.
D
Sure
yeah
I
have
some
updates.
The
Fitch
dashboard
configuration
from
the
back
end
I've
gotten
some
feedback,
thanks
to
Ellen,
for
linking
me
to
the
equal
like
issues
for
the
back
end
with
this
I.
Do
wonder
if
we
we
can
technically
I.
Think
I
can
unblock
this
and
we
could
technically
start
with
this
like
in
the
next
following
or
future
Milestones.
But
I
do
wonder
if
we
should
wait
to
First
consolidate
the
storage
locations,
because
that
means
we
might
have
to
do
work
again.
A
D
Yeah
so
I'll
I'm,
just
calling
that
out.
I'll
also
noted
on
the
issue.
The
next
following
three
ones,
I
think
are
all
related
to
the
graphql
bug
where
that
is
blocking
my
Mr,
because
I'm
just
remembering.
D
Because
waiting
for
events
isn't
being
returned
when
cube
throws
a
no
database
error.
I
think
Alan
just
has
a
merge
request
that
fixes
that
that
is
currently
passing
through
the
merge
pipeline.
So
once
that
is
merged,
I'll
confirm
it
and
I
think
then
everything
can
be
unblocked.
A
E
Not
for
now
so
I'm,
just
starting
out
with
the
draft
for
that
and
I
think
I
will
reach
out
to
to
Yan
with
some
questions
or
clarification
to
see
created
the
issue.
Okay,.
A
F
Yeah,
sorry,
that
should
be
in
review.
I've
got
the
Mr
Brave
to
go
I'm,
just
kind
of
testing
it
and
then
submitting
it
to
review
great.
A
Max
anything
with
the
keep
schemas
for
snowplow
generated
columns.
G
I'm
not
sure
I
thought
that
was
done,
but
I'm
wondering
if
there's
a
reason
why
it's
not
there.
Okay
I
will
have
to
double
check
but
I'm
pretty
sure
the
the
updated
Cube
schemas
are
merged
in.
G
A
Good
cool
and
then
I,
don't
know
if
Hot
Wheels
jumped
on
the
car
yet
so
he
has
a
follow-up
for
saving
custom
dashboards,
but
we
can
check
in
on
that
later
and
then
Rob
you've
got
the
next
two
issues
in
Dev.
Anything
yeah.
B
I
have
proof
of
Concepts.
Both
of
these
I've
had
some
great
feedback
from
everyone.
So
thank
you
very
much
for
chiming
in
this
is
very
much
an
area
of
the
code
of
work
that
I'm
not
super
familiar
with,
but
I'm
learning
as
I
go
so
hopefully,
I
should
have
these
in
at
least
one
of
these
in
review
by
the
end
of
the
day,
if
not
two
fingers
crossed.
A
Nice
cool,
as
far
as
what's
in
review,
as
mentioned
we're
holding
on
the
deployments
until
the
snowplanet
integration
work
is
done.
Then
we
can
start
going
through
Dev
staging
and
production
verifying
it
as
we
go
along.
A
A
This
is
ready
to
go
so
add
that
to
that
this
one
was
just
moved,
and
then
we
have
verification
for
consolidating
pod
analytics,
analytics
feature.
Flags
I
think
we
have
to
actually
still
separate
one
out
and
we
can
double
check
that
later,
with
allele
you've
got
add
empty
States
and
panels
from
L
win,
which
is
in
verification
and
then
Alan.
You
have
the
remaining
two
issues
as
far
as,
what's
in
verification
anything
to
call
out
here.
F
A
F
A
A
Cool
then
Ellen
has
fixed
a
couple
of
bugs
here
where
line
chart
visualization
tax
disease
don't
start
at
zero,
and
the
visualization
designer
should
fail
gracefully
when
the
cube
data
fails
to
load.
They've
also
got
a
application
setting
for
the
collector
host
now,
so
our
instrumentation
documentation
should
be
usable
in
terms
of
copy
and
pasting
it
directly
and
then
the
snow
plot
collector
is
officially
inside
of
our
project
analytics
cluster.
A
So
as
soon
as
we
wrap
up
the
integration
work,
we
can
start
beginning
our
plan
for
switching
over
to
snowplow
so
that
about
wraps
up
sorry
I've
been
checking
chat.
You
added
an
issue
Max
that
you
were
working
on.
Yes,
that's
right,
cool
anything
to
call
out
here.
G
Other
than
that
I've
wasted
three
hours
today
on
a
really
really
simple
bug
where
I
updated
the
clickhouse
password
and
didn't
restart
the
Pod
and
spent
literally
hours
trying
to
figure
out
why
I
couldn't
log
in
so
it's
been
a
learning
experience.
That's
for
sure,
I
should
I'm
going
to
have
the
approve
a
concept,
probably
working
some
way
during
tomorrow.
My
working
day
sounds.
A
We'll
have
to
throw
that
perhaps
in
the
documentation
somewhere
cool
so
that
wraps
up
the
billboard
review.
Unless
there's
anything
else.
Anyone
wanted
to
call
out
all
right
add
a
quick
kind
of
wanted
to
pull
the
group
on
like
anything
that
we
might
be
missing
in
terms
of
the
snowplow
rollover.
A
So
we
can
get
that
all
updated
and
good
to
go,
because
as
soon
as
we
do
that,
then
we
actually
can
figure
out
how
we're
going
to
operationalize
everything
and
that
will
give
us
Clarity
in
terms
of
what
we
can
move
forward.
With
with,
like
the
remaining
back
in
front
of
work.
We'd
like
to
do
so
I'm
just
kind
of
wanted
to
pull
the
group
and
it
could
be
async
or
it
could
be
here.
A
But
if
I'm
missing
anything
in
terms
of
what
needs
to
be
updated,
and
so
we
can
make
sure
that
we
have
issues
for
everything,
I.
Think
for
updating
the
snowplug
updating
back
infras
notebook
configurator.
We
have
an
issue
there.
A
cube
schema
is
already
there
as
we
reviewed
on
the
billboard,
but
for
the
outboarding
flow
and
like
making
sure
that
we
like
are
able
to
switch
everything
over.
A
That
would
be
dependent
on
what
is
changing
on
the
back
end,
as
well
as
like
making
sure
that
we
have
feature
five
for
everything
so
that
we,
we
don't
flip
things
over
when
snowplow
isn't
ready.
So
Rob
us
all.
You
have
a
comment
here.
B
Yeah
I
need
to
say
that
the
onboarding
we
have
a
graphical
endpoint
that
the
front
end
makes
a
mutation
request
to
so
as
long
as
the
input
and
output
of
that
is
still
identical,
then
there's
nothing
for
front
end
to
do.
It
should
just
work.
So
as
long
as
the
back
end
flicks
reflect
to
toggle
between
the
two,
it
should
be
seamless.
A
Sounds
good,
we
are
using
an
app
ID,
so
we
could
bring
those
over
as
far
as
the
setup
process.
A
The
only
thing
is
is
that
we
would
need
to
update
the
SDK
on
any
of
the
like
currently
running
projects,
so
that
it
will
start
sending
events
to
snowplow
in
the
snow
plow
format.
Instead.
A
D
A
You
have
a
comment
here:
do
you
want
a
localizer
should
I
sure.
D
It's
very
minor,
but
the
front
end
does
specifically
reference
the
Jitsu
key
in
the
query
for
the
instrumentation
details,
so
we'll
just
need
to
rename
that
to
app
ID,
for
example,
but
that's
super
small
yeah.