►
From YouTube: Monitor:APM Weekly Meeting 2020-05-13
Description
Weekly meeting for the Monitor:APM team
A
B
Know
so,
I
add
a
to
agenda
item.
One
of
them
is
on
the
no
stop
metric
I
know
if
you're
familiar
I've
linked
to
the
section
on
the
handbook
that
explained
what
is
the
nose-down
metric,
but
in
a
nutshell,
this
is
a
product
indicator
and
every
team
needs
to
have
an
austere
metric,
which
is
a
single
metric
and
indicates
of
the
work
that
we
are
doing.
If
we
are
successful
on
the
feature
that
we
are
listening
and
the
objective
objective
is
to
make
sure
we
will
encase
star
metrics
will
give
them
taste.
B
Every
time.
I
do
a
dashboard,
it
counts
as
a
single
view,
and
we
want
to
make
sure
our
users
will
go
back
to
those
dashboards.
So
this
is
why
we
have
this
as
our
first
metric
psychrometric
is
the
log
view
the
amount
of
time
that
a
user
is
accessing
the
log
Explorer
and
doing
any
action
that
it
does
every
time
the
page
refresh
this
is
count
is
view,
and
since
the
Northstar
metric
is
single
view,
is
a
single
metric
we've
combined
those
together
into
a
single
one,
and
this
more
or
less
explained.
B
What
is
the
direction
of
of
this
group
today?
So
I
know
that
we
are
heavily
focusing
on
metrics,
but
we
were
focusing
on
logging
a
couple
of
months
ago
and
I
expect
us
to
go
between
logs
and
metrics
like
try
to
make
sure
we
are
putting
enough
investment
on
both
areas
and
both
solution
to
make
sure
we
will
drive
this
no-star
metric.
B
It
makes
sense,
hopefully
and
I-
also
have
the
next
agenda
item
and
so
I
know
Matt
that
you
send
the
message
to
the
slack
channel,
but
I
wanted
to
raise
these
issues.
Well,
it
was
an
interesting
conversation
on
the
infrastructure
group
called
weed
seed
on
dogfooding
matrix.
Hopefully
you
all
the
chance
to
watch
it
and
my
tech
forum
from
this
conversation,
first
of
all,
I
I,
think
I
believe
I
actually
know
that
this
team
has
done
tremendous
work
on
dog,
fooding
metrics.
B
We
put
a
lot
of
time
and
effort
on
making
sure
our
info
team
will
be
able
to
use
our
dashboards
and
I
really
believe
that
after
13.1
maybe
13
to
2
what
you
depend
on
the
amount
of
deliverable
items
will
be
able
to
do.
This
I
think
that
the
info
team
really
start
using
and
not
just
looking.
Today
they
are
just
looking
and
they
are
doing
it.
B
You
know
when,
when
we
tell
them
ok,
can
you
look
and
tell
us
if
it
makes
sense,
but
I
only
think
that
the
work
that
the
team
is
doing
after
the
next
iteration
or
maybe
the
one
afterward
will
start
seeing
the
info
team
really
use
the
metric
dashboard
and
from
that
we
will
get
feedback
of
that.
So
I
just
want
to
give
you
my
my
take
on
this
and
yeah
and
I.
If
you
didn't
have
a
chance
to
watch
it,
I
recommend
you
see
it.
A
A
Yeah
I
think
our
team
is
doing
a
good
job
of
that
first
part
of
providing
it,
but
now
we
have
to
get
the
get
people
to
to
actually
use
it
and
try
it
out,
and
it
was
interesting
how
much
time
feel
like
about
half
that
call
was
spent
on
talking
about
dog,
fooding
metrics
so
interesting
to
see
how
important
that
seemed
to
be
to
I
said
so.
That's
good,
yeah.
B
And
we
are
taking
down
some
stats,
I
mean
we
have
a
biweekly
meeting
with
info
team
and
we'd
encourage
all
of
you
to
join.
If
you
feel
like
it's,
the
second
Wednesday
and
I
think
that
we
are
going
to
add
additional
people
from
them
for
team,
more
stakeholders,
so
we'll
get
some.
Maybe
we'll
get
some
commitment
from
them
on.
You
know
how
how
and
when
they
should
start
using
our
our
features.
A
Okay,
I
had
one
item,
it
just
kind
of
a
reminder:
I'll
do
that
and
then
I
can
read
the
other
ones
here.
But
let's
reminder
that
we're
almost
through
with
13,
oh
the
milestone
and
I
think
there's
I
think
we
usually
say
about
the
18th.
So
we
have
about
five
days
left
four
or
five
days
left
to
kind
of
wrap
everything
up.
A
A
C
Hey
sorry,
yes,
I
just
want
to
announce
that
we
are
removing.
We
were
previously
removing
a
deliverable
label
and
filler
labels.
They
were
in
verification,
but
from
a
p.m.
and
health
team,
I
was
getting
feedback
that
it
was
confusing
so
for
now
moving
on
forward.
We
won't
be
removing
those
labels
whenever
something
is
moved
to
verification.
So
hopefully
this
makes
clears
things
up
and
makes
things
less
confusing.
So
let
me
know
if
you've
got
any
questions
about
that.
A
Okay,
I
can
just
read
through
like
what's
Sophie
I
put
in
here.
So
there's.
The
quad
planning
process,
which
is
the
QWOP
Sophia
from
the
quality
side,
is
something
to
refine
that
improve
collaboration.
So
there's
new
new
labels
to
help
kind
of
raise
awareness
of
where
we
are
in
that
process.
So
so
there's
the
quad
planning,
ready
label
and
then
it'll
basically
be
a
way
besides
just
kind
of
manually,
doing
it
to
raise
awareness
of
that.
B
I
see
that
you
mentioned
that
a
product
manager
should
apply
to
the
quad
planning,
maybe
I'll
reach
out
to
her.
If
you
don't,
you
don't
have
the
details,
but
on
which
issues
should
we
do
it
or
should
we
do
it
on
all
issues
she
should
we
do,
should
I.
Do
it
for
issues
importance,
I
mean,
what's
the
suggestion
around
it
or
just
do
it
apply
cost
above
all
the
issues
that
we
are
planning
for
13.1
or
the
coming
iteration
yeah
I.
A
A
B
C
Think
I
don't
want
to
put
your
spot,
but
I
think
it'd
be
really
cool
to
learn
more
about
some
of
the
user
interviews,
or
maybe
some
of
the
murals
going
through
that
during
this
extra
time
would
be
helpful
to
help
us
better
understand
kind
of
our
users
and
kind
of
where
we're
going.
But
that's
just
my
thoughts.
B
Think
it's
important
for
all
of
you
fails
to
be
well
of
the
work
that
we
are
doing
so
understand.
The
two
men
were
not
working
and
avoid.
You
know
not
like
inventing
things
and
also
to
know,
as
you
mentioned,
to
know
all
users,
so
definitely
something
that
I
would
like
to
to
bring
into
the
meeting
I
I
wonder
if
what
I
was
thinking
is
I
mean
we
are
doing
all
kinds
of
interviews.
Do
you
think
is?
B
Will
it
be
useful
to
try
to
bring
like
the
research
that
are
more
relevant
to
what
the
team
is
doing
because,
for
instance,
I
have
done
like
the
comparative
analysis
for
logging,
which
I
say
I
think
is
important,
but
it's
not
like
relevant
today.
It
can
be
really
fun
tracking
it
in
a
month
or
two
month
or
something
like
that.
B
D
D
E
So
just
on
this
call,
you
know
it's
the
end
of
the
milestone,
so
we're
kind
of
still
wrapping
things
up,
but
in
the
future
for
sure
we
want
to
be
doing
more
of
that
and
I'm
sure
it
won't
be
helpful
to
everyone
and
also
we're
going
to
be
sharing
stuff
in
slack.
I've
been
sharing
a
little
bit
here
and
there
are
some
updates
on
the
user
experience.
The
research
that
were
running
so
yeah
just
keep
an
eye
out
in
the
APM
channel
I.
A
B
E
E
Maybe
you
can
help
us
catch
any
weird
parts
in
the
experience
you
know
and
just
do
some
like
quick
and
dirty
solution,
validation,
I
think
sometimes
that
can
be
helpful,
maybe
not
for
every
meeting,
but
I
think
there
are
definitely
ways
for
us
to
leverage
this
time
better
and
if
we
were
all
stopping
whatever
we're
doing
getting
on
a
call
gun.
We
might
as
well
use
this
time.
It's
only
once
a
week.