►
From YouTube: Scalability - Talking about Stage Group Dashboards
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
So
I'm
just
trying
to
think
if
there's
a
really
simple
dashboard
here
like
what
the
most
trivial
one
is,
I
don't
think
so
I'll
use
nfs
because
it's
almost
trivial
so
like
for
the
nfs
dashboard.
Until
pretty
recently
it
looked
like
I'll
just
edit
it
so
that
it
looks
like
how
it
used
to
look.
It
used
to
look
like
that
right
and
it
basically
says
give
me
a
service
overview
dashboard
for
the
nfs
service,
and
this
is
kind
of
deprecated.
So
we
could
probably
do
that.
A
A
Let's
take
a
look
yeah,
I
mean
it's
really
rubbing
against
the
bottom
now,
but
so
you
know
this
is
all
generated
on
the
fly
and
then
there's
a
there's,
an
area
at
the
bottom,
where
you
can
just
you
know,
add
some
extra
bits
and
then
it
goes
in
and
that's
this
kind
of
nfs
specific
stuff
that
I've
put
in
since
then,
but
effectively.
The
first
dashboard
that
we
got
was.
B
That's
why
I
was
imagining
because
that's
what
I
was
imagining
because,
like
the
the
actual
group
names,
they
need
to
be
like
folders
in
here
or
files
in
here,
like,
depending
on
how
we're
stretching.
B
B
Idea
because,
like
that's
where
they
would
do
the
customizations,
but
then
the
mapping
of
feature
category
to
that'll
happen
inside
that
yeah.
A
C
B
B
Yeah,
I
would
rather
we
my
concern
with
giving
people
a
generate
dashboard.
Is
that,
like
yeah,
you
kind
of
get
a
bystander
effect
where,
like
everybody
assumes
that
somebody
else
is
going
to
be
using
that,
whereas,
if
we
like
yeah
focus
on
them
there,
we
go
yeah.
A
B
Whereas
if
we
give
it
to
specific
teams
like
there's
more
of
an
onus
on
them,
like
social
pressure
for
them
to
like
actually
like
work
with
us
here-
and
you
know
we
can
like,
I
said-
I
get
what
you
mean
about
getting
into
the
weeds
with
customizations,
but
I
think
the
way
andrew
sort
of
laid
it
out
like
there's
the
common
components
and
then
the
to
the
dashboard
and
then
there's
the
like
custom
components.
So
for
the
global
search
team.
B
They'd
have
like
elastic,
search,
timings
and
elastic
search
service
for
package
team.
They'd
have
the
registry
service
for.
A
B
Because
apartments
we
can
take
italy
and
distribution,
I
guess
and
memory.
Okay
for
most
teams,
yeah
there
are
controllers
and
there
are
sidekick
queues.
Monolith,
teams,
yeah
and
distribution
and
memory
wouldn't
really
have
these
dashboards
anyway.
I
guess
memory
might
use
the
course
image
scalar
stuff,
but
yeah.
D
If
we
generate
this
dashboard
without
the
customization
pieces,
that
is
at
the
bottom,
it's
just
the
standard
normal
piece
and
we
explain
to
people
how
to
use
this
and
we
publish
it
out
saying
this.
Is
there
and
we're
going
to
be
working
with,
for
example,
the
registry?
Sorry
the
the
package
team
about
this
and
we
go
through
and
we
customize
it
for
them,
and
then
we
select
pages
and
we
go
through
and
we
do
the
customization
for
them.
D
B
So
I
think
you
could
do
both
at
once.
If
you
want,
like
you,
know,
there's
nothing
stopping
say
like
you
know,
we
build
the
generic
dashboard,
but
then
we
need
to
like
map
that
to
map
the
future
categories,
to
teams
so,
like
bob
goes,
and
does
that
and
I
go
and
work
with
package
or
vice
versa
or
jacob
does
something
you
know
like
you
know
you
get
the
idea
like.
A
Those
there's
a
third
stream
of
work,
and
this
is
why
I
wanted
to
jump
in
the
call-
and
that
is
the
the
the
new
slis
where
the
teams
are
defining
their
slis
and
that's
works
going
to
be
happening.
Kind
of
in
parallel
to
all
of
this
and
we'll
have
the
first
of
those
sli's
coming
on
board
online.
While
you're
working
on
this
and
and.
A
A
V2
proposal,
so
that's
kind
of
all
taking
shape
at
the
moment
and
obviously
what
we
need
is
a
place
to
go
and
show
the
service
level
indicators
for
feature
category
x
and,
like
literally,
I
was
thinking
about
this
and
writing
some
stuff
up
in
a
proposal
while
when
I
saw
your
thread
come
on,
which
is
why
I
was
eagle-eyed.
You
know
well.
D
I
think
the
same
thing
would
apply
that
we
we've
got
the
base
of
what's
there
and
then
we
need
to
go
and
engage
with
the
stage
groups
to
put
in
the
customizations
and
to
put
in
the
new
sli
stuff,
but
like
there's
a
certain
amount
that
we
just
give
to
them
and
then
like
we
give
to
everyone,
and
then
we
have
to
go
and
do
specific
things
with
specific
people.
After
that.
A
B
B
Are
front-end
dashboards
because
there's
the
largest
content
for
paint
stuff,
so
yeah
we'll
use
influx
db
or
something.
D
B
C
B
C
Yes,
so
collect
a
set
of
feature
categories
that
apply
to
a
group,
and
then
we
should
only
have
to
write
one
line
of
chase
on
it
to
generate
the
dashboard
for
yes
and
then
below
that
everything
custom,
yeah.
B
B
Yeah,
I
don't
think
it's
too
hard.
I
just
you
know,
I
think
you'd
want
things
around
that
you
want
to
make.
You
want
to
make
sure
that
there
aren't
paths
that
are
like
orphaned,
like
you
know,
we've
renamed
a
stage
group
or
whatever,
but
they
still
have
like
dashboard
paths
at
some
old
place
like
or
you
know
stuff
like
that
and
also
well.
I
guess
we
don't
really
need
to
solve
this
now.
I
was
also
wondering
like
what
happens
when
we
move
a
feature
category
between
groups
to
say
all
of
a
sudden.
A
A
A
You
know
json
that's
either
in
the
in
the
repository
or
pulled
from
the
other
repository
you
know
so
that
we
can
generate
different
rows
depending
on
the
detail.
B
Yeah
and
one
more
thing
we
don't
need
to
solve
now,
but
we
need
to
keep
in
mind,
is
like
we
change
feature
category
names,
so
we
like
changed
the
kanban
boards
feature
category
which
would
just
be
called
boards
and
at
some
point
we
might
want
to
do
something
with
that.
But
again
for
now
like
I
think
we
can
say
we
don't
need
it
right
now,
but
for
that.
B
B
If
we're
pulling
in
the
file
from
the
repo,
it
won't
have
the
old
names,
but
again
we
don't
need
to
solve
that
now,
like,
let's
cross
that
bridge
when
we
come
to
it
yeah.
B
C
D
D
Second,
piece
generate
the
dashboards
for
everyone
using
the
one
line
online
magic,
publish
that,
along
with
some
kind
of
tutorial
or
documentation,
information
for
what
they're,
what
there
is,
and
then
we
pick
a
handful
of
probably
just
one
or
two
instead
of
a
whole
handful
of
stage
groups
to
do
to
work
with
them
to
do
the
customization
for
that
and
see
during
that
process.
If
there's
any
way
to
make
the
customization
easier
for
that,
for
others,.
A
I
think
yeah.
B
D
Cool
well,
if
that
all
sounds
good,
then
I'm
going
to
write
that
up
into
the
epic
and
publish
that
out
today
so
awesome.
This
has
been
super
helpful.
So
thank
you
for
all
being
willing
to
jump
on
a
call
really
quickly.
B
It's
all
right,
I
guess
none
of
us
had
any
meetings
today
anyway,
because
that's
how
it
works.
So
that's
a
good
day
to
grab
people.