►
A
A
A
Let's
jump
in
okay,
I've
already
created
an
account
here,
so
you're
gonna
see
me
log
in,
but
I'd
create
an
account
when
I
first
found
out
about
them.
Okay
looks
like
it
already
logged
me
in
this
is
my
account
yep
okay.
So
here
I
am,
I
looks
like
they're
describing
something
let
me
make
this
a
little
bit
bigger
for
those
following
home
looks
like
they're
describing
something
called
a
component
comment:
components
are
like
containers
containing
five
resources.
If
you're
trying
to
monitor
your
homepage,
then
you
create
a
container
called
home.
A
Who's
our
group
manager
in
the
ops
section-
okay,
I
can
play
around
with
this
too
looks
like
their
roles
available,
are
owner
administrator
member
viewer.
I've
got
a
team,
it
doesn't
seem
like
there's
any
way
for
me
to
like
group,
my
team
into
individuals,
but
maybe
that
comes
when
I
create
components.
So,
let's
create
a
component.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Okay!
So
here's
my
incident,
I'm
on
the
homepage
component.
I've
got
an
instant
log.
Here's
my
basic
instant
home
page
hits
is
offline.
All
right,
which
is
offline.
This
is
currently
investigating
by
our
team.
That's
the
description!
What's
this
description
of?
Oh,
that's,
the
status,
oh
cool,
okay,
so
maybe
I
can
publish
this
somewhere
and
someone's
great,
because
monitors
have
priorities,
hi,
okay,
so
instant
that
is
offline.
I
can
acknowledge
okay,
so
it's
acknowledged.
A
A
Although
I
wonder
what
would
happen
if
I
wanted
to
hit
return
in
that
in
that
box
itself.
Oh,
I
like
that
internal
notes
and
external
notes,
where's
my
like
I
can
delete
the
incident,
so
I
add
incidence
still
investigating
my
internal
node
is
18.
What's
going
on,
I
guess
at
this
point
I
probably
should
have
had
the
slack
notification
or
a
slack
integration
setups
that
I
imagine
your
most
of
your
collaboration
is
going
to
happen
there.
What
I'm
wondering
is
where
can
I
see
my
my
external
view
of
the
status
page?
A
A
A
A
A
A
A
Add
both
charts
and
save
it.
Okay,
cool
now,
here's
my
size,
page,
perfect,
okay,
and
there
should
be
an
instant
already
going
on
okay.
So
all
services
are
offline,
that's
cool!
Well,
it's
not
cool,
but
it
already
is
showing
me
that
it's
given
me
hits
and
response
time.
I
response
time
went
up
really
high
gives
me
my
current
uptime
tells
me
about
instance.
The
homepage
is
offline.
It
says
currently
investigating
our
team
is
infringement
zone
resources
affected?
That's
great
and
that's
given
me
updates.
The
incident
was
acknowledged.
We're
looking
into
this
thing.
A
A
A
A
A
A
A
A
A
But
the
instance
says
it's
resolved
and
it
automatically
fixed
that,
for
me,
that's
great.
That
was
super
cool
experience.
Okay,
let's
go
back
and
close
these
so
great
connection
to
status,
page
nice,
clean
status,
page
that
you
can
organize
by
components
and
then
showcase
what
incidents
you
could
add.
Like
a
little
description,
I
think
I
remember
on
each
one
of
these
monitors
and
components,
pretty
cool,
pretty
very
straightforward.
I
like
that.
I
like
the
concept
of
adding
components
and
monitors.
A
A
A
A
A
A
A
Oh
members
who
have
resolved
most
incidents,
that's
interesting
and
then
the
monitors
with
the
most
incidents
cool,
those
make
sense
is
very
useful.
Starting
reports
looks
like
they
have
consulting
and
services
let's
go
back
to,
while
this
is
in
a
specific
project,
and
you
can
organize
members
of
that
project
and
then
put
them
on
on
call
schedules
to
find
components
and
monitors
that
automatically
create
and
resolve
incidents
have
a
status
page
to
communicate
that
to
team
members.
I
think
let's
go
back
to
project
settings.
A
A
A
I
can
see
how
it
would
help
teams
quickly
ramp
up
to
creating
this
kind
of
holistic
incident
response
capability,
starting
with
very
essential
monitors,
and
you
could
build
out
more
and
more,
not
didn't
seem,
like
a
lot
of,
I
think,
there's
an
api,
but
I
would
wonder
how
much
a
team
would
struggle
with
the
kind
of
ui
configuration
of
all
of
those
components,
so
that
might
be
difficult.
I
imagine
in
the
api
there's
some
way
to
kind
of
like
bulk
process
and
update
and
manage.
A
Maybe
that's
what
the
get
integration
is
about
is
that
you
could
define
a
lot
of
that
content
in
some
git
repository,
so
you
could
kind
of
programmatically
update
your
monitoring
things.
I
really
liked
was
the
kind
of
just
responsiveness
of
the
ui.
It
quickly
gave
me
an
insight.
It
quickly
popped
up
in
my
browser
that
there
was
an
incident
which
you
know
recognizes
that
that
tool
should
be
your
home
page
and
you
will
like
immediately
get
alerted
to
a
new
incident
being
created.
A
I
liked
the
smarts
of
creating
and
resolving-
and
I
didn't
have
to
do
a
lot
of
configuration
to
say,
like
here's,
the
threshold
for
when
you
should
create
an
incident
or
not.
It
did
that
for
me
by
default,
but
I
still
had
a
kind
of
if
I
wanted
to
advanced
option
capability
to
configure
those
things.
I
really
liked
the
just
kind
of
immediate
ease
of
use
of
the
status
page
that
gave
me
a
status
page
immediately
with
what
I
thought
was
very
reasonable
for
me
to
present
to
my
customers.
A
I
didn't
do
the
instrumentation,
but
the
instrumentation
setup
with
npm
looked
fairly
straightforward.
I
liked
the
api
yeah
we
I
didn't
dive
too
much
in
the
apx.
I
wasn't
using
a
web
app,
but
I
could.
I
could
see
there
being
value
to
kind
of
like
the
synthetic
testing
of
your
api
as
monitors,
which
again
makes
sense.