►
From YouTube: GitLab 13.1 Kickoff - Monitor:APM
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I
want
this
is
the
kickoff
video
for
APM
13.1
and
before
we
get
going
and
go
over
the
deliverable
for
this
list.
I
want
to
make
sure
we
know
what
are
the
goals
and
the
first
goal
of
the
iteration
is
to
allow
the
use
of
Alison's
to
easily
navigate
form
into
the
metric
dashboard.
We
are
doing
that
in
order
to
allow
our
info
team
to
easily
move
between
or
navigate
between
diplomatic
chart
into
qivana.
We
know
walking
toward
replacing
qivana.
However,
we
know
that
won't
be
able
to
replace
them
at
the
moment.
A
By
allow
allowing
our
team
to
easily
transition
between
our
charts
and
dha'fana,
we
will
enable
them
to
start
using
our
metric
dashboard
in
each
and
every
flow
they
have.
The
second
must
the
second
goal
of
this
iteration
is
to
make
sure
the
data
we
present
is
accurate.
We've
seen
some
inconsistency
in
the
data
and
can
easily
be
concealed.
A
Let's
go
over
to
the
livable
list.
Issue
number
one,
some
some
work
that
is
left
from
the
previous
iteration
in
the
previous
iteration
13.0.
We
announced
the
availability
of
adding
annotation
to
ematic
dashboard
and
this
one.
This
issue
is
to
create
some
sort
of
a
job
that
will
delete
the
annotation
that
are
older
than
13
days
in
order
to
make
sure
not
to
the
database.
Our
database
won't
be
be
run
out
of
space,
and
the
second
issue
is
linking
from
one
dashboard
to
another.
A
I'm
gonna
go
ahead
and
open
the
issue
and
would
like
to
allow
users
to
click
on
any
any
chart,
and
from
that
chart
we
see
some
sort
of
a
menu.
Will
they
be
they'll,
be
able
to
navigate
to
different
places
and
different
links,
either
within
our
metrics
chart
or
external
links.
The
next
one
is
ad
auth
token
occasion
to
manual
instance
of
vomitus.
This
is
primarily
and
to
allow
the
our
permit
use
instance
of
tennis
instance.
That
is
it.
A
Has
that
it's
a
PIR
behind
of
token
authentication
to
be
able
to
connect
to
our
metallic
to
our
metric
dashboard
number
four
in
the
list
is
to
add
some
sort
of
a
validation
to
our
dashboard.
As
we
are
adding
more
and
more
features,
we
are
making
our
dashboard
ml
very
complex
and
we
make
the
life
of
our
users
a
bit
complicated
and,
in
this
issue,
will
be
able
to
present
our
user
with
some
sort
of
information
and,
as
we
conduct
a
validation
on
the
correctness
of
all
EML
files.
A
Issue
number
five
add
related
dashboard
link
and
we
have
one
issue
for
making
sure
we
have
an
ability
to
drill
from
a
metric
from
a
chart.
This
issue
is
allowing
our
users
to
create
related
links
on
a
specific
dashboard,
so
whenever
a
user
will
open
a
dashboard
they'll
be
able
to
configure
which
dashboard
which
link
they
would
like
to
navigate
form
within
that
dashboard.
A
This
is
the
last
part
of
our
variables
on
our
metric
dashboard
in
iteration
number
thirteen
we
delivered
the
variables
on
a
metric
dashboard,
so
user
can
configure
a
variable
which
is
constant
or
a
variable.
That
is
on
an
array,
and
this
issue
is
to
allow
some
sort
of
a
dynamic,
dynamic
variables.
So,
instead
of
putting
a
list
two
variables,
the
user
will
need
to
put
some
sort
of
a
pom
QL
and
that
punky
well
will
result
with
the
list
of
variables
or
list
of
of
values,
and
those
values
would
be
the
options
of
the
variables.
A
Number
eight
is
improve
the
tooltip
interaction.
Our
tooltip
interaction
is
not
that
smooth
and
it
results
that
it
is
covering
the
the
metric
chart.
So
it's
when
you
have
a
lot
of
information
and
you
hover
over
that
metric
chart
you'll
see
that
the
tooltip
is
disturbing
the
walk,
so
we
want
to
make
sure
it
will
be
smoother.
This
is
one
example
on
how
it
can
look.
A
Number
9
is
the
telemetry
for
the
no
stop
metric.
We
want
to
capture
the
number
of
users
that
are
viewing
our
login
number
10,
introducing
the
range
variables
right
now
today,
when
we
are
presenting
single
state,
single
stat
value
and
the
value
is
calculated
over
a
period
of
constant
time
so
right
now
it
is
calculated
over
seven
days.
A
So
it
doesn't
matter
if
you're,
viewing
single
state
single
stat
and
doesn't
matter
how
you
choose
your
your
time,
picker
and
you
will
always
see
the
same
value
so
by
introducing-
and
this
variable
here
will
be
able
to
calculate
the
single
style
single
start
over
a
period
of
time.
So,
for
instance,
if
you
want
to
calculate
your
uptime,
obviously
your
uptime
uptime
may
be
different
if
you
are
looking
on
a
period
of
a
month
or
a
period
of
a
year
or
a
period
of
a
week.
So
this
issue
come
to
us
of
this
demand.
A
A
Moving
our
URL
of
custom
metric
dashboard
issue,
number
12
and
basically
it
will
create
some
sort
of
vanity
URL
for
our
metric
dashboard.
So
it
would
be
easier
for
the
user
to
move
between
the
dashboard
dashboard
they
won't
be
able.
They
won't
need
only
to
use
the
drop
the
drop
down
if
they
know,
for
instance,
the
name
of
the
dashboard
can
simply
replace
it
by
the
name
here
and
they'll
be
able
to
to
move
between.
So
the
proposal
is
to
make
this
URL
look
something
more
digestible,
something
like
that.