►
From YouTube: Monitor:APM Weekly Team Meeting - 2020-02-05
Description
Weekly meeting for the Monitor:APM team
A
A
A
A
Okay,
I'll
take
that
as
a
No
and
then
I
was
trying
to
check
with
the
team
for
self
monitoring
deliverable
issues
in
this
milestone.
That's
something
that
we
really
want
to
prioritize
and
complete
out
this
release
and
I
wanted
to
see.
If
anyone
was
stuck
on
anything
anything,
we
can
do
to
move
faster
or
prioritize
different
people's
work
so
that
we
can
make
sure
that
that
makes
it
in
is
there
any
buddy
wants
to
highlight
anything.
A
B
D
D
C
C
C
C
We
put
the
chart
in
the
agenda,
but
it's
far
surpassed
what
we
had
previous
months.
December
was
kind
of
an
outlier,
because
a
lot
of
people
were
on
vacation
but
months
before
that,
even
it
was
far
ahead
of
that.
So
I
really
appreciate
all
the
hard
work
people
have
been
putting
in
towards
this
iteration
value
and
yeah
I.
Think
going
forward.
We'll
keep
thinking
about
ways
to
kind
of
keep
this
momentum
going
and
keep
working
towards
it.
C
C
Okay,
so
yeah
the
next
one
wanted
to
talk,
bring
up
about
dog
fooding.
This
is
a
very
high
priority
for
the
organization,
not
just
our
team,
but
across
the
across
the
company
dog
fooding
monitoring
is
a
big
big
push
right
now,
so
there's
just
give
a
little
background.
There's
I,
post
the
first
epic
in
here
is
a
link
that
we're
trying
to
organize
everything.
So
there's
that
one
I
know
Jose
I
think
started
I
think
it
was
Jose,
hey
this
cloning,
the
SLA
dashboard
our
time
dashboard,
whatever
you
want
to
call
it.
C
C
I
know:
we've
identified
a
few
things,
there's
a
in
that
first
epoch.
There's
excuse
me
sub
that
make
about
kind
of
gaps
that
we're
identifying
so
as
we're
finding
things
that
we
can't
kind
of
directly
copy
over
from
graph
Anna
we're
gonna
track
them
as
issues
in
there.
So
it's
I
think
this
is
one
of
the
benefits
of
doing
this
dog
fooding
effort.
To
is
to
identify
any
gaps,
yeah.
B
I
think
just
to
trim
in
a
bit.
This
is
actually
related
to
my
last
comment
in
this
dog
is
second-last,
so
we
identify
the
gaps
which
was
done
by
the
walk
by
by
losing
weight
well
by
the
way
and
I
think
that,
since
this
is
a
high
priority
for
the
team
for
the
organization,
actually
we
have
the
12.9
planning
issue
and
I.
Have
it
I
want
to
sign
off
on
that
and
say?
Ok.
This
is
the
planning
issue
photo.
B
However,
since
we're
identify
several
issues
as
gaps,
we
might
shift
some
of
the
peyote
and
add
some
of
those
to
12.9.
So
what
I've
asked
Clemente
and
Matt
is
well.
You
go
over
those
issues
and
try
to
identify
what
are
the
thing
that
you
think
the
least
effort
that
would
take
us
like
the
minimum
amount
of
time.
B
So
we
can
squeeze
them
in
that
iteration
in
this
iteration
in
12.9
and
schedule
the
big
one
for
for
the
for
the
next
iteration,
because
we
do
have
some
commitment
that
we
want
to
deliver
for
12.9
already
so
I
don't
want
to
like
change
completely
the
priority,
but
I
do
want
at
least
to
get
a
head
start
for
12.9.
So
if
we
can
identify
those
and
we
can
start
working
on
them
and
then
4:13,
we
can
really
like
give
them
the
proper
attention
for
those
there.
For
those
issues.
C
A
That
yeah
yep
yes,
so
everyone
should
have
access
I
added
it
through
a
little
subgroup
on
the
instance,
so
everyone
that
has
already
logged
in
once
should
be
part
of
those
groups.
I
can't
create
well,
maybe
I
could
well
I,
didn't
I
think
there
might
be
a
way
to
invite
emails
actually,
but
I
did
not
add
any
one
that
did
not
have
an
account.
So
let
me
know
everyone
should
have
access,
though
I
think
everyone
here
is
at
least
logged
in
to
ops.
I
feel
I've
done.
A
C
B
I
was
so
full
logging,
a
couple
of
aspect
that
we
can
look
at
when
we
say
dope
footing.
So
today
we
are
trying
to
put
matrix
using
the
infrastructure
team
and
the
fact
that
we
can
do.
That
is
simply
because
we
can
connect
to
an
external
permit
use,
so
they
are
actually
using
fairness,
fairness,
so
those
of
you
are
not
aware,
is
basically
scalable
Palmateer,
so
it
runs
on
top
of
multiple
instance
of
perimeters
and
get
the
metrics
from
there.
B
So
we
actually
connected
Pharaohs
to
the
ops
that
get
lab
dot
dot
net
and
the
fact
that
we
are
able
to
do
this
exercises
because
we
can
connect
to
an
external
Prometheus
or
Venice
with
it's
a
bit
different
I
think
that
if
we
will
ask
the
infrastructure
team
to
dogfood
logging,
they
will
ask
us
to
do
the
same.
They
have
an
elastic,
an
elastic
search
instance
running,
and
they
would
ask
us
okay,
feed
on
the
data
from
an
external
elastic
into
your
own
Explorer.
B
So
this
is
a
valid
use
case,
okay,
but
this
is
not
something
that
we
support
today
and
not
sure
when
who
supported
obviously
further
down.
We
will
want
to
support
something
like
that,
but
not
today,
so
it
means
that
for
dog
fooding,
what
is
left
for
us
is
to
share
our
solution
with
other
stages,
and
there
are
a
lot
of
demands
actually
from
multiple
groups
in
the
organization
on
using
the
log
Explorer
in
the
cone
state.
B
So
so
this
is
definitely
something
that
we
are
aiming
to
take
on
and
I
pushed
I
posted
the
link
of
the
issue.
There
is
a
discussion
with
the
defend
him
about
that,
but
then
it
will
require
some
design
work
first,
so
maybe
you
know
in
probably
four
well.
Thirteen
will
need
to
do
the
design
and
it's
a
big
different
design
than
the
log
Explorer
that
we
have
today
and
we
can
talk
about
it
like
in
a
different
and
different
time
when
we
have
like
a
little
plan.
B
A
Great
thanks
I
want
to
touch
on
something
real,
quick,
so
correct
me
if
I'm
wrong,
but
I
feel,
like
my
understanding,
was
for
q1
we're
still
gonna,
just
mainly
focus
on
dogfooding
metrics,
but
we're
talking
about
like
future
like
as
we
you
know,
move
along
with
our
dogfooding.
That's
kind
of
future
projection
right,
not
necessarily
things
were
actively
trying
to
reach
out
I'm
like.
B
It's
not
it's
not
it's
like
the
purpose
of
what
I
just
discuss
is
actually
not
putting.
The
dogfooding
will
be
like
a
side
effect,
but
yeah
it'sit's
actually
a
feature
that
we
will
have
that
will
be
used
by
other
stages
and
we'll
get
feedback
by
the
customers
that
are
using
it
and
also
the
engineers.
A
B
It's
not
we.
We
can
think
about
the
priority.
You
know
and
the
planning
issue
and
see
if
we'll
have
time
for
that,
but
it's
definitely
not
in
the
same
party
as,
for
instance,
dogfooding
metrics
opposeed
got
a
logging,
therefore,
that
we
have.
Although
this
is
something
that
the
organization
would
like
us
to
collaborate,
cool.
A
Cool
thanks
for
clarifying
I
did
have
a
follow
up.
I
was
wondering
if
we
knew
how
many
like
what
is
our
goal
for
how
many
dashboards
we
aim
to
clone.
You
know
we
have
that
one
issue
for
the
uptime,
SLA,
dashboard
and
I
think
we've
been
doing
really
good
good
on
like
progress
and
identifying
gaps,
but
it's
trying
to
see
if
we've
we've
come
to
any
conclusion
of
how
many
dashboards
we
want
to
do
in
one
corner.
You
know.
B
That's
that's
a
good
question,
because
I
this
is
something
that
I
wanted
to
ask
Sam,
because
he
asked
us
to
look
at
another
dashboard,
and
you
know
after
that,
you
versus
another
one
another
one
another
one.
So
I
want
to
first
make
sure
that
everyone
understand
that
we
are
working
on
a
single
dashboard,
because
we
have
enough
work
on
our
plate
just
by
cloning.
This
one
but
it'll
define
the
gaps
and
yeah
we
need
to.
We
need
to
reach
out
and
ask
okay
how
many,
but
you
want
us
to
to
work
on.
Basically,
what
is?
B
C
C
So
she
one
is
suggesting
adding
scope
of
scope
of
work
for
UX
to
milestone
planning
issue,
so
we
can
estimate
capacity
easier,
but
I
think
that
comment.
You
said
it
too,
but
I
think
that
seems
straight
for
makes
sense.
You
know
she
had
a
she
added
a
comment
in
the
planning
issue.
Already
that's
linked
here.
C
B
I
realize
the
bullet
point
about
the
planning
issue
and
the
next
one
is
the
least
possible
12.8.
As
always,
the
time
had
come
for
me
to
pinging
all
of
you
and
making
all
of
you
complete
or
not
complete.
So
expect
me
to
reach
out
over
issues
and
select
asking
you
any
update
on
several
issues
which
are
related
to
release
post
and
lament.
Regarding
your
question
and
Amy
I
think
Amy
start
shadowing
axle
on
12.9.
B
F
Say
my
name
three
times
and
I
show
up
to
answer
the
question.
It
is
complicated.
That's
the
the
reason
you
weren't
sure
I
am
supposed
to
only
officially
start
shadowing
for
12.9,
but
Axl
is
about
to
take
two
weeks
of
vacation,
starting
as
of
Friday,
so
it
looks
like
I
may
be
starting
a
little
earlier
than
any
of
us
planned
on.
So
what
we
plan
to
do
for
12.8
I
will
step
in
on
as
much
as
I
am
able
and
anything
that
I
am
NOT
able
to
handle.
F
F
I
have
been
a
good
lad
for
about
a
month
and
a
half
I
am
still
busily
making
all
the
mistakes
one
must
make
when,
when
you're,
new
and
I
will
be
taking
over
the
monitor
and
defense
stages
for
an
axle
around
twelve
nine
twelve
ten
I'll
try
to
take
over
them
as
quickly
as
possible
once
I'm
ramped
up.
But
who
knows
what
I'm
gonna
learn
in
the
next
couple
of
months
feel
free
to
schedule.
F
C
C
So
if
you
will
be
attending
contribute
and
don't
have
other
things
going
on
that
day,
I
started
this
issue
today,
so
we
can
start
collaborating
what
the
plans
are,
what
some
ideas
we
have
for
for
that
day,
so
yeah
well
we're
kind
of
it's
kind
of
in
the
air
of
how
how
we're
gonna
do
that,
but
I
wanted
to
at
least
start
the
planning
process
and
start
discussions
and
start
getting
some
ideas
from
people.
So
yeah
I,
don't
know!
If
you
had
comment.
If
you
wanted
to
mention
that.
A
Yeah
just
want
to
mention
that
you
know,
since
Matt
and
I
are
crossover,
helping
with
the
entire
monitor
stage
with
two
groups,
we're
still
figuring
out
whether
we
want
to
combine
them
for
one
all
day
or
whether
we're
gonna
split
part
of
it
or
something.
If
you
have
suggestions
or
ideas,
feel
free
to
put
it
on
the
issue.
But
that's
that's
where
we're
at.
We
haven't
fully
decided
yet,
but
we'll
probably
decide
something
soon,
yeah
for
sure.
C
Thanks
and
yeah
I
in
that
issue,
I
mentioned
to
like
anyone,
who's
kind
of
the
stable
counterparts
for
monitor
or
welcome
at
these
team
days
as
well.
I,
don't
know
I,
think
product
is
having
some
of
their
own
meanings
and
I.
Don't
know
about
like
a
me
like
the
technical
writing
or
anything
so
as
we
figure
that
out
just
know,
you're,
of
course
welcome
with
us,
but
yeah
well,
we'll
be
doing
more
planning.
They
just
are
the
contribute
planning
team.
C
B
Yeah
I've,
actually
one
question
I'm,
not
sure
if
it
was
I
asked
at
that
on
the
the
issue.
But
I
wasn't
sure.
If
someone
answer
me
because
you
mentioned
me,
the
ISM
issued
schedule
for
12.8
on
moving
I
think
it's
custom
metrics
to
to
call
it
was
broken
down
into
multiple
emails
like
six.
Seven
and
I
was
wondering
if
I
mean
who's
working
on
that
I
was
wondering.
A
From
my
perspective,
the
expectation
for
that
issue
was
just
playing
break
down,
since
that
was
with
the
label.
So
I
just
had
engineers
break
it
down
into
the
issues.
So
no
work
has
done
yet.
My
expectation
wasn't
necessarily
tied
to
team
work
on
it,
but
we
we
could
try
to
see
if
we
can
get
started.
If
that's
what
we
want
to
go.
B
We
just
communicate
to
users
that
we
are
going
to
do
that
and
there
is
an
epic
and
it's
up
for
us
to
decide
and
we
are
not
going
to
do
it
like
single-handedly.
We
are
going
to
once.
We
have
something
one
curve:
let's
move
it,
let's
move
it,
let's
not
wait.
So
it's
not
like
I'm,
not
waiting
for
everything
to
move
to
call
and
then
say:
okay,
let's
move
it
to
call
if
something
isn't
called.