►
From YouTube: Settings UX - Monitor / Ops
Description
Amelia and Michael discussion settings with operations
A
A
B
A
A
B
A
A
A
B
B
A
A
And
it's
a
mess
so
yeah,
I
think
one
other
thing
so
yeah.
I
think
the
the
like
the
page
itself,
I
think,
operates
the
same
as
many
of
the
other
settings
pages
do
with
like
expandable
collapsible
sections,
the
I'm
trying
to
think
the
only
other
settings
thing
that
the
other
team
apm,
which
no
longer
exists,
was
trying
to
start
introduce
introducing
and
that
I
think
we
want
to
try
to
work
a
little
bit
more
towards
is
having,
and
this
one
isn't
actually
set
up.
A
But
you
can
see
this
metric
settings
so
having
more
in
context,
settings
options
or
at
least
linking
to
these
settings
pages
from
within
the
actual
pages,
where
you're
accessing
those
features.
So
that's
like
something
that
we're
trying
to
start
doing,
but
we
haven't
done
a
great
job
of
yet
more
contextual
settings
links.
B
Okay,
what
what
was
your
group
thinking
around?
Let's
say
you
went
down
with
this
monitor
approach
of
having
the
settings
button
linking
over
to
a
settings
page.
How
would
you
navigate
between
the
settings
page
and
back
to
this
dashboard
or
whatever
main
screen
like
what
were
you
thinking
of
the
navigation
patterns
between
the
two
two
views.
A
Sure
so
a
lot
of
these
these
items
under
setting
operations,
they're
sort
of
you
set
it
up
once
when
you're
setting
up
the
page
you're
setting
up
the
feature,
and
then
you
don't
ever
go
back
there
again.
So
I
think
we're
trying
to
separate
out
the
experiences
for
features
like
that.
We're
kind
of
configuring
it
getting
the
page
just
to
appear
getting
the
content
to
appear
on
the
page
and
then
settings
that
you
might
need
to
come
back
and
kind
of
tweak
as
you're
interacting
with
the
page.
A
A
Let's
look
under
there
and
metrics
that
maybe
you
want
to
change
the
dashboard
time
zone
or
something
that
might
be
something
that
you
need
to
access
even
after
the
page
is
formatted,
but
now
once
you're
here,
you'd
have
to
go
back
to
the
nav
to
navigate
back
to
metrics.
There's
no,
like
quick
link
back
after
you've
made
that
change
to
get
back
to
the
where
you
were
you'd
have
to
remember
where
you
were
and
navigate
back
on
your
own.
A
Not
really
anymore,
some
one
of
the
things
that
we
were
talking
about
so
most
of
the
up,
the
things
that
impact
the
operations
items
are
here,
the
one
that
isn't
is,
and
there
was
an
issue
that
the
apm
team
had
before
they
were
disbanded,
which
was
to
move
this
prometheus
configuration
over
into
operation
settings.
So
that
is
like
the
one
piece
that
is
kind
of
floating
out
on
its
own
right
now,
and
I
don't
know
if
that
will
ever
get
moved
now
that
the
apm
team
is
no
longer.
A
I
don't
know
at
what
point
that
work
would
ever
get
prioritized
by
the
health
team.
So
there
is
that
piece
that
was
sort
of
planned
as
the
like
final
piece
of
moving
everything
over
that
is
kind
of
hanging
in
the
air.
But
I
think
one
of
the
big
things
that
we've,
that's
always
been
a
gray
area
in
monitor
is
a
lot
of
the
things
that
we
that
are
operation
settings
items
are
actually
integrations
so
like
we
can
utilize
kind
of
the
slack
application
and
the
slack
notification
for
for
incident
management.
A
A
Most
of
the
integrations
live
on
this
list.
So
should
we
put
it
here
with
all
of
these
other
integrations,
which
is
a
logical
place
to
put
it?
But
then
we
also
have
this
operations
page,
where
all
of
the
other
instant
and
alert
items
are
so
now.
We've
kind
of
painted
ourselves
into
the
situation
where
or
into
this
corner,
where
we
don't
have
a
clear
answer
to
questions
like
that,
because
it
could
actually
fit
in
two
places
and
which
one's
the
most
logical.
And
why
should
one
thing
be
in
one
place
rather
than
the
other?
A
B
A
A
Yeah
so
like,
when
we've
utilized
it
it's
right
here
for
like
alerts,
you
can
specify
a
specific
channel
just
for
alerts.
So
even
if
somebody
changed
this
chan
channel
for
something
else,
merge
requests
or
whatever
it
wouldn't
impact,
how
we're
using
it
for
alerts.
So
I
think
in
in
that
slack
context,
because
it
is
so
granular
we
haven't
had
any
conflicts.
I'm
surprised
we
haven't,
had
conflicts
with
prometheus,
but
maybe
that's
just
because
not
a
lot
of
people
are
using
it
for
monitoring.
B
All
right
yeah,
that
makes
sense,
but
I
think
if
we
follow
some
kind
of
pattern,
like
the
slack
where
almost
each
feature
has
its
own,
like
section
within
that
integration
to
say
like
these,
are
the
configurations
specific
to
that
then
you're
not
stepping
on
toes
of
other
features
and
you
don't
get
wires
crossed.
So
that
might
be
something
we
explore
to
formalize
over
time
here:
cool.
A
We
have
issues
to
have
like
a
whole
section
for
operations
and
then
to
be
able
to
turn
off
the
visibility
of
all
of
these
items,
for
people
who
don't
use
them
and
to
turn
off
the
whole
category.
But
we
haven't,
we
haven't
implemented
it
yet,
and
I
don't
know
if
this
pattern
is
going
to
change,
but
we,
like
metrics
dashboard,
has
been
added
on
here,
but
none
of
the
other
operations
pages
have.
So
we
do
have
issues
for
that
work,
but
they
haven't
happened
yet.
B
A
A
So
I
think
we
would
want
to
allow
people
to
decide
which
of
those
features
they
want
to
to
use,
and
it's
very
possible
that
some
that
people
use
some,
but
not
all
of
them,
because
there's
like
a
whole
set
for
observability
people
might
have
other
tools
for
observability
that
which
are
the
metrics
logs
tracing
and
error
tracking.
They
might
not
use
any
of
those,
but
they
might
use
alerts
and
incidents.
So
if
I
think
it's,
I
think
we
will
need
more
than
just
operations,
visibility,
toggleable.
B
Yeah
yeah,
which
is
like
finding
things
that
we
can
probably
implement.
So
it's
it's
going
to
be
like
the
same
kind
of
ui
pattern
here,
we're
not
going
to
change
that
up
right
away,
we're
going
to
probably
revisit
changing
the
ui
in
in
a
later
date,
because
yeah
we
just
want
to
get
some
stuff
out,
iteratively
and
then
focus
on
layout
and
all
that
stuff
later
and
then
formalizing
those
patterns
in
the
future
through
pajamas
and
that's
kind
of
like
the
path
that
we're
heading
down
right
now.
A
B
A
Point
because
it
was,
I
don't
for
a
lot
of
different
reasons.
I
guess
the
product
team
decided
not
to
move
forward
with
that.
So
we
have
this,
which
is
not
great.
It's
like
a
super
super
long
form
and
like
in
terms
of
experience,
I'm
not
like
very
proud
of
this,
but
I
think
that
the
direction
that
we
were
going
to
go
with
this
with
the
card
view,
I
think,
is
something
that
I
I've
also
seen.
B
A
A
Decorations
one
here
there
it
is
yeah,
so
we
were
trying
to
build
something
more
like
this.
So
for
adding
integrations
like
more
of
a
card
view
and
then
like
once,
you
click
to
add
something.
It's
like
super
easy
and
then
you
just
save
it,
and
it's
like
visible
like
what
you're
adding
and
if
it's
been
installed
or
not,
and
it's
pretty
easy
to
see
it
just
makes
it
really
visible.