►
From YouTube: UX Showcase Monitor: Documentation and Status Page
Description
The video talks about how the Monitor team is working on improving their documentation and working on a Status Page.
A
Hey
everyone:
this
is
an
idea
with
the
UX
showcase
for
the
monitor
team
and
today,
we'll
be
talking
about
how
we're
collaborating
and
crossed,
monitor
team,
to
improve
gitlab
docks
for
monitoring
and
also
how
Amelia
and
the
health
team
are
building
our
first-ever
gift
lab
Status
page.
So,
let's
dive
in.
A
So
let's
talk
about
github
Docs
for
monitoring
first
and
for
a
little
background.
Monitoring.
The
performance
of
an
application
is
an
extremely
important
step
in
making
sure
of
its
availability
and
reliability
so
give
lab
we're
currently
focusing
on
building
a
solution
that
would
allow
our
users
to
monitor
the
performance
and
health
of
their
application,
all
in
one
place
within
get
lab.
A
So
github
monitoring
features
include
things
like
metrics
dashboards,
logs
tracing
incident
management,
air
tracking
and
more
and
most
of
the
categories
are
currently
viable,
and
you
can
learn
more
about
different
categories
that
we
have
product
direction
and
their
maturity.
Add
this
link
that
are
provided
in
this
slide.
A
So
we
know
that
enabling
the
monitoring
features
and
instrumenting
ones
application
to
achieve
observability
is
a
very
difficult
and
confusing
task,
especially
for
those
doing
it
for
the
first
time
and
coincidentally,
being
pretty
new
at
lab.
I
was
also
doing
it
for
the
first
time.
So
it
was
a
great
opportunity
for
me
to
document
the
process
for
enabling
monitoring
in
gitlab
and
to
document
all
the
spots
where
I
stumbled,
where
I
felt
like
I
didn't
have
enough
information
to
proceed
with
the
process
as
someone
who's
doing
it
for
the
first
time.
A
So
after
looking
at
this,
we
asked
ourselves
a
question:
how
can
we
make
it
easier
to
enable
monitoring
in
gitlab
and
turned
out
that
documentation
for
enabling
monitoring
in
gitlab
is
very
very
lacking?
Yet
we
believe
that
it's
an
extremely
important
part
of
the
product,
especially
at
its
current
maturity
level.
So
we
really
need
to
leverage
good
documentation
to
guide
our
users
in
the
process
to
help
them,
especially
those
users
enabling
monitoring
for
the
first
time,
it's
tremendous
for
the
first
time.
A
So
as
the
first
step
before
we
go
on
to
tinker
with
the
actual
process
for
enabling
monitoring
which
we
are
planning
to
do,
but
as
the
first
step,
we
decided
to
tackle
the
poor
documentation.
So
let's
improve
documentation
and
the
first
step
in
improving
documentation
was
to
understand
what
is
the
current
structure
for
monitoring
documentation?
Where
do
the
users
go
to
find
information
about
enabling
monitoring,
and
why
is
the
current
structure
the
way
it
is?
How
did
we
come
to
this?
A
So
then
I
went
back
to
the
mural
board
and
I
documented
the
current
structure
of
the
dogs
and
turned
out
that
it
is
indeed
very
confusing.
So
it
wasn't
just
me
it
wasn't
just
because
I
may
be
not
very
technical
or
I
was
just
doing
it.
For
the
first
time
the
documentation
is
very
fragmented
and
kind
of
scattered
across
the
gitlab
dog
site
and
in
many
places
it's
also
incomplete.
So
here
in
the
red
post-its,
you
can
also
see
that
those
are
all
of
my
notes
where
I
was
confused
and
I
wasn't
sure.
A
Why
does
this
page
have
a
certain
header?
Why
is
it
called
this
way?
Why
is
it
in
this
place
in
the
github
Docs
navigation,
so
I
had
lots
of
questions
and
I
was
very
confused
and
the
current
state
of
the
documentation
is
so
poor
that
we're
actually
pretty
confident
that
we
can
make
really
great
improvements
right
away
so
lesson
from
the
docs,
so
yeah
as
I
said
we're
we're
pretty
confident
about
how
we
want
to
approach
improving
the
documentation
because
the
the
Doc's
are
very
scattered
and
incomplete.
A
So
we
know
that
we
need
to
fill
those
gaps,
so
we
decided
to
not
start
with
a
problem,
validation
effort
and
just
jump
into
trying
out
an
MVC
improvement
first.
So
it's
the
first
step.
We
want
to
do
an
expert
card
sorting
where
we
will
involve
the
whole
ops
team.
Anyone
who
wants
to
participate
can
we'll
be
doing
this
in
this
milestone
and
based
on
the
results
of
the
card
sort.
We
will
hopefully
have
a
good
idea
for
what
the
new
structure
should
be
then
we'll
implement
it.
A
We
will
work
with
our
technical
writers
to
to
create
the
improved
documentation,
fill
in
the
gaps
in
the
content
and
change
the
structure
of
the
docs
change,
the
navigation
of
the
for
for
monitoring,
Docs
and
then
we're
planning
to
conduct
a
solution,
validation
effort.
So
then
we
can
understand
how
we
need
to
iterate.
How
can
we
improve
it
further
and
whether
we
were
right
in
the
new
structure
that
we
proposed?
A
A
A
So,
in
the
end,
it
was
decided
that
we
will
have
a
separate
instance,
ops
that
give
lab
dotnet,
but
there
was
a
problem,
it's
a
private
instance.
So
if
we
move
there,
it
means
we're
losing
some
of
the
visibility
and
transparency
that
we
have
around
our
incident
issues.
So
there
was
a
need
to
fix
that
so
to
do
that.
The
health
team,
under
the
direction
of
Amelia
who's
been
working
on
the
designs
for
the
NBC
page
decided
to
work
on
the
status
page,
get
labs
own
status,
page.
A
So
what
they
did,
they
analyzed
the
current
status
page
offering
on
status
IO.
This
is
what
we
use
currently
for
the
get
lab
status,
page
and
Amelia
also
checked
out.
A
bunch
of
other
different
status
pages
did
a
bit
of
competitor
analysis,
and
eventually
they
landed
on
this
beautiful
vision,
design
where
you
could
see
the
incident
updates
for
each
service,
as
well
as
a
full
list
of
incidents.
A
So
what
you
see
here
is
definitely
like
a
visionary
mock-up
and
it
had
to
be
broken
down
into
several
different
iterations
and
how
the
healthy
approached
it
they
thought.
Okay,
what
do
we
primarily
need
to
unblock
our
sres
from
dog
fooding
incent
management?
So
that's
how
they
were
able
to
prioritize
and
do
the
breakdown.
A
A
So
this
is
the
final
breakdown
and
the
MVC
will
be
completed
in
12.9.
So
it's
it's
almost
completed.
Now
the
first
MVC,
the
second
MVC-
will
be
worked
on
12:10
and
then,
after
that,
the
health
team
will
be
gathering
some
feedback
from
the
info
team
and
then
focus
on
getting
the
status
page
to
viable.