►
From YouTube: GitLab 12.6 Kickoff - Monitor:Health
A
So
here
is
our
planning
issue
for
12.6
I've
linked
our
plan
here
this
particular
milestone.
We
have
us
holidays,
Thanksgiving
and
then,
at
the
end
of
the
milestone,
I
anticipate
many
of
us
having
time
off
also
for
end-of-the-year
holidays,
so
it
might
seem
a
little
bit
light,
but
we
want
to
make
sure
that
we're
not
over
committing
and
that
you
know
if
we
magically
get
everything
done,
then
we
can
pull
some
more
stuff
in
all
right,
I'm,
going
to
walk
through
each
one,
and
we
can
talk
about
them
as
we
get
there.
A
So
first
one
adding
century
as
a
kit
lab
managed
app,
so
the
ability
to
deploy
it
to
kubernetes
cluster
that
you
have
connected
to
a
kit
lab
project.
So
this
is
still
project
based.
This
is
not
based
on
group
level
clusters,
although
that's
an
interesting
thing,
we
will
consider
for
the
future.
This
particular
issue
is
just
to
make
it
easy
for
an
individual
to
stand
up
error
tracking
for
a
single
repository
that
they
have
within
a
github
project.
A
A
C
A
A
B
A
C
A
Awesome
so,
as
we
make
the
list
of
century
areas
and
get
lab
better,
we
had
more
pertinent
information
to
it
and
we
give
field
the
ability
to
filter
it
and
sort
it.
We
want
to
give
people
the
ability
to
respond
to
areas
within
get
lab
and
so
creating
issues
from
the
century.
Detail
page
is
the
next
thing
we're
working
on
until
six
so
case.
Anybody,
it's
not
familiar
with
that
is
we
have
this
beautiful
new
detail,
page
that's
releasing
in
12:5
and
we're
gonna.
Add
the
ability
to
create
new
issues
for
right.
A
A
E
E
F
D
A
We
are
releasing
the
ability,
it's
gonna,
be
in
the
error,
detail
page,
so
I
don't
have
easy
access
to
designs
of
that.
It
looks
like
this.
The
or
a
detail
page
looks
like
this,
and
so
this
issue
is
just
copying
with
the
arrow
detail.
Page
looks
like
into
an
issue
and
since
we
already
figured
out
how
to
do
the
secretaries
that
it
was
why,
as
part
of
the
scope,
I
am
NOT
against
creating
another
issue,
but
it's.
F
E
A
H
Sorry,
just
to
make
sure
I
understand
have
we
talked
to
its
plan
right.
That
manages,
like
all
the
components
on
this
page,
because
if
we're
adding
the
stack
trace,
we're
now
playing
with
like
the
component
order
here
right,
because
it's
not
going
to
be
a
part
of
the
issue
description.
If
we're
using
that
component
Olenna.
H
C
H
C
D
H
B
B
A
A
This
one
is
simple:
this
is
just
adding
metrics
for
seeing
how
many
people
actually
create
issues
on
centuries
and
I
had
a
question
on
this
one,
because
I
originally
wrote
it
so
that
we
want
to
count
the
number
of
issues
created
from
the
century
or
a
detail
page,
but
there's
a
feature
in
the
century
where
you
can
create
a
collab
issue
from
century.
For
an
error
and
to
me
the
motivation
and
either
scenario
is
the
same.
A
So
I
think
that
we
should
probably
count
both
and
add
those
together
to
get
an
understanding
of
how
many
issues
people
are
creating
for
century
errors,
regardless
of
where
they
created
from.
Is
it
possible
to
know
if
an
issue
was
created
from
century,
and
we
don't
know
that
can
be
part
of
this
investigation.
A
A
E
A
And
we'll
make
that
part
of
the
thank
you
feeling
we'll
make
that
part
of
the
investigation
of
this
and,
if
it's
not
possible
to
know
I
can
assess
how
difficult
it
is
to
start
tracking
that
I'd
love
to
get
a
sense
of
you
know
everyone's
doing
it
from
century
and
not
from
get
lab
or
people
are
barely
using
the
future
home
century.
To
the
extent
that
we
have
information
on
that,
okay.
D
C
D
G
C
B
B
A
A
F
A
A
A
A
A
All
right,
so
this
one
we
just
had
an
excellent
conversation
with
Dennis
tang,
an
engineering
manager
on
the
manage
team
about
how
is
the
integration
between
gitlab
and
century
works.
So
there's
still
going
to
be
a
little
bit
of
Investigation
that
may
affect
this
issue,
but
essentially
on
the
new
era,
detail
page.
C
A
Rylander's
yeah:
this
is
a
great
question
and
I
think
this
is
very
had
a
couple
miscommunications.
My
understanding
is
that
we
want
to
link
to
the
gitlab
commit
as
gitlab
is
where
we
are
going
to
fix
the
problem.
So
we
want
to
keep
people
and
get
web,
and
if
you
have
access
to
the
gitlab
commit
you
have
access
to
the
individual
who
created
that
commit.
A
D
A
I'll,
let
it
back
to
your
question
about
our
conversation
we
just
had
to
Dennis.
We
are
going
to
pause
on
linking
to
that
pause.
We're
gonna
have
another
issue
where
we
add
the
century
release
information
to
the
error.
That
will
be
a
different
issue.
The
scope
of
this
one
will
be
to
link
to
the
suspect
commit
from
which
they
are
originated
in
jail.
Ab.
That
makes
sense
to
everybody.
C
A
A
Okay,
so
this
particular
one
we
are
working
to
get
access
to
a
test
instance
of
century
that
Dennis
has
set
up
so
that
we
can
test
this
as
the
current
get
lab
at
century
and
since
is
about
eighteen
months
behind
and
on
a
really
old
version.
So
it's
not
using
any
of
the
new
suspect
suspect
commit
functionality,
that's
injuries
created,
and
we
want
to
be
able
to
use
that
all
right.
Any
questions.
C
A
Okay,
so
in
twelve
five
we're
gonna
have
a
brand
new
error,
detail
page
in
twelve
six,
we're
working
on
the
ability
to
create
an
issue
from
that
page
so
that
all
of
the
error
details
potentially
the
stacktrace
appear
in
that
issue.
The
scope
of
this
issue
is
to
link
that
back
to
the
area
detail
page.
So
if
Elena
and
has
been
triaging
errors,
she
finds
a
critical
one.
She
creates
an
issue
for
it
and
I'm
doing
the
same
I'm,
not
creating
duplicate
issues.
A
A
D
G
A
There's
been
a
lot
of
questions
and
I've,
been
asking
a
lot
of
team
members
to
try
and
help
me
figure
out
how
we
can
associate
century
errors
with
Gila
commits
releases
and
merge
requests,
and
so
I
wanted
to
create
a
spike
issue
to
capture
that
work
and
for
if
we
wanted
to
assign
this
to
somebody
for
doing
that
research.
But
it's
here
to
capture
the
research
necessary
to
figure
out
how
to
do
this.
A
I'm
going
to
clarify
something
here
when
I
say
release
originally
I
meant
get
web
release.
We
had
a
conversation
this
morning
that
uncovered
that
it
might
be
more
useful
to
be
linking
to
the
century
release
page
in
century
P.
So
when
we're
saying
release,
I
need
to
be
really
careful
to
say,
get
live,
release
or
century
release,
and
we
still
need
to
figure
out
which
one
or
both
is
most
useful
to
people.
Does
anybody
have
any
questions
around
that
up
until
this
moment,
I've
been
confusing
everyone,
so
I'm
trying
to
be
clear
now.
B
A
A
We
don't
dog
food
this
as
heavily
as
I
think
we
could
so
originally
when
we
were
planning
a
scope
of
work.
My
thought
was:
let's
correlate
a
century
error
to
the
gitlab,
commit
a
get
lab,
merge,
requests
and
a
get
lab
release.
Well,
we
obviously
use
commits-
and
we
obviously
use
merge
requests
very
heavily.
We
are
not
using
the
release
feature
as
much,
but
based
on
some
conversations.
I've
had
so
far
century
releases
in
century.
Show
you
a
page
of
all
of
the
commits
that
are
part
of
that
release
and
errors
associated
with
that
release.
A
So,
while
it's
not
the
get
lab
release,
they
are
one-to-one
and
the
UI
and
century
is
very
helpful
for
digging
through
all
the
errors
that
were
introduced
with
a
new
release.
So
since
we
don't
have
that
particular
functionality
in
git
lab,
we
want
to
link
to
the
century
release
that
makes
sense.
It's
confusing.
E
E
F
F
B
F
A
A
You
have
to
go
in
century,
create
a
release
and
then
tell
sentry
all
of
the
commits
that
release
is
going
to
contain,
and
then
our
few
deploy
you
have
to
tell
it
again
that
you
released
it
and
Dennis
said
if
our
integration
is
upgraded
and
were
fully
integrated
with
century.
We
shouldn't
have
to
do
this.
It
should
happen
automatically.
F
A
A
Okay,
moving
right
along
the
next
few
of
these
are
confidential
issues,
so
I
don't
know
if
I
want
to
show
them
on
this
public
recording.
So
this
is
all
monitor,
related
app
limits
work.
All
these
were
created.
We've
got
a
backlog
of
them
for
the
monitor
stage.
We're
sharing
these
with
the
APN
side
of
the
house
and
they're,
essentially
to
protect
ourselves
from
someone
utilizing
unbounded
features.
A
A
D
H
B
That's
right,
I
think
it
hasn't
happened
to
anybody
for
a
while
on
this
team
and
we
tried
to
close
it
at
some
point
and
then,
as
soon
as
we
closed
it,
then
somebody
else
chimed
in
and
was
like
well
wait.
This
is
still
a
problem
for,
for
us,
so
I
mean
if
we're
not
seeing
this
anymore.
We
could
try
to
close
this
again
but
I
guess:
let's
let
Shawn
look
into
it
a
little
further
to
determine
that.
Let's.
A
E
A
A
We
just
finished
a
huge
round
of
solution,
validation,
research
with
talking
to
more
people
about
their
error,
tracking
workflows,
getting
feedback
on
designs,
it's
actually
really
cool
or
one
of
the
team's
pioneering
this
new
product
development
workflow.
So
the
fact
that
we're
able
to
do
some
usability,
testing
and
interviews
was
so
helpful
in
planning,
12.7,
and
so
the
things
that
we're
working
on
validating
and
designing
for
are
trying
to
add
more
links
to
merge,
requests
and
releases
that
we've
talked
about
before.
A
So
that's
gonna
be
on
the
arrow
detail,
page,
adding
more
information
to
the
arrow
detail.
Page
the
language,
the
framework
priority
or
urgency
are
potentially
things
that
we'll
get
back
via
the
API,
we're
not
saying
that
they
are,
but
we're
trying
to
look
at
all
the
information
all
of
the
tags,
that
errors
have
and
give
people
as
much
pertinent
information
and
get
up
as
possible,
and
then
this
is
something
else.
This
is
a
new.
A
Action
that
emerged
from
research
that
people
really
enjoy
having
to
be
able
to
do
two
errors,
so
the
ability
to
ignore
an
error-
and
this
came
from
people
who
are
using
roll
bar
from
people
who
are
using
air
brake.
This
is
not
deletion.
This
is
not
closing.
This
is
you
know,
areas
are
noisy
and
plentiful,
and
so
I
want
to
be
able
to
refine
my
view
by
ignoring
something
and
removing
it
from
that
view
will
still
exist
in
the
country,
and
the
NBC
of
this
will
likely
be
remove
a
single
instance
of
an
error.
A
D
A
Thank
you
for
calling
that
out
Amelia.
We
want
to
add
different
sorts
of
filtering
to
the
area
list
within
collab
as
well,
and
so
the
ideas
that
we
are
playing
with
right
now
are
by
environment,
release,
merger
quest,
and
then
this
notion
of
user
name
or
user
ID.
We
have
not
flush
those
out.
So
when
we
have
more
information,
we'll
talk
about
those
in
the
team
meetings
as
we
move
through
12.6
and
I
will
link
those
in
the
12.6
planning
issues.
Thank
you
for
highlighting
that
for
documentation
and
transparency.