►
From YouTube: Monitor:APM Weekly Meeting 2020-02-26
Description
Weekly meeting for the Monitor:APM team
A
B
Yes,
so
when
talking
to
the
SRA
team
and
doing
the
monitoring
dogfooding,
these
are
a
team
prefers
to
use
multi-line
strings
for
Yama
dashboards
and
I
found
out
that
this
might
be
a
bug.
I'm,
not
sure,
when
useful
to
line
strings.
Equally,
ranges
for
queries
do
not
result
properly,
which
results
and
charts
not
rendering
at
all.
B
D
C
C
Yeah
I
just
wanted
to
get
some
feedback
on
an
issue
that
came
out
of
one
of
my
code
reviews.
There
pointed
out
that
our
performance
monitoring,
dashboard
controller
actions
are
only
returning
JSON,
and
so
they
could
be
moved
to
the
API.
So
if
anybody
has
any
context
for
why
we
wouldn't
want
to
do
that
or
any
opinions
about
that,
please
leave
some
feedback
in
that
issue.
Otherwise,
we'll
move
those
over
to
the
API.
D
Okay,
so
I
think
I've
announced
this
to
my
team
already,
but
to
the
greater
team
and
I
just
want
to
make
sure
everyone's
clear
on
that
I'll
be
out
next
week
and
the
week
after
I'll
be
back
for
a
week,
a
peck
hours
and
then
off
again
and
then
I'll
see
y'all
contribute
after
that,
and
then
that's
gonna
cover
for
front
end
during
that
time.
If
you
don't
need
any
iam
help
which
hopefully
y'all
don't
need
any
help,
but
just
in
case
and
I
think
Matt's
also
gonna
be
out
when
I'm
back
at
that
week.
A
D
Yep
looks
like
Kevin
endeavour
also
out
next
week,
but
yeah,
and
then
I
wanted
to
share
this
board.
That
I
was
doing
work
in
progress.
I
just
want
to
share
with
the
team
I'm
still
still
talking
with
Dov
and
Matt
about
this,
but
wanted
to
share
the
greater
team
just
to
see
initial
thoughts.
So
if
y'all
looking
at
the
planning
board,
let
me
try
to
share
my
screen
to
help
make
this
more.
D
Cool,
so
y'all
should
hopefully
be
able
to
see
my
screen
now
currently.
Does
the
Planning
Board?
It's
not
super
great,
it's
great
at
helping
us
visualize,
12.9
and
12.10,
but
you
know
we
have
50
issues.
We
have
you
know
those
cut
lines
and
this
kind
of
gets
longer
longer
and
with
quad
planning.
Now
that
we
have,
you
know,
Sophia,
helping
right
right,
some
issues
for
tests
to
investigate
during
the
milestone
and
then
also
great
work
from
you
know,
Amy
contributing
to
documentation.
D
This
list
is
starting
to
get
out
of
hand
and
really
hard
to
navigate
and
understand,
and
sometimes
you
know
they
reorder.
Oh
sorry,
I
actually
should
have
hidden
two
security
issues.
Sorry
Matt,
oh,
but
this
is
kind
of
where
we
were
so
here.
I'm
testing
out
a
new
board
flow
to
make
it
easier
to
visualize
those
sections
that
we
kind
of
in
our
mental
model
already
have
considering.
We
don't
really
move
things
from
12.9
felt
attend
all
the
time.
This
might
be
a
better
workflow
for
us,
so
we
have
deliverable.
D
Unfortunately,
there's
no
columns
for
like
not
deliverable
so
I
have
to
create
a
new
label
called
filler
for
now,
and
then
we
have
verification,
design,
technical
writing
and
quality.
So
this,
hopefully,
should
help
us
better
organize
and
have
a
better
understanding
for
engineering
side.
It's
kind
of
these
three
columns
that
we
are
kind
of
more
focused
on
deliverable.
We
might
actually
set
like
a
limit
of
how
many
max
we
want
to
do
and
then
maybe
set
a
max
for
how
many
of
these
we
want
to
do
as
well.
D
That
way,
you
know
we're
not
having
like
a
hundred
issues
here.
That
makes
it
hard
to
understand
a
priority
in
case
things
move
around
so
I'd
love
to
get
some
feedback
feel
free
to
you
know
timer
now
come
on
Doc
or
send
me
a
message,
I'm,
leaning
towards
that.
We
should
move
towards
this
because
it's
a
little
bit
better
to
understand,
but
I'm.
Also
there
might
be
other
things
that
could
be
better
I'd
love
to
hear
from
you
all
as
well.
D
If
I
share
here
like
on
the
board,
scope
its
scoped,
it
all
done
nine,
so
we
would
have
to
change
those
every
release.
I
could
get
a
little
bit
weird
when
we're
in
between
releases
I
guess
we
could
have
a
third
board.
Maybe
I,
don't
know
those
are
just
some
ideas,
ideally
the
mouse.
Don't
you
show
up
here
something
we
can
give
the
UX
team
for
the
plan
team
some
feedback,
because
that's
what
makes
sense
to
me,
but
maybe
maybe
someday
you.
F
D
Feels
like
a
bug
so
I'm
happy
to
happy
to
also
bring
this
up
with
the
plan
team
to
see.
If
they
can,
you
know,
add
the
milestone
here.
Maybe
that
might
be
easier
for
us,
but
it
is
true
thanks
for
bringing
that
up
Justin,
it
does
make
it
little
bit
harder
to
you
know:
visualize,
hey
we're
almost
done
we're
told
on
nigh
on
doing
you
move
everything
told
us
ten,
because
this
is
that's
what's
beneficial
about
here
is
we're
close
to
the
end
release.
A
D
D
E
D
Could
you
say,
oh
I'm,
just
trying
to
get
feedback
and
see
like
so
even
this
conversation
has
been
very
helpful,
getting
the
understanding
the
trade
offs
by
using
this
board
so
on
trade
offices,
what
Justin
mentioned
as
to
get
close
to
milestone
it
can
be
harder
to
to
move
things
over
because
you're,
don't
you're
thinking
about
everything
in
like
one
full
milestone,
you
don't
think
about
them
next
to
each
other
and
then
the
other
trade
off
is
when
deliverables
or
in
verification
mode.
If
we
take
off
the
deliverable
label,
then
you
lose
inside.
Of
that.
D
G
D
From
my
perspective,
it's
more
so
like
hey,
like
we're
almost
at
the
end
of
the
milestone
and
we've
started
the
next
milestone,
but
we
have
all
these
filler
issues
that
are
just
hanging
in
this
milestone
and
we
just
need
to
be
cognizant
of
moving
them
in
the
past
and
we
don't
have
somebody
to
visualize
it.
They
just
have
these
issues
that
are
in
like
really
old
miles.
Some
that
we
forget
about.
That's,
not
good
issue,
hygiene.
D
You
know
it's
possible
that
you
know
dove
Matt
and
I
end
up
being
the
ones
that
look
at
this
old
planning
board,
so
we're
the
ones
they're
in
charge
of
moving
things
so
that
we
don't
get
lost
in
old
milestones
and
then
the
rest
of
the
team
uses
this
new
model.
So
it's
easier
for
the
rest
of
team
to
be
effective.
That
could
be
one
potential
way
to
kind
of
mitigate
that.
Well,.
E
It's
almost
like
the
two
boards
are
still
relevant
just
for
different
use
cases
right
like
the
yeah.
The
current
board
is
good
for
Road
mapping.
You
know:
where
are
we
gonna
go
for
each
of
these
milestones
and
then
this
is
the
active
board
for
the
release,
so
we
could
see
how
it
fits.
You
know
the
big
mental
model
of
how
much
do
we
all
have
to
work
on
for
this
release,
but
yeah
someone's
gonna
have
to
keep
track
down
the
model.
Further
release
someone's
gonna
feel
like.
C
F
Think
I
think
the
the
current
milestone,
because
the
Kohen
board
is
definitely
relevant
for
both
world
mapping
and
planning.
It's
really
easy
for
me
to
move
from
one
milestone
to
the
other,
go
to
the
backlog
and
you
know
check.
What's
what's
the
complaint
and
assess
based
on
like
previous
milestone
and
so
I
used,
I
use
the
current
milestone
a
lot
for
the
planning,
but
then
again
for
the
very
fine.
What
is
the
code
status
for
the
specific
milestone?
I
think
this
one
is
both
of
them
relevant
and
probably
still
there.
D
Yeah,
the
workflow
board
is
helpful
for
Matt
and
I.
Won't
weird,
like
you
know,
halfway
through
the
milestone
or
towards
the
end
and
we're
like
is
our
deliverables
gonna
make
it
that's
kind
of
where
we
look
at
it,
but
the
workflow
dashboard,
if
you
don't
use
the
deliverable
label
and
you're
looking
everything
then
like
a
lot
of
filler
issues
are
meant
to
not
be
done
so
that
I
can
get
a
little
bit
crowded.
D
E
D
F
F
I
The
first
one
is
about
using
Cabana
to
troubleshoot
issues
with
the
Key
Club,
but
we
could
also
gather
the
insights
how
Cabana
is
used
by
a
seller
team
to
view
fruit
locks,
so
it
could
be
insightful
in
terms
of
logging
and
the
second
one
is
about
the
graph
on
the
dashboards
that
the
SR
Azra
each
team
is
using
to
monitor
how
github
is
performing,
which
is
also
very
insightful.
So
just
wanted
to
point
at
this.
The
resources
out.
F
It's
really
great,
if
you
like,
the
understanding
of
how
our
users
are
all
potential
users
are
using
some
of
the
stores
which
we
sometimes
mimic
and
try
to
copy
some
to
what
they're
doing
it's
I
mean
it's
ticket.
We
are
walking
on
the
wrong
path
here
and
still
building
our
own,
take
on
like
the
gitlab
style,
monitoring
and
no
Explorer,
but
it's
always
good
to
keep
an
eye
on
our
competitors.