►
From YouTube: GitLab 14.6 Kickoff - Monitor:Monitor
Description
Monitor 14.6 Planning Issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/89
A
For
this
milestone,
like
I
said,
we're
going
to
be
working
on
incident
timelines,
so
the
focus
for
incident
timelines
will
be
adding
new
timeline
events
and
then
also
the
ability
to
delete
those
timeline.
Events
just
a
reminder:
incident
timelines
are
an
important
part
of
record
keeping
for
incidents.
A
They
give
a
high
level
overview
to
executives
and
external
viewers
of
what
happened
during
the
incident
and
the
steps
that
were
taken
to
be
resolved.
So
it's
intended
to
be
a
little
bit
less
noisy
than
what
you
see
in
system
notes.
The
current
process
for
creating
incident
timelines,
adding
a
list
of
what
happened
and
when
to
the
incident
description.
Often
after
the
incident
ends,
is
a
manual
and
time
consuming
process.
So
we're
really
excited
to
get
started
on
this
work.
A
A
ux
roadmap
is
going
to
help
us
kind
of
focus
on
a
larger
problem
area
rather
than
feature
by
feature
and
amelia,
and
I
will
be
working
on
this
together
to
make
sure
that
we're
aligned
with
kind
of
our
overall
strategy
for
the
next
couple
quarters
within
monitor
we're
also
going
to
work
on
a
lightning
design
jam.
It's
just
a
one-hour
session,
we'll
be
doing
part
of
it
asynchronously
and
synchronously.
But
we
want
to
ask
the
question:
how
might
we
increase
incident
management
usage
numbers
for
monitor?
A
Dz
has
done
a
great
job
of
releasing
some
new
changes
to
air
tracking,
but
I
also
want
to
add
some
think
about
start
thinking
about
what
types
of
instrumentation
we
want
to
have
around
that
and
then
also
create
an
opportunity.
Canvas
for
air
tracking
there's
also
been
a
lot
of
different
players
in
the
market,
and
I
think
it's
important
to
capture
that
and
I
plan
on
doing
speed
runs
for
these
three
different
vendors,
especially
as
we
saw
recently
in
slack.