►
From YouTube: Monitor:APM Weekly Meeting - 2019-09-19
Description
Weekly meeting for the Monitor:APM Group. Discussed 12.3 and 12.4 planning, SMAU, and the instance administration project.
A
B
B
B
A
C
D
B
B
A
The
question
then
is
like:
if
we
finish
all
the
work,
then
we
can
just
pull
in
more
stuff
from
12/5,
but
I
think
this
lists
you
did
a
so
I
want
to.
First.
Thank
you
because
that
was
must
have
been
a
ton
of
work
to
get
through
to
all
50
of
those
hoes
and
lay
her
down
I.
Don't
envy
that
task
uh-huh,
but
I
yeah.
If
I
was
very
excited
to
see
the
trim
down,
West
and
I
think
we
could
I.
B
A
A
I
tried
to
update
the
workflow
labels
on
others,
so
I'll
I'll
take
another
pass
through
that
list
and
I'll
try
to
comment
about
how
much
I
think
is
left
on
each
one
and
then
I
can
take
everyone
to
give
me
or
I'll.
Take
whoever's
working
on
it
too,
to
check
my
check
my
assumptions
to
make
sure
I
was
on
the
right
path
but
yeah,
because,
as
of
now
I,
don't
we
can't
get
anything
else
into
twelve
three.
So
everything
in
that
twelve
three
column,
it's
gonna
need
to
move
somewhere.
A
Although
I
shouldn't
I
shouldn't,
say
that
some
of
those
issues
that
I
know
are
in
12,
three
have
already
been
merged
and
we
just
have
to
verify
them.
So
as
soon
as
that's
done
so
I
think
those
ones
could
stay
in
twelve,
three
and
as
soon
as
they're
done
we'll
just
close
them
and
then
that'll
be
it
so
I'll
I'll
flag,
those
as
well,
for
which
ones
can
stay
and
maybe
move
some
and
I'll.
Let
you
know
which
ones
need
to
get
moved
so
I
started
doing
that
yesterday
and
I'll
keep
working
on
that
today.
A
B
B
Two
things
to
ask
so,
first
of
all,
one
thing
is
on
me,
but
it's
important
also
for
you
to
know
probably
every
feature
that
I
probably
ask:
we
will
have
the
language
that
would
be
able
to
measure
we
have
to
so.
Keep
that
keep
that
in
mind.
What
does
it
mean
for
you?
We
will
make
sure,
as
I
mentioned.
Think
about.
B
B
B
B
E
It
just
seems
to
we
count
on
that
being
a
was
a
big
seller.
It's
a
big
selling
point
of
of
gitlab,
and
you
know
a
lot
of
these
features,
I
evaluate
them
in
terms
of
how
impressed
or
my
buddy's
gonna
be
when
I
show
them
this
and
right
now,
I'm,
not
at
the
point
where
I'm
like
here.
Let
me
show
you
how
Auto
DevOps
works
good,
you
know,
I
I
knew
I.
Would
you
know
potentially
not
get
it
right
and
it'd?
Take
me
a
couple
hours
to
get
it
done,
and
it
really
ought
to
be.
E
I
should
be
able
to
do
whatever
this
idea
to
deploy
is
I
mean
I,
know
that
some
of
the
some
of
the
sales
or
nice,
maybe
not
sales
people.
What
support
people
can
do
this
idea
to
deploy
idea
to
production
demo
at
meetups
and
stuff
I
would
I
just
think
that
that
Auto
DevOps
in
a
production
environment
is,
it
doesn't
seem
like
it's
all
that
easy
to
do.
D
B
B
B
B
B
We
have
contact
and
Josh
was
in
contact
with
him.
He
is
more
than
happy
to
set
up
a
call
with
us,
and
so
we
can
walk
us
through
some
of
those
concerns.
But
before
that
it's
important,
we
know
what
exactly
we
need
from
you.
I
don't
want
to
walk
into
the
mythically
without
any
anyone.
Do
it
anymore.
So
if
we
start
good
as
the
this
investigation
and
see
that
we
hit
some
sort
of
the
water,
we
have
some
questions
that
we
don't
really
know.
We
can
set
up
a
discussion.
B
E
E
B
B
E
B
It
would
take
a
while
until
would
be
able
to
take
to
consider,
take
finality.
I
have
no
problem
taking
if
it's
enough,
because
I
think
that,
and
most
cases
probably
to
be
good
enough.
If
you
want
to
just
search
to
the
lots
but
then
again
in
plastic,
such
is
the
right
tool
for
a
straightest
point
of
time
to
preserve
a
production
ready
and
we
have
support
with
elastic.
So
if
you
want
you
get
in
touch
with
anyone,
we
can.
We
can
talk
about.
Of
course,
if
you
want
to
leverage
this.
A
We
have
a
it's
linked
in
the
agenda
here,
there's
a
issue
that
we
opened
that
we
kind
of
leave
open
for
the
duration
and
then
typically,
we
don't
do
well.
I'm,
not
sure.
Maybe
people
who
have
been
here
longer
can
help
me
I.
Don't
think
we
actually
do
like
a
retrospective
meeting
to
kind
of
recap
all
of
this,
but
we.
C
Used
to
okay,
and
then
we
stopped
for
some
reason,
I
think,
is
that
we
scaled
way
too
big,
because
what
happened
is
that
every
single
department
will
say
things
on
the
retrospective
meeting
and
it
could
be
anyone
from
that
department.
It
could
be
back
in
engineer
a
friend
an
engineer,
whatever
things
that
you
had
in
mind
that
should
be
discussed
in
a
retrospective
company-wide.
You
could
do
that
problem
is
that
that
doesn't
scale
well
with
700
people,
especially
when
one
hour
time
frame,
so
we
had
to
change
it
to
something
more
manageable.
C
A
So
I
think
the
process.
Now,
then,
is
we
have
this
issue
that
we
open
every
team.
Does
we
fill
it
up
at
least
monitor,
fills
it
out
during
the
milestone.
So
we
probably
need
a
new
one
shortly
here,
but
then
this
gets
rolled
up
into
like
the
engineering
wide
retrospective,
which
is
like
a
document.
So
usually
one
of
the
engineering
managers
will
kind
of
consolidate
this
into
a
few
of
the
main
points
for
that
main,
like
Department,
why
hide
engineering
wide
retrospective
and
then
there's
a
call
that
does
happen
for
at
that
level?
B
B
A
F
So
the
additional
discussion
on
the
issue,
if
you
check
it
out
the
word,
there
was
discussion
about
creating
the
sub
monitoring
project
on
a
button
click
in
the
admin
area,
but
eventually
we
decided
to
create
the
project
without
any
use
or
infraction,
but
the
problem
with
that
is,
we
don't
have
a
good
system
in
place
currently
to
to
create
data
on
a
good
lab
instance.
You
know
automatically.
F
B
F
Yeah
yeah,
but
the
problem
with
creating
it
automatically
is
that
we
only
currently
do
things
automatically
with
a
migration,
but
creating
something
like
this
in
a
migration
caused
a
lot
of
problems.
You
can
see
I've
linked
some
in
the
comment
that
I've
linked
I've
listed
out
some
problems
that
it
caused.
So
it
would
probably
be
a
better
idea
to
not
do
it
in
a
Magnusson.
F
E
E
Little-Known
fact
yeah,
if
you
just
if
you
just
get
pushed
to
your
lab
instance,
it'll,
create
a
it'll,
create
a
project,
but
it's
gonna
be
really
bare-bones
right.
It's
not
gonna
have
but
I,
don't
know.
If
there's
a
mechanism
we
can
do
to,
you
know
provide
a
provided
tour
file
or
something
that's
like
okay,.
F
E
A
E
B
B
C
E
But
I
do
it
I?
Do
it
all
the
time
I
mean
I
literally,
did
it
four
or
five
times
last
week,
just
you
know,
spin
up
a
new
GDK
and
then
first
thing
I
do
is
push
my
auto
devops
projects.
To
that
thing,
I
don't
have
to
go
import.
Anything
and
I
have
to
create
a
project
or
anything,
push
that
thing
to
it
and
bam
done
works
with
you
know,
get
laughs
Dougie.
Let's
see
why.
B
A
A
A
B
B
B
G
B
A
Yeah,
the
original
issue
is
full:
there's
lots
of
comments
about
a
lot
of
different
parts
of
this,
so
it
might
make
sense
to
open
a
new
issue
just
to
focus
everybody
on
what's
left
and
what
needs
to
get
done,
especially
if
there
is
a
small
front
end
piece,
then
we
can
mention
that
in
there
and
it'll
be
very
clear
of
what
what
needs
to
happen
and
then
we
can
also
talk
about
design
in
there
with
Amelia.
Maybe
that
is
that
would
be
my
vote.
I
think
you
know.
B
A
A
So
if
you
have
things
that
went
well,
we
didn't
go
well
things
we
want
to
improve.
Then
we
should
please
remember
to
kind
of
add
them
in
here,
so
we
can
do
a
better
job
of
tracking
them,
and
then
we
could
talk
about
it
more,
but
I
wanted
to
I
think
in
this
meeting.
Just
kind
of
at
the
end
of
each
meeting.
I
just
want
to
remind
people
to
to
be
thinking
about
this,
so
we
can
constantly
try
to
improve.