►
From YouTube: Error Budget Attribution for Purchase group
Description
2 min video showing budget attribution for the Purchase group.
https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1114
A
Hi
everyone-
this
is
bob
from
the
scalability
team.
I
wanted
to
show
really
quickly
the
new
panels
we've
added
to
the
stage
group
dashboard
that
should
make
it
easier
to
dig
into
where
an
error
budget
is
being
spent.
I'm
going
to
do
this
in
the
context
of
the
purchase
group
because
they
have
been
spending
more
more
of
their
budget
than
the
20
minutes
that
we
that
we
have.
A
So,
let's
start
by
going
to
their
dashboard
and
as
you
can
see,
there's
a
new
row
here
and
when
we
expand
this
the
top.
This
is
going
to
list
all
the
all
the
failures,
the
top
one
is
going
to
be
the
one
that
is
going
to
have
the
biggest
negative
effect
and
then
on
the
remaining
error.
Ratchet
there's
some
short
explanation
here
on
the
side
regarding
the
most
common
components.
A
For
now,
only
puma
and
sidekick
are
documented
here,
including
with
some
links
to
the
logs
that
allow
people
to
dig
deeper
into
what
is
causing
the
problem.
So,
as
you
can
see
here,
and
the
biggest
source
of
the
budget
spent
is
puma
aptx
and
this
means
slow
request
to
the
rails
app.
So
any
requests
and
taking
longer
than
one
second
would
qualify
as
that.
So
if
you
want
to
see
which
endpoint
is
causing
that
we
can
open
up
the
logs.