►
From YouTube: GitLab 13.0 Kickoff - Overview
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
My
name
is
Scott
Williamson
I'm,
the
EVP
of
product
management
at
gitlab.
I
want
to
welcome
you
to
the
13th
at
O.
Kickoff
call
this
one
is
particularly
exciting
because
it's
a
major
release,
13,
oh,
and
we
expect
it
to
be
super
important
and
have
an
extra
large
impact
team.
So
to
orient
you
here,
I'm
going
to
share
my
screen
for
a
second.
We
have
a
page
on
our
handbook.
A
The
URL
is
about
that
gate,
lab
comm,
slash
direction,
slash
kickoff,
so
we'll
be
presenting
from
here
the
it's
organized
in
what
we
call
sections
there
are
four
of
them
and
within
that
we
have
kickoff
videos
for
the
groups
that
roll
up
two
sections.
So
each
group
record
the
video
once
a
month
telling
their
story
about
where
they're
headed-
and
we
have
four
leaders
here
for
each
of
these
sections
who
are
gonna,
provide
some
highlights,
but
there's
a
whole
lot
more
in
here.
A
So
if
you
could
check
out
the
videos,
if
you're
interested
that'd
be
great,
you
can
also
weigh
in
on
the
specific
issues
linked
here
and
provide
your
feedback.
We
would
love
for
your
involvement
input
as
we
go
here
so
with
that
I'm
gonna
turn
it
over
to
David
DeSanto
who's
gonna
cover
secure,
defend.
First,
then,
we'll
move
to
Josh
Lambert
for
enablement,
Erik
brakeman
for
dev
and
Kenny
for
ops
over
to
you,
David
thanks.
B
So
the
first
item
to
highlight
for
you
from
static
analysis,
is
removing
secret
detection
to
its
own
template.
That
way,
you
can
begin
to
see
expanse
of
what
you
can
support
with
secret
detection.
The
other
item,
which
I
think
is
a
very
exciting
one,
is
providing
SAS
support
for
the.net
framework.
We've
talked
in
previous
release.
Kickoff
calls
about
the
support
for
dotnet
core,
but
if
you
are
using
the
dotnet
framework
with
a
Windows
runner
you're
building
your
software
there,
you
can
now
run
SAS
against
that
dotnet
framework
and
identify
vulnerabilities
within
your
codebase.
B
Switching
to
dynamic
analysis.
There's
a
couple
of
exciting
items
that
they're
working
on
there
as
well.
The
first
is
going
to
be
a
carryover
from
1210
to
13.0,
but
this
allows
us
to
show
evidence
for
the
vulnerability
within
the
security
report.
There's
a
code
snippet
here
of
the
output
from
the
report.
You
can
see
that
it's
providing
the
detail,
so
you
understand
truly.
Why
that's
a
vulnerability
and
from
there
you
can
begin
to
remediate
and
improve
the
code
quality.
B
The
next
item
is
extending
the
pipeline
report
to
include
the
URLs
that
were
scanned,
so
you
can
understand
the
resources
and
get
back
up
the
top
here
to
kind
of
show
you
what
that
looks
like
right
off
the
top
of
the
security
report.
You're
going
to
be
able
to
see
the
items
that
were
found,
this
source
code
looks
like
it's
really
bad.
By
the
way
it's
got.
2,000
vulnerabilities,
that's
just
side!
No!
B
That's
just
a
mock
up,
but
here
you
can
see
the
the
count
of
the
URLs
that
were
scanned
and
then
be
able
to
drill
into
the
resources
and
then
finally,
we
wanted
to
highlight
one
thing:
that's
deprecating
at
13.0,
though
the
use
of
only
accepts
as
part
of
your
sassed
and
recive
secure
support
and
your
templates
is
being
deprecated
in
favor
of
roles.
So
if
you
are
using
Auto
DevOps
today
or
some,
the
security
templates
you'll
see
that
change
in
13.0.
B
We
highly
recommend
that
you
go
back
through
your
configurations
if
you've
done
custom
ones
and
identify
where
you
need
to
make
that
switch
over
to
roles
from
the
only
except
current
structure.
That's
there
today
to
defend.
We've
spent
the
last
several
kickoff
calls
talking
about
our
standalone
vulnerabilities,
rollout
and
that's
coming
out
in
12:10.
So
that's
a
very
exciting
milestone.
The
defending
you
should
be
very
proud
of
all
the
hard
work
they've
pinned
in
over
the
last
several
months.
B
Everybody's
gonna
definitely
benefit
from
that
with
that
rollout
of
standalone
vulnerabilities
in
12.10
we're
offering
export
from
the
project
level
dashboard.
So
you
can
consume
the
data
on
the
dashboard.
In
another
application
to
help
your
prioritization
or
your
compliance
requirements
and
with
13.0
we're
adding
it
at
the
instance
level
as
well
so
off
the
instance
level,
dashboard
you'll
also
be
able
to
export
to
show
you
what
that
kind
of
looks
like
that
would
be
in
the
CSV
in
the
project
level,
you
have
the
first
handful
there.
B
Those
will
be
the
same,
however,
at
that
table,
you'll
also
get
to
see
the
group
and
the
project
that
that
vulnerability
is
from.
So
this
is
a
really
nice
big
step
towards
our
goal
of
providing
history
and
historical
trends
and
all
the
other
information
that
will
be
enabled
by
our
new
standalone
vulnerabilities
and
being
able
to
make
vulnerabilities
a
first-class
object.
In
your
experience,
here's
a
screenshot
of
the
dashboard
you
can
see
up
at
the
top
next
to
the
Edit
dashboard
button.
B
There
is
an
export
button
and
that'll
give
you
the
CSV
for
that
dashboard
on
the
container
security
side,
we're
focusing
on
a
couple
of
items
in
13.0.
The
first
is
allowing
you
to
easily
turn
your
network
policies
on
and
off.
You'll
see
this
within
the
left,
navigation
under
security
and
compliance.
There
is
a
section
called
configuration
and
we've
added
monitoring
and
response
below
the
testing
configuration,
so
here
at
the
top,
as
your
secure
configuration
down
here
is
your
defend
configuration
I'm
following
our
goals
of
being
iterative.
B
The
first
rollout
of
this
takes
you
directly
over
to
the
documentation
to
show
you
how
to
easily
enable
and
disable
the
network
policies
in
future.
Iterations
that'll
become
a
button
that
actually
allows
you
to
fully
anyone
disabled
with
just
a
click.
The
last
item
I
want
to
highlight
for
you
before
handing
it
over
to
Josh
for
enablement,
is
this
is
not
a
a
public-facing
deliverable
but
we're
doing
our
prototyping
for
the
first
release
of
container
behavioral
analytics
we're
very
excited
about
this,
so
we're
prototyping
with
an
open-source
tool
called
Wazza.
B
This
is
going
to
allow
us
to
provide,
within
your
container
file
integrity
monitoring
application,
allow
listing
blocking
of
exploits
targeting
known
vulnerabilities
and
helping
us
identify
overhead
on
your
applications
and
where
we
can
optimize.
So
this
is
a
great
step
forward
towards
that
goal
of
releasing
this
later
in
the
year
is
a
minimal
release
and
setting
is
up
for
success
to
quickly
get
to
viable.
B
C
Cotton
thanks
David
so
similar
to
what
David
mentioned.
We
have
a
lot
going
on
this
release
and
will
only
cover
it's
the
highlights
here.
So
please
do
check
out
the
videos
that
said
much
of
the
work
here
as
a
result
of
a
lot
of
effort
over
this
series
of
last
few
releases
to
help
prepare
us
for
a
lot
of
the
big
changes.
C
They
should
take
some
manual
actions
which
are
documented
to
upgrade
as
well
so
with
the
new
version
of
post
press
they're
about
13
users
will
have
to
be
running
at
least
posters
11
prior
to
upgrading
to
the
throw
to
the
window
release
because
we'll
also
be
going
through
and
removing
mind
at
6
and
10.
These
changes
will
allow
us
to
take
advantage
of
a
number
of
features
like
partitioning
that
can
allow
us
to
further
scale
and
improve
the
performance
of
gitlab.
C
Also
simply
the
new
engine
of
Postgres
itself.
Impressions
11
has
shown
about
8%
performance
improvement
across
the
board
as
well.
So
a
number
of
exciting
improvements
here
and
a
lot
of
us
were
the
reason
when
we're
shifting
over
to
this
release
now
similar
another
big
change.
Our
making
here
that
has
been
in
the
works
for
a
while
is
we
are
switching
application
server
from
unicorn
to
Puma.
C
Kuma
is
a
multi-threaded
application
server
and
it
offers
an
hour
testing
about
a
40%
memory
reduction
compared
to
unicorn,
you
recommended
settings,
and
so
we
will
be
making
improve
the
default
in
30
Neto.
They
do
have
different
settings,
and
so
you
should
be
aware
that
there
are
some
manual
migration
if
you
have
customized
the
settings
for
unicorn
to
move
them
over
to
Puma.
C
If
you,
for
some
reason,
do
not
want
to
move
to
Puma
and
Veneto,
you
can
still
reenable
unicorn
as
well
and
just
be
mindful
that
Unicorn
is
deprecated
and
we're
removing
it
in
a
future
release
year,
continuing
any
performance
and
availability
theme.
We
also
want
to
start
testing
some
coming
cat
lab
user
journeys
and
capturing
their
performance.
C
So,
for
example,
we
do
a
lot
of
you
have
score
cards
and
we
actually
have
a
lot
of
number
of
workflows
here
in
get
lab
that
people
perform
pretty
routinely
and
we'd
like
to
take
a
chance
to
actually
use
synthetic
testing
to
walk
through
those
workflows
and
capture
the
step
by
step
performance
among
them.
For
example,
how
does
it
take
to
open
your
to
Do's
click?
C
On
the
first
issue
comment-
and
perhaps
at
mentioned
someone-
this
can
serve
as
a
good
baseline
and
also
is
pretty
tangible
performance
for
product
managers
to
aid
them
in
prioritizing
and
understanding
the
impact
of
these
performance
improvements
across
these
common
user
journeys.
So
we're
excited
for
this
as
a
couple
other
benefits
as
well
here,
but
we're
kind
of
shifting
the
memory
team
away
from
the
memory
improvements
of
Puma
and
on
to
more
performance
improvements
here,
more
broadly
with
this
release.
C
C
Tracing
has
been
available
in
get
lab
as
an
experimental
feature
for
about
a
year
and
be
great
to
take
and
remove
the
experimental
label
and
again
make
it
available
for
everyone
not
just
get
leather
comm,
but
also
our
self-made
miss
users
as
well
to
help
inspect
and
troubleshoot.
What's
going
on
there
instances
on
the
availability
slide,
we've
been
making
progress
on
a
self-service
replication
framework.
C
Similarly,
we're
also
working
on
improving
the
support
for
plan
fail
overs.
So
when
a
user
currently
goes
through
and
influenced
a
plan
filler,
it
has
a
number
of
steps
and
there
also
isn't
an
easy
way
to,
in
some
cases,
pause
activity
in
the
primary
while
you're
waiting
for
the
secondary
to
catch
up
to
ensure
you
don't
have
any
few
minutes
of
potential
data
loss
there
and
so
we're
implementing
a
read-only
mode
as
well.
C
We've
heard
some
some
larger
customers
that
they
oftentimes
like
to
take
a
backup
of
get
lab,
validate
the
backup
before
going
on
and
upgrading
the
instance,
and
sometimes
they
take
down
their
instance,
for
example,
during
this
process,
or
make
it
unavailable
for
writes
because
they
want
to
ensure
that
they
have
that
complete
backup
and
it's
ready
to
go
in
case.
Something
happens
by
enabling
Bluegreen
deployments
with
Geo.
C
We
can
allow
them
to
essentially
unhook
or
pause
replication
in
the
secondary
while
they
go
through
and
upgrade
the
primary
and
then
they
have
that
kind
of
warm
backup,
ready
and
the
older
release.
Encasement
does
happen
with
the
primary
and
this
can
help
to
facilitate
more
online
zero
downtime
upgrades
for
some
larger
and
more
conservative
customers
that
we
have
running
self-managed
so
excited
about
that
feature
there
again
on
the
available
we're
also
working
on
implementing
zero
downtime
re-indexing.
C
For
our
advanced
global
search
feature,
we
recently
made
some
major
savings
on
the
index
size
of
about
40
percent
through
making
some
schema
changes,
the
schema
changes
require
re-index
currently
and
right
now.
You
have
to
essentially
rebuild
the
current
index
that
you're
actually
using
to
search
from
from
the
start
again
and
so
you'll
see
a
great
degree
of
search
performance
when
that
happens,
we'd
like
to
make
sure
that
we
can
offer
a
zero
downtime,
we
indexing.
C
So
if,
as
you
make
future
schema
changes
in
the
future,
you
don't
have
to
have
have
a
period
of
time
where
that
reactors
are
the
images
rebuilding
where
your
users
might
have
an
impact
to
search
experience.
So
those
are
some
the
major
changes
we
have
going
on
in
this
release.
Pretty
exciting
changes
here
are
pretty
big
changes.
If
you
have
some
comments,
leave
them
in
the
issues
and
with
that
I'll
hand
it
over
to
Eric,
so
take
us
through
depth
thanks
Josh.
D
When
I
go
ahead
and
share
my
screen
and
we'll
get
started
all
right,
so
my
name
is
Eric
Brinkman
I'm,
the
director
of
product
for
the
deaf
section,
the
Deaf
section,
is
responsible
for
the
first
three
stages
of
the
DevOps
life
cycle,
so
that's
managed
plan
and
create
and
I'll
walk
through
each
of
those
stages
in
order,
let's
go
ahead
and
start
with
manage
and
then
manage
we're
going
to
focus
on
two
big
themes.
The
first
is
group
management
and
the
second
is
compliance.
D
Oops,
alright,
so
with
respect
to
group
management,
one
of
the
big
things
we're
going
to
be
focused
on
is
enabling
group
manage
accounts
on
get
lab
comm
by
default
group.
Manage
accounts
has
been
available
for
a
while
and
it's
a
great
feature
that
provides
isolation
and
that
sense
of
control
for
users
and
organizations
in
get
comm
in
a
multi-tenant
environment.
D
So
we
want
to
get
these
two
issues
done
and
then
we're
gonna
go
ahead
and
enable
group
manage
accounts
for
get
lab
comm
by
default,
which
would
be
really
really
exciting
and
carrying
on
the
group
management
features
we're
going
to
configure
push
rules
at
the
group
level.
This
is
possible
to
do
today,
at
the
instance
level
and
at
the
project
level,
but
on
get
lab
comm
a
lot
of
organizations
only
really
have
access
to
manage
their
organization.
D
At
the
group
level,
so
this
will
really
help
those
organizations
in
get
lab
comm
and
even
help
self
manage
customers
that
really
want
to
configure
push
rules
at
the
group
level,
so
really
exciting.
To
see
this
land
in
13,
dotto
and
moving
on
to
the
rest
of
the
compliance
features.
So
we're
going
to
add
an
audit
event
for
impersonated
events.
This
is
something
that's
really
important
for
repudiation
and
making
sure
that
you
can
prove
that
an
action
taken
by
user
was
was
done
via
impersonation
or
not
so
really
exciting.
D
This
is
a
really
important
feature
to
make
sure
that
we
organizations
can
have
proper
separation
of
duties,
but
we
want
to
make
this
configurable
at
the
project
level
as
well,
so
we're
going
to
go
ahead
and
do
that
in
13.0,
and
then
we're
also
going
to
iterate
on
our
group
compliance
dashboard
by
adding
a
visual
indicator
for
our
projects
and
our
approval
settings
in
the
compliance
dashboard
to
indicate
if
a
certain
project
has
the
proper
separation
of
duties
or
not
so
really
exciting,
to
see
some
iteration
here.
The
managed
team
also
has
the
managed
stage.
D
Also
has
two
other
groups:
import
and
analytics
and
I
wanted
to
highlight
a
few
of
the
things
that
those
groups
are
also
working
on.
So
the
import
team
is
working
on
a
better
user
experience
for
project
creation.
If
you've,
if
you've
used
our
project
creation
workflow,
it's
it's
a
little
bit
confusing
and
in
fact
that
you
think
you
might
move
from
from
left
to
right
on
this
screen.
D
But
if
you
go
ahead
and
click
this
create
project
button,
you
can
actually
never
go
and
import,
and
so
we
want
to
make
that
a
little
bit
more
explicit
by
just
simply
creating
a
new
screen.
That'll
give
you
that
choice
from
the
start,
which
will
really
help
that
import
and
project
creation
experience
and
then
we're
also
going
to
iterate
on
group
import
and
export
by
providing
anbc
on
the
user
on
the
user
interface.
For
this
feature.
So
this
is
a.
D
D
So
this
will
be
a
nice
iteration
here
to
pull
in
the
issues
to
drill
down
into
the
analytics
features
here
and
then
also
pull
in
the
metadata
associated
with
those
issues
so
really
exciting
stuff.
Coming
from
the
manage
team
and
13o
moving
on
to
the
plan
stage
in
the
plant
stage,
we
have
two
big
features
or
two
big
themes.
D
The
next
step
here
is
user
mapping
between
your
JIRA
instance
and
your
git
lab
instance,
and
this
will
allow
for
two
big
things:
one
it
allow
for
us
to
pull
over
assignees,
gracefully
and
it'll
also
allow
for
us
to
pull
over
the
comments
and
attribute
those
comments
in
an
issue
appropriately
to
the
right
user.
We're
also
going
to
continue
iterating
on
markdown
parsing
to
make
issues.
Look
a
little
better
I'm,
so
excited
to
see
some
of
the
work
that
the
teams
doing
here
on
the
JIRA
importer
and
with
respect
to
epic
improvements.
D
We've
got
a
number
of
really
nice
quality
of
life,
improvements
coming
down
the
pipe
and
1304
epics.
The
first
is
the
ability
to
add
an
epoch
when
you
create
a
new
issue
in
the
UI,
if
you've
created
issues
in
gitlab,
this
probably
looks
pretty
familiar
to
you
and
what
we're
going
to
do
is
simply
add
an
epoch
drop-down
here,
so
that
you
can
easily
add
your
epic
or
the
issue
to
the
epic
at
the
time
of
issue
creation.
We're
also
going
to
let
you
bulk
edit,
the
epic
assignment
on
issues.
D
So
in
13
dotto
we
are
finally
going
to
not
general
availability
for
giddily
high
high
availability.
Sorry
generally
available
general
availability
for
giddily
high
availability
and
really
really
excited
to
see
the
team
as
a
iterated
on
this
over
the
past
year.
And
what
this
means
for
us
is
that
all
the
components
in
the
get
early
architecture
are
now
h.a.
So
that
includes
the
prefect
router
the
protects
database
and
then
all
of
the
get
elite
clusters.
Please
remember
that
we
have.
We
have
focused
on
availability
over
consistency,
see
here.
D
So
this
does
employ
a
and
eventually
consistent
model,
but
will
continue
to
iterate
on
this
by
making
Italy
H
a
strongly
consistent
and
then
also
investigating
things
like
Auto
rebalancing
of
shards
and
distributed
reads
in
each
Italy
cluster,
so
really
exciting
for
to
see
this
land
and
kinga.
It
also
got
some
really
great
features
coming
to
the
mr
code
review
features
as
well,
so
we
want
to
launch
commenting
on
multiple
lines
and
a
merger
quest.
If
and
then
we
also
want
to
support
multiple
code
owners
sections,
so
the
code
owner
file
is
really
useful.
D
If
you're,
you
know
a
small
or
less
complex
organization,
because
it
only
allows
you
to
apply
one
rule
for
each
path.
But
if
you
have
an
organization
where
you
need
to
apply
say
you
know
front-end
back-end
UX
to
a
specific
path.
We
want
to
make
that
available
in
the
code
in
our
style,
so
we'll
be
doing
that
by
adding
in
various
sections
in
the
code
owners
file,
which
will
be
a
great
improvement
for
those
larger
organizations
in
1210.
D
We've
also
made
our
first
NBC
iteration
of
the
static
site
editor
and
we're
going
to
iterate
on
that
in
13
dotto
by
replacing
the
static
site,
editor
text
area
with
it.
What
you
see
is
what
you
get
marked
down.
Editor
I'm
so
excited
to
see
those
improvements
there
and
then
we're
also
going
to
continue
the
work
that
the
web
IDE
has
been
doing
on
dart,
theming
and
so
in
13.0.
D
We
know
that
a
lot
of
users
who
want
to
use
snippets
want
to
collaborate
on
the
star
them,
clone
them
fork
them
and
version
them,
and
really
excited
to
see
that
the
teams
are
iterating
on
this
for
a
number
of
releases,
and
this
is
finally
ready
to
land
in
13
dotto
and
just
as
a
fun
fact.
This
issue
has
opened
over
four
years
ago
and
has
it
more
than
247
upvotes
so
quite
excited
to
see
this
functionality
land.
E
Zarek
I'll
show
my
screen.
My
name
is
Kenny
Johnston
I'm,
covering
the
dev
section
that
includes
verify
package,
release,
configure
and
monitor
stages.
I
wanted
to
start
by
highlighting
the
the
ops
section
includes
were
give
up
is
a
is
a
well-known
tool
for
source
control
and
CI,
and
we're
really
focusing
on
expanding
the
additional
stages
in
the
ops
section
and
our
users.
Usage
of
those,
so
I
wanted
to
highlight
two
key
features:
we're
adding
in
the
release
stage
that
do
just
that.
E
The
first
is
the
addition
of
being
able
to
use
vault
variables
in
your
CI
gamal.
This
is
a
much
sought
after
feature
that
our
users
have
been
asking
for
that
enable
users
who
had
to
store
their
secrets,
their
kind
of
critical
CI
secrets
in
in
vault
in
a
different
tool
and
want
to
be
able
to
reference
those
directly
and
in
there
CI
mo
so
really
excited
about
this
iteration
we've
been
making
progress
towards
this
over
the
last
couple
of
weeks.
E
First
hour
of
releases,
the
next
one
I
wanted
to
highlight
is
adding
ECS
as
a
deploy
target
for
auto
dev
ops.
This
is
pretty
critical
because
to
date,
gitlab
has
our
auto
dev
ops
tool
has
allowed
you
to
automatically
deploy
to
kubernetes
clusters
that
you've
attached,
but
we've
not
gone
after
other
infrastructure
targets,
and
this
is
our
first
addition
of
an
additional
infrastructure
target
that
really
helps
kind
of
broaden
the
funnel
of
users
of
auto
dev
ops,
as
well
as
users
of
our
other
release
features.
E
So
super
excited
about
those
two
as
a
single
application
for
the
entire
develops
lifecycle.
It's
really
important
that
we
not
just
focus
on
the
capabilities
there,
but
also
the
experience
and
so
I
wanted
to
highlight
a
couple
of
kind
of
key
incremental
improvements
to
the
usability
of
core
functions
in
each
one
of
these
stages.
I'll
jump
straight
to
the
screenshots
for
each
the
first
is
pipelines.
If
you've
ever
used,
git
lab
CI,
you
have
the
experience
of
looking
at
sometimes
huge
numbers
of
pipelines
that
I've
all
been
running
and
it's
hard
to
filter
them.
E
We're
gonna
be
adding
pipeline
filtering.
So
today
you
can
switch
between
these
tabs,
which
are
available,
but
you
can't
get
the
kind
of
like
full
freeform
filtering.
That
would
be
useful
to
filter
the
pipeline's
as
you
look
at
them
and
try
to
find
the
specific
pipeline
you're
looking
for
now
will
for
be
focused
on
allowing
that
filtering
by
author,
as
well
as
branch
or
source.
So
those
are
two
kind
of
high
priority
filters
that
we'll
be
adding
to
the
pipeline
filter
view.
Our
next
usability
improvement
is
in
the
package
stage.
E
E
The
next
improvement
in
usability
comes
in
feature
flags
in
the
release
stage,
so
feature
flags
are
a
really
helpful
tool
for
progressive
delivery.
They
don't
have
a
lot
of
connection
to
other
parts
of
get
lab
today,
but
we're
in
13
not
oh
we're
going
to
be
adding
connections
between
feature
flags
and
issues.
So
here's
an
example
where
you
can
have
related
issues
to
feature
flags
to
help.
E
You
understand:
why
did
we
create
this
feature
flag
in
the
first
place,
as
well
as
the
reverse
of
looking
at
an
issue
and
seeing
if
there
are
related
feature
flags?
This
is
a
really
useful
and
drawing
connections
between
different
parts
of
the
DevOps
lifecycle
right
here
in
one
tool,
the
next
thing
we're
gonna
be
doing
is
jumping
to
our
monitor
stage,
adding
usability
improvements
to
the
dashboard.
E
So
today
your
dashboards
are
are
typically
one
often
defined
and
created
without
much
variability,
but
most
users
of
dashboards
for
kind
of
critical
operations,
tasks
create
singular
dashboards
that
then
have
different
variables
that
you
can
select
in
order
to
filter
the
whole
dashboard
and
all
the
charts
in
that
dashboard.
Just
specific
types
of
activities
you
can
see
some
examples
of
run
or
groups
or
data
centers
or
adding
your
own.
E
So
we're
going
to
be
adding
this
variability
inputs
for
dashboards
metrics
dashboards
in
30,
not
oh,
and
we're
also
going
to
be
improving
dashboards
so
that
you
can
star
them,
for
example,
or
you
can
jump
in
and
view
them
in
full
screen
this
little
jump
down
to
view
a
full-screen
version
of
a
specific
chart,
we're
improving
the
legends.
You
can
see
this
view
here.
We
have
a
kind
of
scroll
ability,
improvement
for
and
then
lastly,
this
is
a
net
new
MVC,
but
is
really
about
the
workflow
of
triaging.
E
Incidents
right
in
gitlab
is
we're
adding
an
MVC
for
alert
management,
so
this
will
allow
you
to
point
your
tool,
whether
it's
prometheus
or
others,
that
is
generating
alerts
to
get
lab
and
then
surface
those
alerts
right
and
get
lab.
So
you
can
see
a
list
of
alerts,
for
example,
and
then
you
can
look
at
a
detail
of
alerts
and
in
future,
iterations
we'll
be
adding
the
ability
to
create
an
issue
directly
from
those
alerts.
E
All
really
great
usability
improvements
to
different
parts
of
the
ops
stages
in
the
DevOps
lifecycle
that
I'm
really
excited
about,
as
others
mentioned
great
videos
from
the
team
that
you
can
go
check
out
right
here
on
this
kickoff
page
I
encourage
you
to
do
so.
With
that
I
will
hand
it
back
to
you.
Scott
Wow,.
A
There
is
a
lot
coming
in
13
super,
exciting,
I,
don't
think,
there's
any
doubt
this
will
be
the
best
release
ever
so,
thanks
to
all
the
teams
behind
this,
it's
remarkable
to
me
how
productive
all
these
groups
have
been
despite
the
chaos
in
the
world,
so
really
really
proud
to
see.
All
this
coming
a
lot
coming
soon,
I
want
to
remind
everyone.
We
do
plan
ambitiously.
This
is
our
statement
about
what
we
intend
to
do
and
believe
we
can
do
but
think
plans.
I
can
and
will
change.
A
So
please
allow
a
little
bit
of
drift
from
what
we
presented
here
with
what
ships
when
13o
goes
out.
Finally,
I
would
like
to
also
ask
for
feedback.
We
want
to
make
sure
this
review
is
the
best
it
can
possibly
be.
There
is
a
link
to
a
feedback
form
here
in
the
overview
on
this
kickoff
page,
so
love
your
thoughts
on
what
you
liked
about
this
and
what
could
be
better
so
I.
Thank
you
all
for
taking
the
time
to
watch
this
and
wish
everyone
good
health
and
safety
out
there
have
a
good
one.