►
From YouTube: 2022-12-21 - Dashboards working group
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
Did
anyone
watch
the
product
analytics
video
I
made
it
through
half
last
night
on
2X
and
then
I
had
something
else
come
up,
but
I
highly
recommend
it.
If
anybody,
if
you
haven't
yet
just
kind
of
see
how
that
team's
thinking
about
dashboards,
Tim's,
Allman
kind
of,
is
walking
through
building
out
one
in
real
time
and
it's
a
really
different
setup
that
I
was
picturing
in
my
mind,
because
they're
using
an
external
repo
and
code
and
yaml
to
structure
the
dashboards.
A
Okay,
I
went
through
just
and
added
an
MR
to
update
our
dates
and
make
them
official,
so
I
link
that
there
I
just
took
them
from
what
we
agreed
on
in
the
last
meeting
and
added
them
to
the
handbook.
A
They
also
have
a
lot
of
interesting
like
behind
the
scenes
stuff
that
I
think
a
lot
of
dashboarding
software
has
such
as
setting
up
data
sources
like
whether
it's
a
DB
or
an
API
concepts
of
graphs,
plugins,
queries,
time
series
and
then
I
didn't
get
enough
time
to
go
into
visualization.
But
that's
kind
of
what
they're
calling
the
content
in
the
panel
could
be.
A
visualization,
which
also
is
very
general,
could
apply
to
tables,
could
apply
to
a
graph,
could
be
anything
really
so
a
diagram,
even
so
that
was
kind
of
cool
house.
A
I
thought
in
my
mind,
because
grafana
tracks
such
complex,
complex
data,
like
your
what
you're
monitoring,
servers
and
there's
a
lot
of
like
Nuance
to
it,
I
thought
that
it
would
be
very
complicated.
But
they've
made
the
shell
of
what
it
is
quite
simple,
which
I
really
really
like.
A
A
A
I've
also
went
through
e-charts
just
the
example
that
was
linked
and
tried
to
see
if
there
was
more
to
it,
but
what
it
really
does.
Look
like
it's
a
it's
just
all
the
different
ways
you
could
do
a
visualization
or
a
chart,
and-
and
we
have
them
all
at
our
fingertips,
depending
on
how
we
structure
dashboards.
These
could
any
of
these
ways
of
showing
the
data
could
be
present
in
gitlab
because
of
this
Library.
B
B
I
thought
that's
what
you
said
in
terms
of
oh.
A
C
Yeah
the
way
I
see
e
shorts
is
it's
all
the
potential
different
ways
that
we
have
to
display
data.
It
still
needs
to
be
curated
and
wrapped
in
our
UI
Library
gitlab
UI,
but
it's
that
is
a
fairly
simple
and
straightforward
task,
and
we
know
what
we
have
here
in
each
Arts
we
can
use.
So
there
is
a
little
bit
of
work
to
it.
It's
not
like
the
caveat
is
not
as
simple
as
just
I
want
that
and
it's
immediately
there,
but
it
is
still
straightforward.
A
C
Chart
later
well,
that's
part
of
charge,
gay
charge,
heat
map,
single
stats,
sparkling,
charts,
column,
charts,
so
yeah,
but
it
it
would
be
good
still
to
I
guess,
have
an
idea
of
take
stock
of
what
we
can
like
what
we
currently
support
and
see.
If
there's
any
future
need
that
we
can
already
map
out
for
what
other
charts
we
would
like
to
import.
So
we
can
kind
of
get
those
into
the
pipeline
and
have
them
ready.
B
A
C
C
A
B
A
So
I
feel
like
because
there
was
a
question
of.
Could
we
also
kind
of
grafana
is
all
of
observability
right,
so
is
it?
Could
we
map
to
go?
They
have
a
thing
called
go
UI
they're
using
which
is
essentially
grafana,
I
feel
like
if
we
keep
our
definition
simple
enough,
no
matter
what
we
call
them
on
the
get
lab
side,
they
could
map
over
to
such
a
simple
system
on
the
grafana
side,
or
we
could
adopt
them
the
namings
from
it.
C
Yeah
I'd
probably
vote
for
just
adopting
them
since
we're
fairly
close,
already
yeah,
like,
for
example,
in
product
analytics.
We
only
have
one
difference
and
that's
between
widgets
and
panels,
but
I
know
that
panels
and
witches
is
Radio
contentious
word,
because
some
groups
are
already
using
panels.
So
if
grafana
is
doing
it,
it's
their
brain
better,
it.
B
C
No
so,
which
is,
are
the
panel
I
guess,
which
is
our
you
could
say
more
of
a
legacy
term.
C
It's
what
everything
used
to
be
called
on
a
dashboard
so
anyone's
not
familiar
with
like
WordPress
or
whatever
we'll
know,
but
yeah
I
mean
panel
also
makes
perfect
sense.
B
C
B
A
B
A
So
I
think
the
takeaway
from
the
exploration
of
grafana
would
be.
We
like
those
two
simple
terms
as
a
starting
point.
We
could
also
talk
about
the
word
visualization.
If
that
is
something
that
Rings
true
for
us
or
if
we
want
to
think
of
something
else,
such
as
content
or
something
that's
more.
Generic.
C
So
product
analytics
is
once
again
using
visualizations.
It's
actually
something
I
suggested
after
we
it.
We
went
through
a
series
of
words
each
one,
not
fitting
the
encapsulating
everything
that's
a
panel
or
widget
could
hold,
for
example,
because
the
charts
isn't
like
the
right
word,
because
it
could
be
a
table,
you
kind
of
call
it
yeah.
It
needs
to
encapsulate
that
it
could
be
a
single
stat.
It
could
just
be
a
number
it
could
be,
a
table
could
be
a
chart,
could
be
a
picture.
Visualization
seems
to
be
the
right.
A
C
A
A
Okay,
that's
cool
I,
love
hearing
that
there's
already
overlap
between
those
two
huge
massive
areas
of
progression
on
dashboards,
but
I
think
that's
going
to
make
things
a
lot
more
simple,
I!
Guess
it's
I
haven't
really
wrapped
my
head
around
all
those
other
dashboards
or
how
many
other
alternates
there
are,
though,
in
the
gitlab
world
that
may
have
a
different
term.
C
I
think
the
term
for
a
lot
of
the
other
dashboards
aren't
as
critical
necessarily
because,
for
example,
it
matters
more
in
the
design
phase.
Once
you
start
building
it
we're
just
using,
for
example,
table
or
static
components,
AKA
like
the
panels
that
were
placed,
but
for
something
like
a
customizable
dashboard
that
users
and
customers
need
to
interact
with
now.
The
naming
starts
becoming
quite
important,
because
you
need
to
explain
those
Concepts
to
a
user
in
a
way
that
they
can
understand
it
and
then
use
the
customizable
system
to
build
their
own
dashboards.
A
B
C
A
C
A
Yes,
okay,
so
I
think
that's
a
good
model
to
follow
and
we're
already
kind
of
like
that's.
What
we
want
to
do
is
just
get
a
list.
I
like
how
simple
theirs
is,
in
definition
and
I,
think
we
could
get
there
with
ours
fairly
quickly.
Maybe
we'll
see
where
we
end
up
the
last
one
was
sisins
is
being
used,
so
I
referenced,
just
the
link
to
it.
A
That
was
that
Justin
posted
it's
just
really
going
to
the
the
main
internal
sessence
UI,
so
nothing
new
there
really
I'm,
not
gonna,
say
it
out
loud
on
the
call
because,
like
this
is
going
to
YouTube,
but
I
did
put
a
little
note
there
of
I,
don't
know
if
that's
common
knowledge
or
not,
but
anyways
I
think
that
we'll
be
okay
to
not
analyze
that
participants
right
now
and
just
it's
got
a
lot
of
complexity.
A
But
unless
someone
feels
that
that
is
important
to
do,
we
could
also
look
at
what
they
call
things.
I
think
it
was
a
hard
system
to
use
internally
and
it
was
harder
to
build
queries
and
things
like
that.
So
I
I
don't
know
if
it's
a
if
it's
the
best
to
model
our
web
app
after
that's
just
my
opinion.
So
if
anyone
else
feels
strongly
about
it
for
sure
we
could
do
an
analysis
on
their
glossary
or
their
panels
or
how
they're
calling
things.
A
A
The
next
item-
I
added,
was
an
interesting
Discovery,
and
maybe
everyone
else
knew
this,
but
we
do
already
have
the
term
widgets
in
our
Docs.
It's
used
by
the
work
items
that
are
building
built
out.
There's
custom
fields
on
an
issue,
for
example
health
status
and
I-
think
they're
going
to
do
other
ones
down
the
line
like
maybe
there
could
be
a
widget
that
would
like
some
all
of
the
weights
in
an
epic
or
give
you
some
kind
of
output,
that's
different,
just
from
a
normal
column,
and
so
they've
decided
to
call
it
a
widget.
A
Okay,
what
do
we
think
is
the
best
way
to
formalize
Amelia's
work
into
a
definition
list
so
similar
to
just
and
sing
with
I
think
grafana.
Everything
like
should
I
just
start
an
issue
where
we
kind
of
start
just
writing
into
the
description
with
headers
like
areas
that
we've
already
like
learned
or
defined,
or
counted.
A
Or
should
we
start
in
a
Google
doc,
where
we've
just
got
fluidity
of
defining
like
if
she
found
so
many
different
uses
of
this
of
different
terms?
Around
regions
I
feel
we
have
to
bring
it
over
into
text
at
some
point,
so
we
can
start
like
choosing
definitions
or
putting
or
start
working
on
what
we
call
them.
C
Depending
on
the
amount
of
data,
if
it's
a
lot,
I
would
go
with
what
Dana
suggested
in
a
previous
call,
which
is
using,
maybe
Google
Sheets
easy
to
collaborate
with
and
makes
it
easy
to
work
with
a
lot
of
data.
But.
B
A
A
You
know
I,
we
could
have
multiple
tabs
yeah,
like
you
mentioned,
so
we
could
have
different
ways
of
looking
at
these
things.
A
I
think
our
next
deadline
is
January,
10th,
that's
to
get
out
of
investigation
into
definition,
and
so
I
guess
for
to
be
able
to
do
definition.
I
think
we
should
probably
just
have
all
the
instances
transferred
into
the
sheet
so
I'm
thinking
for
me.
I'll-
probably
work
on
it
when
I
get
back
so
like
January,
4th,
5th
6th
ish
and
just
try
to
get
a
bunch
of
terms
in
there
grouped
up
in
some
way
and
not
do
it
now
like
not
over
the
holidays,
I'm
off
from
tomorrow
until
June
3rd.
A
Well,
I'm,
looking
at
your
thing,
yeah,
that's
the
wrong
date.
B
B
Group
is
over
thank.
A
B
A
B
A
B
Okay,
I
added
a
note
that
you've
you're
making
this
change.
B
A
C
Formatting,
the
regions,
no
I
I,
think
everything
is
captured
in
terms
of
going
further
into
like
the
smaller
details
and
some
of
the
nomenclature
like
do
we
use
grafana
and
stuff
I
think
that
will
that
will
come
out
in
the
sheets
also.
B
B
A
C
Figuring
out
like
what
to
call
it
internally,
but
if
there's
any
like
question
marks,
like
I
said,
hopefully
the
sheet
will
will
come
together
and
pick
a
group
name
and
put
it
on
the
sheet.