►
From YouTube: Monitor:APM Weekly Meeting - 2020-03-04
Description
Weekly meeting for the Monitor:APM team
A
A
A
Alright,
hey
everyone
know
if
you
start
yet,
but
we
can
get
going
so
I
just
have
a
first
one
was
just
kind
of
an
announcement.
Clemente
talked
about
this
a
little
bit
last
week,
but
we
started
a
new
milestone
board,
so
it
kind
of
breaks
down
our
our
work
for
a
given
milestone
in
two
different
columns
like
deliverable
filler
issues,
things
that
are
in
verification
or
design,
technical
or
inequality.
So
all
those
are
can
different
columns
so
that
hopefully
it'll
be
easier.
A
B
Maybe
there
are
any
volunteers
here
or
maybe
there
is
someone
that
you
think
would
be
a
good
fit
just
to
walk
us
through
the
process
of
instrumenting
it.
Let
me
add
metrics,
so
we
can
document
every
single
step
and
then
see
how
we
can
improve
that
process.
So
yeah,
just
let
me
know
if
you
could
do
that
or
you
know
someone
who
could
do
that
is.
B
Think
we're
talking
about
instrumental
application,
but
I
would
need
to
check
in
with
dothe
to
see
if
either
would
be
more
beneficial
because
our
I
guess
our
main
goal
is
to
understand
what
would
the
process
be
from
the
users
perspective
right,
but
I
think
knowing
what's
the
process
to
instrumental
get
so
application
probably
would
also
be
helpful
because
our
goals
are
to
dock
food,
the
product,
so
yeah
I'll
check
with
Dovan.
That
and
I
will
let
you
know.
C
A
A
I
think
it's
pretty
basic
I
know
they
said
a
monitoring
expert
but
really
I
think
it
was
basically
just
setting
up
and
explaining
some
of
the
kind
of
the
gitlab
RB
file,
config
files
and
just
some
of
the
basics
of
kind
of
getting
some
of
the
metrics
set
up
so
Rubin
I
saw
you
mention
you
could
maybe
help
with
this,
which
would
be
awesome.
So,
let's
start
with
that,
and
then
we
can
see
kind
of
get
some
more
details
of
of
what
they're
looking
for
and
we
could
pull
in
more
people.
A
B
So
when
I
was
going
through,
the
flow
I
documented,
all
the
user
flows
and
pain
points
that
a
user
might
be
having
in
the
process
and
then
there's
no
good
documentation
to
support
them
during
those
points
of
frustration.
So
we
want
to
fix
that,
and
currently
I
am
documenting
the
information
architecture
for
deep
lab
monitoring
dogs.
You
can
go
to
this
issue
that
I
linked.
You
can
also
check
out
the
mural
where
I'm
documenting
the
structure
and
I'm
trying
to
identify
what
pages
contain.
What
information?
What
is
the
navigation
structure
doesn't
make
sense?
B
It
doesn't
quite
often
so
we
want
to
understand
exactly
why
it's
confusing
how
its
kind
of
fusing
and
we
redesign
it
to
have
amazing
documentation
because
I
think
it's
a
big
part
of
our
product.
So
if
you
have
check
out
the
mural,
you
can
comment
straight
on
mural.
If
you
think
something
is
missing,
maybe
I
missed
some
pages
or
if
you
have
any
suggestions,
just
call
them
on
straight
on
mural
or
you
can
also
go
to
the
issue
and
comment
there.
So
we
can
all
calibrate
there
and
make
our
dogs
awesome.
A
D
Me
and
Josh
was
recently
working
on
the
annotation
spike
issue
and
we
discovered
quite
important
technical
depth
in
our
architecture,
which
is
the
lack
of
the
way
to
undefined
identify
panels
within
the
dashboards,
and
it's
blocking
not
only
the
or
virtual
blocking,
the
not
only
the
annotations,
but
also
the
others
and
the
reordering
the
dashboard
panel.
So
this
like
number
of
features
which
are
blocked
by
this
and
since
this
decision,
how
to
identify
the
panels
and
how
to
process
especially
custom
dashboard
yamo
definitions
in
order
to
apply
the
IDS.