►
From YouTube: Monitor:APM Weekly Meeting - 2020-01-15
Description
Weekly meeting for the Monitor:APM group. We discussed 12.7 and 12.8 planning.
A
Alright,
hello,
everyone:
this
is
the
monitor,
APM
weekly
meeting
for
January
15th
yep,
so
start
in
on
some
of
the
things
on
the
agenda.
The
first
thing
I
wanted
to
can't
just
talk
about
what
the
team
is
in
the
handbook.
We
have
a
section
about
incremental
velocity,
I,
don't
know
if
everyone
has
seen
this
or
has
read
through
it,
but
I
wanted
to
see.
We
could
talk
a
little
bit
about
what
it
is
and
then
see
if
people
have
thoughts
or
how
how
it
works
in
practice,
but
basically
the
idea.
A
So
at
a
team
level
we
want
to
measure
MMR's
per
engineer.
It's
also
called
mr
rate,
but
one
way
to
get
to
that
is
to
deliver
a
lot
of
small
M
R's,
and
this
part
of
the
handbook
lists
out
some
ways
that
we
can
address
that.
So
one
thing
is
to
you
know:
if
you
come
across
some
problem
that
can
be
fixed
in
half
a
day
or
less
just.
Do
it
break
down
feature
issues
into
small
M
R's
that
only
take
maybe
two
days
to
actually
work
on
and
then
there's
some
others.
A
A
A
All
right
here:
how
about
do
we
for
our
feature,
big?
Our
issue
is:
do
we?
How
are
we
doing
on
breaking
this
down
into
small
m
RS
that
can
like
incrementally
be
delivered?
The
handbook
recommends
things
that
can
be
like
the
work
is
done
in
less
than
two
days.
It's
gonna
take
longer
to
get
it
reviewed,
but
how
close
are
we
to
that?
Do
you
think
I.
B
Think
we're
definitely
putting
in
more
efforts
to
break
the
issues
down
into
smaller
issues.
I
can
start
with
myself,
I
think
leave
your
milestone
or
the
one
before
that
they
show
was
in
a
good
shape.
It
was
pretty
small
and
achievable,
and
I
was
able
to
make
it
down
into
two
or
three
a
Mars.
So
there
have
been
instances
where
I
think
as
a
team,
we
did
well
breaking
down
issues.
There
are
still
some
issues
that
come
into
the
milestone:
they're,
not
completely
ready
to
break
down.
A
Yeah
I
think
yes,
I,
agree
with
that
that
we're
making
progress
I
think
this
has
been
something
we've
been
trying
to
work
on
for
the
last
couple
milestones,
but
that
wasn't
sure
how
people
thought
about
how
close
we
were.
So
that's
why
I
was
kind
of
wanted
to
bring
this
up.
We
can
also
kind
of
discuss
this
async
as
well
of
people
that's
easier
to
I
kind
of
sprung
this
on
us
without
get
me
everyone,
a
heads
up
so
uh-huh-huh
we
can.
A
A
A
A
E
D
All
the
back
in
api's
have
been
merged,
the
Efrain
portion
has
been
merged
as
well.
Rubin
just
told
me
that
there
is
like
it's
really
tiny
issue
when
we
send
a
boolean
value,
but
since
this
is
behind
a
feature
flag,
there's
no
no,
no
issues
whatsoever.
We
haven't
inactivated
the
feature
flag.
We
could
just
wait
for
that
patch
to
the
life
I
mean
in
the
case
of
the
front
end.
He
told
me
I
mean
just
with
the
notes
here.
D
All
right
so
basically
I
just
need
to
change
a
couple.
Api
endpoints,
just
to
reflect
the
current
sign
again
should
not
be
hard.
It's
just
like
a
pull
strings
and
we
should
be
good
to
go
other
than
that
after
we
meshed
us
too.
We
can
just
activate
the
feature
flag
from
staging
and
start
vacation.
Okay,.
A
Great
yeah
this
one
yeah
in
production
will
be
interesting
if
we
want
to
want
to
discuss
if
we
want
to
enable
it
only
because
we'll
be
able
to
create
the
create
the
self-monitoring,
but
there
won't
be
much
content
or
March
value
to
customers.
Yet
so
we
can
figure
that
out
when
we're
gonna
get
to
that
point.
Okay,
thanks!
A
F
I
think
most
of
you
might
have
seen
it
already
working
the
only
reason
that
I,
for
which
I
didn't
fully
disclose,
because
there
is
one
small
issue
still
open
regarding
empty
data
in
one
of
the
charts,
but
I
think
this
has
been
reported
separately.
So
I
think
we
should
handle
it
there
and
then
just
close
this
issue.
Ok,.
G
B
C
A
C
A
Good
so
then,
in
the
next
column
for
in
review,
so
these
are
ones
I
assume,
there's
four
generally
there's
an
EM
are
open
but
not
merged.
Yet
that's
not
right.
Everyone
feel
free,
let
me
know,
but
let's
just
walk
through
some
of
those,
the
first
one
or
all
of
those.
First
one
is
ad
time
filtering
to
the
logged
view.
A
F
D
E
F
H
C
A
B
A
E
A
F
A
A
Sounds
good
and
then
so
we
have
a
few
that
are
in
dev
now
so
there's
this
big
log.
So
this
is
this
first
one
is
like
a
meta
issue
just
to
track
all
of
these
other
MRA's
and
issues.
There's
a
whole
list
of
em
RS
here
so
so
you
can
see.
Most
of
them
are
merged,
I
think
check
with
agent
tomorrow.
I
think
most
of
them
are
I
think
this
is
ready
to
at
least
the
main
part
of
this
feature
is
ready
to
be
deployed.
A
D
On
that
one
I
noticed
a
couple
of
performance
issues
and
issues.
I
left
a
comment
there
to
update
on
the
situation
and
today,
I
thought
off
and
I
wait
to
break
this
up
a
little
bit
further
and
I.
Think
I
might
be
able
to
submit
a
couple
of
requests
to
get
people
review
this
as
soon
as
possible,
because
I
decided
to
change
from
the
Korean
logic
to
use
us.
So
it's
a
little
bit
more
portable
and
so
components
can
be
even
less
coupled
together
if
possible.
D
A
A
E
I
A
A
Alright,
just
a
reminder
and
the
agenda
destoy
didn't
forget
to
add
any
thoughts
you
had
for
the
12.7
retrospective
at
issues.
Open
I
didn't
do
a
good
job
of
having
the
12.6
one
opened
in
time,
so
that
was
really
delayed.
So
we
didn't
get
much
feedback
on
that.
So
I'm
gonna
make
sure
to
remind
everyone
that
we
do
have
a
retrospective
for
12.7
and
we'd
love
to
hear
feedback
from
everyone.
K
I'll
go
ahead
of
her
below
so
I
wrote,
yeah
yeah,
so
some
teams
have
Auto
async
retro
issue
creation
system.
We
kind
of
we're
gonna
do
that
at
one
point,
I
think
we've
got
the
fall
so
I'm.
Looking
for
volunteers
who
are
interested
to
help
make
this
happen,
so
you
can
volunteer
now
or
what
Matt
and
I
know
at
some
point
so
cool
cause.
They
volunteered
Thanks
cool.
I
Hi
I'm,
just
letting
y'all
know
so.
We've
both
the
product
designers
have
been
kind
of
covering
both
teams
and
Christy
was
the
kina.
It
probably
was
confusing
for
all
of
you
did
not
really
know
who
to
talk
to
and
also
she
thought
it
would
be
better
if,
like
the
PM's
timezone
and
the
product
designers
time
zones
overlapped
as
closely
as
possible
so
that
it's
easier
to
synchronously
collaborate
necessary
so
she's
recommending
they
split
up
and
since
Nadia
and
over
in
more
similar
time
zones,
Nadia
will
be
on
a
p.m.
I
but
kind
of
go
to
designer
for
a
p.m.
going
forward
and
I
will
be
on
health
because
my
time
zone
was
closer
to
saris
and
we're
both
planning
on
finishing
about
anything.
That's
assigned
to
us
currently,
and
we
do
both
have
twelve
eight
items
assigned
to
us.
So
if,
if
we're
on,
if
we're
assigned
to
those
issues,
we'll
still
finish
them
out,
we'll
still
be
able
to
answer
questions.
I
Okay,
I'll
just
be
for
kind
of
new
issues
that
we're
taking
on
is
we're
like
going
into
planning
for
12.9
and
and
yeah
I'm
still
here
to
answer
questions
and
still
yeah
available.
If
I
can
help
with
anything
so
I'm
trying
to
go
through
and
clean
everything
up
and
make
sure
everything
is
done,
but
if
I'm
missing
anything,
please
feel
free
to
ping
me.
K
So
I
was
trying
to
look
through
their
notes
and
I.
Don't
think
it
was
a
noun,
but
so
here
I
am
here
because
since
trails
departure,
I'm
interim
and
inching
the
front
and
a
PM
team,
the
front
team
of
the
APM
team
already
was
aware
of
this,
but
I'm
not
sure
of
the
back
in
TMU,
or
maybe
it
was
somewhere
hidden
in
slide.
K
Think
right
now
it's
sixty
or
seventy
something
for
talk
about
eight,
and
that's
that's
a
lot.
So
we're
gonna
try
to
narrow
it
down.
So
it's
more
clear
what
the
expectations
are
for
the
team
to
deliver
and
ship
on
time,
and
that
way
it
doesn't
feel
like
we're
constantly
missing
a
bunch
of
things.
So
if
you
have
any
thinking
you're
going
to
help
with
anything,
there's
gonna
be
lots
of
opportunities
for
me,
I'm
also
going
to
be
interim,
managing
the
front-end
configure
team,
and
so
I'm
gonna
always
be
looking
for
volunteers
to
help
out.
K
J
So
the
extent
that
we
can
as
a
product
steam,
assist
by
scheduling
less
being
very
crisp
about
what
the
core
priorities
are,
allowing
for
more
slack
throughout
the
course
of
a
milestone.
I
know
having
spoken
to
douve
that
he's
supportive
I
am,
however,
standing
here
as
Dov's
keep
taking
over
for
douve,
while
he's
in
CEO
shadow
and
I
do
need
to
record
by
tomorrow
evening
at
the
12.8
kickoff.
J
J
Let's
continue
to
focus
on
the
items
that
were
priorities
but
not
delivered
in
twelve
seven
in
order
to
also
accomplish
Clements
task
of
not
continuing
to
overload
the
planning
so
Matt
I,
don't
know
if
you
you
and
I
talked
about
this
last
week,
I
don't
know
if
we
have
a
sense
of
the
current
12.
Eight
board
is
in
a
good
state.
Clearly,
if
there's
60
issues
it's
not
and
how
we
can
get
to
what
we
think
is
reasonable.
J
K
J
Is
it
helpful
if
I
take,
because
you
thing
I
just
watched
was
in
twelve
thousand
seven,
it
seems
like
there's
not
a
lot
of
stuff.
That's
you
know.
It's
not
like
we're
gonna
be
pushing
30
new
issues
on
Friday
that
didn't
make
twelve
seven,
so
the
current
state
would
be
a
good
place
for
me
to
just
reprioritize
what's
in
12.8
this
afternoon,
so
that
you
can
then
take
a
review
of
it
tomorrow
morning,
yeah.
K
A
A
J
Take
a
read
review
of
it,
I'm
always
sensitive
when
we
like
part
of
the
rationale
that
Clemente
is
talking
about
about
scheduling.
Less
is
also
this
feeling
that,
like
oh,
we
didn't
accomplish
luck
because
we
push
this
a
lot
of
stuff
out.
I'm
super
satisfied
with
the
stuff
that
has
already
been
shipped
for
12.7
out
of
this
team.
This,
the
additional
stuff
in
log,
explores
seemed
like
largely
nice-to-haves
and
a
bunch
of
the
other
items.
I've
been
creating
the
least
posts
tickets
for
super
excited
about
all
that,
especially
given
it
was
a
holiday
month.