►
From YouTube: 2022 -12-06 - 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).
B
A
Okay,
so
we
got
enough
information
from
surveying.
One
thread
that
I
started
here
in
terms
of
asking
sales
for
feedback.
I
started
an
issue
that
basically
is
asking
them.
How
do
you
sell
this
thing?
What
are
you
calling
it
when
you
talk
to
customers
and
I
included
the
list
we
found
in
the
other
issue?
A
I
was
just
talking
to
one
of
the
Tams
who
said:
I
should
also
post
that
I'm
just
pasting
in
what
he
said.
He
basically
said
posted
also
a
customer
success
which
I'll
do
so
they
can.
We
can
look
at
our
Tams
who
talk
with
our
current
customers,
as
well
as
sales
who
are
going
after
actual
customer
new
customers.
A
That's
one
way
we
can
use
this
and
see
how
it
sort
of
relates
to
selling.
A
C
Yeah
I
wasn't
sure
if
this
was
kind
of
outside
of
the
scope
of
where
your
head
was
at
with
this.
But
you
know,
since
we
have
a
list
of
various
dashboards
across
the
product.
C
I
know
that,
like
Becca
had
shared
in
our
slack
channel
that
you
know,
dashboards
are
kind
of
hard
to
find
and
are
all
over
the
product
in
terms
of
navigation.
So
I
wasn't
sure
if
we
wanted
to
capture
some
like
analytic
data
on
you
know
how
they're
being
used,
I,
I,
guess
like
how
often
they're
being
accessed
and
and
found,
and
things
like
that,
but
I'm.
It's
just
a
suggestion.
I
wasn't
sure
if
that
was
kind
of
outside.
A
A
A
So
I
don't
know
if
they're
doing
like
a
macro
level
look,
but
this
that
would
be
really
cool
to
do
if
we
could
give
them
the
list,
maybe
in
the
future,
even
as
an
output
from
this
it's
like
here's,
a
list
of
all
of
the
dashboards.
You
should
probably
be
tracking
these
in
some
way
or
something
like
that.
A
A
Oh
and
I
did
skip
the
second
bullet.
I
have
an
idea
for
getting
it
earlier
in
the
day,
but
that
would
involve
a
few
people
working
earlier
in
their
time
zone,
so
I'm
gonna,
reach
out
to
them
individually
and
I,
don't
want
to
pressure
anyone
to
work
outside
of
their
time
zone.
So
if
no
one
is
100,
yes,
I
want
to
start
it
7
A.M,
or
something
like
that.
A
I'll
just
split
it
into
two
on
every
every
week,
there'll
be
like
an
early
and
a
later,
the
later
one
will
probably
be
right
around
now
that
sort
of
hits
USA
and
then
the
earlier
one
will
grab
Europe
so
I
just
wanted.
I
did
create
a
spreadsheet
to
try
to
like
align
everyone's
time
zones
and
I'm,
not
quite
at
the
end
of
it.
So
I
just
wanted
to
mention
that.
A
So
what
dashboards
are
configurable
should
they
be
configurable
as
a
general
rule?
When
is
this
explicitly
not
the
case,
and
why
so
he's
got
a
lot?
We
could
just
quickly
probably
go
through
and
talk
through
some
of
these
questions
from
the
team's
point
of
view
and
then
I
guess
make
the
decision.
Do
we
want
to
put
configurable
into
our
exit
criteria
or
do
we
want
to
have
that
be
like
another
action
or
verb
for
kind
of
managing
about
all
dashboards?
B
Yeah,
well,
it
might
help
is,
if
you
can,
because
you
already
have
the
list
of
like
29
different
dashboards
right.
So
if
you
can
go
through
and
kind
of
describe,
if
anyone
can
go
through
it
but
like
if
someone
can
go
through
it
and
say
hey,
these
are
like
viewable
or
maybe
not
editable,
but
you
can
like
add
filters
or
like
change
the
query
in
some
way
versus
I.
Think,
generally
speaking,
and
maybe
on
you
can
correct
me
if
I'm
wrong,
but
like
we
don't
really
have
a
strong
concept
of
configurable
dashboards.
B
Yet
that's
something
that
we're
exploring
with
Cloud
analytics.
That's
something
that
optimizes
looking
at,
but
as
far
as
an
established
pattern.
Well,
it
wouldn't
be
it's
not
established
unless
it's
in
pajamas
right,
so
I,
don't
think
we
have
one
but
we're
like
kind
of
dancing
around
that
right
now.
So
my
not
to
my
knowledge,
I
think
most
dashboards,
we're
going
to
see
in
this
list
are
going
to
be
just
like
you
can
filter
data
down,
but
it's
not
like
actually
savable
or
that
I
guess
that's
part
of
what
we
would
want
to
Define.
E
Dashboard
that
was
configurable
it's
now
defecated
I
can
share
it
really
quick.
Just
so
y'all
can
see
it.
It
doesn't
work
right
now
because
it's
been
deprecated
but
the
metrics
dashboard
used
to
be
you
could
like
create
and
edit
directly
from
the
dashboard
and
yeah.
None
of
this
works
anymore
because
it's
being
removed
and
replaced
replaced,
but
that
did
exist
until.
F
E
But
only
on
this
page,
I
think
and
yeah
I
think
you
could
even
create
custom,
so
you
could
duplicate
and
then
create
custom
ones,
I
think
as
well
in
the
ey
here,
but
yeah
I,
don't
know
how
much
we
want
to
continue
using
those
patterns
or
not
and
and
I.
Don't
know
that
this
dashboard
was
on
that
list,
because
it's
it
doesn't
really
function
anymore,
but
I
can
add
it
to
the
list.
A
Sure
yeah,
if
you
could
link
it
in
the
agenda
too,
on
the
point
I'd
be
curious,
just
to
go.
Look
at
it
and
poke
around
I.
Didn't
know
that
so
most
of
our
dashboards
are
not
Marshalls.
Coming
from
the
standpoint
with
observability,
where
we've
got
a
lot
of
grafana
charts
coming
in
and
configurable
dashboards,
so
he's
trying
to
make
sure
that
we
think
about
this
from
a
high
level,
where
we're
sort
of
merging
Two
Worlds,
together
with
the
acquisition
and
keeping
configurability
in
mind.
B
Again,
I
can
I
can
document
this
as
well,
but
product
analytics
is
approaching
configurability
as
a
way
to
allow
users
to
be
able
to
focus
in
on
specific
behaviors,
whether
it's
characteristics
of
Their
audience
or
people
visiting
their
applications
versus
what
they're
doing
and
being
able
to
like
focus
on
specific
events
that
they're
tracking.
D
B
A
Foreign
is
almost
I,
don't
know,
but
it
could
be
setting
up
the
whole
thing
or
panels
and
filtering,
maybe
a
like
a
micro
on
each
individual
panel
or
part.
But.
A
G
I
can
say,
I
think
someone's
comment
about
this.
Being
a
facet
of
the
pages
is
relevant
to
us
and
maybe
part
of
the
definition
is
it
can
be
up
to
the
design,
team
or
group
team
when
something
is
configurable
versus
static
and
then
what
level
is
that?
Because
the
filtering
that's
just
kind
of
configuration,
but
it's
not
right.
Is
that
a
sticky
configuration?
Is
it
something
saved,
or
is
it
just
at
the
time
of
using
the
page?
So
it
might
just
be
depth
of
the
description
of
what
we
mean
by
that.
E
It
feels
like
most
dashboarding
products
do
offer,
configuration
and
and
editing
so
like
it
seems
like
we
probably
yeah
whether
we
want
to
offer
that
on
every
page,
I
guess
I,
don't
I,
don't
know
it's
to
Justin's
point,
but
it
does
seem
like
something
that
we
should.
If
we
want
to
have
dashboards,
that
kind
of
compete
in
the
marketplace
or
whatever
or
like.
F
G
G
Think
that
fits
into
what
we
Define
as
a
dashboard
versus
a
page
or
start
page
or
something
like
that
like
I,
know
vulnerability
reports
they're
about
to
they're
working
on
a
feature
to
allow
that
report
to
have
multiple
saved
views.
It's
the
same
report,
but
you
filtered
it
and
then
you've
saved.
That
view
is
that
a
dashboard
I
don't
know.
B
Yeah,
if
you
don't
mind,
I
can
kind
of
share
what
we've
been
working
on
in
product
analytics,
Kristen
you're
also
talking
about-
and
this
is
something
we're
trying
to
figure
out-
is
like.
We
have
dashboard
level
controls
like
being
able
to
filter
and
like
change
the
date
range
and
that
controls
all
the
data
visually
below
it.
But
then
we
are
offering
customizability
within
what
we're
calling
widgets
currently,
but
we
can
obviously
like
talk
and
change
that,
but
each
individual,
it's
probably
going
to
be
better
if
I
just
show
it.
B
Let's
start
with
that,
so
everyone
can
see
my
screen,
and
so
this
is
just
let
me
zoom
out
of
the
way,
because
it
looks
just
be
the
star.
This
is
just
Tim
in
our
group
meeting
just
talking
about
like
the
configurability
of
it.
So
we
have
like
an
edit
mode
which
again,
like
the
ZX
interactions,
are
just
very
raw
I'm,
just
trying
to
get
like
the
functional
proof
of
Concepts
out
there.
B
But
you
know
what
we're
calling
these
are
all
widgets
so,
like
this
table,
there's
another
table
above
there
and
there's
a
line
chart.
All
of
these
are
called
widgets
and
so
part
of
like
what
we're
trying
to
figure
out
is
okay.
We
have
this
configurability
at
the
dashboard
level
of
constraining
how
much
data
or
the
time
range.
B
Theoretically,
the
user
may
want
to
do
something
if
this
is
like
a
report
or
a
dashboard
to
like
constrain
it
further
in,
like
at
the
widget
level
like
I,
want
this
graph,
specifically
to
like
only
show
specific
segment
of
data
from
what
the
dashboard
is
already
limited
to
so
like
I,
don't
know
if
that's
something
we'd
have
to
like,
but
no
sorry.
That
is
definitely
something
we'll
have
to
like
document
in
terms
of
that's
something.
B
We
want
users
to
be
able
to
do
or
not
right
now,
we're
just
exploring
the
capability
of
that,
but
yeah
it's
it
can
get
really
messy
very
quickly,
but
yeah
I
think
we
definitely
want
a
way
to
like
I.
Definitely
we
want
to
have
standards.
If
dashboards
should
all
dashboards
be
configurable,
probably
not,
but
if
they
do,
we
should
have
some
like
kind
of
guiding
principles
of
what
they
should
do
and
how
the
interaction
should
work
and
and
fold
that
back
into
pajamas.
A
It
sounds
like
a
theme
too,
of
maybe
the
designer
is
configuring,
the
dashboard
with
the
right
things
and
then
whether
we
open
that
up
to
the
user
to
further
refine
it
or
make
it
slightly
different.
But
there
may
be
states
where,
like
the
designers
at
gitlab,
configure
dashboards
that
are
uneditable
and
they
have
that
they
just
sit
there.
B
B
For
sure,
like
we
have
a
cons,
or
there
is
a
a
functional
concept
of
locking
these
these
widgets,
so
that
you
can't
like
some
of
these.
You
can't
change
so
like
it's
ultimately
up
to
the
groups
to
like
determine
what
they
intend
the
user
to
be
able
to
customize
and
not.
B
A
So,
in
the
interest
of
time,
I
wanted
to
just
quickly
get
through
this
part.
Before
we
get
into
the
meat
of
milestoning
and
I
know,
we've
only
got
about
seven
minutes
left,
it
sounds
to
me
like
we
may
all
decide.
Yes,
we
can
add
configuration,
but
I
wanted
to
make
sure
that
Justin,
you
could
say
your
point
as
well.
We've
got
one
here
also
for
me:
Han.
G
I
know
observability
is
going
to
be,
allowing
that
you'll
be
able
to
add
data
sets
to
be
able
to
create
multiple
dashboards
off
of
it,
select
which
dashboard
you
want
manipulate
the
arrangement
of
the
dashboard,
you're,
all
grafana
type,
stuff
and
they're
planning
on
making
that
a
tool
that
can
be
used
by
anyone,
not
just
observability
right,
so
it'll,
create
this
framework
or
whatever.
That
should
be
usable
by
any
other
group.
A
F
Yeah
I
can
quickly
verbalize
that,
so
the
question
is
how's
the
configuration
going
to
be
stored.
Is
it
going
to
be
in
a
git
repository
as
far
as
project
analytics
is
concerned?
Yes,
because
we're
we
would
like
to
make
use
of
the
whole
Mr
flow
to,
because
that
gives
the
whole
access
to
like
roles
and
authentication
authorization
on
like
who
can
edit
stuff.
F
F
So
what
we
plan
to
make
use
of
is
the
dot
gitlab
directory
I
believe
it's
already
being
used
by
another
feature,
but
Dennis.
Please
follow
in
my
blank
memory
there,
for
which
feature
that
is,
if
dashboards
or
no
for
in
general,
the
dot
gitlab
directory.
F
Yeah
great
thanks
so
yeah,
it's
it's
an
existing
directory
there
for
gitlab
configurations
inside
your
repo.
So
we
would
like
to
leverage
that
for
dashboards.
F
Another
thing
I
quickly
want
to
mention
it's.
It's
not
really
a
dashboard,
but
I.
Guess
like
the
Epic
board,
is
like
an
example
of
something
that's
configurable
and
stored
and
that's
yeah
and
that's
also
customizable.
B
A
Configurability
can
just
be
the
definition
also
of,
however,
we
serve
in
gives
us
the
yaml
grouped
underneath
sections
on
the
dashboard.
So
that's
one
high
level.
This
is
what
we're
kind
of
getting
to
is.
This
is
like
one
way
to
configure
a
dashboard
or
list
all
of
its
content
in
the
back
end,
yeah.
B
That's
that's:
how
product
analytics
and
Optimizer
approaching
it
currently
I,
don't
know
how
epics
are
currently
functioning,
but
we
want
to
be
able
to
just
have
everything
exposed
that
if
we
don't
offer
the
like
the
UI
to
be
able
to
customize
It,
ultimately,
customers
can
go
in
and
change
it
themselves
and
it's
broken
down
into
the
level.
However,
we
Define
the
nomenclature
and
the
the
hierarchy
of
of
that.
That
will
be
how
they
can
access
it
as
well.
C
B
Yeah
because,
ultimately,
you
know
we're,
there
will
definitely
be
kind
of
like
a
engineering
principles
in
terms
of
how
we
want
to
approach
dashboards
as
well,
to
make
sure
we're
consistent
across
the
code
base
and
that's
just
to
kind
of
like
give
you
a
preview
of
what
we're
looking
at
Beyond
The
Dot
gitlab
folders
like
we're
looking
at
because
right
now
that
only
works
in
the
project
repository
that
you're
currently
working
in
and
that
works.
B
But
that
also
involves
like
kind
of
messing
with
the
gate,
history
of
your
of
like
customers,
given
project
which
can
be
seen
as
not
undesirable,
and
we
have
previous
patterns,
security
pipelines,
compliance
pipelines,
group
level,
project
templates,
where
you
actually
designate
a
subgroup
or
a
project
that
contains
the
same
files
that
ultimately
it
boils
down
to
a
repository.
But
it's
dedicated
to
that
purpose.
And
so
that's
something.
We're
exploring,
because
optimize
is
working
on
building
executive
dashboards
at
the
group
level
which
we're
not
currently
focused
on.
B
But
ultimately,
that's
where
we
would
like
to
go
towards
and
that's
going
to
be
kind
of
like
a
overall
guiding
principle
of
like
here's,
where
you
need
to
store
configuration
data
so
anytime.
Anyone
has
a
configurable
dashboard
like
if
we've
got
29
different
dashboards
here,
then,
theoretically,
there's
29
different
folders.
You
can
add
to
your
dashboard
repository
to
configure
assuming
they're
all
configurable.
D
B
B
Happy
to
change
it
because
we
again
this
is
all
Alpha.
This
is
all
subject
to
change
on
our
end,
so
we're
happy
to
to
update,
as
as
the
working
group
sees
fit.
A
Okay,
that
makes
sense
from
my
standpoint,
but
I,
don't
know
what
we'll
end
up
with
or
how
like
a
filter
or
things
like
that
fit
into
that
world
too,
when
you
have
just
such
a
simple
model
like
filters
could
be
at
the
top
or
the
bottom,
and
let's
not
really
represented
in
that
it's
obviously
fairly
simple.
To
start.
A
Okay,
let's
hop
down,
do
we
have
a
consensus,
though,
just
from
this
discussion
that
we
will
move
forward
with
configurability
from
Marshall's
original
question.
E
Just
as
I
know,
I
added
to
a
couple
docs
links
up
above
to
the
old
custom
dashboards.
E
E
Historical
recommend
or
references
as
well.
A
A
Does
anyone
have
any
ideas
of
what
those
should
be
to
get
us
to
the
end,
and
these
could
be
phases
like
right
now
we're
in
Discovery
like
we
just
did
the
issue
Discovery
and
coding
for
four
weeks
or
writing
the
spec
or
doing
prototyping
and
mural
and
kind
of
coding,
those
to
specific
Milestones
or
times
in
this
12
weeks.
B
B
B
So
I
think
that
that
seems
like
the
logical
next
step
in
my
opinion,
but
happy
to
hear
others.
Thoughts.
E
Do
we
need
to
map
out
map
out
like
the
pieces
so
like
if
we
look
at
a
dashboard,
so
we
have
filters,
we
have.
You
know
visualizations
whatever,
just
like
rough,
like
box
out
what
is
on
a
dashboard
and
so
then
we
know
like
exactly
what
we
need
to
Define
because
I
don't
know.
Maybe
that's
been
done.
This
is
my.
A
Done
that
has
not
been
done
yet.
I
would
love
to
see
that
visually
and
like
groupings
of
things
like
verbs,
like
edit
configure
like
just
in
some
visual
way
and
each
item
that
we
see
maybe
mapping
the
pieces,
would
come
after.
The
investigation
like
next
and
sort
of
in
combo
with
defining
but
I
wasn't
referencing
that
whole
list.
A
E
I
think
if
we
had
a
map
like
if
we
have
like
say
a
box
that
said
filters,
this
is
like
we
have
filters
on
all
of
our
dashboards.
E
Then
we
know
that
we
need
to
Define
what
filters
are
and
what
they
can
do
and
I
mean
I
feel
like
some
of
it's
like
semi-obvious,
but
it
just
spelling
it
out
in
that
way
at
least
will
give
us
like
blocks
of
content,
that
we
know
that
we
need
to
provide
definitions
for
or
and
then
designs
for
as
it
as
we
get
to
that
point.
C
So
kind
of
like
it
has
this
check
versus
it
doesn't
have
this
x
sort
of
thing.
E
I
think
I'm
thinking
about
it
more
in
like
in
terms
of
like
regions
of
of
the
dashboard
So
like
just
very
high
level,
not
in
terms
of
like
what
component
we're
using
to
build
it
necessarily
yet
more.
Just
like
there
there
will
be
a
visualization,
we're
not
defining
what
kinds
of
visualizations,
or
maybe
we
are
I,
don't
know,
but
just
like
blocks
of
content
so
that
we
have
so
we
can
just
pin
down
what
we
need
to
Define
here,
and
maybe
we
maybe
we
all
know
what
we
need
to
Define.
B
A
B
A
A
B
Can
we
can
provide
like
a
frame
of
reference
like
from
our
version
of
like
what
we're,
what
we're
planning
to
do
and
what
what
we
think
the
building
blocks
are
and-
and
we
can
potentially
use
that
as
an
exercise,
to
compare
against
the
other
dashboards
to
see
if
we're
missing
anything
like
that,
that
seems
reasonable.
D
D
I'm
happy
to
help
with
with
that,
we.