►
From YouTube: Discuss Monitor:APM 12.3 Planning
Description
https://gitlab.com/groups/gitlab-org/-/boards/1065731?label_name[]=group%3A%3Aapm
B
C
C
C
Those
at
some
point
before
we
start
doing
the
12.3,
deliverable
and
planning
and
stuff
I
think
we
have
to
kind
of
understand
what
in
12.2
needs
to
move
over
sound
right,
exactly
sure
when
that
should
happen,
because,
like
we
were
talking
about
yesterday,
the
dates
are
kind
of
overlapping.
So
if
we're
still
working
on
12.2
for
another
week
or
ten
days,
potentially
or
I
should
say
the
work
that
we
do
for
the
next
10
days
could
potentially
get
into
12.2
all
right.
What
we
want
to
start
thinking
about
12.3
or
whatever
the
future
releases.
C
You
know
last
week
or
a
week
ago
they
it's
like,
there's
some
we'll
have
to
kind
of
think
about.
We
don't
have
to
talk
about
right
now,
but
how
how
that
overlap
happens,
and
that's
kind
of
talking
a
little
bit
yesterday
and
I'd
like
to
kind
of
start
documenting
some
of
that.
So
maybe
I'll
write
something
up
and
create
a
mr
that
we
can
start
reviewing.
Okay.
B
C
C
C
B
C
A
C
C
B
C
B
C
That
one
is
deliverable,
I,
think
yep,
okay,
so
this
PG
bounce,
your
exporter,
I
just
I'm,
pretty
sure
this
should
be
deliverable.
I
was
just
trying
to
capture
more
information
and
then,
as
I
dug
into
it
a
little
bit.
It
looks
like
we
did
some
service
discovery
stuff,
for
maybe
it
was
for
council,
so
so
I
think
my
my
hesitation
with
deliverable
on
this
one
was
just
that
I
wasn't
clear
exactly
what
working
we
went.
A
C
C
C
B
C
I
noticed
a
lot
of
those
issues
were
lightly
defined,
we'll
call
it,
which
was
probably
enough
for
someone
like
Ben
to
tackle.
It
probably
was
plenty
of
information
for
him,
and
that
just
remind
him
what
needs
to
happen.
But
if
the
APM
team
is
going
to
be
working
on
them
more,
then
they
might
need
a
little
more
definition.
So,
okay.
C
That
one
right
and
that
one
just
I,
think
it's
deliverable
with
the
caveat
that
there
were
some
comments
in
that
one
about.
Should
we
even
have
a
get
lab,
monitor,
slash
exporters
project
at
all?
Is
there
some
performance
things,
but
just
the
rename
part
of
it
I
counted
as
deliverable
and
I
put
a
comment
in
there
to
that
effect:
okay,
cool!
If
there's
other
follow-on
things
about
improving
performance
or
anything,
then
we
can
address
that
in
two
separate
issues.
Yeah.
A
C
A
B
B
C
B
Yeah
the
comment
that
we
kind
of
talked
about
this
in
the
staff
yesterday,
but
my
my
starting
point
is
product
prioritizes
issues
and
if
one
of
those
as
a
Docs
issue,
then
you
as
the
engineering
manager,
coordinate
resources
and
if
there
is
a
Docs
writer
available
great.
If
there's
not
okay
should
I
have
a
engineering
team
member
complete
the
docs
sure.
C
B
Like
it,
so
the
process
is
always
that
keep
that
in
mind
that
an
engineering
team
member
who
submits
a
Docs
update
as
I
understand
it.
It
has
to
be
reviewed
and
approved
by
the
technical
writing
team.
Okay,
you're.
It's
always
gonna
happen.
It's
just
matter.
If
we've
been
assigning
like
waiting
to
assign
them
to
a
member
of
the
technical
writing
team
and
that
we
shouldn't
slow
down
for
that.
C
B
A
A
C
B
A
C
B
C
C
Potentially
could
be
a
couple
more
so
hard
for
me
to
know
like
where
the
cutoff
is
and
like
what's
deliverable
what's
stretch
based
on
the
conversation
we
had
yesterday
about,
like
deliverable,
should
mean
almost
positive
that
we're
gonna
deliver.
It
I
tried
to
put
in
about
the
same
number
as
we've
been
of
issues
as
we've
been
doing.
C
A
C
C
A
A
B
B
C
B
That's
fine,
but
it's
just
a
reality
and
yes,
I
can
go,
look
through
and
say
which
ones
can
we
swap
out
so
I'm
gonna?
Add
this
one
and
if
then,
when
we
review
the
ones
that
are
listed
as
okay,
we
can
do
that.
I,
look
at
the
rest
of
the
direction
items.
These
are
all
support
for
other
chart
types
and
okay
with
those
yeah.
C
C
A
B
C
A
B
B
C
C
A
B
Okay,
so
the
other
thing
I
just
want
to
check
I
feel
like
if
I
look
at
how
many
we
have
so
again,
I'm
I
don't
want
to
be
the
like
shirk
product
manager
who
says
but
you're
saying
it's
like
the
you're
comfortable,
but
I
will
have
some
other
items
beyond
that.
We
would
have
called
stretch
before
sure.
C
B
B
C
B
C
A
B
C
C
B
C
C
You
for
yeah
totally
was.
Thank
you.
Sorry,
it
was
a
little
delayed.
I
would
have
liked
to
have
done
this
a
little
earlier,
but
now
that
we're
kind
of
getting
into
the
flow
of
it
I
think
it's
all
go
better,
and
then
it
will
help
me
help
the
new
product
manager
at
the
end
of
the
month
for
future
releases
to
to
kind
of
have
this
cycle
down
and
kind
of
be
able
to
walk
through
this
like
this.
So
that's
super.
A
B
A
B
C
B
C
C
B
C
B
C
B
So,
like
an
hour
of
time
to
figure
out,
have
we
talked
about
this
in
the
team?
What's
the
current
status?
Is
there
documentation,
that's
already
created
in
a
separate
issue?
That
is
really
what
I'm
looking
for
not
go.
Do
the
math
issue
in
1213
yep
sounds
good,
okay
cool.
We
gotta
jump
to
that
meeting.
Thank
you.