►
From YouTube: GitLab "Insights"-type functionality
Description
Just a quick overview of some of the functionality in GitLab that might be considered "Insights" oriented. I made this slide deck for a customer and decided to share it in a video in case it's useful to anyone else.
Some of this is a little out of date.
Recorded by Francis Potter.
A
Hi
this
is
Francis
Potter
solution,
architect
with
gitlab
and
today
I'm
going
to
talk
about
incites
type
functionality
in
git
lab
because
there's
a
lot
of
different
functionality
in
the
product
that
is
kind
of
insightful,
and
it
can
be
a
little
confusing
as
to
what
all
there
is
and
where
it
is,
and
so
I
put
this
together
for
a
customer
and
just
thought
I
would
share
it
in
a
video
format
in
case
it's
useful
to
anyone
else.
This
is
not
restricted
to
the
product
feature.
A
Called
insights,
I
think
there's
a
little
bit
of
confusion
around
the
names
of
some
of
these
features
so
I'm.
This
is
in
site
type
functionality
and
get
lab
and
I've
loosely
grouped
them
in
ways.
That
kind
of
made
sense
to
me
so
bear
with
me
here
we're
going
to
start
with
insights
related
to
productivity
and
speed,
because
one
of
the
main
value
drivers
forget
lab,
of
course,
is
to
help
our
customers
deliver
better
products
faster.
So
and
the
top
one
is
cycle
analytics
now
cycle
analytics
is
the
current
name.
A
Supposedly
it
might
be
renamed
value
stream
analytics
at
some
point
in
the
near
future.
But
that's
the
current
name
and
notice
on
each
of
my
slides
I've
got
where
you
find
this
feature,
because
they're
these
these
features
are
not
all
in
the
same
place.
There's
no
one
navigational
approach
to
them
all.
So
there's
a
little
handy
guide
here:
we've
actually
got
product
project-level
cycle
analytics
from
the
project
overview,
tab
and
there's
also
a
top
level
cycle
analytics,
but
you
can
actually
get
cycle
analytics
by
group.
A
If
you
want
it
now,
cycle
analytics
is
showing
you
the
amount
of
time
that
that
your
work
is
taking
in
each
stage
and
those
stages
are
defined
in
specific
ways
that
make
sense
to
get
lab.
But
in
fact,
there's
coming
soon
a
new
feature:
that's
going
to
allow
administrators
to
configure
what
those
stages
are
and
how
they're
defined
so
that
you
can
actually
have
your
own
stages.
A
This
is
cool,
but
only
really
useful
if
you're,
using
all
the
parts
of
get
lab
right
now,
and
so
it's
kind
of,
although
it's
in
many
ways
the
cornerstone
of
get
Labatt's,
it's
a
little
bit
of
a
challenge
to
actually
get
meaning
out
of
it.
Currently
then,
there's
insights.
This
is
actually
called
insights
it
for
issue
merger
quests.
A
This
is
kind
of
a
query
based
chart
thing,
it's
that
I'm
showing
issues
here,
but
you
can
also
look
at
merger
quests
and
you
can
actually
design
the
queries
in
yeah
Mille
and
designate
how
you're
querying
the
issue
and
merger
quests
so
that
you
can
show
different
different
factors
and
break
it
down
in
different
ways.
This
is
super
super
powerful.
If
what
you're
looking
at
is
issues
and
merge
requests
over
time,
there's
another
feature
called
productivity
analytics,
which
is
mostly
focused
on
merge
requests.
A
This
is
only
accessible
from
the
analytics
tab
at
the
top
of
the
UI
I
believe,
and
so
some
of
this
is
sort
of
similar
to
the
insights.
Merge
request
stuff,
but
you
can
also
look
at
some
details
like
time
from
last
commit
to
merge
and
number
of
lines
of
code
per
commit.
So
you
can
look
at
kind
of
a
little
bit
kind
of
different,
different
sort
of
data
in
productivity
analytics.
A
There's
also
issue
analytics,
which
is
only
available
at
the
group
level
as
near
as
I
can
tell.
This
is
a
subset
of
the
information.
That's
available
in
insights
and
insights
is
a
more
powerful
features
so
with
like
the
query,
language
and
everything
so
I'm,
not
really
sure
if
this
is
useful,
but
maybe
it
is
certainly
you
don't
have
to
write
a
llamo
file
in
order
to
use
it.
So
then,
moving
on
that
was
what
we
just
looked
at,
was
insights
related
to
productivity
and
speed.
A
This
is
actually
I
think
one
of
the
more
interesting
charts
in
all
of
gitlab,
because
it
gives
you
at
a
glance
kind
of
a
sense
of
who's,
been
contributing
who
hasn't
over
time.
You
can
also
pick
your
brands
for
that,
then
there's
contributor
activity.
This
is
just
a
slightly
different
view
on
the
same
thing,
this
might
not
be
sort
of.
A
A
It's
got,
pushes
merge,
requests
and
issues
by
contributor,
and
this
is
actually
in
a
separate
area.
This
is
a
group
level
feature
in
a
separate
area
from
the
contributors
graph
that
we
saw
a
few
minutes
ago,
but
once
again,
you
know
useful
for
telling
who's
been,
making
the
most
doing
the
most
work
and
making
the
most
contribution
to
a
project.
It
doesn't
look
like
there's
a
lot
of
options
here,
though,
so
this
is
a
pretty
fixed
chart.
A
Finally,
you
can
actually
look
at
the
programming
language
in
the
repository
now.
This
is
a
weird
little
feature
if
you're
in
a
repository,
it's
called
charts,
which
is
confusing
because
we
usually
when
we
use
the
word
chart
we're
talking
about
helmet
arts,
which
are
a
completely
different
thing
from
this,
and
there
are
two
charts
on
the
charts
page.
The
top
one
is
programming
languages
used
in
this
repository
and
the
bottom
one
is
commit.
A
Statistics
now
I'm
pretty
sure
that
most
of
this
information
is
available
elsewhere
for
the
programming
language
is
used
in
the
repository
is
available
as
a
little
strip
right
across
the
top
of
the
repo,
in
the
main
view,
so
I'm
not
really
sure
you'd
come
here
too
often
for
that
and
the
commit
information
is
in
some
of
the
other
charts
and
pages
that
we
saw
under
speed
so
I'm
guessing.
This
is
kind
of
an
older
feature,
that's
maybe
being
sort
of
superseded
by
some
of
the
things
that
have
come
in
more
recently.
A
A
First
off,
there's
a
great
thing
called
a
pipeline's
chart
which,
unlike
all
the
other
churches,
kind
of
got
these
like
smoothed
out
curves
to
it,
but
this
is
kind
of
giving
you
a
sense
of
how
much
activity
there's
now
six
I'm
a
success,
there's
been
with
your
pipelines
over
a
recent
period
of
time.
Once
again,
it
seems
like
there's
not
a
lot
of
controls
here
to
really
control
anything,
but
it's
pretty
to
look
at
and
you
might
have
to
see
if,
like
you've,
had
a
lot
of
failures
recently
or
something
like
that.
A
This
is
available
at
the
project
level
under
CI
CD.
Once
again,
it's
called
charts,
there's
also
the
pipeline's
list
itself,
which
is
a
little
bit
more
of
a
functional
page
than
really
an
insights
thing,
but
there's
so
much
here.
This
is
kind
of
in
many
ways.
If
you're
running
CI
CD
is
many
ways
sort
of
the
centerpiece
of
your
work
with
gitlab,
you
could
see
at
a
glance
the
recent
pipelines
whether
they've
succeeded
or
failed
who
ran
them.
A
What
what
all
the
jobs
were,
how
long
it
took
and
you
can
like
link
out
to
the
environments
and
the
blogs
and
everything
for
directly
from
here,
and
so
once
again,
this
is
kind
of
an
added
Lance
view
of
what's
going
on
with
the
CI
CD
for
the
project,
there's
also
the
environments
and
deployments
list.
This
is
under
environments
under
your
project
operations
and
once
again,
it's
sort
of
at
a
glance.
What's
up
in
each
environment,
how
much
activity
there
or
how?
A
How
many
pods
are
in
each
environment
if
you're
using
kubernetes-
and
you
can
link
out
to
here
from
here
to
either
the
environment
itself
in
a
web
browser
or
to
the
to
the
terminal
in
that
environment?
So
this
is
a
really
kind
of
a
central
place.
It's
both
insight
as
well
as
kind
of
active
use
within
environments
and
deployments
and
I
think
of
it
as
sort
of
an
insight
type
of
functionality.
A
They
kind
of
rolling
up,
there's
the
environments
dashboard,
which
just
came
out
a
couple
of
releases
ago,
and
this
actually
shows
you
that
information
about
each
environment,
but
in
more
of
kind
of
a
nugget
form-
and
you
can
actually
configure
this
for
yourself,
so
you're,
showing
the
environments
that
really
matter
to
you
on
on
one
page
and
this
cuts
across
multiple
projects.
So
you
can
really
kind
of
monitor.
What's
going
on
in
a
lot
of
different
environments,
all
from
one
location.
A
Finally,
there's
a
think
of
operations,
dashboard
which
actually
preceded
environments,
dashboard
and
looks
really
similar,
and
it
can
be
a
little
bit
confusing,
but
you
could
think
of
operations
dashboard
as
being
more
general
there's
a
there's,
a
cell
for
each
project
instead
of
a
cell
for
each
environment.
Also,
this
is
going
to
give
you
see:
ICD
information
or
CI
information
pipeline
information,
even
if
you're
not
using
CDU.
If
there
are
no
environments
at
all
for
a
project,
this
is
still
relevant.
So
this
is
more
at
a
project
level.
A
I
actually
didn't
add
those
in
this
presentation,
because
the
customer
who
is
asking
about
them
wasn't
really
looking
at
them
very
much,
but
it's
really
important
to
mention
insights
related
to
application
security,
so
I
hope
this
has
been
helpful
and
interesting.
I'm
going
to
make
these
slides
available
too,
or
you
can
ask
me
if
you
want
to
see
them
and
thanks
a
bunch.