►
From YouTube: GitLab 14.5 Kickoff - Monitor:Monitor
Description
Monitor 14.5 Planning Issue: https://gitlab.com/gitlab-org/monitor/monitor/-/issues/81
A
So
the
goals
for
this
milestone
are
to
enhance
some
of
the
alert
and
incident
features
to
better
enable
our
teams
to
do
some
dog
fooding
of
these
features,
and
in
addition
to
that,
we
will
try
trying
to
stay
ahead
of
the
curve
and
try
and
validate
some
features
that
could
be
dog
food
in
the
future.
We
do
have
some
work
to
finish
up.
That
is
nearly
complete
from
14.4,
but
let's
go
ahead
and
dive
into
the
details.
A
We
have
some
customers
that
are
asking
for
some
enhancements
to
allowing
http
endpoints
for
alerts
to
include
bearer
tokens,
as
well
as
some
generic
authorization
internally,
we
have
a
customer
that
is
wanting
to
dog
food
alerts,
but
wants
to
kind
of
cross
reference
and
reconcile
with
the
system
that
they
already
have
in
place
right
now,
when
you
post
an
alert
using
a
generic
http
endpoint,
you
only
get
a
200
upon
a
successful
post
and
they're
looking
for
some
more
information.
So
what
is
the
alert
id
just
to
make
sure
that
things
are
working?
A
As
expected,
we
have
some
performance
indicators
that
we
want
to
update.
That
will
give
us
some
more
information
right
now.
This
performance
indicator
is
just
showing
us
that
these
numbers
are
increasing,
so
the
count
of
projects
for
incidents
are
being
created
is
increasing,
but
we
don't
know
how
much
month
over
month,
so
we're
going
to
break
that
down
a
little
bit
more.
A
This
is
for
slack
and
incident
management
workflows
we're
going
to
be
interviewing
some
internal
customers,
as
well
as
some
external
customers,
to
better
understand
how
we
could
incorporate
this
into
some
of
the
features
that
we
have
right
now.
Our
internal
teams
have
some
homegrown
tools
and
maybe
there's
an
opportunity
there
to
augment
some
of
those,
or
maybe
there
are
some
other
insights
from
internal
customers
to
make
those
really
lovable
features
I'll,
also
be
working
on
validating
some
requirements
for
an
internal
analytics
dashboard
for
the
infrastructure
team,
for
instance.
A
Right
now
they
are
doing
they're
doing
some
of
their
own
reporting
and
they're,
also
using
alerts
outside
of
outside
of
git
lab,
but
is
there
an
opportunity
that
we
could
pull
some
of
that
into
pull
some
of
that
into
git?
Lab
alerts
go
into
git
lab
and
then
we
can
kind
of
build
out
some
of
some
of
those
dashboards
for
the
teams
and
help
further
enable
that
dog
fooding
just
circling
back
some
of
the
work
that
we
need
to
finish
are
doing
some
permission,
updates
for
creating
incidents.
A
Staying
ahead,
we're
going
to
be
doing
a
technical
evaluation
for
incident
timelines,
and
then
we
also
have
some
work
to
finish
up
on
the
notifications
for
manually
created
incidents.
These
are
not
the
top
priorities
for
this
milestone,
but
hopefully
we
will
get
to
most,
if
not
all,
of
the
things
that
are
on
this
issue.
That's
all
for
now.
Thank
you.
Bye.