►
From YouTube: Miguel from Monitor APM explains the chart builder POC
Description
Please add comments and ideas at the merge request:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35727
Related issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/219641
A
A
A
The
spike
that
I'm
referring
to
is
going
to
be
exploiting
this
milestone.
We
don't
have
any
UX
for
it
yet,
and
we
only
have
a
very
basic
concept
so
today,
I
want
to
show
what
is
my
idea
to
build
it
and
what
are
the
things
we
should
do
in
order
to
create
it.
So,
first
of
all
small
refresher,
when
we
want
to
create
a
new
dashboard
panel,
we
want
to
do
it
through
a
camel
file
that
defines
a
few
data
or
or
features
that
we're
using
in
the
panel.
A
A
The
actual
panel
will
be
displayed
data
and
that
it
will
actually
look
like
a
real
panel
of
dashboard
and
then
some
Yaman
input
that
is
going
to
be
dependent
that
they
we
create
the
panel
or
the
chart,
in
this
case
I'm
using
a
JSON
format,
because
it's
easier
to
transform
in
the
front-end
but
in
moving
forward
and
as
we
build,
is
to
actually
do
a
original
input
here.
I
have
added
the
panel
information
I'm,
not
using
the
query
range
that
we
sent
primitive
spots.
A
A
We
used
to
preview
the
actual
output.
Let
me
see
so.
If
the
user
wants
to
change
the
input,
they
will
be
able
to
change
it.
Let's
see
here,
just
a
1
and
I'm
going
to
submit
it
again
and
then
they
will
immediately
see
the
real
panel
that
they
will
see
with
the
Witter
changes.
The
more
interesting
area
starts
when
we
can
change
the
type
and
for
the
same
data,
I'm
able
to
go
to
uncreate
ER
or
show
a
single
stats,
which
is
another
type
of
visualization.
A
Let's
wait
a
few
seconds
for
it
to
load
yep.
Here
we
have
the
actual
start
with
the
title
that
we
chose
and
the
ideas
that
users
will
be
able
to
constantly
update
or
editor
pergamo
input
advanced
and
then,
when
they
click
Submit,
they
will
be
able
to
see
an
uptick.
Of
course,
this
form
could
evolve
to
having
more
fields
to
make
it
a
little
bit
more
easier,
so
that
people
are
not
anything
that
Yemen
directly,
but
a
list
of
fields
that
they
want.
A
A
So
we
have.
We
have
things
like
services
that
allow
us
to
communicate
with
Prometheans
directly
here,
I
mark
a
few
things:
I'm
a
back-end
parsing.
The
demo
I
also
propose
that
we
then
use
just
this
single
page
component,
but
that
we
also
create
other
components
inside
so
that
as
they
get
more
complex,
we
can
keep
our
code
more
simple,
and
this
is.