►
From YouTube: GitLab 13.2 Kick-off - Monitor:Health
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Oh
hi
welcome
to
the
13.2
kickoff
for
the
Health
Group
and
monitor
stage.
My
name
is
Sarah
Weller
and
I'm
the
senior
product
manager
for
this
group.
So
in
13.2
we've
got
a
couple
of
exciting
highlights.
Overall,
our
team
will
be
working
to
continue
to
improve
the
triage
workflow
in
the
categories
of
alert
and
incident
management
in
gitlab
to
kick
us
off.
One
of
the
first
top-level
items
that
we'll
be
working
on
is
an
MVC
integration
with
ops.
Genie
optionee
is
a
popular
tool
for
Operations
tasks,
especially
anything
ITSM
related.
A
There
is
an
opportunity
in
the
future
where
get
lab
invests
in
a
deep-fry
directional
integration
with
ops
genie
so
before
we
invest
in
that,
we
want
to
make
sure
that
there's
excitement
and
need
for
that
in
our
community.
So
with
this
integration
that
we'll
finish
within
one
month,
we're
going
to
start
with
a
very
simple
linking
between
the
platforms
and
that's
going
to
generate
awareness
and
excitement
the
community,
which
will
be
tracking
usage
on
to
validate
future
investment.
A
Next
up,
we're
gonna
begin
surfacing
different
observability
artifacts
and
linking
them
into
the
triage
workflow.
So
metrics
and
logs
are
the
two
observability
artifacts
that
we're
focusing
on
in
13.2.
Both
of
these
resources
help
responders
solve
problems
faster.
They
are
a
natural
part
of
the
investigative
workflow,
and
so
if
we
can
bring
those
closer
to
the
alert,
the
alert
being
the
notification
that
the
responder
received
to
understand
that
something
was
wrong.
We
can
significantly
cut
down
the
amount
of
time
it
takes
someone
to
understand
the
root
cause
of
an
incident.
A
So
what
that's
going
to
look
like
is
a
gitlab
alert
with
the
metrics
chart
for
that
alert
embedded
directly
in
it,
so
we're
gonna
be
starting
with
Prometheus
alerts.
Both
forget
lab
manage
Prometheus
following
that
up
with
externally
managed
instance
of
Prometheus.
So,
as
I
just
mentioned,
the
second
linked
observability
artifact
will
be
working
on
our
logs
again
when
triaging
alerts,
users
may
be
able
to
quickly
investigate
the
issue
logs
help
with
that
investigation
help
define
the
root
cause.
So
what
that
will
look
like
is
similar
to
metrics.
A
A
This
is
a
very
common
pattern
when
setting
up
integrations
between
any
tools
so
that
the
user
has
peace
of
mind,
that
critical
alerts
aren't
going
to
get
dropped
on
the
floor,
so
just
a
little
peek
into
what
that's
gonna
look
like
this
is
going
to
be
part
of
the
alert
endpoint
configuration
page
in
addition
to
the
URL
and
authorization
key.
We're
gonna
pre
populate
with
a
very
simple
payload,
so
that
someone
can
test
settings
and
make
sure
that
their
endpoint
is
working
as
expect
and
last
but
not
least,
on
our
list
of
highlights.
A
Pedro
duty
is
also
very
common,
commonly
used
on-call
paging
tool
and
market,
and
we
want
to
address
our
set
of
customers
who
use
Pedro
duty
and
give
them
the
ability
to
move
as
much
of
their
incident
management
processes
in
ticket
lab
as
possible.
As
that's
where
a
lot
of
the
root
cause
analysis
and
remediation
workflows
tend
to
happen
so
leveraging
web
hooks
will
be
creating
the
ability
for
responders
to
automatically
generate
that
Levis
use
based
on
page
of
duty
incidents
thanks
so
much
for
watching,
and
that
way
is
kickoff
30
tattoo.
For
the
health
group.