►
From YouTube: Monitor:APM Weekly Meeting 2019-12-11 (Higher Quality)
Description
Weekly meeting for the Monitor:APM team including a discussion about the 12.7 milestone.
A
B
C
B
B
B
The
second
issue
is
actually
the
ability
to
drill
into
the
log
Explorer
only
specific
time
frame,
so
we
need
to
make
sure
we
are
passing
the
time
frame
parameters
and
by
the
way,
those
two
issues
are
critical
for
our
triaging
flow,
so
triage
to
minimal.
We
discussed
this
several
meetings
ago,
and
so
those
two
issues
are
critical
to
be
in,
for
that
solid
epic
to
be
completed
on
a
complete
list
to
get
start
with
epic
third
issue
Dropbox
for
metrics
and
environment.
B
C
B
B
B
So
a
tool
to
total
infrastructure
dashboard,
so
this
dashboard
that
I
showed
you
previously.
When
we
hover
over
it,
you
want
to
make
sure
that
we
are
seeing
besides
the
name
of
the
pod,
we
want
to
see
the
metric
that
we
choose
for
choosing
CPU
and
we
hover
over.
This
pod
will
see
the
name
and
we
see
the
value
of.
D
Yeah
I've
got
a
question
on
that.
If
you
look
at
the
pipeline,
we
normally
don't
switch
over
to
a
pipeline.
But
if
you
look
at
a
pipeline
in
the
left
right
hand,
column,
it's
usually
got
like
it's,
usually
the
department
of
redundancy
department
where
it's
got
like
two.
You
know
there's
a
name
of
the
thing
and
then
the
name
of
the
things
up
in
the
tooltip
or
whatever
it
would
it
be
int
non-obvious.
B
Think
it
makes
sense,
not
sure
if
we
can
do
it.
If
we
need
to
do
it
in
this,
if
we
can
do
it
in
the
same
iteration
like
in
the
same
memo,
if
we're
already
there
and
it's
easy
to
do,
I
think
it
makes
to
remove
the
production,
because
you're
right
you
already
have
production,
doesn't
make
same
production.
B
D
B
Cool
thanks,
okay,
so
this
one.
Actually
we
still
have
some
discussions
around
it.
I
would
like
the
opinion.
So
the
idea
here
is
when
you
configure
a
custom
metrics,
you
need
to
go
to
a
page
to
add
to
different
page
permit,
use,
manage
I,
think
and
add
custom
ethic
and
you
define
it
and
then
you
go
back
to
the
dashboard
to
see
how
it
looks
and
I
was
thinking
of.
Maybe
we
can
add
a
link
here
to
add
metrics
so
from
here.
You'll
go
directly
to
that
page.
B
D
Probably,
let's
put
it
on
the
we
shall
probably
shouldn't
put
it
on
all
of
them,
but
because
the
adding
ones
are
only
for
custom
metrics,
so
that
would
be
down.
You
know
when
you
listen
to
custom.
Metric
you'd
probably
want
to
have
that
button
on
the
custom
metric,
but
that
would
that
would
call
out
those
things
as
custom
metrics
as
well.
B
Okay,
right,
okay,
I,
wasn't
thinking
about
that,
so
only
on
the
custom,
Ettrick,
dashboard,
yeah,
you're,
I,
think
you're
right.
We
should
comment
here
and
the
second
thing
that
I'm
asking
that
I
ask
I
mean
if
we
work
on
this
in
iteration.
We
make
sense
to
first
like
provide
a
link
to
the
custom
metric
page
and
only
after
the
afterworld
like
complete
the
entire
thing.
So
this
is.
This
will
be
like
the
finest
the
final
stage.
The
final
stage
will
be
when
we
click
on
this.
You
will
see
this
a
pop-up
you
will.
B
C
B
F
Yeah
I
think
I
mean
I,
don't
have
a
problem
with
just
starting
out
with
just
hitting
edit
metric,
and
then
it
takes
us
over
to
that
page.
I'd
left
a
comment
in
the
issue
we
had
was
like
we'd
done,
that
same
approach
for
for
the
add
metric
actually
for
the
add
metric
button
like
when
we
first
implemented
that
it
just
kicked
you
over
to
that
page.
Instead
of
leaving
you
on
the
dashboard,
which
is
not
a
problem,
it's
a
great
first
iteration,
let's
break
it
down,
keep
it
simple.
F
We
know
that
the
definition
have
done
for
this
issue
is
that
it's
all
there
on
the
metrics,
dashboard,
I,
think
I
think
we
should
be
fine
just
as
long
as
we
don't.
You
know,
lose
sight
of
this
and
then
end
up
like
absolute
4,
&
5
milestones
down
the
road
and
it's
still
kind
of
redirecting
users
over
there.
Absolutely.
B
H
B
B
B
B
D
Literally,
there's
a
little
bit
of
inside
baseball
associated
with
this,
because
I
do
know
that
we
look
at
the
metric
information
that
comes
back.
Is
that
right?
Do
we
look
at
the
metric
information
that
comes
back
to
get
the
metric
to
assign
the
alert
to,
or
is
it
maybe
it's
defined
for
the
dashboard
I'll?
Take
that
back
I'm,
not
sure
it
seemed
like
there
was
a
thing
where
we
use
the
data
use.
Some
component
of
the
data
that
came
back
to
get
that
alert.
Id
are
the
Prometheus
metric
alert
metric
I.
Do.
I
D
D
Do
we
really
speed
to
be
banging
on
it
all
the
time
you
know
every
time
we
refresh
this
page
because
there's
a
lot
of
you
know,
we
request
Prometheus
to
give
us
back
data
for
everything
every
time
and
a
lot
of
these
metrics
don't
return
stuff
like
the
the
one
about
ingress
version,
16
versus
regular,
new
ingress
or
whatever.
So
that's
it.
That's
different
from
this.
B
Yeah
I
mean
the
way
the
way
I
say
it
is
that
I
don't
again
I,
don't
mind
just
for
us
to
start
working
on
that
to
say:
okay,
when
the
configuration
or
connectivity
problem,
let's
not
put
the
mode,
add
more
pattern
which
allow
you
to
set
up
an
alert
on
the
chart,
but
I
do
see.
I
can
argue
that
we
need
this
in
spite
of
this.
This
issue,
but
just
agree
I
mean,
but
just
for
keeping
the
issue.
B
B
Another
revision
when,
when
one
will
implement
this,
maybe
we
edit
as
well,
because
in
then
in
a
normal
solution,
monitoring
solution
there
are
less
defined
on
the
fly
you
set
up
the
metric
and
while
you're
setting
up
the
metric
you
can
set
up.
You
don't
wait
for
the
alert
you
don't
care.
If
there
is
a
connectivity
or
configuration
problem,
you
fix
that
afterward.
You
need
to
make
sure
the
alerts
out
there.
The
second
data,
so
you.
D
J
D
The
ability
to
be
able
set
those
alerts
up
because
a
lot
of
times
you
set
up
an
alert
and
then
it's
you,
don't
even
see
it
on
the
page
if
the
dating
coming
in
so
unless
I
think
this
that
satisfies
the
law
of
least
astonishment.
It's
astonishing.
When
you
don't
see
the
ability
to
do
alerts,
because
there
were
some.
H
K
That's
the
case,
I
think
maybe
we're
proposing
in
your
latest
comment
on
the
issue
to
allow
setting
up
an
alert
whenever
there's
no
data
for
whatever
reason,
regardless
of
whether
it's
a
connection,
a
sure
configuration
problem
and
then
I
think
we
should
do
some
solution
notation
around
it.
Some
testing
with
the
users
to
see
if
you
know
our
assumptions
will
be
confirmed,
but
if
that's
the
expectation
to
be
able
to
stop
an
alert
on
the
fly
without
waiting
for
the
data
to
come
in
I.
Think
perhaps
we
should
do
that.
K
B
Only
the
only
problem
that
we
see
is
David
mentioned.
We
are
waiting
for
some
data
because
when
you
define
an
alert
there
is
a
drop-down
and
you
see
the
metric
name.
If
you
have
a
configuration
problem,
Oh
a
connection
problem
at
the
beginning,
you'll
probably
won't
even
get
the
metric
name,
which
means
you
won't
be
able
to
define.
So
some
data
need
to
at
least
some
pieces
of
information.
It
could
come
back
from
parameters
I'm,
not
sure
what,
but
what
I'm
saying
is.
If
we
have
this
information
we
cannot.
B
K
B
L
It's
a
technical
definition
is
pretty
much
because
of
an
issue
that
was
addressed
in
this
milestone,
which
is
pretty
much
changing
the
requirement
of
a
view
component
property
from
true
to
false
and
a
based
on
tests.
I
just
created
this
technical
debt
issue
as
to
iterate
upon
that.
It
should
be
very
easy.
B
A
C
B
C
B
Essentially,
I
mean
once
will
get
implement
once
the
clone
of
a
dash
boat
will
get
implemented.
Apparently
it
will
just
take
the
common
metrics,
the
yml
file
we
go
out,
and
this
is
not
really
duplicate
pairs,
but
this
is
not
really
doing
what
it
needs
to
do.
It's
not
is
not
a
well-defined
action.
When
we
say
we
clone
a
dashboard
I
think
it
means
that
you
need
to
clone
all
the
metrics
in
this
mode
on
the
chart.
So
today
was
the
front-end
will
be
implemented.
J
It
would
be
a
back-end
issue
so
right
now
the
implementation
is
that,
basically,
the
section
looks
for
the
template,
yml
file
and
without
change,
checking
for
the
database.
There's
the
customers
are
defined,
so
the
next
step
is
to
take
the
section
and
check
to
the
database
if
there
are
custom,
metrics
and
somehow
inject
those
custom
metrics
into
the
weimar
file,
which
is
being
created
as
a
result
of
this
action
cool.
Thank
you
for
that.
B
Okay,
this
is
because
this
is
the
issue
like
the
large
issue
that
Google
is
working
on.
What
should
we
present
when
we
have
no
data,
timeout
connection,
failure
or
configuration
required,
I?
Think
put
a
comment
here.
If
we
should
have
like
four
issues.
Only
one
issue
with
for
a
mouse
I
don't
have
it's
up,
for
we
will
get
a
sign
yeah.
F
I
think
the
plan
currently
is
to
start
with
the
general
node
data
state.
Now
we
at
least
have
something,
and
then
we
can
iterate
and
add
those
other
pieces
in
so
yeah,
so
we're
gonna
iterate
on
it
and
start
with
just
the
general
node
data
state
and
then
we'll
add
each
of
the
different
states.
Time
out
connection
fail
connection
required
as
we
as
we
go.
That
doesn't
necessarily
mean
it'll
span,
multiple
milestones,
but
it
will
have
multiple
iterations
and
maybe
it
spends
a
milestone
or
two.
You
know,
I,
don't
know.
D
C
B
G
B
D
B
A
B
Yeah
yeah,
we
definitely
need
to
put
them
on
the
issue
for
sure
and
we
need
to
make
sure
we
are
updating
the
the
like
the
summary.
If
we
have
some
sort
of
a
decision
because
I
found
it
very
hard,
you
know
when
I'm
working
on
an
issue
and
we
come
to
a
consensus,
then
it
can
can
take
me
like
a
week
or
two
weeks
to
go
over.
It.
I
mean
some
of
the
issues
that
I
went
with
you
today,
even
issues
that
I've
come
like
two
weeks
ago
and
I
never
touched
them.
B
So
I
also
sometimes
forget
doing
that.
You
know,
but
let's
try
to
make
sure
that
once
issues
we
reach
a
consensus.
Let's
first
like
put
a
comment
that
you've
updated
the
issue.
So
we
know
that
issue
is
updated
and
an
update
the
issue
and
I'll
do
it
and
if
you
can
do
it
as
well,
each
of
you
can
do
that.
It
will.
J
A
A
B
B
Thanks,
yes,
so
the
next.
The
next
announcement
is
that,
apparently,
all
features
in
monitor
are
moving
to
call.
This
is
the
epoch.
We
got
the
approval
from
Sid
and
yeah.
This
is
the
epoch,
and
you
can
see
that
sit
comment
here.
This
is
well
sick
comment
that
he
put
that,
which
means
that
we
will
move
all
of
them
to
call.
What
does
it
mean?
It
means
that
we
all
need
to
create
an
issue
for
each
one
of
those.
B
Each
one
of
those
areas
probably
make
this:
this
is
an
epic
I'll,
open
issues.
Let's
move
this
without
their
debt
and
we
will
schedule
them.
You
know
in
an
iteration.
We
won't
make
them
all
of
them.
In
the
same
in
the
same
in
a
single
iteration,
we
will
spread
it
across
multiple
iterations,
obviously,
and
if
we
need
to
break
it
even
down
in
it
even
further
we'll
do
that.
B
A
A
D
A
I
just
had
a
question
since
I
haven't
been
through.
This
is
how
like
what
is
the
processor?
What
is
the
coding
changes
that
are
gonna
be
needed?
Do
we
have
like?
Do
we
just
do
and
checks
to
see
what
the
environment
or
what
the
status
is
of
the
customer
whoever's
using
it
and
then
allow
it
or
not?
I,
don't
know
someone
who's
been
here.
Good
answer.
F
Don't
know
it's
been
a
while
since
I've
seen
it
for
monitor
specifically
I,
don't
know
if
that's
happening
on
the
back
end
I
think
most
of
it
happens
on
the
back
end,
although
there
may
be
some
front-end
stuff
as
well.
If
we're
passing
that
through
through
that
way,
but
but
the
actual
tools
that
we
have
for
doing
that
are
in
Ruby,
so
it'll
definitely
involve
at
least
back
end,
if
not
back
into
the
front
end
to
make
it
happen.
But
yeah.
A
I
Good,
oh
yeah.
Sorry
I
had
one
question
because
so
now
that
all
these
features
are
gonna
go
to
Corso,
which
means
we're
gonna,
have
more
user
interaction,
more
user
volume.
I
guess
so
should
be.
We
visit
all
the
telemetry
stuff
so
that
we're
capturing
the
right
metrics
and
we
have
enough
data
because
there's
a
great
opportunity.
We're
gonna
have
increased
using
volume,
user
activity
volume
so
just
go
through
all
the
actions.
I'll
be
really
tracking
everything
from
instrumentation
perspective
and
get
those
things
straight
before
we
release
it
to
the
wild.
I.
B
Sometimes
it
helps
sometimes
forgetting,
but
ideally
every
new
feature
that
we
implement
should
have
a
follow-up
ml
of
an
issue
on
capturing
the
relevant
metric
around.
That
I
think
this
is
an
important
piece
of
information
we
need
to
know
in
order
to
make
up
our
product
more
better.
So
absolutely
agree
that.
F
Yeah,
that's
a
really
exciting
change,
I
think,
even
just
with
more
people
invested
in
it,
we
might
even
see
like
an
uptick
in
community
contributions,
or
you
know
that
would
be
an
ideal
situation
as
well
as
if
people
are
invested
in
it
and
care
about
it.
We
may
be
able
to
leverage
that
as
well,
which
which
would
be
great,
for
you,
know,
velocity
and
getting
there
faster,
but.
B
L
F
G
That's
that's
done.
That's
actually
merged
a
couple
hours
ago:
oh
good
yeah!
So
it's
it
was
pretty
good.
We
finally
found
a
middle
ground
and
yeah
took
a
day
or
two
to
finalize
and
it's
not
good
to
go,
and
so
that
was
blocking
another
amount
of
mine
and
I.
Think
one
of
my
girls-
and
so
this
is
now
unblocked
and
we
can
start
really
working
on
features.
G
G
That's
what
I
mean
it's
in
terms
of
code
and
adding
the
features
I
think
it's
probably
going
to
be
pretty
straightforward.
The
only
thing
I'm
a
bit
worried
about
is
refreshing
automatically,
because
there's
some
architects
architecture
changes
that
we
need
to
do
and
I
think
David
has
been
looking
into
that,
but
in
terms
of
just
adding
the
dropdowns
and
the
filters,
that's
that
that
should
be
pretty
easy.
Now
that
we
have,
then
your
ap
I.