►
From YouTube: Monitor:APM Weekly Meeting - 2020-06-10
Description
Weekly meeting for the Monitor:APM team
A
All
right,
hello,
everyone
welcome
to
the
monitor
p.m.
weekly
meeting,
so
we'll
start
on
the
agenda.
Normally
I
won't
do
this,
but
we
added
a
can
based
on
Nadia
suggestion.
We
added
a
read-only
section
so
read
that
first
and
we
won't
be
covering
that,
but
I
think
that's
a
great
idea
and
a
good
way
to
add
things
to
agendas
for
people
to
see.
A
B
Hi
everyone,
so
quite
a
few
of
you
participated
in
the
discussions
around
our
vision
for
metrics,
for
how
the
dashboards
can
be
edited.
The
differences
between
default
and
custom,
dashboards
and
kind
of
you
know
how
should
we
treat
them
in
the
UI
and
so
on
and
so
forth.
So
as
the
outcome
of
all
of
those
amazing
discussions
which
you
can
check
out
in
the
issue
description
that
I
linked
here
in
the
agenda,
you
can
see
the
whole
summary
there.
B
So
dobe
and
I
are
proposing
that
we
work
on
that
in
the
nearest
future
and
then
there
are
also
lots
of
design
issues
that
are
linked
in
the
plenty
issue
you
that
I'll
be
working
on
in
13.2.
So
some
of
those
improvements
like
improving
the
experience
for
adding
a
metric,
designing
the
chart
builder
slash
preview
things
like
that,
so
you
can.
You
can
have
a
look
at
the
specific
issues,
I'll
be
working
on
that
and
we
will
be
implementing
those
improvements
or
the
next
few
iterations.
B
B
Okay,
so
we're
not
really
changing
anything
about
how
any
of
our
dashboards
work.
The
only
thing.
The
only
intention
here
in
this
iteration
is
to
make
it
easier
for
the
user
to
access
metric
settings
and
to
create
a
new
dashboard.
One
interesting
change
that
we're
planning
is
to
give
to
give
the
user
an
option
to
create
a
dashboard
by
duplicating
the
current
dashboard.
So
the
idea
is
that
duplicating
the
dashboard
is
part
of
the
create
a
dashboard
flow.
It's
just.
B
Instead
of
creating
that
from
scratch,
you
can
duplicate
the
current
dashboard
and
kind
of
use
it
as
a
template
and
go
from
there.
So
we
want
to
do
that
and
so
yeah
these,
and
for
so
we
want
to
do
that
for
the
custom
dashboards
as
well
for
default
Edwards,
the
user
can
add
a
metric
for
custom
dashboards.
The
user
can
edit
the
dashboard
and
we're
also
providing
some
more
helpful
tool
tips
along
the
way
and
in
the
13.2
design
issues.
I
will
also
be
working
on
defining
more
helpful
alerts
throughout
the
whole
metrics
experience.
B
C
Want
to
add,
it
was
a
discussion
that
we
had.
It
was
like
a
big
and
I
think
it's
a
big
step
toward
making
our
solution
my
own
solution
better.
This
is
one
of
the
big
things
that
I
would
like
us
in
the
future
iteration,
so
I
think
it
makes
sense
that
we
had
like
you
it
in
epic
and
then
a
design
which
was
like
a
design,
slash,
discuss,
issue
and
out
of
that,
there
will
be
like
multiple
design
issues.
C
So
I
know
that
we
need
to
think
about
MVC,
and
this
is
also
something
that
I
want
to
do
it,
because
this
was
a
big
thing
that
now
we
have
like
more
things
that
came
out
of
it
so
like
we
didn't
had
like
an
MVC
and
for
this
iteration,
but
given
the
the
scale
of
this
project,
I
think
it
makes
sense.
Now
we
need
to
tone
down
a
bit
and
think
about
the
MVC
approach.
Okay,
and
this
is
what
we
need
to
focus
on
and
make
sure
we
don't
over
engineer
and
the
feature
so
yeah.
B
So
we
explored
a
lot
of
different
ideas
for
what
the
first
time
matrix
experience
should
look
like
and
again
and
again
we
face
the
obstacle
of
being
unable
to
make
the
out-of-the-box
dashboard
exactly
the
same
in
terms
of
functionality
and
how
it
works
as
any
other
dashboards,
because
we
think
that
this
would
be
the
like.
The
ideal
experience,
the
most
straightforward
for
the
news:
yeah,
you
can
have
the
out-of-the-box
dashboards,
but
you
still
probably
want
to
build
upon
them.
You
want
to
make
them
your
own.
B
You
know
adjust
them
to
your
needs,
but
we
can't
have
that
right
now,
so
we
want
to
do
that
in
the
future,
but
we
can't
have
them
right
now.
So
our
idea
around
kind
of
to
go
around
that
is
to
make
the
out-of-the-box
dashboards
read-only
to
simplify
that.
Okay,
we
have.
We
have
these
out-of-the-box
task
force,
but
they
are
read-only
and
you
can
duplicate
them
kind
of
use
them
as
a
template
to
build
upon
them.
B
It's
not
super
easy
to
make
it
obvious
in
the
UI
to
make
sure
that
it's
clear
to
the
user
right
away,
that
they
are
read-only
and
then
it
kind
of
seems
like
we're
still
using
them
as
a
template.
So
the
way
for
the
user
to
build
upon
them
is
to
duplicate
them
and
use
them
as
a
template.
So
then
there's
this
whole
idea
of
having
a
template
library
for
dashboards,
which
could
also
be
a
part
of
the
metrics,
first-time
experience.
B
So
when
you
enable
metrics
when
you
land
in
your
on
your
home
page
for
the
first
time,
you
could
see
a
fully
set
up,
out-of-the-box
dashboard,
but
unfortunately
right
now
it's
it's
read-only
or
you
could
have
like
a
list
of
a
bunch
of
templates
and
you
can
maybe
preview
and
they
made
some
visionary
mock-ups
for
that,
just
to
kind
of
illustrate
the
idea.
And
then
you
can
take
one
of
the
templates
that
you
think
is
interesting.
B
That
meets
your
needs
and
then
you
can
move
forward
with
that
and
we
could
even
streamline
the
whole
metric
experience
further
for
first-time
users
by
building
Prometheus
configuration
into
this
experience.
So
as
a
user,
when
I
land
into
metrics
for
the
first
time
like
I've,
never
I've,
never
opened
the
metrics
page
and
I
open
it
for
the
first
time,
it's
always
much
better
to
see
something
to
see
some
dashboards
or
to
see
a
very
good
that
it's
very
easy
to
get
started
rather
than
to
just
see
like
an
empty
state.
B
And
then
you
I
have
to
configure
something.
I
have
to
configure
prometheus,
go
through
all
those
steps
and,
in
the
meantime,
I
haven't
really
seen
what
metrics
look
like
and
what
they
can
do
for
me.
So
we
explored
some
of
those
ideas
how
to
create
a
better
first
time,
experience
for
matrix
users,
so
the
short-term
vision
is
to
make
the
default
or
out-of-the-box
dashboards
read-only
and
to
make
it
very
clear
to
the
user
that
they
are
read-only
to
provide
them
with
some
to
propose
some
next
steps
like
what
can
they
do
next?
B
How
can
they
explore
metrics
further,
and
then
we
also
explored
the
long
term
idea
of
having
a
template
library.
Therefore,
a
template
library,
so
Dube
and
I
had
a
little
chat
about
yesterday
and
I
think
we
both
agreed
that
it's
a
it's
a
really
good
goal
to
have
for
the
long
term,
but
it
would
probably
be
very
difficult
or
you
know
it
would
be
a
lot
of
effort.
It
will
be
a
lot
of
effort
to
get
there,
but
it's
really
exciting
that
we're
already
talking
about
it
and
having
it.
B
You
know
and
we're
thinking
about
what
it
could
look
like,
because
we
can
start
to
slowly
move
towards
that
and
I
know
that
if
you
have,
you
had
some
great
ideas
around
this
and
proposed
that
we
we
use
templates
in
the
metrics
experience.
So
if
you
have
any
more
ideas
around
it,
there's
an
issue
to
explore
this
I
linked.
It
I
believe
I
linked
it
in
the
agenda.
I.
D
B
Totally,
it's
just
we're,
you
know
it's,
it's
not
something
we
can
address
in
like
the
next
milestone
or
two,
and
we
really
want
to
fix
the
broken
Parsons
experience
now.
I
agree.
I
think
it
would
be
a
great
experience
to
offer
to
our
users
yeah.
C
Think
I
think
that
it's
more
it's
more.
This
experience
is
more
relevant
if
you
have
a
lot
of
out
of
the
box,
but
right
now
we
have
only
one.
If
we
will
work
on
what
we
planned,
then
I
mean
some
users
may
complain.
I
wanna
see
this
dashboard,
but
we
have
a
way
out
of
it
by
customizing
the
landing
page.
So
if
the
customer
can
customize
its
own
dashboard.
B
And
if,
if
you
have
any
ideas
around
any
or
any
of
the
proposed
improvements,
either
for
the
NBC
that
we're
going
to
work
on
them
in
the
next
milestone
and
then
I
will
be
taking
you
on
the
designs
that
I
work
on
to
get
your
feedback
as
well
throughout
13.2,
and
if
you
have
any
more
specific
ideas
around
the
role
of
work
templates
in
the
experience
and
how
we
can
you
know
leverage
it.
The
most
feel
free
to
comment
in
this
metrics
def
for
startup
screen
issue.
B
D
E
Yeah
about
showing
that
I
heard
that
it's
hard
to
convey
that
dashboard
is
read-only
the
main
dashboard
and
seeing
that
this
default
dashboard
is
the
starting
point,
and
the
user
doesn't
know
yet
that
there's
the
possibility
to
edit
something.
Maybe
we
can
show
the
edit
button
in
a
disabled
State
to
both
show
that
this
is
read-only
and
that
there
is
a
slight
possibility
at
some
point
if
the
user
changes
something
for
it
to
be
editable
like
if
he
adds
a
custom
dashboard.
B
No
totally
it's
a
great
idea
and
actually
I
explored
it
in
in
the
wireframes.
So
it
was
one
of
the
options
that
we
looked
at
and
I
have
I
have
an
issue
that
I'll
be
working
on
13.2,
to
flesh
out
those
designs
and
to
you
know
to
to
decide
exactly
what
it's
going
to
look
like
and
how
many
different
things
we
need
in
the
UI
to
make
it
clear,
but
I
think
there
are
pros
and
cons
to
having
a
disabled
button.
But
yeah
I
agreed
that
we
could
do
that
right.
C
Cool
I
can
go
next,
and
so
there
were
several
questions
from
the
team
here.
I
mean
after
we
had
our
discussion,
the
high-level
discussion
last
week
and
even
prior
to
that,
but
who's
our
target
audience
and
well.
Building
the
solutions
for
so
I
carried
an
email
and
base
of
some
comments
that
I
got
from
implementing
and
Kevin
I
was
update
this
amount
and
you
can
really
talk,
but
just
like
a
quick
summary.
C
So
obviously
I
do
believe
that
in
like
in
a
period
of
one
to
two
years,
we
can
make
github,
we
felt
choice
for
the
day-to-day
monitoring
tool
for
cloud
native,
hey
I
think
we
should
focus
on
small
and
medium
businesses
today
and
because
of
multiple
reasons
and
one
of
them
we
focus
on
cloud
native
and
small.
Medium
businesses
are
more
likely
to
move
to
to
be
a
cloud
native.
Actually
I
just
had
a
chat
was
the
preparation
call
with
one
large
customer
yeah.
C
They
are
moving
like
10%
of
the
infrastructure
to
to
kubernetes
only
10%
in
2021,
and
they
are
talking
about
something
like
5,000
5,000
servers
like
10%
little
kubernetes.
So
we
are
seeing
this
more
and
more
I
mean
larger
two-bys
are
still
a
still
to
some
extent
like
in
the
old
way
of
managing
applications,
and
they
are
now
just
moving
into
into
community.
So
every
time
you
are
in
a
call
with
this
kind
of
customer,
they
are
asking
you
okay,
great
kubernetes
is
nice,
some
experience
with
experimented
with
running.
C
Today
you
know
just
google
it
you
can
find
and
full
of
articles
talking
about
it,
and
you
know
we
know
that
Key
Club
is
positioned
in
the
space
and
a
lot
of
our
customers
are
actually
moving
to
get
up
because
we
we
are
doubling
down
on
cloud
native
if
we
know
that
we
are
focusing
on
developers
and
DevOps
engineers,
because
we
know
that
developers
in
this
segment
probably
take
like
more
tasks
than
just
just
being
a
developer.
Sometimes
the
developer
is
more
than
that.
C
It's
also
a
list
manager
and
also
in
charge
of
monitoring
the
application,
and
it
makes
sense
to
to
address,
to
address
them
and
obviously,
in
terms
of
spending
budget,
small
medium
based
businesses,
less
willing
to
spend
budget
on
expensive
monitoring
system.
So
they
are
more
open
minded
or
very
discussion.
We'd
like
an
open
source
solution,
because
our
monotone
is
free
and,
to
some
extent
a
lot
of
large
enterprise
when
they
hear
about
open
source
solution.
They
think
it's.
It's
like
it's
something.
C
That
is
it's
it's
a
bit
immature
and
this
is
by
the
way,
a
strategy
that
the
large
vendors
are
doing.
They
are
like
they
are
doing
a
lot
of
fads
around
open
source
and
they
are
treating
open
source
and,
like
free
features,
some
sort
of
a
nice
experiment
that
they
don't
have
any
enterprise
that
is
backing
them
or
thought.
C
A
trend
in
the
market
is
changing
and
I
think
that,
even
with
the
effect
of
coffee
aid
and
in
basically
trends
that
we
see
in
the
market,
companies
are
more
willing
to
have
a
discussion
about
open
source
solution
because
they
realize
that
to
some
extent
it
is
the
future,
and
we
are
also
seeing
large
enterprise
that
are
adopting
open
source
standard.
But
still
small
and
medium
businesses
are
more
willing
to
have
a
discussion
with
those
type
of
solution.
C
And
obviously,
if
we
go
to
the
strategy,
it
means
that
we're
less
likely
to
compete
head-on
with
established
vandals,
and
we
know
that
we
do
fall
short
in
terms
of
our
our
feature:
capabilities
and
our
feature
parity.
If
we
go
against
like
that
of
New
Relic
up
dynamic,
all
of
those
larger
enterprise
that
they
have
all
the
bells
and
whistles,
and
because
this
was
their
primary
goal
and
primarily
business,
and
they
have
like
hundreds
of
developers
that
are
only
working
on
on
this,
so
unite
of
this
I
think.
C
This
is
why
it
we've
selected
those
is
our
targeted
customer.
Having
said
that,
over
the
last
couple
of
iteration,
we
are
building
features
for
our
internal
SL
team,
and
we
do
that
from
several
reasons.
One
of
them
is
first
of
all,
we
do
see
them
as
as
a
target
audience
in
the
future.
So
when
we
are
building
it,
it
always
good
to
have
a
discussion
with
them
at
least
to
understand
what
they
need
to
do.
And
how
can
we
solve
that
problem?
C
Then
we
get
like
good
feedback
because
at
the
end
of
the
day
or
discussions
that
I
have
with
customers
just
to
get
the
right
requirement
and
if
I
have
a
customer
that
I
can
just
slack
and
say:
hey,
let's
hop
on
jump
on
his
own
call
and
tell
me
what
you
think
about
this
and
that
then
this
these
discussions
are
valuable
to
us.
So
this
is
why
we're
building
those
solution
to
two
12's
arrays
and
once
we
will
see
that
we've
succeed
with
that
and
they
are
starting
to
to
use
our
tools.
A
A
So
maybe
maybe
this
is
a
little
early
for
this,
but
I
open
this
issue,
so
we
can
discuss
further,
but
for
the
last
few
weeks
or
ten
weeks
or
something
we've,
we've
not
been
using
15
minutes
for
sure
we've
gone
up
to
30
or
a
little
more
a
couple
times,
but
so
I
just
want
to
get
everyone's
feedback
on
that.
So
please
add
to
that
issue
and
then
I'll
pass
it
on
to
cool.
D
Yeah,
it's
just
ironic.
Every
time
we
talk
about
shortening
the
meeting,
we
end
up
taking
just
as
long
but
anyways
yeah.
So
the
topic
we
had
is
prometheus
training
I
had
a
conversation
with
someone,
the
team
wanting
to
do
more
training
and
I
think
this
would
be
beneficial
for
everyone,
who's
interested.
So
man
I
recently
talked
with
Ben,
who
is
part
of
Prometheus
team
and
also
works
at
a
lab,
and
there
was
a
course
that
was
identified.
As
you
know,
a
good
example
of
what
we
could
probably
try
to
do.
D
This
is
not
necessarily
like
fronting
or
back-end
I
think
it
kind
of
goes
through
a
lot
of
the
fundamentals
and
basics,
from
kind
of
how
to
gather
your
metrics
and
so
forth.
I'm,
not
sure
if
the
rod
has
already
done
this
before
cuz.
He
sent
me
something
related
to
this.
At
one
point:
isn't
maybe
he
did
the
free
one.
D
So
what
I'll
do
after?
This
call?
Is
create
an
issue
I'll
ping
it
on
the
select
Channel
and
then
if
people
are
interested
can
chime
in
there
and
then
we
can
yeah
sounds
like
from
the
dock
that
people
are
interested.
So
we'll
sounds
like
this.
Something
will
probably
move
forward
with
cool
any
any
comments
on
this.
D
Cool
sounds
like
almost
everybody
will
do
this,
so
that's
cool
and
then
the
last
announcement
was
just
Jose's
out
this
week,
but
I
just
wanted
to
congratulate
him
and
when
he
watches
the
recording
or
whenever
you
see
him.
The
next
meeting
congratulate
him
for
becoming
a
front-end
maintainer,
very
exciting
yeah,
so
he'll
be
back
next
week.