►
From YouTube: 2023-02-07 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
Foreign
welcome
everyone
to
the
February
7th
project
analytics
group-
sync.
Hopefully
everyone
can
see
my
screen
some
thumbs
up.
Thank
you
cool,
so
I'm
just
going
to
go
through
the
list
of
open
issues.
For
now
we
have
product
analytics
to
gitlab
project
for
specific,
opt-in,
opt-in,
users,
some
action
items
here
actually
to
announce
it's
a
little
bit
more
wider
just
so
we
can
get
more
people
in
there
right
now.
A
I
think
there's
only
three
people
that
have
opted
in
including
this
group,
if
you're
interested
in
opting
and
so
that
we
can
collect
data
on
the
project
itself.
Please
feel
free
to
add
yourself
to
the
issue.
Description,
go
ahead
and
skip
over
the
59
planning
issue,
and
we've
got
filtering
sessions
by
date
range
those
exception.
I
believe
this
is
the
follow-up
out
of
Beyond's
work
for
the
date
range
dashboard
level,
control
Mac.
Is
there
anything
you
want
to
speak
to
yeah.
B
Pretty
move
workflow
into
in
Dev
because
I'm
in
the
process
of
attempting
to
fix
it
with
varying
levels
of
success,
so
yeah
this
is
narrowed.
It
down
to
the
problem
is
the
join
between
the
Jitsu,
attract
events
Cube
and
the
sessions,
one
because
it's
joining
them
with
a
greater
than
or
equal
to
condition
and
clickhouse
doesn't
support
that.
So
we
can't
do
it,
and
so
you
try
and
combine
a
session
data
with
Dimension
from
attract
event.
It
just
doesn't
work.
B
So
that's
because
I
followed
the
initial
Cube
tutorial
on
how
to
do
this,
which
is
not
good,
we'll
just
click
out
so
I'm
currently
scouring
the
clickhouse
documentation
for
a
more
native
friendly
way
to
do
this,
so
yeah
I'm
in
Dev,
trying
to
find
a
solution
for
this
got.
A
It
cool
this
issue
is
for
actually
defining
a
collector
host
so
that
we
can
display
that
for
instrument
annotation
details
I
think
we
covered
that
last
week,
so
anyone
here
yet
and
I
also
need
to
get
the
emerge
request
where
we
kind
of
hack
that
together
for
the
internal
preview
working,
so
we
can
correct
that
at
least
immediately.
A
We
have
a
new
issue
just
for
discussion
here
about
the
query.
Designer
I
think
we
have
an
agenda
point,
so
we
can
come
back
to
that
later,
so
we
can
go
ahead
and
move
to
planning
breakdown.
So
our
first
issue
here
is
the
API
to
retrieve
the
state
of
a
product
analytics
stack,
monitor
anything
you'd
like
to
speak
to
here.
C
Not
much
to
say,
and
that's
the
current
pen
that
there
is
I
think
will
hold
up
but
I'm,
currently
just
following
the
discussions
around
how
generic
are
analytics
listing
and
dashboard
pages
are
going
to
be
to
see
if
it's
going
to
influence
this
at
all
I.
Don't
think
it
should,
because
this
is
more
focused
on
the
onboarding
state
of
it,
but
I'm
just
keeping
an
eye
on
that
and
once
there's
been
some
more
consensus
or
progress.
There.
I'll
move
this
to
ready
for
development.
A
C
A
All
right,
we
have
the
dashboard
which
retains
fluid
container
after
visiting
a
dashboard
or
the
panel
designer
yeah.
D
I,
don't
know
if
you
wanted
to
take
this
out
or
the
Milestone
or
not
subject
to
severity
for
I
put
it
in,
but
we
can
always
take
it
out
if
we
choose.
Otherwise.
It
is
just
that
when
you
go
to
the
panel
designer
or
visit
a
dashboard
and
go
back
rather
than
being
constrained,
it
retains
that
full
fluid
fluid
container,
which
is
a
bit
buggy,
especially
as
we
move
to
a
shared
listing.
A
Yeah,
it
would
have
eventually
affect
the
dashboarding
move
in
there,
but
I
think
for
the
severity
and
no.
A
A
discussion
to
discuss
whether
it
should
be
in
the
smallest
or
not,
but
we
can
follow
the
facing
cool
and
then
we've
got
the
two
dashboard
issues
for
the
audience
and
behavior.
We
might
just
want
to
close
these
out
in
favor
of
just
having
the
follow-up
issues,
because
at
this
point,
I
think
we
can
just
iterate
from
there.
We
also
have
changing
default
name
for
analytics
event,
table
name
from
Jitsu
to
something
else.
B
B
Want
to
cover
yeah
I
mean
this
is
kind
of
done,
although
bad
communication
for
me
here
so
the
change
in
the
gitlab
repo
is
now
fixed.
So
we're
now
referring
to
tracked
events
rather
than
jitsu,
but
the
change
of
the
Dead
is
good
production
and
I.
Think
Dennis
is
looking
at
that
now,
so
I
assume
it
will
be
broken
in
at
least
Canary,
if
not
production,
until
that's
fixed.
A
So
we
need
a,
we
haven't:
merged
requests
for
the
dev
kit
and
so
I
just
need
to
promote
those
to
production.
We
should
be
good
to
go.
Is
my
understanding
of
that
yep?
A
Okay,
so
I'll
do
another
I'll,
updating,
schema
and
or
the
Q
files
and
I'll
do
another
Helm
update
cool
and
then
you've
got
the
next
one
as
well.
Max.
B
Yeah
I've
not
really
touched.
This
I
think
we've
agreed
tentatively
that
the
initial
iteration
of
this
will
just
be
a
documentation
change
where
we
explain
how
you
can
pull
the
data
out
of
cube
directly
so
I
don't
know
if
Samuel
would
create
another
issue
for
that,
specifically
or,
if
I,
just
tagger
an
implementation
plan
onto
this
issue.
The
spike
issue,
it's
up
to
you,
how
you
want
to
do
that.
F
Well,
so
the
spike
was
about
getting
the
implementation
plan
issues
created.
So
what
I'd
suggest
is
create
an
issue
for
the
more
effort
involved,
but
probably
longer
term
solution
and
then
create
an
issue
to
track
just
the
documentation
issues
we
can
put
the
bigger
age
and
a
backlog
and
get
it
scheduled
sometime
in
the
future
and
then
we'll
put
the
documentation
issue
in
sooner.
Okay,
I'll
take
that
stuff
to
name
them.
A
All
right,
this
issue
is
unchanged.
The
scope
has
changed
since
I'm
working
to
get
the
redness
working
in
a
cluster
environment,
specifically
like
multiple
Masters
and
replicas.
So
that's
a
little
taken
a
lower
priority
at
the
moment
with
the
schema
promotions
that
we
have
to
do.
G
Yeah
Dennis
it
so
yeah.
If
please
excuse
me
for
my
voice
today
know
what
happened
with
Metro
I
realized
that
one
of
the
issues
that
I
was
working
on
was
not
on
the
board.
It
didn't
have
a
milestone.
So
can
you
please
refresh
so
it
appears
there
and
then
I
added
it
like
after
you
loaded
the
page,
okay
yeah
that
one
so
I'm
currently
working
on
this.
This
is
basically.
A
G
You
all
know
that
we
have
some
issues
with
responsiveness
and
the
width
of
the
and
and
the
way
that
the
the
elements
behave
in
different
screens,
and
we
also
have
this
issue
with
the
hate
that
sometimes
it
can
be
unbounded
basically
so
so
yeah
I'm
solving
this
I
already
have
some
early
feedback
from
from
Rob,
so
so
yeah.
Hopefully
hopefully
we
get
these
Improvement
out
soon.
So
so
it
looks
way
better.
G
D
Yep
we,
this
is
in
final
backend
maintenance
review.
The
maintainer
was
off
yesterday,
so
I'm
giving
them
today,
but
if
they
still
don't
get
to
it,
I'll
swap
to
a
different
maintainer
other
than
that
we've
got
all
the
reviews
necessary
to
get
this
merged.
B
A
All
right:
well,
hopefully,
we
can
get
someone
to
do.
The
final
merge,
yeah
the
date
range
filter.
C
Yeah
thanks
to
Rob
and
axel
for
reviewing
this,
it's
working
nicely
just
some
small
changes
that
I
need
to
make
and
then
I
have
a
follow-up
Mr
for
this
or
a
split
into
two
emails,
one
for
adding
the
deck
range
filters
and
the
other
one
for
syncing
it
with
URL
managing
State.
The
managing
State
change
is
also
working
nicely
locally,
so
expect
a
new
Mr
for
one
of
you
to
review
also
within
the
next
24
hours.
Let's
say.
B
Yeah
this
hasn't
changed
from
last
week
because
the
changes
to
the
schema
aren't
in
production.
I
can't
verify
it
on
the
main
web
application.
Yet
I've
got
no
reason
to
believe
it
doesn't
work,
but
I
can't
say
it's
been
verified.
A
Yeah
I'll
promote
the
cubes
first
and
then
I'll
I
need
to
move
the
funnel
changes
and
just
make
sure
it
doesn't
break.
But
I'll
focus
on
that
next
cool.
A
Sweet
all
right
and
then
I
think
add
button
to
go
back
to
tracking
view
is
our
last
bookmark,
so
we
have
I,
think
six
or
so
issues
in
the
done
closed
column.
So
we
have
ADD
dashboard
items
to
the
project
analytics
submenu
Rob.
Anything
you
want
to
comment
on
here.
D
If
you
want
to
enable
the
combined
analytics
dashboards
feature
flag,
you
can
have
your
own
dashboards
item
on
the
project
level
on
the
analytics
submenu.
It's
the
first
step
in
the
process
of
getting
that
shared
dashboard
listing
completed.
A
Very
cool:
we
have
the
competitive
analysis,
which
was
in
support
of
our
Q4
fiscal
year.
23
okr
I
believe
I
spoke
to
that
previously.
That's
just
closed
at
four
sake
of
completion,
but
feel
free
to
check
that
out
and
then
actually
you
have
the
next
two.
G
Yeah,
so
we
have
about
a
DPC
and
the
privacy
mode
on
on
the
SDK
now,
and
we
also
introduced
the
the
concept
of
options
to
the
to
the
SDK,
because
we
we
were
basically
using
them
reactively
and
it
looks
pretty
good.
I
haven't
Rob
mentioned
that
he
could
publish
a
new
version
of
of
the
package
right
after
these
two
were
merge,
although
I
haven't
I,
haven't
greenlighted
or
having
boiler
Rob
with
that,
because
because
of
what
I'm
working
on
right
now
with
learner
but
yeah,
this
is.
This
is
ready
for.
A
G
A
Cool
and
I
have
the
last
one.
This
was
just
a
discussion
about
whether
or
not
we
need
to
make
any
more
modifications
to
reference
Jiu
Jitsu,
but
as
the
last
group
sync,
we
decided
as
long
as
it's
not
user
phasing.
It's
fine
as
we'll,
eventually
just
swap
everything
over
to
snow
flower
and
such
so
that
covers
our
build
review.
Anything
anyone
would
like
to
bring
up
any
other
issues
that
aren't
on
the
board
or
anything
like
that.
E
And
to
find
my
mute,
but
behind
the
microphone
yes,
so
great
to
see
the.
E
There
was
some
discussion
about,
and
then
it's
called
this
out
correctly
is
that
we
should
find
a
final
name,
as
name
in
his
heart,
so
I'm
calling
it
once
and
twice
and
free
how
we
should
name
the
query
designer
to
basically
building
Dynamic
data
queries
with
a
visualization
for
product
Analytics.
E
A
E
That
was
also
the
topic
that
this
is
definitely
helpful
as
the
basis
of
a
data
Explorer,
so
that
you
simply
don't
build
a
new
panel,
but
simply
work
and
play
around
with
the
data,
so
it
might
be
also
linkable
or
reachable
without
the
dashboard,
for
example.
That
was
also
something
same
mentioned
at
some
point
that
this
might
be
helpful.
So.
A
I
can
see
us
exposing
a
data
Explorer
where
it's
just
literally
that
without
you
know,
adding
a
dashboard
or
something
like
that.
But
that's
why
I
picked
visualization
designer,
but
I
almost
also
really
don't
care
I
just
get
really
confused
when
we're
referring
to
five
different
things
and
all
the
same
thing.
F
D
E
The
thing
is
that
in
a
panel
is
simply
for
me,
a
box
where
something
is
displayed
which
could
be
a
component.
Let's
say
it's
a
headline
or
a
title:
to
make
it
really
easy
and
understandable,
or
it
can
be,
a
complex
visualization,
which
always
has
a
query
next
to
it,
which
is
then
basically
displaying
something
in
a
panel.
F
I
also,
don't
think
many
of
our
users
are
going
to
understand
the
Nuance
of
our
distinction
between
visualization
and
panel
I.
Do
like
us
getting
away
from
the
word
query
because
query,
at
least
for
me
makes
me
think
of
databases.
So
now
I'm
thinking,
oh,
am
I,
doing
SQL
now,
which
that's
not
what
we're
doing
here
so
that
that's
my
input.
H
So
yeah
I
was
thinking
for
the
same
reason
like
I
think
we
should
donate,
should
be
descriptive
about
the
user
will
actually
see
what
we
expect
when
they
read
that
name,
so
not
how
I
Implement,
if
it's
a
data
explorating
this
to
generic,
like
how
do
you
explore
data
and
they
might
need
to
do
something
to
run
some
analytics
on
that?
So
it's
it's
more
of
a
process,
but
the
visualization
is
like
Tim
and
Sam
said
it
so,
whether
it's
a
pen
or
something
for
graph
they
they
know
what
to
expect.
A
A
But
I
guess
we
can
create
an
issue
for
this
and
we
can
all
vote
on
it
and
then
we
can
just
put
a
due
date
for
Friday.
If
anyone
like
to
volunteer
to
do
that
or
I
can
default.
E
I
would
I
would
put
those
options
simply
enough
right
in
the
issue
that
already
you're
already
opened,
because
we
mixed
the
discussion
already
in
there,
take
it
from
there
and
until
Friday.
We
have
a
front
runner
with
two
pluses
on
that
end,
but
then,
if,
if
no
huge
thing
comes
up
until
Friday,
let's
go
with
them.
C
C
We
can
make
it
that
it's
outputting
actually
visualizations
and
then
improve
the
flow
of
how
that
gets
added
to
dashboards,
because
that's
also
something
we
need
to
explore,
because
the
the
only
thing
that
it's
doing
additionally
that
breaks
the
mold
is
we're
giving
a
title
to
a
panel.
C
My
my
input
is
I.
Think
visualization
designer
is
the
name
to
go
for,
in
my
opinion
and
I,
I
think
Rob
isn't
being
overly
pedantic
and
what
the
output
is
because,
like
it
is
outputting
at
a
panel.
We
just
need
to
maybe
change
that
to
Output
an
actual
visualization
file,
because
currently
it's
like
a
panel
wrapped
in
a
visualization,
I
think
or
something.
D
Yeah
I
agree
if
it's
a
visualization
name
instead
of
like
the
title,
if
you
just
call
a
visualization
name
or
whatever
outputs
of
visualization,
and
then
that
flow,
when
you
add
it
to
the
dashboard,
it
adds
it
to
a
new
panel,
and
then
you
can
type
in
your
title
and
stuff
into
that
panel.
Visualization
designer
works
for
me
meets
our
own
internal
criteria
and
also
meets
the
yaml
output
that
we
would
expect
from
it
as
well.
C
Sure
I'll
I'll
add
it
to
the
issue,
just
make
a
comment
there,
but
like
what
maybe
needs
to
change
or
what
what
our
suggestion
is.
A
G
And
maybe
we
can
narrow
it
down
to
use
the
word
designer,
because
that's
what
clicks
on
for
me,
for
example,
versus
Explorer
I
I,
do
prefer
it
to
have.
The
word
designer.
In
fact,
I
was
I
was
about
to
say
that
we
might
go
with
a
simple
one
with
query
designer,
but
after
hearing
Dennis
and
some
points,
yeah
I
will
go
with
the
second
one
and
just
a
comment.
E
Good
then,
there
was
also
the
discussion
coming
up
around
my
YouTube
query.
Designers
just
wanted
to
make
I
I
left
a
comment
yesterday,
but
just
wanted
to
see
if
there
are
any
questions
or
misunderstandings.
What
I
meant
with
this
to
see
if
we
can
discuss
the
sink,
if
there
are
some
open
topics
to
make
it
very
easy,
is
always
fun.
E
You
have
a
visualization
designer
for
product
analytics
to
say,
Okay
I
want
to
add
a
panel
which
displays
product
analytics
data.
So
you
click,
OK
I,
want
to
add
something
product
analytics
related
either
it's
already
existing
one
of
the
yammers
that
you
have
already
created,
or
you
create
a
new
visualization.
E
Okay
super,
my
youngest
was
just
telling
me
that
he's
back
again
and
then
you
basically
go
through
the
flow
use,
a
set
of
visualization.
You
edited
the
panel
to
a
panel
at
the
end,
but
the
same
could
go
also
in
a
different
way
where
you
say:
Okay
I
want
to
add
some
value
stream
analytics
data,
and
the
question
is:
if.
A
E
Would
take
any
of
that
logic
and
put
it
in
the
same
type
of
career
designer
visualization
designer,
as
we
already
have
a
product
analytics
or
make
a
very
custom
one
for
product
analytics
where
we
rather
highlight
issues
and
merge
requests
and
already
have
some
opinions
about
what
can
be
filtered
and
suggest
have
a
project
picker
for
the
projects
that
you
would
want
to
filter
the
data
down
Etc.
So
that's.
The
only
thing
whatever
is
output
at
the
end
is
always
a
Yammer
for
visualization,
which
contains
the
query
and
all
the
visualization
parameters.
E
It's
only
that
we
might
have
at
some
point
different
kinds
of
interfaces
to
have
them
more
accustomed
to
the
specific
use
case,
rather
than
have
one
generic,
where
we
simply
released
table
field
names
and
table
names,
because
this
is
the
complexity
that
we
already
have
in
in
something
like
science.
At
the
moment,
for
example,.
A
Different
user
experience
every
time
someone
wants
to
like
for
every
context
then,
like
my
my
main
issue,
is
just
I.
Don't
my
main
thing
is
that
I,
don't
think
this
is
documented
anywhere
so,
like
I,
would
love
to
capture
that
now
or
we
can
I.
Can
we
can
capture
in
this
meeting
and
we
can
transcribe
it
afterwards
yeah.
A
It
is
because
that,
what's
not
clear
is
how
that
experience
is
going
to
look
because
I
wasn't
sure
if
there
would
just
be
a
screen
in
front
before
you
get
to
the
point
where
you
define
your
dimensions
and
measure
some
filters
where
you
just
select
what
type
of
data
source
you'd
want
and
from
that
it
would
just
you
know,
filter
based
on
what
data
source
you're
using
and
up
from
that
what
visualizations
are
supported.
A
E
Monolithics,
where
you
say
Okay
I
want
to
know
how
many
issues
we
are
producing
for
this
label
every
month
and
care
designer,
for
that
would
most
probably
to
be
more
accustomed
to
that
use
case.
If
this
comes
at
some
point
might
be
more
accustomed
to
that
use
case.
Maybe
we
can
reuse
components
to
98
the
same
ones.
Maybe
we
even
do
the
same
character?
Designer
I
don't
know.
E
Yet
it's
just
that
there
might
be
some
data
sources
where
we
take
a
different
look
but
create
the
same
file
types
at
the
end
of
it
and
under
the
hood
for
us
it
stays
the
same
because
I
don't
want
to
have
now
a
yaml
file.
Format
for
product
analytics,
I
think
the
concept
that
Giannis
has
created
with
the
data
source,
with
the
query,
the
data
source
and
how
it's
injected
is
perfect.
E
This
is
fantastic,
but
from
our
customer
and
user
perspective
having
something
that
that
abstracts
already
right
now,
the
query
designer
abstracts
already
from
the
user
way
that
there
are
two
different
views
between
sessions
and
events,
and
you
don't
even
see
it.
You
simply
say
I
want
to
know
the
active
users
and
you
don't
need
to
know
that
kind
of
table
name
and
so
on
and
so
on.
So
this
is.
This
is
just
out,
maybe
in
six
months,
maybe
in
three
months.
E
Maybe
we,
if
you
see
something
and
optimize
just
to
make
you
aware
of
my
thoughts.
F
That
that'd
be
what
I'd
be
interested
in
a
little
bit
more
detail
on,
seeing
something
a
little
bit
more
more
concrete.
There
yeah.
A
A
Like
when
we
were
discussing
URLs
sorry
when
we
were
discussing
URLs
it'd
be
like
multiple
query
designers,
so
does
that
mean
like
we
go
back
to
what
we
had
before
with
analytics
having
10
different
links
to
different
dashboards?
Like
do
we
have
a
menu
at
some
point,
that
flight
goes
to
different
kinds
of
like
query
designs.
That's
that's
one
yeah
really
curious
about
yeah,
because.
A
We
know
we're
going
to
reuse
it
then
I,
don't
know
that
we
need
to
really
just
make
a
distinction
that
it's
the
product
analytics
query
designer,
at
least
for
now.
There.
A
C
Yeah
I'm
I'm,
with
Tim
and
also
Dennis's
last
comment.
That's
naming
this
product
analytics
Creator
designer
is
gonna
like
lead
other
teams
into
creating
their
own
one
and
maybe
duplicating
it.
It
would
be
great
for
me
if
we
could
lead
both
from
an
engineer
and
a
user
perspective
lead
people
into
using
the
same
one
and
then
sharing
as
much
as
possible.
So
as
to
mentioned
like
the
first
drop
down,
could
be
like
hey.
What
is
your
data
source?
Where
is
it
going
to
come
from?
C
D
I
would
like
to
say
first
thank
you
Tim
for
engaging
with
this,
because
I
am
the
one
that
raised
it,
because
I
was
very
confused
as
and
I
appreciate
you
sort
of
blurting
out
everything.
That's
been
sort
of
being
discussed
with
yourself
and
others
in
terms
of
the
main
concern
right
now
was
just
around
the
URL
construct
concept
and
just
getting
the
ideas
of
where
we're
thinking
the
product
will
go
over
the
next
six
months,
the
vision.
D
So
if
we
can
document
the
general
con
Vision
that
we're
aiming
for
even
if
it
can
change
at
any
point,
obviously
that'd
be
great
from
a
URL
point
of
view.
I
feel
like
this
sounds
like
initially.
D
We
could
just
go
down
the
visualize
forward,
slash
visualization
designer,
and
then,
if
we
want
to
split,
we
could
then
have
after
that
forward,
slash
analytics
forward,
slash,
VSA
forward,
slash
whatever,
and
that
then
allows
if
we
have
our
project
out
before
we
make
that
split,
we
can
easily
redirect
the
we
can
easily
just
have
some
kind
of
face,
facial
in
the
front
Zone.
What
source
are
you
looking
to
implement
yeah
at
that
page,
and
that
is
one
step
removed
from
where
people
had
their
bookmark
anyway?
D
So
it's
not
breaking
necessarily
the
user
flow
so
from
a
URL
point
of
view,
I'd
say:
keep
it
generic
and
then
we
can
bespoke
it
narrow
it
down
slightly
and
make
that
easier.
If
we
want
want
to
go
down
this
route,
I
do
like
the
idea
of
having
a
pre-faced
data
data
source
and
then
customize
the
UI
based
off
that
data
source,
because
we
won't
have
every
visualization
type
for
every
data
source,
most
likely.
E
Yeah
and
it
becomes
super
complex
that
that
I
think
is
one
of
the
great
problems
of
size.
Sense.
It's
like
or
also
post
talk.
If
you
have
ever
used,
postdoc
I
did
a
little
bit.
It's
like
here's,
everything
and
and
there's
like
makes
it
much
harder
to
get
to
results.
I
believe
so
cool
same
you
had
a
thing
about
I.
Think
real.
F
A
It'll
be
fixed,
bye,
cool
I
just
wanted
to
clarify
that
that
marriage
request
does
not
fix
the
production
issue.