►
From YouTube: Monitor:APM Weekly Meeting 2012-02-12
Description
Weekly meeting for the Monitor:APM team
B
B
C
C
B
B
A
A
Yeah
so
there'll
be
some
back
and
forth
the
infinite
scroll
issue
and
for
the
log
Explorer.
Basically,
you
read
through
the
comments
there
they're,
not
a
lot
of
concern.
That
is
like
one
specific
questions
that
I
would
like
to
get.
Maybe
your
thoughts
on
the
issue,
which
is
what
do
we
mean
by
infinite
scrolling?
A
So
if
I'm
logging
into
the
love,
Explorer
and
I
pick
the
time
range,
past
30
minutes,
for
instance,
should
I
be
able
to
scroll
beyond
that.
First
30
minutes,
let's
say
the
time
browsing
through
the
loads
and
then
I
scroll
up
should
I
hit
like
the
wall
in
in
the
in
the
last
30
minutes
and
in
order
to
see
beyond
that
should
I
change
the
time
the
time
picker.
So
that's
that's
I
think
this
is
like
the
main
concern.
A
There
are
some
other
questions
which
I
answer
based
on
my
experience
and
you're
all
welcome
to
answer
and
so
I
think
we
decided
that
from
the
majority
of
the
question
we
do
have
a
plan
on
how
to
proceed.
We
have
many
items
that
we
want
to
implement
before.
We
will
address
some
of
those
concerns
and
we
can
definitely
start
using
the
research
to
better
understand
and
get
some
answers
to
our
questions
and
I
think
what
we've
decided
and
I
actually
need
to
get
the
consensus
around
that
that
fall
and
MVC
fold
infinite
scrolling
issue.
A
We
want
to
address
the
500
line
limitation,
at
least
for
now.
What
is
the
500
line
limitation?
Basically,
we
cannot
go
beyond
500
line,
so
it
doesn't
matter
if
I'm
choosing
last
30
minutes
last
15
minutes
or
last
8
hours.
If
I
have
more
than
500
lines,
that
will
be
the
limitation,
so
I
think
that
specifically
thought
that
in
showing
the
law
on
the
infinite
scrolling
and
let's
leave
a
side,
if
you
want
to
go
beyond
the
timescale,
let's
at
least
make
sure
that
we
are
not
hitting
this
limitation.
A
If
the
user
chose
the
last
30
minutes,
let's
at
least
give
the
user
the
last
30
minutes.
If
the
user
asked
for
specific
time
gap,
let's
give
them.
Let's
keep
the
user
that
time
get
as
an
MVC
and
then
we
can
do
the
user
research
and
understand
usually
settle
for
the
time
bit
or
maybe
he
want
to
scroll
beyond
the
tangle.
So
that's
that's
basically
the
the
conversation
around
that
and
if
that
makes
sense-
and
we
can
collaborate
on
that
ASIC.
A
A
Next,
one
is
for
me
so
I've
linked
an
issue
which
is
which
is
open
and
I
know
that
Miguel
is
working
on
that,
which
is
to
add
a
link
to
the
embedded
panel
to
go
to
the
log
page.
If
you,
if
you
go
to
the
issue,
you
see
that
panel,
we
can
embed
the
actual
chart
in
an
incident
and
if
we
will
be
able
to
add
a
link
to
the
log
page,
then
we
can
basically
say
that
we've
completed
to
the
edge
to
minimal
workflow
and
which
is
the
workflow
that
we
want
to
go.
Eventually.
A
E
E
A
D
A
A
Thing
I
mean
we
had
an
issue
and
like
one
single
issue
for
have
the
ability
to
do
real
form
from
blog
Explorer
from
incident
to
the
log,
Explorer
and
I.
Think
you've
been
in
the
issue
and
I
asked
Sarah
for
assistant,
because
the
triage
to
to
minimal
is
something
that
we
already
walk
on
that
and
we
wanted
to
finalize
that.
That's
like
a
leftover
could
be
situation
and
and
I
thought
that
it
is
going
to
be
like
pretty
big
big
f
fault,
but
it
appears
that
there
is
a
shot.
A
There
is
a
little
shortcut
here
and
just
by
completing
that
that
issue.
So
what
Miguel
told
me
that
we
basically
get
this
for
free,
because
we've
already
added
the
drill
down
form
the
metric
chart
to
the
log
Explorer.
So
at
least
based
on
what
Miguel
told
me
is
that
it's
not
a
lot
a
lot
of
effort
just
to
complete
that
cycle
and
make
sure
that
users
will
be
able
to
drill
down
form.
The
log
Explorer
form
the
incident
to
do
not
explore
because
we
already
have
the
foundation.
A
A
A
A
So
we
talked
about
it
briefly
about
okay,
that
we
have
about
co-founder
dashboards,
so
we
can.
Can
we
walk,
maybe
because
I
saw
that
the
last
task
of
trying
to
clone
the
governer
dashboard
was
pretty
quick
and
we
were
able
to
discover
multiple
issues.
So
it
would
be
good
if
you
can
expose
additional
gaps
that
we
can
try
to
tackle
for
the
next
iteration.
So
I
can
plan
up
ahead.
I.
D
Think
for
this
one
it's
kind
of
what
I
wrote
down
to
Andrew
earlier
today.
He
seems
to
indicate
it.
I
still
didn't
really
fully
understand
what
he
was
saying,
but
my
understanding
was
you
know
we
use
JSON
net
for
current
graph
on
a
set
up
where
there's
some
tool
that
converts
that
into
how
grifone
a
parse
is
it
and
there
might
be
a
better
approach
to
how
we're
kind
of
writing
our
or
schema
or
making
it
more
scalable.
D
A
D
A
D
D
A
If
you
think
it
makes
sense
yeah
but
III,
ideally,
I
would
like
to
avoid
what
happened
to
us
in
this
iteration
is
that
we
discover
those
issues
and
we
need
to
quickly
adjust
not
that
it's
it's
a
bad
thing.
It's
good
that
we
we
did
that,
but
it
kind
of
like
affect
the
the
planning
that
the
12.9
and
I
want
to
make
sure
that
in
13
we
will
know
out
ahead.
What
are
the
critical
issues
that
we
want
you
to
plan?
This
is
why
I
want
to
do
it
sooner
rather
than
later,.
G
Didn't
we
discuss
about
this
issue
early
in
the
morning
a
synchronously
I
do
remember
that
we
were
discussing
about
the
argument.
Support
for
the
monitoring,
dashboard
and
I
believe
that
we
wanted
to
move
the
epoch
to
another
one,
so
we
can
perhaps
adjusted
to
a
later
milestone
the
perhaps
we
might
want
to
move
it
to
everyone.
G
Yeah
really
responded.
I
was
just
wondering
if
it's
a
good
idea
to
get
ahead
of
time,
so
we
can
actually
ship
this
in
12.8
to
send
the
removal
of
the
features
like
mush
request
to
a
final
maintainer
review.
It's
already
been
approved
by
book
back
in
the
front,
then
it's
just
waiting
on
merge,
but
since
there
it
depends
on
some
issues
more
to
be
more
specific,
this
one
because
the
other
ones
have
been
merged.
I'm
wondering
if
sending
this
to
a
final
maintainer.