►
From YouTube: Monitor:APM Weekly Meeting - 2019-12-18
Description
Weekly team meeting for the Monitor:APM group. We reviewed the remaining 12.6 issues and covered a number of announcements.
A
A
Ok,
just
a
heads
up,
then
I
think
a
lot
of
people
will
be
out
the
next
couple
weeks.
Ok,
I
can
take
care
of
that.
Then
the
next
one
I
just
a
reminder
so
kind
of
engineering
cutoff
for
12.6.
If
you
haven't
gotten
your
merge
requests
merged
is
yesterday
today
ish,
so
just
to
remember
too,
if
you're
not
gonna.
If
the
issue
is
you're
assigned
to
the
mrs
aren't
merged
or
they're
not
going
to
get
into
the
12.6
release,
then
we
have
to
make
sure
we
move
the
issues.
A
B
B
So
everything
that
will
not
get
much
so
I
mean.
Maybe
it's
it's
better,
just
to
make
sure
that
if
you
know
the
things
will
be
merged
and
will
be
in
eventually
12.6
then
maybe
put
a
comment
down.
So
when
I
will
look
at
the
ball
and
I
will
see
like
a
handful
of
issues
now,
okay,
those
mine
that
you
have
the
comment
there,
I
should
not
know
I
should
I
couldn't
I
should
know
them.
So
everything
that
is
not
closed.
Basically,
we
move
so
it's
not
closed
and
you
know
that
it's
going
to
be
merged.
B
A
Okay,
so
yeah
at
least
put
accountant.
The
big
thing
is
making
sure
it's
in
the
right
workflow
state.
So
if
it's
in
review
or
workflow
verification
that
that
goes
a
long
way
to
so
and
be
sure
about
that,
anyone
else
have
thoughts
about
that.
I
know
there
was
a
thread
in
our
slack
about
weights
or
Kirsty.
I
know
you
asked
about,
should
it
be?
What
percentage
to
use
I
think
the
big
thing
for
those
verification,
I
think
this
is
what
doe
of
you
are
saying
in
slack
goes
for
those
verification
issues
or
review
issues.
A
A
Okay,
okay,
all
right.
The
last
thing
I
had
was
I
just
made
a
change
to
the
handbook
about
discussion
issues
I
merged
that,
but
we
can
certainly
be
happy
to
continue
the
discussion
about
how
we
handle
those
and
make
more
changes,
but
basically
my
I.
The
process
that
seemed
to
work
the
best
over
the
last
few
months
was
we
create
issues
for
discussion.
A
B
A
D
I,
like
what
you've
proposed,
yeah
I,
think
I
sort
of
a
back
and
forth
like
with
the
clothing
issue
and
starting
afresh
moans,
because
all
of
that
discussion
is
sometimes
useful.
So
maybe
even
if
we
just
link
back
to
the
issue
original,
if
it's
close,
just
so
I,
feel
like
some
of
the
questions
come
up
again
during
implementation.
If
someone
wasn't
involved
in
the
original
discussion,
so
might
be
worth
at
least
looking
back
if
they
realize
she's
closed.
A
E
Indeed,
so
a
bit
of
sad
news
to
share
with
you
all
today,
I
have
actually
just
today
handed
in
my
two
weeks
notice.
So
I
will
be
leaving
gitlab
on
January
3rd
I
wanted
to
stress
to
you
all.
It's
certainly
not
because
of
discontentment
or
dissatisfaction
in
any
way.
I
love,
gitlab,
I'm
gonna
continue
to
be
a
user
and
an
evangelist
of
get
lab
as
you
all
grow
and
move
towards.
E
You
know
the
IPO
coming
up
at
the
end
of
this
year,
so
really
really
excited
about
the
direction
get
labs,
headed
and
excited
to
to
cheer
you
all
on
from
the
from
the
sidelines
here.
I
also
want
to
distress
that
this
is.
This
has
happened
very
quickly,
so
Christopher
and
Dan
have
just
heard
about
this,
so
we
don't
really
have
a
plan
in
place
yet
for
that
transition.
E
We're
going
to
be
working
on
that
here
over
the
next
couple
days,
just
to
make
sure
that
you
know
that
you
all
are
set
up
in
a
good
position
to
move
forward
and
that
we
don't
hinder
progress
or
velocity
in
any
way
as
I
kind
of
step
out
of
this
role,
and
so
so
more
details
on
that
will
be
forthcoming.
I
will
be,
of
course,
available
for
questions
or
anything
if
you
guys
have
any,
please
feel
free
to
reach
out
on
slack
or
ping
me
or
we
can
jump
in
a
one-to-one
and
yeah.
E
B
E
F
Like
it's
been
a
pleasure,
the
short
time
we've
got
to
work
together
as
wearing
my
inner
director.
As
you
know,
it's
been
really
really
good
and
I
wish
you
the
best,
and
we
obviously
want
you
to
follow
your
dreams
and
all
of
the
usual
things.
But
if
anyone
has
any
questions
myself
Christopher,
should
you
want
to
reach
out
to
Christopher
as
well?
F
That's
why
we're
here
just
to
you
know,
make
sure
everyone
here
knows
that
we
are
doing
the
best
we
can
to
make
this
a
nice
easy
transition
for
everyone
and
to
let
you
all
know
that
if
you
have
any
questions
at
all,
please
ask
and
please
bear
with
us
while
we're
coming
up
with
a
good
plan
here
to
make
this
transition.
You
know
relatively
smooth
as
far
as
much
as
possible,
there's
no
replace
anything
Adriel,
but
someone
will
and
will
be
able
to
come
along
and
assist
in
that
manager
capacity,
so
I.
G
I'll,
just
pile
on
and
say
really
appreciate
all
the
hard
work
a
troll
sent
her
a
gala
and
super
bummed
about
this.
Obviously,
it's
kind
of
caught
us
off
guard
a
little
bit
so
I'll
be
somewhat
transparent
in
regards
to
we're
scrambling
a
little
bit.
I
really
want
to
hear
from
folks
get
some
input
on
things
will
more
than
likely
look
for
some
additional
managerial
help
in
the
interim
just
kind
of
bridge
the
period
of
time,
but
want
to
make
sure
people's
concerns.
G
G
So
that's
a
definitely
a
component
of
this
as
well
that
if
you'll
obviously
have
on
day,
one
is
as
a
hiring
needs
that
we
need
to
be
thinking
about,
as
we
move
forward
again
want
to
stress
super
Bauman's
as
CHR
I'll
leave,
but
when
I
wish
them
the
best
and
if
folks
have
concerns,
definitely
please
raise
them
both
with
Daniel
and
myself.
My
schedules
pretty
open
from
not
necessarily
from
a
availability
perspective,
but
it's
open
for
Prosecco.
You
can
definitely
sign
up
for
anytime
and
I'll,
make
the
time
available
and
if
you
can't.
I
Go
ahead
just
a
few
awards
and
think
a
year
for
all
the
support
he
has
given
me.
I
know
it
has
to
be
a
bit
flexible
with
me,
sometimes
with
the
scheduling
and
more
things.
I
want
to
thank
you
for,
although
all
the
big
all
the
good
process
and
all
the
and
thank
you
for
working
together
with
us
here,.
H
E
H
That
not
have
you
on
this
call.
I
wish
you
the
best
of
luck.
So
I
got
a
issue
today
that
hold
or
is
order
is
looking
to
upgrade
prometheus
helm.
Chart
it's
going
to
take
Prometheus
for
a
big
bump
from
two
point,
two
two
point:
thirteen-
and
this
is
something
I
think
we
we
do
a
lot
of
web
mocks
and
we
don't
do
much.
We
don't
have
any.
H
F
H
A
F
H
B
H
A
F
F
A
F
H
F
H
H
H
B
H
J
So
if
anybody
has
any
talks
about
it,
please
check
the
mr
out
and
also
shout
out
to
david
and
drive
for
helping
a
lot
with
that
and
because
there's
nobody
else
after
me.
I
just
want
to
say
a
little
bit.
Thank
you!
Oh
really,
it's
really
been
a
pleasure
working
with
you
and
definitely
miss
you
here
and
back.
You
meant.
H
F
B
A
F
F
So
that's
mostly
for
the
front
end
team,
so
hopefully
people
will
be
able
to
attend.
I
tried
to
find
a
time
that
was
good
for
everybody,
but
anyways
other
questions
there
that
maybe
time
you
do
it
in
otherwise
again.
Thank
you
so
much
Adriel
and
think.
Thank
you
for
everyone
having
us
all
along
their
meeting
as
well.
It's
a
bit
weird
when
random
people
show
up.
So
thanks,
very
much.
Okay.
If
everyone
enjoys
their
day
and
has
a
great
holiday.
J
A
B
Let's
walk
the
boat
I
mean
today
is
the
last
day
for
1206
right,
so
we
can
maybe
go
over
and
pick
some
issues
that
we
think
are
interesting
and
just
you
know
give
some
status.
Maybe
maybe
we
can
update
some
of
them
afterward
if
we
all
here,
please
for
the
issues
that
you
know
if
they
feel
comfortable
talking
about
them.
Sure.
B
B
So
there
was
one
issue
that
I
wanted
to
discuss.
The
plan
I
can
put
like
comment
there,
but
we
can.
We
can
I
know
it
could
be
like
closing
these
issues,
so
you
can
drag
it
to
the
next
one
and
then
maybe
just
iterate
on
it.
Even
if
it's
closed
and
but
basically
you
want
to
comment
on
this
I
mean
moves.
It.
K
B
A
A
B
B
I
B
Fantastic
thank
you
for
that.
But
I
was
the
one
who
think
that
I
forgot
to
to
mention
please
when,
whenever
I'm
like
asking
a
question
on
the
thread,
if
someone
is
replying,
please
please
let
mention
me
because
I
walk
with
the
to-do
list
and
it's
very
hard
to
keep
track
on
all
the
threads
that
are
open
and
I
would
really
want
you
to
comment.
So
try
to
admit
to
me.
If
you
wanted
mention
me,
you
probably
won't
get
a
respond.
B
H
L
L
L
F
B
B
D
D
H
D
B
J
B
H
L
H
L
L
B
H
B
B
Disaffection
dashboard:
there
is
a
user
flow.
When
you
click
on,
you
can
see
the
pod
metrics.
Now
the
dashboard
already
created.
Okay,
it's
it's,
there,
I
mean
basically
the
beckoned
walk
is
completed
and
what
I
asked
Ruben
is
that
maybe
we
have
like
a
low-hanging
Foothill,
because
the
charts
are
available,
but
in
order
to
use
it
not
as
a
part
of
the
infrastructure,
but
not
as
a
part
of
the
user
flow.
B
To
do
that,
we
will
probably
need
to
create
a
dashboard
with
the
drop
down
where
we
choose
a
specific
port,
because
each
each
pump
each
pump
you'll
query
actually
take
a
specific
port
and
query
the
data
escape
the
metric
on
that
individual
pod.
So
in
the
flow
we
don't
select
the
port,
because
when
the
user
hit
this
city's
dashboard,
it
is
going
to
the
dashboard
while
is
clicking
on
one
of
the
pods.
B
But
if
we
want
to
make
it
as
a
part
of
our
general
dashboard,
then
all
we
need
to
do
basically
is
to
allow
the
user
to
select
the
port.
So
we're
probably
to
have
some
point
and
work
like
some
sort
of
it
drop
down
to
select
a
code,
and
we
can
have
this
this
mode
available
for
the
general
use
and
not
only
for
the
infrastructure
book
flow,
so
I'm
I'm
thinking,
maybe
that
create
another
issue.
Just
for
the
front-end
and
we'll
have
like
another
girls
ready
for
the
pod
matrix.
H
Actually
got
it
now
that
you
mentioned
this.
Talk
to
a
friend
of
mine
yesterday
that
had
interviewed
with
a
large
cloud
provider
and
was
describing
to
me
some
of
their
workflow
and
the
workflow
they
went
to
put
together
was
something
about
as
a
review.
You
know,
as
they
generated
a
review
app.
They
wanted
to
generate
a
graph
on
a
dashboard
custom
to
that
custom
to
that
review
app
and
then
be
able
to
store
that
information
and
go
back
and
review
things
in
the
you
know
as
things
that
would
be
both.
H
B
B
B
C
B
H
B
J
H
H
B
B
B
B
B
E
Well,
it's
a
big
investment
on
the
side
of
the
back
end,
I,
think
more
so
than
the
front
end,
but
it
basically
kind
of
lets
us
iterate
faster,
as
we
you
know,
would
have
a
little
bit
more
direct
access
to
the
resources
that
are
available,
but
but
I
guess
what
I'm
trying
to
say
is
I,
don't
know
that
it's
necessarily
a
blocker
for
us
moving
forward
for
any
of
the
things
we're
working
on.
It's
more
just
an
improvement
to
help
us
to
just
ease
the
development
process.
Moving
forward,
yeah.
J
Environments
and
the
a
beard
we
have
it
doesn't
give
all
the
necessary
attributes
that
we
need
so
we're
having
to
do
a
little
bit
of
a
hack
on
the
front
hips
to
get
a
construct.
Some
attributes
so
having
graph
QL
would
definitely
alleviate
that
issue
and
I
worked
with
Kristi
along
along
with
Kristi
on
this
to
explore.
The
existing
back-end
API
is
to
see
if
we
can
get
around
this
hack,
but
it
looks
like
there
is
no
way
to
do
that.
J
I
One
one
selling
point
or
for
DAF
is
that
the
approach
that
we're
taking
is
is
to
publish
the
graph
QL
API
is
that
we
create
to
the
public
there's
still
a
little
bit
of
discussion,
of
how
we
make
changes
to
the
API.
But
the
approach
for
now
is
to
publish
like
make
it
part
of
the
product.
So
if
we
create,
for
example,
and
environments
and
point
now
not
only
we
in
the
front-end
can
use
them.
Also,
the
customers
of
of
get
lab
can
use
those
API
s.
I
B
The
importance
of
you
know
putting
some
more
work
on
that
so
yeah
I,
remember
the
environment
issue
that
we
have
like
around
their
query
in
the
metric
was
across
multiple
environment
and
it
may
end
up
blocking
the
infrastructure
both
as
well
and
also
your
point
again.
Prs
is
also
valid.
Yeah
I
think
yeah
I
think
we
need
to
probably
spend
some
time
here.