►
From YouTube: 2022-07-25 Analytics Section Meeting
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
July
25th
version
of
the
analytics
section
meeting
got
a
number
of
topics
here.
You
can
go
through.
Matt
got
you
from
monitor,
observability
I,
believe
you
were
having
a
conversation
with
Kenny
and
you
might
have
a
ton
of
insight
that
we
can
benefit
from
from
your
months
spent.
Would
you
like
to
start
yeah
and.
B
Actually
Matt
before
we
start
I
did
want
to
give
one
a
little
bit
of
Preamble.
So,
first
of
all,
Matt's
awesome
and
I'm
excited
to
have
him
chat
with
you.
All
I
do
want
to
say,
like
a
principal
of
mine
in
thinking
about,
like
obviously,
both
parts
of
the
application
that
we're
building
in
observability
and
in
analytics
have
a
lot
of
potential
overlap,
including
are
using
likely
going
to
use
a
common
data
store
in
clickhouse,
but
I
want
to
try
to
operate
them
as
independently
as
possible.
B
So
what
we
should
think
about
when
Matt's
explaining
what
they've
learned
is
lessons
learned
that
we
can
apply
going
forward
as
opposed
to
like
trying
to
couple
the
groups
to
say,
like?
Oh
one
group
work
on
this
part
and
we'll
use
it
and
the
other
group
work
on
another
part,
because
these
are
all
so
both
early
Investments
for
git
lab,
and
so
it's
important
that
we
are
structured
to
move
quickly
rather
than
necessarily
be
coupled
together
as
groups.
So
I
just
want
to
make
sure
I.
Give
that
caveat
before
we
start
makes.
A
C
Cool
yeah
thanks
Kenny
thanks
Dennis
I'm
Matt
I'm
from
the
monitor
observability
group,
I
came
over
to
gitlab
as
part
of
the
Ops
Trace
acquisition
and
in
the
last
six
months,
we've
really
been
building
a
lot
of
what
I
think
new
folks
are
probably
going
to
end
up
having
to
build,
and
so
that's
why
I
wanted
to.
You
know
sort
of
bridge
this
discussion
a
little
bit
because
I,
you
know
and
I
think
that
it's
a
good
principle
to
operate
by
you
know.
C
Having
kind
of
you
know
separate
dependencies
and
trying
not
to
you
know,
overlap
too
much,
but
you
know
in
the
last
six
months
we
have
invested
a
lot
in
I
think
what
you
guys
are
gonna
have
to
redo.
So
you
know
I
think
that
there
is,
you
know,
we're
happy
here
to.
If
you
want
to
stay,
you
know
a
little
bit
more
independent,
we're
happy
to
help
in
any
way
we
can.
But
there
is
a
lot
of
benefit
too
from
you
know,
sharing
some
of
what
we've
built.
C
At
the
same
time,
we've
built
a
lot
of
automation
around
kubernetes.
C
You
know
infrastructure
life
cycle
of
kubernetes
clusters
with
click
house,
on
top
of
it
click
our
scaling
limits,
quota
management
inside
of
Click
house
end-to-end,
testing
of
the
entire
System
Authentication
on
the
apis.
You
know
that
connect
back
with
the
gitlab
instance.
C
You
know,
there's
there's
loads
and
loads
and
loads
of
things
that
you
know
for
the
back
end.
A
lot
of
their
stuff
is
not
seen
by
a
user,
but
they
will
be
things
that
an
operator
of
gitlab
for
self-hosted
or
for
our
own
internal
SRE
team.
They
will
have
to
interact
with
the
system
and
so
I
think
that,
from
a
product
standpoint
to
a
user
experience,
you
know
we
don't
want
to
diverge
too
much.
C
In
parallel,
we
should
at
least
make
sure
that
we're
building
things
that
align
with
some
principles-
I,
guess
you
know
to
make
it
easier
for
those
folks
that
are
going
to
be.
You
know,
managing
the
life
cycle
of
of
get
lab
and
its
entirety
of
observability
and
analytics
analytics
and
whatnot.
So
we
I
just
wanted
to
start.
C
The
conversation
and
kind
of
you
know
introduce
things
for
a
start
as
a
way
that
I
think
that
if
you
did
want
to
use
what
we
have
I
think
it
really
could
accelerate,
where
you
guys
are
knowing
the
effort
and
time
we've
had
to
put
in
over
the
last
six
months.
C
But
you
know
that
happy
to
leave
that
over
to
you
guys
to
decide.
You
know
where
you'd
like
to
use
some
things
and
help
and
just
start
the
dialogue.
A
Yeah,
no
that's
great
I,
mean
I,
think
there's
definitely
going
to
be
some
learnings.
We
can
leverage
there
and
you
know
to
your
point.
If
we
operate
by
the
same,
you
know,
principles
then
at
least
sres
won't
have
to
worry
about
managing
two
very
similar
architectures
two
different
ways.
Right.
There
are
some
decisions.
A
We
are
discussions
we
haven't
yet
had
in
terms
of
like
how
we're
gonna
like
organize
the
tenancy
of
or
how
we're
going
to
like,
set
up
this
whole
kind
of
tracking
box
as
we're
currently
calling
it
in
terms
of
jet
ski
clickhouse
and
and
and
cube
in
terms
of
like
you
know,
obviously
we're
going
to
operate
in
multiple
regions.
So
that's
going
to
be
useful
in
terms
of
how
you're
managing
the
provisioning
of
kubernetes
there,
but
then
yeah
when
it
gets
down
to
like
per
customer,
especially
on.com,
I'm,
not
sure.
A
If
well
we
haven't,
we
haven't
gotten
there
yet,
but
I'm
sure
there
will
be
something
we
can
leverage
there.
I
guess
in
terms
of
like
where
we
could
start
to
like
see
where
this
is
happening.
Is
there
a
repository
or
a
desert
documentation?
We
can
start
to
like
look
at
start,
exploring
this
or
absolutely.
C
Yeah
I'll
drop
some
links
in
to
the
notes
here
with
the
repositories
that
are
relevant,
but
you
can
go
through.
You
can
see
all
the
code
there
yeah.
You
know
your
model
around
having
these,
you
know
boxes
that
you're
deploying
into
different
regions
and
different
clouds.
All
fits
our
exact
same
model
too.
C
The
tenancy
model
is
exactly
the
same.
You
know
and
hence
kind
of
why
I
think
personally.
I
think
it
doesn't
make
a
lot
of
sense
to
go
and
rebuild.
Let
you
know,
because
it's
a
I,
think
it's
a
it's
a
massive
undertaking
and
you
need
you
know
to
have
a
team
that
has
you
know
a
lot
of
experience,
I
think
in
the
realm
of
kubernetes,
and
you
know,
I
think
that
we
can
probably
help
you
get
a
lot
further
there.
C
So
there
is,
you
know,
I
sort
of
was
seeing
it
as
a
way
and
I
talked
about
it
with
Sebastian
a
little
bit
too
he's
out
of
office
here
today.
But
you
know
I
think
there
is
a
model
where
we
could
work
on
collaborate
on
the
same
code
without
it
slowing
us
down
and
getting
it
our
way,
because
we
have
all
the
pieces
in
place
that
you
guys
could
just
fill
in
the
bits
that
you
need
and
deploy
without.
You
know
needing
us
to
do
anything
for
you.
B
Yeah,
that
was
the
the
principle
I,
don't
think.
I
very
artfully
said
earlier:
I
I,
like
GitHub,
everyone
can
contribute.
Typically,
we
operate
in
one
code
base,
so
I
was
thinking
about
it.
In
those
terms,
not
what
I
didn't
want
to
create
is
like
if
analytics
needs,
something
they
need
observability
to
ship
something
first,
but
if
we're
all
operating
from
the
same
code
base
I
think
that's
agreed
mental
model.
Yes,.
A
A
shared
framework
that
also
we
can
hopefully
contribute
back
to
to
help.
You
know
you
know
also
just
bring
some
value
to
y'all
but
yeah.
If
we
can,
if
we
can
operate
it
in
such
a
way
that
we
both
benefit
from
it,
but
we
can
contribute
from
shared
work
or
benefit
from
shared
work,
but
then
they'll
contribute
to
it.
I'll
tell
you
that
backwards,
then
that'd
be
great,
because
there's
there's
a
bunch
of
different
topics
that
I
have
running.
In
my
mind
in
terms
of
how
is
this
all
going
to
be
maintained?
A
I've,
you
know
heard
from
multiple
people,
like
click
house
requires
to
some
degree
of
like
you
know,
management,
especially,
and
if
we're
gonna
have
to
have
you
know,
n
number
of
Click
house
instances,
I,
don't
even
know
the
first
thing
about
how
the
things
we're
going
to
be
looking
at
there.
So
if
you've
already
done
some
work
around
that
it's
already
a
huge
boost,
but
then
yeah
everything
from
testing
run
books.
All
that
kind
of
stuff,
like
you
know,
product
analytics
currently
has
two
Engineers.
A
So,
there's
a
lot
of
work
to
be
done
even
just
from
a
feature
perspective
standpoint,
so
yeah
even
getting
into
the
infrastructure
part
of
it
any
anything.
You've
got
well.
At
least
you
know
be
a
huge
starting
point
yeah
for
us.
If
you're
saying
like
where
our
tendency
model
is
the
same,
then
there's
probably
a
lot
of
we
can
just
collaboration
and
boot
Gap
off
of
so
yeah.
A
It's
I
appreciate,
y'all,
bringing
it
up
and
have
coming
to
talk
about
it
and
we'll
be
happy
to
explore
all
the
as
many
Linksys
you
can
throw
through
our
way.
So
of.
C
Course,
yeah
I
think
it's.
You
know,
everybody
comes
out
stronger
and
better
off.
If
we
can
all
collaborate
on
the
same
code
base-
and
you
know
we
have
a-
can
you
mention
in
here
I
think
he's
he's
got
to
take
it
down
a
little
further.
We
do
have
a
contract
with
click
ass,
Inc
and
we've
been
engaged
with
click
ass,
INC
now
for
a
number
of
months
working
with
them
on
a
number
of
issues.
You
know
getting.
C
Reviews
of
you
know
how
we
manage
click
house
things
like
this,
and
so
you
know
we're
we're
building
up
that
muscle
and
the
team
and
we've
also
hired
some
click
house
experts
in
the
team.
So
you
know
we're
kind
of
getting
more
acquainted
with
running
click
house,
and
you
know
it's
quirks
so
you
know
we
can
certainly
help
there
too.
I
think.
C
Cool
I'll
drop
these
links
in
here
for
the
main
repo
there's
still
we're
still
under
heavy
development,
of
course,
so.
D
C
Know
not
everything's
there
you
know
run
books,
you
won't
see
those
in
the
repo.
Yet
you
know
there
is
things
but
you'll
you'll
find
issues
too,
where
we
can
follow
up
on
things
that
are
yet
to
be
done.
The
core,
the
core
tenancy
model,
deployment,
life
cycle
and
authentication.
All
that
stuff
is
all
in
place.
So
yeah.
A
A
Out,
lock
that
up
before
we
start
deploying
it
yeah.
C
B
Yeah,
it's
a
private
Channel,
but
it's
a
direct
connection
between
us
and
click
house
that
we
pay
for
support
from
them.
For
so,
if
the
main
point
Dennis,
you
and
team
want
access
to
that
channel,
let
me
know
I
mean
if
you
want
Dennis
I
can
just
invite
you
to
that
Channel
right
now,
so
you
can
follow
along
okay
and
then
feel
free
to
invite
others
as
needed.
We'll.
A
Do
thanks
for
sharing
awesome,
I,
have
a
couple
of
short
points
and
then
I
can
open
it
up
for
anyone
else.
Sam
is
joining
us
as
interim
product
manager
for
product
analytics.
I
worked
with
them.
I
I
still
work
with
them.
Rather
in
compliance,
yeah
Sam,
you
want
to
do
a
little
quick,
intro.
E
Yeah,
hey
folks,
really
excited
to
be
here,
I
think
product
analytics
is
going
to
be
a
really
exciting
space
to
to
jump
in
and
I'm
excited
to
go
on
that
Journey
with
you
all
together,
like
Dan,
said
I'm
on
the
compliance
team.
The
compliance
group
right
now
started
on
that
group
in
2021.
E
I've
been
with
gitlab
since
2019
I'm,
based
in
Cincinnati
Ohio
in
the
United
States
over
the
next
couple
of
weeks,
I'd
like
to
put
a
coffee
chat
together
with
each
of
you
just
to
get
to
know
you
a
little
bit
more
personally.
Let
you
get
to
know
me
a
little
more
personally
and
we
can
also
talk
about
some
work
stuff
along
the
way,
so
I'm
sure
I
will
have
lots
of
questions
and
things
to
discuss
with
each
of
you
in
the
days
to
come
and
I'm
excited
to
get
things
started
off
here
today.
A
Awesome
Sam,
thank
you
very
cool
and
then
my
last
point
was
just
kind
of
just
giving
a
little
bit
more.
Well,
not
just
sorry
just
wanted
to
highlight
kind
of
next
steps,
so
we're
headed
for
product
analytics
in
that
group,
so
I'm
in
writing
mode,
just
trying
to
organize
a
bunch
of
different
epics
for
all
the
different
categories
and
features,
but
basically
just
kind
of
taking
the
notes
from
our
proof
of
concept.
Demo.
What
we've
been
having
discussions?
A
You
know
online
and
offline
and
I'm
just
trying
to
get
an
idea
of
all
the
things
we've
been
thinking
about
what
we
want
to
do
for
things
like
product
analytics,
experimentation
and
whatnot,
and
starting
to
nail
that
down
into
more
of
an
NBC
in
terms
of
what
we
really
want
to
pursue
for
those,
but
in
terms
of
a
more
immediate
Focus,
I
think
discussions
between
Kenny
and
Tim
and
I
we're
looking
at
product
analytics
or,
more
specifically,
you
know,
web
and
mobile
analytics
in
terms
of
how
just
your
general
setting
up
instrumentation
trying
to
see
what
what
default
dashboards
you
want
to
kind
of
present,
and
also
just
getting
it
a
little
bit
more
productionized,
and
so
getting
some
instrumentation
set
up
to
be
able
to
track,
maybe
the
hand
book.
A
Maybe
our
design
Library,
maybe
even.com,
just
with
a
with
this
targeted
audience
of
just
you
know,
gitlab
org,
just
to
be
able
to
get
more
more
information
there
and
to
start
dog
fooding
and
seeing
what
we
want
to
really
provide
there
in
terms
of
your
general
web
analytics.
So
that's!
What's
coming
up
for
the
product
analytics
group.
B
Yeah
and
Dennis
I
know
I,
don't
know
if
you
want
to
discuss
here
the
like
tactical
process
of
taking
all
of
the
vision,
POC
and
breaking
that
down
into
epics
and
issues
and
kind
of
targeting.
What
our
initial
first
mvcs
versus
subsequent
ones
is
a
big
task.
So
how
can
Sam
still
ramping
up
so
it
should
be
on
me
this
week.
But
how
can
I
help
this
week?
I
know
we
have
some
time,
but
is
there
something
that
I
can
start
contributing
to
or
reviewing
or
yeah.
A
On
paper,
so
I
mean
the
main
point
that
I'm
trying
to
push
out
is
just
to
organize
all
the
different
areas
so
that
we
at
least
have
like
get
organized
within
our
on
gitlab.com.
In
terms
of
like
everyone
can
start
editing
and
having
discussions
there.
So
I
will
drop
a
link
in
the
section
Channel,
probably
end
of
day
to
day
or
tomorrow,
to
just
have
the
general
structure
of
all
the
different
epics
in
terms
of
the
features
and
then
start
building
out
that
list.
A
So
if
anyone
wants
to
jump
in
and
just
start,
you
know,
even
you
know
all
what
all
the
wild
ideas
that
we
were
discussing
in
terms
of
like
what
we
could
provide
to
the
features
like
feel
free
to
add
that
to
the
epics
there's
no
strict
policy
on
who's.
Who
can
do
what
so
as
if
anyone
has
anything
they'd
like
to
add
in
terms
of
like
things
we
should
be
thinking
about
for
any
of
the
features
we
want
to
build
out.
A
B
I
think
what
I
can
do
this
week
is
make
sure
I'm
contributing
to
you
know
like
our
what's
next
section,
we've
been
updating,
but
it's
still
pretty
vague.
I
want
to
maybe
try
to
get
something
very
crisp
that
will
help
if
we
can
use
that
discussion
in
an
MR
to
like
really
Target.
What
is
you
know,
Milestones
one
through
three
or
specific
Focus,
going
to
be
yeah
I'll
work
on
that
for.
A
Sure
yeah,
that's
that's
the
general
goal
of
I
think
what
we'll
both
be
working
on
then
is
just
like
in
San
as
well
as
he
ramps
up
is
just
to
give
a
little
bit
more
of
a
clear
Direction
than
yeah.
We
want
to
build
an
analytics
thing,
so
yeah
sure
yeah.
E
Awesome
I'm
happy
to
help
with
either
of
those
initiatives.
I'll
be
ramping
up,
but
I'm
still
willing
to
contribute
things
this
week.
So
don't
feel
free
feel
free
to
pull
me
into
those
things.
I'm.
A
E
E
A
B
Amanda
I
don't
want
to
put
you
on
the
spot,
but
I.
Your
comment
about
the
visibility
of
this
section
thing,
I
think
seems
material,
but
I
didn't
see.
Anyone
have
a
concern.
I
I
didn't
maybe
completely
understand
it,
but
is.
Is
everyone
aware
of
the
change
in
visibility
for
the
section
group
and
comfortable
with
that
change?.
D
Yeah
so
tldr
bright,
late
Friday.
My
time
we
had
a
report
that
the
metrics
dictionary
was
an
accessible
externally
and
it
turned
out.
It
was
because
we
moved
the
the
metrics
dictionary
project
over
to
the
analytics
group
parent
group
and
that
parent
group
was
Private,
which
caused
only
members
of
that
domain
to
be
able
to
see
it.
So
I
made
the
the
parent
group
The
analytics
group,
as
well
as
the
product
intelligence
subgroup
and
the
metrics
dictionary
project,
all
public
visibility,
so
visibility
settings
are
least
restrictive
to
to
most.
D
So
you
can
still
make
things
more
restrictive
within,
but
if
that's
a
problem,
then
we
can
revert
everything
and
we
can
move
the
metrics
dictionary
out
to
a
separate
location.
A
Got
it
yeah?
No
thanks
for
the
call
out,
because
I
remember
the
visibility
options
being
restricted
and
I
I
hadn't
realized
that
the
well
I
wait
I.
Think
oh
yeah
I
had
the
section
group
had
to
be
created,
so
it
was
just
create
those
primary.
So
we
can
be
public
by
default.
There's
no
problem
at
all
I
think.
That's
a
good
thing
to
call
out.
A
All
right
anyone
else
would
like
to
share
anything
well.
I'm
gonna
start
advertising.
The
job
I
got
the
job
descriptions
done,
I
have
job
Rex
Open,
so
we're
hiring
Engineers
for
for
backing
offender
for
product
analytics.
So
if
you
know
anyone
I'll
I'll
drop
the
links
in
the
in
the
agenda
after
this
call
and
then
feel
free
to
get
some
referrals
I'd
really
much
appreciate
that
if
there's
nothing
else,
everyone
gets
10
minutes
back,
enjoy
your
Mondays
enjoy
your
weeks.