►
From YouTube: Monitor:APM Weekly Meeting 2020-04-01
Description
Weekly meeting for the Monitor:APM group
A
C
Hi
everyone
yeah
so
I'm,
currently
running
card
sort
for
github
Operations
documentation,
which
is
a
research
effort
for
us
to
try
to
understand
what
are
the
mental
models
that
we
have
about
operations
features
and
how
do
we
categorize
this
information,
which
will
help
us
come
up
with
a
better
structure
and
content
for
the
docs?
So
if
you
have
the
time
it
would
only
take
about
20
minutes,
I
I
would
like
to
ask
you
to
participate.
C
Your
feedback
would
be
super
valuable
for
us,
because
the
more
responses
that
we
get
the
more
patterns
we
will
see.
So
please
take
the
time
to
do
that.
Thank
you
and
if
you
have
any
questions,
feel
free
to
ask.
I
was
telling
to
the
issue
there.
That
gives
like
more
detailed
explanation
for
this
effort
and
what
we're
trying
to
achieve.
B
C
E
E
You
get
you
know
the
comment
you
want
to
yeah,
maybe
I
can
so
I
want
to
mention
that
I
hope
that
out
of
the
discussion,
we
can
have
something
actionable
I'm
thinking.
We
could
start
the
discussion
by
asking
what
we
can
do
to
improve
our
UX
process
and
all
right.
Carry
X
review
process
and
yeah
see
see
what
we
can
do
to
to
make
sure
that
things
that
are
affecting
the
UX
negatively,
don't
impacts
and-
and
we
I
know
that
Nadia
has
been
reviewing
at
least
my
merge
requests
about.
E
C
Yeah,
that's
a
good
point.
I
agree,
I've
been
thinking
about
it
and
for
sure
one
of
the
things
I'm
doing
is
setting
up
the
GDK
with
metrics
and
logs
I
already
had
one
failed
attempt
at
this
a
couple
months
back
so
I'm
attempting
it
again
I'm
actually
talking
to
Nikolaj
tomorrow,
so
hopefully
we'll
be
able
to
figure
it
out.
So
that
for
sure
will
be
super
helpful
for
me
to
be
able
to
really
dive
in
and
check
all
the
nitty-gritty
stuff.
C
Otherwise,
yeah
I'll
be
asking
for
more
video
recordings,
just
screen
recordings
of
features
when
we
can
check
any
stays.
If
I
need
to
think
scales
in
a
weird
way,
usually
I
do
that,
but
I
agree.
I,
think
we
need
to
make
sure
that
we're
as
thorough
as
possible
in
reviews
yeah,
if
anyone
has
any
specific
feedback
for
what
UX
could
be
doing
to
ensure
that
the
quality
of
the
products
that
we're
shipping
is
good.
Just
let
me
know
open
to
any
feedback.
F
Hey
sorry
I
just
had
issues
before
so
I.
Think
I
agree
that
video
refused
to
be
could
be
great.
I
also
wanted
to
mention.
You
were
looking
at
setting
up
review
apps
in
one
of
my
Amar's
a
couple
weeks
ago.
I
wonder
if
you
ever
figured
out
how
to
do
it
or
what
you
use
them,
because
I
think
that
would
be
useful
as
well.
Maybe
yeah.
C
G
G
If
we
could
do
something
special
for
environments
like
review
apps,
where
we
don't
necessarily
have
to
depend
on
a
live
kubernetes
instance,
but
we
mark
the
data,
but
that's
still
in
discussion,
but
at
this
stage
I
don't
think
we
can
take
full
advantage
of
review
apps
because
yeah
we
can
deploy
to
kubernetes
instance.
So
we
have
no
data.
So
if
our
best
bet
is
to
pull
it
to
your
local
box
and
run
it.
G
B
G
Mean
I
mean
locally
I
mean
locally
and
run
it
from
there.
In
my
experience,
trying
to
connect
to
mini
cube
has
been
very
bad.
There
have
been
a
lot
of
issues
with
that,
and
it's
very
difficult,
and
it's
just
a
waste
of
time
connecting
to
kubernetes
cluster
is
much
easier
and
straightforward,
but
that
is,
it
does
take
time
to
do
that
and
once
you
have
everything
set
up
there.
F
F
C
Yeah
I've
been
following
that
and
working
together
with
Tristan
to
actually
enable
metrics
and
logs,
and
we
got
stuck
and
weren't
able
to
get
past
that
actually
well.
We
probably
would
succeed
if
we
put
in
many
more
hours,
but
there
was
no
time
but
yeah.
We
got
stuck
with
some
problems
with
get
LeBron
er
some
problems
running
locally
or
something
I,
don't
remember
exactly
what
the
issues
were,
but
there
were
some
complications
so
I'm
trying
to
kind
of
investigate
what
can
be
done.
C
C
B
Maybe
if
I
can
piggyback
on
that,
I
would
very
much
like
to
do
that
as
well
and
similar
to
Nadia
have
also
got
so.
I
can
see,
didn't
have
the
time
to
do
that,
and
it
will
be
great
if,
if
you
are
doing
that
already
so
we
can
do
that
together
or
maybe
maybe
I
called
it,
because
it's
tomorrow,
I
won't
be
able
to
attend.
Oh
if
it's
possible
to
push
it
for
next
week
on
Monday,
if
it's
not
so
urgent,
so
I
can
attend
as
well.
Then
we
can
at
one
time
so
sure
yeah.
C
B
E
B
E
B
E
E
Documentation
on
the
footing,
the
rest
just
mentioned
that
covering
the
previous
meeting,
but
I
would
like
to
bring
it
up
again,
because
I
I
could
not
find
my
way
through.
The
things
that
were
already
done.
I
would
suggest
that
at
least
we
start
by
filling
out
the
readme
in
the
metrics
of
pudding
and
say
how
it
works.
I,
don't
have
maintainer
access
to
that
project
and
that's
okay.
B
H
B
You
invited
Wednesday,
it's
Mia,
Clemente,
Annette
and
members
of
the
intro
team.
You
can
I'm
posting
the
recording.
The
recording
I
can
link
it.
Also
to
this
issue.
It's
not
there,
remember,
don't
slack,
but
all
the
meetings
are
recorded
and
share,
so
don't
feel
like
you
have
to
be
there,
but
if
you
want
to
stay
on
top,
you
can
definitely
watch
that.
It's
a
30
minute.
H
I
I
So
if
you've
seen,
there
are
fana
both
that
the
infrastructure
team
creates,
they
usually
have
at
the
top
row
of
variables
with
dropdowns,
where
you
can
select
values.
So
we
want
to
implement
something
similar
in
our
dashboards,
and
this
is
a
discussion
for
how
what
should
be
the
format
to
define
variables
in
the
dashboard
EML
file.
B
Speaking
of
the
project,
we'll
start
with
defining
those
variables
on
the
back
end
of
the
army
file
and
as
we
progress
in
future
iteration,
we
create
some
sort
of
euy,
so
it
would
be
easier
for
use
of
the
Cato's,
but
that's
something
that
is
not
yet
scoped.
So
right
now
it's
focused
on
young
back-end.
B
I
Yeah
so
I
think
what
you're
talking
about
is
the
query
type
that
gravano
offers
query
type
of
variable,
so
you
define
a
variable
with
that
type
and
you
give
it
a
Prometheus
query,
which
Ravana
will
fire
and
use
the
result
to
populate
the
drop-down
for
that
variable.
So
that
is
something
that
we
proposed
in
iteration
2,
not
out
of
the
embassies.
I
G
That
makes
sense
okay,
because
otherwise,
if
we
want
to
surface
something
like
the
backend
drop
and
I'm
looking
at
the
gate
lab
triage
further,
we
have
and
the
back
end
has
about
15
services,
and
if
the
user
has
to
input
all
these
15
services
and
the
amel
file,
it's
it's
not
scalable,
but
your
second
iteration
proposal
seems
like
they're
going
in
the
right
direction,
at
least
to
me.
Thank
you
for
clarifying.
B
Yeah
make
sense
for
the
user
to
type
you
know.
This
name
of
services
can
be
like
also
like
Wilson
Spode
name,
so
expect
the
user
to
put
life
in
the
great
long
service
name,
hostname,
port
name,
whatever
you
need
to
create
some
sort
of
variable
query
and
the
list
will
be
dynamic
based
on
the
query.
That
can
do
something
for
the
second
iteration,
but
it
needs
to
be
scheduled
like
right
after
it's
not
something
that
we
need
to
wait.