►
From YouTube: Monitor:APM Weekly Meeting - 2019-01-29
Description
Weekly meeting for the Monitor:APM team. Discussed 12.9 planning
A
A
So
the
first
one
is
around
planning
for
12:9.
So
here's
a
he
identified
15
issues,
but
we're
missing
some
of
the
dogfooding
issues
that
we
want
to
do
for
APM,
so
we'll
go
through
those
in
a
second
and
see
just
kind
of
review
what
he
is
identified
so
far.
If
anyone
has
comments
or
thoughts,
we
can
add
them
to
the
issues.
There's.
A
A
So
I
was
just
going
to
go
through.
We
can
kind
of
go
through
all
of
them
at
a
high
level
and
if
there's
questions,
we'll
kind
of
add
them
to
the
add
them
to
the
issue
and
we
can
take
Dover,
but
what
was
responsible
all
right,
so
the
first
one
was
open.
A
few
of
them
here
is
at
infinite
scrolling
to
log
Explorer.
A
A
A
This
one
is
still
labeled
as
Planning
breakdown,
but
I
think
we
need
to
kind
of
figure
out
what
exactly
is
needed
and
then
come
up
with
some
implementation
tasks
for
this
I'm.
Just
gonna
keep
rattling
these
off
unless
people
have
questions
or
comments
feel
free
to
jump
in
at
any
time
and
interrupt
me
I
think
it
looks
like
I
missed
this
one
prove
the
experience,
we're
navigating
from
metrics
chart
to
the
log
Explorer.
A
So
if
you
want,
if
you're
looking
at
a
chart,
this
is
grifone,
but
if
you
were
looking
at
a
chart
being
able
to
kind
of
drill
into
the
from
that
chart
from
a
specific
time
into
the
logs
that
correspond
to
what's
happening
so
I
think
we'll
need
a
little
more
design
work
on
this
on
how
we
want
it
to
look
so,
but
that's
that
one
all
right
so
then
try
to
get
some
more
of
these
going.
A
A
A
B
B
A
A
A
B
It
did-
and
this
is
regarding
the
infrastructure
dashboard
so
currently
in
the
deployed
board
component.
All
we
show
is
just
the
status
of
the
part.
Additionally,
we
want
to
show
new
visualizations,
like
CPU,
metrics
and
quad
usage
other
things.
So
this
is
the
front
end
piece
of
it.
There
is
also
a
back
end
piece
that
should
go
in
before
this
one,
so
I'm
having
conversations
with
DOE
about
this
all
wind
bottom.
So
we
still
have
to
decide
if
this
one
should
go.
First
of
all
the
most
perfect
okay.
A
A
Next
one
is
around
moving
the
three
pillars
of
observability
into
core,
so
yeah
this
will
be
s
1
is
it
marked,
is
ready
for
demo
I'm,
not
sure
if
there's
other
stuff
that
we
need
to
do
but,
like
clamed
said
we
might
need
to
break
this
down
a
little
more
into
either
create
an
epic.
So
we
can
track
all
the
work.
What
the
goal
is
to
have
custom
metrics
being
in
core,
so
I
think
the
health
team
has
already
started
moving
some
of
their
features
into
core,
so
we
will
be
doing
the
same
thing.
B
A
A
A
The
next
one
there's
an
this
is
a
bug
that
we've
seen
around
when
you
try
to
duplicate
a
dashboard,
to
get
an
error
message
and
it
has
to
do
with
developer
or
what
level
of
access
you
have
so.
A
A
Yep
does
any
of
questions
or
thoughts
about
any
of
those,
so
I
think
the
goal
is
to
kind
of
make
sure
we
have
a
better
idea
using
the
planning
issue
and
this
board
by
the
end
of
the
week.
We
want
to
have
I
have
a
kind
of
a
good
sense
of
what
we
want
to
do
for
12.9.
I
know
it
feels
like
we
just
kind
of
started
12.8,
but
the
product
in
the
planning
cycle
for
the
milestone
is
a
couple
weeks
off
set
from
the
engineering.
A
A
We've
seen
this
with
past,
where,
when
I've
done
it
to
where
we
create
an
issue
and
just
put
it
in
the
current
milestone
or
the
next
milestone
or
something
but
for
planning
purposes
would
be
easier
if
we
just
left
it
empty
and
then
leave
a
comment
for
dough
for
where
you
think
the
priority
should
be
that's
just
kind
of
a
public
service
announcement
there
and
then
the
last
question
was
from
dome
about
removing
the
future
flag.
So
that
happened
today,
right
yeah.
A
It's
on
there
yeah,
that's
great!
So
that's
that's
super
exciting.
So,
thanks
to
everyone,
who's
been
working
on
that
it's
it's
pretty
exciting
that
we
got
that
out
and
cut
it
out
so
fast.
So
that's
good!
Okay!
So
those
are
the
issues,
though,
or
the
agenda
topics
that
doe
wanted
to
cover.
What
else
do
people
have
on
that?
They
would
like
to
cover.