►
From YouTube: Demo of General SLA Dashboard Replacement
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
A
So
we
identified
that
the
SLA
dashboard
was
one
that
was
most
a
best
case
for
us
to
replace,
and
so
we've
been
diligently
working
with
the
team
on
how
to
iterate
and
create
an
MVC
replacement
and
so
Jose's
gonna
kind
of
run
through
kind
of
what
we
have
kind
of
see
if
we're
at
a
closer
state
to
replace,
as
well
as
maybe
some
of
the
limitations
of
this
MVC
that
we
have
so
take
it
away.
Jose
thank.
B
C
D
C
Sorry
about
that
bad
timing
I
try
to
get
that
Mr
in
today,
but
it
hasn't
been
reviewed
yet.
But
that
is
why
there
are
six
different
series
on
the
right-hand
side
and
like
multiple
lines
on
your
graphs
as
well.
So
you
can
see
it's
not
a
single
line
there
and
that's
because
we're
currently
moving
from
Prometheus
to
Thanos
for
these
metrics
and
its
ongoing.
Unfortunately,
sorry
I
just
wanted
to
point
that
out
because
it
might
be
confusing
and
also
the
the
fact
that
the
availability
is
116
percent
is
the
same
problem.
E
B
C
B
So,
having
said
that,
a
couple
of
the
limitations
that
we
currently
have
that
everyone
has
but
we're
still
working
on
adding
tequila,
is
the
single
static
colors.
So,
for
example,
if
we
go
to
the
primary
service
average
of
ability
for
period-
and
you
see
the
different
services
such
a
psychic
API-
get
to
see
that
a
closer
to
100%,
you
become
green,
the
lower
the
ability
he
goes
to
red.
In
our
case,
we
just
show
up
green.
We
do
plan
to
introduce
additional
colors.
B
Another
think
that
you're
not
gonna
has
that
we
currently
don't
support
its
the
resizing
of
the
panels,
we're
also
working
on
adding
that
the
barrier
will
drop
down
so
for
in
the
case
of
Griffin
on
you
can
change
the
environment
on
the
fly.
In
a
case
you
had,
this
environments
are
hard-coded.
This
is
a
huge
test.
We've
trained
to
undertake
for
13
point
out.
It
should
be
hopefully
available
entertaining
point
out
as
well
as
the
time
range
variable.
B
So,
as
you
can
see,
we
added
this
like
clarification
here,
seven
days,
because
if
you
change
this
type
here
here
only
effect,
it
will
not
affect
it.
So,
in
a
case,
we're
fine
I'd.
You
change
this
to
seven
days.
One
Mon
one
day
it
will
change
the
query
appropriately,
so
it
you
query,
says
that
you
want
some
base.
One
day
of
data,
refined
I
will
change
it.
We
don't
we're
also
planning
to
support
that
for
a
certain
point
out.
B
Fortunately,
when
deployed
that
what
deployment
that
actually
did
happen
was
the
percent
of
support
for
12.10.
If
we
didn't
used
to
support
like
perceptive
values
like
ebu
show
up
us,
1.0
or
0.98.
Now
we
do
support.
So
that's
as
colossus.
If
we
can
get
to
Griffin
ax
at
the
moment
for
single
stat
panels
and
I
think
that
hoser.
E
B
E
B
B
You
can
see
that
you
have
variable
interpolation
called
range.
We
want
to
support
that
the
same
kind
of
interpolation
I'm,
not
sure
we're
gonna
coat
range.
We're
still
like
in
be
into
decision
making
process
of
what
we're
gonna
call
it
we
do
are.
We
are
currently
implementing
it.
We
just
haven't
quite
decided
what
we're
gonna
call
it.
B
So,
okay,
so
one
of
the
things
that
well,
we
did
find
out
that
your
phone
I
did
it,
but
currently
because
the
panels
or
all
of
the
services
are
working.
There
was
one
point
when
one
of
the
services
and
believe
me
was
a
registry
service
didn't
have
any
data
we're
gonna
find
out
does.
Is
that
we
will?
He
will
not
render
the
panel,
but
in
the
case
of
your
lab,
if
there
is
no
data,
they
will
demolition.
There
will
be
an
empty
state
showing
up
but
currently
says
all
the
single
staff
panels
have
data.
C
I
just
be
a
bit
specific
about
why
that
is
it
because
you
know,
obviously
on
on
the
singles
on
the
single
step
is
multiple
series,
and
so
it
creates
single
stats,
whereas
obviously,
on
the
on
the
get
lab
dashboards,
we
create
one
for
each
series.
So
you
don't
you
don't
have
that
way
of
kind
of
multiplying
out
the
single
stack
panels,
which
is
it
sounds
subtle,
but
it's
quite
an
important
difference,
but
I
just
wanted
to
kind
of
highlight.
B
That
to
it
actually
I
was
going
to
touch
on
that.
But
thank
you
so,
in
the
case
of
like
the
single
only
the
SLE
trains
primary
services,
one
of
the
smaller
differences
is
that,
even
though
the
charts
look
alike
in
terms
of
what
the
rendering
one
of
the
things
that
we
don't
have
is
a
threshold
area
that
show
up
seer
like
as
a
red
area
like
what's
the
lesson
danger
so
where
they
have
ability
Assessor
need
to
be
affected.
B
We
plan
to
support
that
I,
don't
remember
which
milestone
it's
the
one
I'm,
not
sure
I,
think
it's
for
to
point
out
that
my
I
might
be
wrong
as
far
as
another
difference
that
Grenada's
in
between
I'm
in
the
matrix
formula
is
that
all
all
times
from
graph
on
our
etc'
and
the
metrics
dashboard
supports
local.
We
do
have
at
it.
I
have
an
issue
to
add
that
as
a
feature,
so
we
can
just
toggle
between
UTC
and
local
time
cells.
B
And
finally,
a
small,
a
small
difference
between
the
Garifuna
were
in
the
Killa
word
is
that
we
don't
we
haven't
added
or
four
text
panels
such
as
this
one,
where
it
just
mentions
what
this
specific
dashboard
bus.
We
do
plan
to
support
that
again,
I,
don't
remember
which
issues
did
this
for
which
milestone
this
issue
is
scheduled
for,
but
at
the
moment
this
is
all
all
of
the
differences
between
their
fauna
as
well
as
animators
work,
as
well
as
what
things
are
currently
in
and.
B
D
D
D
Right
cool,
so
my
day
usually
starts
with
this
dashboard
and
it
might
not
make
sense
for
a
lot
of
people,
but
because
scalability
is
responsible,
for
you
know,
creating
like
a
lot
of
capacity
for
github.com
I
need
to
understand
the
historical
data
before
I
go
to
future.
So
for
me,
the
last
30
days
is
not
the
only
range
I'm
looking
at
and
looking
at,
not
only
like
6
hours,
7
hours,
I'm,
not
looking
only
7
days,
I'm
looking
at
30
days
and
looking
in
90
days
and
in
some
cases,
even
6
months.
D
So
that
actually
makes
me
gives
me
like
historical
trends
and
allows
me
to
with
some
other
dashboards
think
about
where
we
are
going
to
go
next.
Obviously,
this
is
important,
but
this
is
the
list
of
my
my
worries.
What
mostly
concerns
me
is
this
dashboard
and
these
individual
ones.
So
a
couple
of
things
that
are
really
important
here,
I
regularly
go
like
if
I
change,
the
range
and
I
do
I
often
go
to
this
one
and
I
highlight
it
so
I
used
this
and
then
I
also
zoom
in
as
well.
D
So
I
look
at
why
this
has
actually
happened
here.
So
then
I
take
a
look
at
all
right.
We
have.
Some
of
these
services
are
dropping
rapidly
in
this
period.
Ok,
so
I
want
to
quickly
understand.
Why
did
the
psychic
service
dropped
so
low
I
would
go
to
the
service
dashboard
and
then
I
would
go
and
find?
Where
is
it
psychic,
but
the
graph
owner
does
really
well?
D
Obviously,
right
like
some,
whether
it's
this
is
all
gonna
load
right
now
or
not,
is
a
different
question.
But
let's
say
I
found
something
on
this
request
per
second
I
will
go
in
further
and
zoom
into
that
one
and
try
to
understand
why
the
RPS
is
so
high
from
that.
I
would
go
into
psychic
detail
and
then
try
to
understand,
for
example,
here
the
queue
detail,
for
example,
I'm
not
doing
an
exact
thing
here
and
then
I
would
zoom
into
further
into
one
of
these
dashboards.
D
So
if
I
can
suggest
something
else
that
will
allow
you
to
also
do
your
work
and
also
us
to
do
our
work
as
well
without
significantly
impacting
us
both
but
actually
properly
do
the
dogfooding
part
is
we
have
the
same
dashboard
right,
forget
lab
dotnet.
We
have
it
replicated
on
github.com
right.
We
maintain
those
dashboards
only
because
we
want
to
be
able
to
expose
be
transparent
to
our
users,
customers
and
so
on.
Transparency,
value
right.
D
Those
dashboards
get
little
love
from
us
because
we
live
on
get
all
that
net
because
we
need
to
make
sure
get
all
that
come
is
working
so,
instead
of
stating
that
we
want
to
replace
was
little
about
net
SLA
dashboard.
Maybe
we
could
say
that
we
can
replace
the
customer
facing
one
and
then
work
to
provide
them
that
value,
so
we
are
also
like
Andrew.
D
The
reason
for
that
is,
it's
that's
how
industry
works
basically,
right
like
we
want
to
hold
ourselves
to
the
higher
standard,
but
we
can't
be
paying
penalties
in
like
serious
dollar
amounts,
because
we
didn't
deliver
like
ninety-nine
point,
nine,
nine
and
a
nine,
and
that
we
are
striving
for
in
the
infrastructure.
So
what
if
we
replace
the
dashboard
github.com,
the
SLA,
dashboard
and
director
customers
towards
the
gate,
love
facing
one
and
it
can
be
on
github.com,
thus
resolving
the
need
to
depend
on
whether
it's
observe
comm,
and
we
can
dog
food.
D
It's
that
because
it
is
gonna,
be
used.
It
has
to
be
used
by
us.
It
has
to
be
used
by
our
customers,
because
that's
what
we
are
going
to
be
showing
and
then
you
can
also
then
catch
up
with
everything
else
that
needs
to
be
built
like
there
is
a
lot
that
you
need
to
do
as
you're
stating
here.
So
this
is
my
tiny
rent
open
for
questions
or
suggestions.
E
E
Sorry
operational
use
cases
which
I
think
you're
diving
into
there
and
I
think
it
seems
like
I
mean
I've
been
interesting
to
understand
those
more.
It
seems
like.
Maybe
to
summarize
what
you
presented
there.
It's
really
you
know
it's
something
that
you're
using
the
analog
kind
of
as
a
jumping
off
point
to
analyze,
trends
and
direction
and
stability.
It's
probably
not
something
that
you're
typically
using
like.
E
E
You
know
towards,
like
you
can't
say
it's
just
on
the
side
and
we're
not
using
it,
and
so
you
know
and
how,
in
terms
of
how
we
want
to
face
that
out,
we'd
like
to
you
know
this
dashboards,
it's
referenced
in
the
handbook,
as
an
SLA
dashboard
we'd
like
to
update
that
at
some
point
soon
to
point
to
the
gitlab
version
of
it
and
then
at
some
point
kind
of
shortly.
Following
that,
we
would
like
to
be
able
to
basically
remove
the
graph
on
aversion.
E
You
know
so
that
we
can
say
at
least
for
this
one
piece.
You
know
we're
using
the
gitlab
version.
I
think
that
that'll
really
help
I
mean
just
expose
more
of
the
types
of
things
that
you're
describing
in
terms
of
usability
or
improvements
and
then
kind
of
the
follow
up
goal
kind
of
where
we're
headed
to
words
and
we're
talking
about
this
in
terms
of
the
next
quarters
goal
for
for
a
p.m.,
but
you
know,
is
to
be
able
to
then
kind
of
complete
the
UX
experience
around
these.
E
E
You
know,
I,
think
those
workflows,
as
you
point
out,
are
gonna,
be
challenging
in
the
current
state.
So
the
idea
with
30
no
and
maybe
13-
wants
to
really
you
know.
As
that
framework
becomes
more
fleshed
out,
you
know,
then
we
can
start
to
look
at
a
more
full
sail.
Migration.
You
know,
in
terms
of
you
know
like
where
you're
doing
that
analysis.
D
Sam
I
totally
get
what
you're
aiming
at
and
like
what
you're
trying
to
accomplish
here,
but
you
don't
have
to
also
remember
that
we
are
trying
to
keep
the
lights
on
on
a
very
important
system
for
this
company.
So
what
you're
telling
me
right
now
is
basically
you're
giving
me
a
price
to
race
in
the
Formula
one
track
and
which
the
point
that
it's
gonna
become
a
folder.
C
D
Pressure
on
infra
department
is
to
have
Enterprise
great
performance
as
platform
and
you're,
telling
me
that
you're
gonna
remove
one
of
the
pieces
of
tool
that
are
very
much
connected,
like
I
showed
you
like,
even
if
it
if
it
seems
like
it's,
not
an
important
dashboard,
it's
a
lot
like
it
showed
you
like,
where
it
is
all
connected.
It
informs
decisions
and,
if
I'm
going
to
battling
with
bugs
when
I
need
to
make
a
decision
immediately
on
on
the
stability
of
this
platform,
it's
gonna
be
very
challenging.
It's
not
something.
We're
gonna
be
challenging.
E
And
III
completely
understand
that
I
mean
that
the
goal
here,
just
to
be
explicit
from
my
perspective,
is
not
to
or
inhibit
our
ability
to
operate
the
site
in
any
way,
and
you
know
so,
there's
obviously
there's
some
balance.
You
know
in
terms
of
how
we
you
know,
how
do
we
iterate
on
this?
If
it
is,
you
know
if
these
features
that
we're
building
are
really
in
a
business,
critical
workflow?
That
is
high
stakes.
Ultimately,
you
know
how
do
we
you
know?
E
How
do
we
make
progress
there
and
not
kind
of
get
stuck
in
this
pattern
of
you
know
it's
never
quite
there,
it's
never
quite
there,
and
so
you
know
that's
what
we're
looking
at
here.
I
think
that
I
mean
it
seems
like
from
this
conversation.
We
all
feel
pretty
comfortable
with
saying
well
the
public
version
of
this.
You
know
the
gitlab
calm
version
of
this
that
we
would
direct
customers
or
you
know
the
public
towards
you
know
this.
There's
the
weird
things
about
the
time,
locking
and
you
know
blah
blah
blah.
E
D
But
you're
talking
about
a
completely
different
time
frame
like
I,
am
Gris
with
you
like.
We
want
to
remove
it
at
some
point,
but
I
can't
like
based
on
what
I'm
seeing
right
now.
How
do
we
do
that
in
in
one
quarter,
but
seriously?
That's
not
gonna
work
like
regardless
of
whether
it's
a
mission-critical,
dashboard
or
not.
It
gives
us
insight
in
the
behavior
of
our
system.
D
So
if
you
wanna
tell
us
that
we
need
to
remove
something
like
that
in
two
months,
I'm
extremely
skeptical,
I'm,
fine
with
doing
that
for
a
contractual
SLA
where
you're
gonna
have
decisions
that
are
completely
different
to
the
one
that
is
monitoring
one
right
like
I
said
and
R
is
doing
the
split
between
contractual
and
monitoring
one.
If
the
contractual
one
is
the
one
that
you
want
to
replace
I'm
perfectly
fine
with
that,
because
I.
E
Think
that's
what
we
want
it.
We
want
to
keep
iterating
on
it's
gonna.
What
is
the
right
break
there
cuz
to
do
it
all
right
as
you're
saying
like
that
say
that
may
be
a
long
term
thing
there
may
be.
You
know
far
into
the
future,
just
things
that
it
doesn't
make
sense
to
replace.
But
you
know
how
do
we
break
out
those
use
cases
and
continue
to
say?
E
Oh
for
these
types
of
things,
you
know
it
is
it's
serving
that
purpose
and
as
a
result,
you
know
we're
we're
driving
the
functionality
forward,
because
we
have
you
know
more
focused
feedback
on
that.
I
had
one
question.
I
know
we're
up
on
time
here,
but
all
of
the
dashboards
that
you
went
through
there
and
kind
of
that.
You
know
you
know
an
analysis
workflow
you
demoed
or
those
those
are
all
driven
off-
that
jsj,
a
sonnet
in
run
books.
E
C
E
Great
because
I
think
that
that's
a
really
powerful
tool
here
too,
is
that
the
fact
that
you
have
all
of
this
in
infrastructure
as
code
and
this
nice
pipeline
for
how
you
manage
and
and
deploy
those
and
then
we've
been
able
to
you,
know
kind
of
fork
that
pipeline
and
produce
a
bunch
of
dashboards
that
you
know
maybe
aren't
at
the
same
level
of
usability.
But
you
know
they're
they're,
you
know,
then
it
starts
to.
Let
us
be
a
lot
more
flexible
in
terms
of
you
know,
I
think.
E
Ultimately,
we
want
to
say:
Oh
turn
the
other
stuff
off
cuz.
That
really
proves
that
you
know
we've
done
it,
but
you
know
to
say
we
can
see
those
things
progress
in
parallel
and
you
know
start
to
shift
more
use
cases
towards
the
course
to
get
loud
versions
as
they
get
more
mature
and
not
have
to,
like
you
know,
argue
over
like
a
hard
cut
over
date.
You
know
that,
like
on
this
date,
we're
going
to
you
know
we
have
to
switch
everything
like
we
can
do
it
more
or
gradually.
A
D
Continue
building
the
same
thing
you're
building
for
this
one,
because
this
dashboard
is
gonna
just
have
to
it's
gonna,
be
different.
It's
going
to
be
showing
different
numbers
right
and
there
is
not
much
difference
for
you.
There
is
just
please
don't
state
that
you're
going
to
remove
the
all
of
the
graph
on
is
LA
dashboards.
That's
what
I'm
trying
to
say,
and
you.
C
The
next
step
for
us
is
is
we're
going
to
kind
of
do
a
bit
of
work
on
outside,
and
we
all
need
to
update
some
of
the
queries
that
you
use
as
a,
but
they
trivial
little
changes
and
then
just
my
own.
Then
we
just
need
to
sorry
so
everyone's
going.
We
just
need
to
kind
of
do
a
bit
of
Polish
and
figure
out
what
the
what
the
defaults
for
a
user
would
be.
That
are
different
from
the
defaults
that
we
are
for
seven
days.