►
From YouTube: 2023-03-14 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
March
14th
product
analytics
sync,
the
APAC
American
Edition-
that
we
also
have
our
loan
representative
from
the
Europe
as
well,
so
glad
to
have
you
we'll
go
ahead
and
get
started
then
with
the
billboard.
Hopefully,
everyone
can
see
my
screen
and
we'll
get
right
away
with
that.
So
first
up
an
open
issue
probably
needs
a
bit
more
definition,
but
we've
got
logging
as
something
we
want
to
focus
on
for
infrastructure.
A
As
we
approach
our
first
Alpha
customer
Max,
you've
done
some
work
around
like
oh
there's,
monitoring
anything
you
kind
of
want
to
speak
to
here.
B
Yeah,
so
it's
not,
as
you
said,
it's
not
super
well
defined
right
now,
but
it
was
more
a
case
of
figuring
out
what
we
can
do
so
yeah
standard
out
logging
for
all
of
our
kubernetes
parts
is
kind
of
working.
So
we
do
have
problems
we
can.
We
can
go
and
look
at
the
actual
logs
in
Google
console
I've
set
up
a
couple
of
monitoring
alerts,
so
high
CPU
usage
or
unexpected
restarts
of
kubernetes
PODS
will
show
up
in
the
new
infrared
alerts
channel
in
Slack.
B
So
far,
that's
shown
a
couple
of
sort
of
slightly
very,
very
short-lived
spikes
in
CPU
usage
in
Click
house,
but
nothing
of
any
major
concern
really.
The
next
step
is
to
see
if
we
can
get
the
standard
outlooks
into
our
standard.
Elasticsearch
kibana
sort
of
set
up
I'm,
not
sure
how
to
do
that.
Yet.
But
that's
the
next
step,
yeah.
A
And
that's
that's
kind
of
where
I
need
to
do
a
bit
more
work
on
defining
it.
So
for
those
that
aren't
aware,
we
use
elastic,
search,
log,
slash,
Cabana
or
I
think
we
also
might
use
foot
D
I'm,
not
really
sure,
actually
in
some
cases,
but
basically
just
a
way
for
us
to
actually
push
those
logs
into
a
central
location
so
that
we
can
report
on
them,
especially
because
in
some
cases
when
pods
disappear
and
the
logs
Disappear
With
It
it's
hard
to
kind
of
keep
track
of
everything.
A
So
it'd
be
good
to
like
have
that
ready
in
terms
of
how
infrastructure
at
gitlab
would
normally
expect
to
expect
these
services
to
be
able
to
log.
A
So
I'll
try
to
work
on
adding
a
little
bit
more
in
terms
of
definition
of
done,
so
that
we
can
at
least
see
if
we
need
to
separate
that
out
and
break
that
out
into
multiple
milestones
and
things
like
that.
But
yeah
awesome,
just
opening
up
design
making
sure
we're
not
missing
anything
is
to
need
an
assignee
and
chemical
is
not
online.
A
So
we
can
go
ahead
and
just
probably
just
go
past
this
and
see
if
where
we
can
get
support,
when
there's
capacity,
we
have
an
issue
for
removing
product
analytics,
specific
dashboard
listing,
which
I
believe
is
no
longer
blocked
since
we've
just
merged
in
a
lot
of
that
shared
listing
stuff.
But
we
can
of
all
about
my
async
with
Rob
there's
nothing
in
ready
for
development,
which
is
great,
considering
we
were
approaching
1511
and
then
for
in
Dev,
we've
got
the
blog
post
about
the
product,
analytics
internal
preview
Sam.
C
A
Great
all
right
and
then
we've
also
got
the
ad
product
analytics
application
setting
for
collect
to
host
doesn't
look
like
we've
had
a
recent
update
from
Julio,
so
I
guess.
B
It's
in
that's
in
my
court.
He
I
posted
to
me
for
my
10
review
earlier
when
I
had
one
comment
which
I've
not
responded
to,
but
I
think
I'll
be
merging
it
tomorrow.
B
A
C
A
Great
I,
don't
think
Tim's
on
the
call,
and
we
have
an
ad
dashboard
button,
which
I
think
is
has
been
merged.
But
you
follow
up
on
that
and
then
we've
got
a
follow-up
for
adding
a
future
spec
for
the
dashboards
visualization
designer.
Oh
and
you
have
these
issues
or
anything
you'd
like
to
call
out
for
this.
One.
A
Sounds
good
moving
on
to
in
review,
You've
also
got
the
column
chart
issue
anything
here.
C
A
Awesome
that'd
be
great
to
use
them
I
think
we
can
probably
throw
a
funnels
at
that
as
well
in
terms
of
visualizing
that
it's
got
the
next
one
I
haven't
been
able
to
get
to
this
one
and
I
closed
the
other
ones
which
I'll
speak
to
in
the
closed
column,
but
still
need
to
put
together
the
production
change
request
for
infrastructure
to
be
able
to
connect
these
two
environments.
A
One
thing
that's
hanging
up
is
that
they
may
or
may
not
recording,
but
they
need
to
change
the
credentials
to
be
specific
environment.
Specific,
so
I'd
like
to
do
that
before
I
connect
the
demonstration
clusters,
so
just
yeah
that
seems
like
a
minimum
bar
for
security.
A
Moving
on
we've
got
expect
violations
in
the
metric
chart.
Spec
I,
don't
believe
Lawrence
is
on
the
call,
so
we
can
move
on
unless
anyone
has
any
context
here
and
then
update,
chart
visualization
to
fill
the
panel
container,
which
is
assigned
to
yawn,
which
the
Mrs
to
fix
is
ready
and
it's
been
merged.
So
we
just
need
to
wait
for
the
gitlab
uip
packaged
version
to
be
pumped,
which
has
also
been
merged.
A
So
this
should
probably
be
in
verification,
but
I'll
follow
up
with
Beyond
on
that
the
other
two
issues
have
been
just
recently
moved
through
in
review,
so
I
think
we
can
move
on
to
verification
which
is
handle
if
the
dashboard
is
not
available
with
a404
solution.
See,
if
there's
anything
to
do
here,.
A
Doesn't
look
too,
it
doesn't
look
to
be
the
case,
so
all
right,
I'm,
looking
at
our
bookmark
for
close
issues,
we
have
panel
titles,
should
be
truncated
on
small
sizes,
which
means
we
are
probably
about
eight
issues
closed
since
then,
and
we
have
update
the
learner
setup
so
it
actually
publishes
the
packages
that
looks
like
it's
been
closed.
B
Not
massively
like
we
now
have
the
the
basic
sort
of
nuts
and
bolts
to
write.
Schema
specs
for
cube
I
haven't
written
a
huge
Suite
of
tests
since
we're
going
to
replace
Jitsu
soon
so
I'm
Keen
that
we
don't
test
specific
SQL
columns,
because
we
don't
know
if
they're
going
to
exist
soon,
but
once
we
make
that
transition,
then
it
should
be
relatively
easy
to
add.
Quite
a
few
specs
quite
quickly
and
they'll
run
on
CIS.
A
Cool
then
we
have
a
follow
to
add
qjs
to
renovate,
but
I
think
there's
an
update
that
Rob
has
put
async
but
I
believe
most,
if
not
all,
of
the
dependencies
that
we
care
about
in
robotic
analytics
are
now
added
to
renovate
bot,
so
I
think
we'll
get
to
that
update
in
a
sec
so
other
than
that
we
have
the
line
chart
which
does
not
fill
the
container
height
when
it
sets
Auto
I'm
gonna
assume
now
that
the
charts,
now,
at
least
for
the
line
chart,
fill
the
entire
container
height,
which
is
going
to
be
nice
for
kind
of
a
ux,
Polish
point
of
view
and
we've
also
removed
the
date
range
limit
for
the
analytics
dashboards,
which
we
had
said
previously
to
seven
days
and
30
30
days.
A
So
until
we
kind
of
start
identifying
performance
issues
or
constraints
that
we
actually
need
to
implement,
then
we
will
do
so
accordingly.
A
We've
also
got
the
product
analytics
dashboard
listing
with
the
new
shared
dashboards
listing
at
the
project
level.
So
this
is
what
I
was
referring
to
earlier.
As
far
as
the
new
dashboard
listing
I
believe
that
what
comes
after
this
is
just
making
sure
we
can
initiate
the
onboarding
process
from
this
new
area.
So
I
know
that
was
a
lot
of
merge
requests
and
refactoring
and
rebasing
from
a
lot
of
people.
So
I'm
glad
we
got
that
in
apart
from
that,
I
have
the
remaining
two
issues.
A
Data
persistence
is
now
set
up
in
the
Jesse
redis
service,
which
will
just
help,
keep
it
more
reliable
until
we
replace
it
with
snowplow
and
so
far,
everything's
looking
good
as
far
as
events
still
going
to
where
they
need
to
go,
and
then
this
one
has
just
been
closed
out,
because
we've
opened
new
issues
as
far
as
anything
that
needs
to
be
built
for
making
sure
that
we
read
customer
built
dashboards
correctly,
as
well
as
making
sure
that
we
Supply
the
pre-configured
ones
as
well,
so
that
wraps
up
our
billboard
review
unless
there's
anything.
A
I
need
to
add
the
bookmark,
but
I'll
do
that
after
I
just
wanted
to
call
out
the
1511
planning
issue.
I
know
some
of
the
team
has
been
asking
about
kind
of
what
to
pull
on
next,
and
so,
while
James,
Sam
and
I
are
working
to
kind
of
finalize
that
there
are
kind
of
some
top
priorities
there
that
some
people
have
already
been
pulling
in.
So
as
we
wrap
up
this
current
Milestone
feel
free
to
take
a
look
at
that.
A
At
the
same
time,
I
will
ping
everyone
who
hasn't
added
their
capacity
just
so
we
have
awareness
about
how
much
capacity
we're
going
to
have
for
1511
before
we
wrap
up
our
final
15.x
release.
Is
that
correct?
We're
going
to
16?
Oh
after
15,
11,
right,
yeah.
A
Exciting,
so
you
got
any
ideas
for
breaking
changes.
Now
is
the
time
other
than
in
there
just
kidding
we're
also
anyways,
all
right
wow.
This
is
gonna,
be
just
me
talking.
Almost
anyone
would
like
to
vocalize
the
show
and
tell
points
I'll
just
hold
for
a
few
seconds
there
well
I
drink
some
liquids.
B
I'm
happy
today,
if
you
want
Dennis,
thank
you
Max,
so
yeah
Rob
who's,
not
on
the
call
first
of
all
in
the
migration
to
share
dashboard
listening
is
now
complete
and
the
optimized
group
have
been
informed,
so
they
can
work
on
bringing
it
to
the
group
level
and
the
next
sort
of
stage.
B
My
understanding
of
this
process
is
that
there
was
a
lot
of
separate
Mrs
so
moving
the
onboarding
process
to
the
new
listing
and
also
from
Rob
all
front-end
team
members
are
now
assigned
by
the
renovate
to
version
Mrs
for
cube.js
and
grid
stack
npn
package
changes,
so
we
can
keep
the
libraries
up
to
date
without
doing
all
the
initial
legwork.
B
The
second
point
on
that
I'll
be
honest.
Didn't
make
a
lot
of
sense
to
me,
so
someone
would
like
to
explain
to
me
what
the
renovate
block
does
at
some
point.
I
would
appreciate
that.
A
Yeah
checks,
it's
a
pipeline,
you
can
run
or
script
externally.
You
can
run
where
it
checks
your
repositories,
current
versions
of
the
dependencies
you're
using
and
we'll
compare.
B
A
What's
currently
released
so
especially
for
things
like
security
updates
like
zero
days
and
things
like
that,
but,
of
course,
just
being
able
to
get
bug,
fixes
and
improvements
without
us
having
to
manually
check
it.
That's
what
renovate
Bots
for.