►
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
Welcome
to
the
threat,
insights
weekly
group
call.
I
added
something
new
to
our
agenda.
I
really
like
the
way
the
secure
stage
highlights
their
accomplishments
tiago,
and
I
thought
it
would
make
sense
to
the
weekly
group
meetings
instead
of
our
bi-weekly
threat
management,
sub
department
level
meeting.
So
there's
a
list
here
of
the
issues
that
have
been
closed
since
the
11th.
So
since
the
last
time
we
met,
we've
got
a
script.
That'll
keep
this
up
to
date
and
we're
just
gonna
share
what
we've
closed.
We
don't
need
to
go
through
it.
A
B
I
I
had
I
had
something
about
the
ping.
I
don't
think
we
need.
We
need
to
talk
about
that
so,
but
but
matt
might
want
to
update
the
thing
that
we're
not
going
to
look
in
there.
What
your
recommendation
is
matt.
C
Good
call
so
I
haven't
had
the
meeting
yet
so
I
can't
say
definitively
so
thank
you
for
those
folks
that
helped
thiago
and
myself
get
a
rough
swag
on
taking
our
metrics
collection
and
migrating
it
to
the
usage
ping.
C
The
quick
recap
on
that
is:
there's
a
big
push
specifically
from
product
management,
but
I
think
organization
wide
to
capture
the
monthly
active
user
counts
at
all
the
all
the
different
levels.
So
category
group
stage
whatever
the
challenge
is,
we
are
only
getting
session
level
data.
So
it's
not
individual
user
actions
and
those
are
not
considered
accurate
enough
for
gathering
this.
C
Now,
as
it's
called
the
monthly
active
user
data,
the
telemetry
team
is
working
towards
resolving
that
and
then
also
taking
what
we
use
today
for
snowplow
and
making
that
the
default
solution
for
gathering
metrics
for
self-managed
customers,
whereas
today
it's
usage,
ping
a
lot
of
back
and
forth
on
this
one.
C
Have
that
on
anyway,
then,
we're
only
buying
ourselves,
probably
nine
weeks
at
most
before
the
telemetry
team
is
supposed
to
have
delivered
the
snow
plow
for
self-managed
with
user
level
capture
anyway,
and
if
we
miss
that
by
a
milestone,
then
we're
buying
ourselves
roughly
five
weeks.
So
why
would
we
re-implement
all
of
the
metrics
multiple
times
so
that's
kind
of
where
I'm
at
and
then
we'll
see
how
this
meeting
goes
tomorrow
with
the
the
product
management
leadership?
C
A
Anyone
else
to
update
anyone
on
previous
discussions.
This
is
your
time
all
right.
We
got
some
demos.
Take
a
look
at
them.
Swash
gave
us
some
screenshots
and
a
youtube
video.
I
haven't
had
a
chance
to
watch
those
yet
and
thanks
alexander
separation
of
security,
dashboard
and
vulnerability
vulnerability
report
on
groups
should
we
have
that
done
now
for
all
three
dashboards
alexander,
no,
which
ones.
D
C
A
D
No
okay.
A
A
One
thing
I
haven't
seen
a
demo
of
and
what
would
be
cool
if
we
could
get
someone
to
record
one
is
around
the
related
issues
and
where
we're
at
with
that,
I
think
we
might
still
have
a
little
bit
of
work
around
the
history
display
of
relating
and
creating
issues.
But
I
know
we've
made
a
lot
of
progress
on
that.
D
A
C
Hey
lindsay,
I
have
something
that's
kind
of
related
to
this,
but
it
doesn't
fit
within
one
of
our
menu
or
our
agenda
items
so
andy
and
I
were
just
chatting
there
is
there's
a
lot
of
conversation,
that's
going
on
today
that
haven't
yet
captured
and
synthesized,
but
we're
still
trying
to
make
sure
for
the
new.
C
Like
the
mr
experience
and
some
of
the
forward-looking
design
work
around
the
triage
experience,
we
got
an
interesting
perspective
from
thomas
and
one
of
the
things
that
we
want
to
maybe
put
a
hold
on
is
not
going
to
the
tabbed
view
for
the
vulnerability
list.
So
if
you
look
at
a
lot
of
the
mock-ups
for
all
the
redesigns
there's,
it's
kind
of
a
subtle
design
change,
but
there's
now
tabs
for
the
different
states.
So
there's
a
detected
tab,
there's
a
closed
and
then
all
tab.
A
C
C
Yeah,
so
it's
this
little
thing
right
here
so
today
everything
is
all
on
one
page
and
then
we're
going
to
go
to
these
tabs
by
the
different
states.
I
didn't
actually
see
an
issue
for
that
in
the
breakdown.
So
I
don't
know
if
I
missed
it
or
not,
but
I
guess
I'm
saying
like
let's
hold
off
and
not
do
that,
I
was
going
to
grab
it
out
of
13
4
if
it
did
exist.
C
It
is
today
yeah,
let's
hold
off
on
the
implementation
of
just
this
reworking
of
the
tab,
so,
like
the
all
tab
is
effectively
the
current
list
as
it
stands
today,
and
then
these
are
basically
just
like
pre-done
filters
more
or
less
so
this
one
design
element,
let's
hold
off
on
that
for
right
now.
So
if
there's
not
an
issue,
I
mean
we
can
even
create
it
and
just
put
it
in
a
future
state
or
not.
C
C
Cool
and
if
you
don't
find
one
like
like,
I
said,
that's
actually
probably
fortuitous.
I
know
this
is
kind
of
a
last-minute
thing
and
we're
changing.
A
A
A
Oh,
I
met
you
out
of
this
up
here.
I'm
going
to
remove
my
trying
to
play
stenographer
in
this
meeting
from
up
here
and
let's
take
a
look
at
this
warn
about
failed
jobs
on
the
project
security
dashboard.
You
know,
we've
talked
about
this
a
couple
of
times,
but
there's
been
a
lot
of
discussion
and
some
updates
that
have
been
made
to
the
design
since
we
first
talked
about
it.
A
D
D
This
is
a
tough
one,
call
it
I'll
kick
it
over
to
matt
that
teammate,
I'm
gonna
go
mute.
D
Yeah,
I
think
it
got
pulled
back
to
just
and
let's
make
sure,
are
the
final
designs
in
the
issue
description
or
in.
C
Yeah,
so
really
what
we're
talking
about
is
this
little
header
bar
up
here
after
many
many
back
and
forth
about
you
know,
do
we
want
to
show
specific
details
about
the
job
succeeding
or,
failing
or
like
you
know,
pipelines
or
whatever?
This
is
what
we
we
ultimately
landed
on
we're
calling
out
again.
This
is
just
on
the
default
branch,
so
that
people
know
that
last
updated
is
just
the
time
the
job
I
believe
completed,
and
then
this
is
a
link
to
the
specific,
I
think
that's
the
job
itself
pipeline,
the
pipeline
yeah
and
then
so.
C
A
C
Yeah
there
were
definitely
a
lot
more
moving
parts
before
that,
but
so
yeah.
So
that's
pretty
much
where
we
landed
on
that
one.
A
Alexander
does
looking
at
jonathan
and
daniel
they're,
not
adamantly
shaking
their
head.
Now,
yes,
okay,
there
we
go.
I
saw
a
headshake
and
a
thumbs
up,
so
you
know
our
first
question
is
always
are
the
requirements
clear
enough?
So
does
anyone
have
any
questions
on
the
requirements
or
edge
cases
or
functionality.
D
Yeah,
what
matt,
what
should
the
show
if
a
pipeline
has
not
been
run
yet.
C
Good
question
I
think
we
had
was
here.
One
part.
D
C
Let
me
see
if
I
can
find
there
was
this
very
similar
question
and
another
issue,
and
I
think
it
pretty
much
boiled
down
to
it'd
be
awesome
if
we
could
just
let
the
user
know
that
there
is
not
a
a
security
job,
that's
ever
been
run
against
this
particular
pipeline.
Go
here
and
basically,
click
to
trigger
a
fresh
pipeline
run
against
the
default
branch.
C
Let
me
see
if
I
can
find
it.
It
might
actually
be
buried
down
in
a
previous
design
on
one
of
the
comments
here,
but
yeah,
you
definitely
need
to.
B
C
A
All
right,
if
anyone
thinks
of
anything,
you
know,
feel
free
to
put
it
in
the
issue.
I
think
we
can
at
least
ponder
the
other
questions
to
see
if
there's
any
gachas
any
dependencies
of
the
work
to
be
accomplished.
Other
teams.
A
B
B
B
E
E
Yeah
allen
had
a
a
comment
about
just
using
the
pipeline
dot
security
scans.
The
search
there.
A
Excellent,
the
third
question
we've
questioned:
maybe
we
don't
need
to
be
asking
this
one
is
the
research
and
solution
validation
all
complete,
and
I
know
that
matt
and
andy-
you
guys
have
been
through
a
lot
with
this
one.
You
guys
have
any
further
confirmation
or
work
to
do
in
that
front.
C
C
I
don't
remember
what
the
name
was
before
that,
so
we're
just
bringing
something
back
into
the
ui
that
we
had
before.
E
A
E
A
Smaller
all
right,
so
I
added
a
new
question
just
based
on.
I
had
a
coffee
chat
last
week
with
will
meek,
who
is
our
stable
counterpart
in
tests,
and
I
learned
a
lot
about
how
our
end-to-end
tests
work
and
how
he
has
been
manually,
going
through
all
of
the
secure
stage,
issues
each
milestone
to
try
and
identify
where
there
might
need
to
be
work
to
end
tests
and
things
that
he
might
need
to
support
to
make
that
easier
for
him
as
part
of
our
planning
breakdown.
A
You
know
get
this
on
your
roadmap,
so
someone
disagree
with
me
if
they
think
I'm
totally
off
the
mark
here.
This
does
feel
like
something
that
could
use
assistance
from
an
end-to-end
test
perspective
from.
A
Will
sure
yeah
it
feels
like
the
kind
of
things
that
we
cover
in
those
types
of
selenium
tests.
So
you
know
eventually
we
might
have
more
ownership
over
this,
but
for
right
now
this
was
his
expectations.
He
says
you'd
like
the
engineers
to
write
unit
tests,
but
he's
holding
himself
accountable
for
those
end-to-end
tests
all
right,
so
we'll
go
ahead
and
mention
him
in
this
issue.
Matt
and
andy.
Do
we
know
I
mean
this
is
going
to
be.
A
D
C
A
A
That's
all
I
had
for
that
one.
If
anyone
else
has
any
thing
on
that
particular
issue
for
plenty
breakdown,
go
ahead
and
bring
it
up.
B
Yeah
I
wanted
to
to
mention,
because
last
week
we
had
a
small
wave
of
two
three
s
ones
and
I
wanna
thank
everyone
who
jumped
on
it
to
to
resolve
it,
and
I
wanna
understand
a
little
bit
why
they
popping
up
all
of
the
sudden,
and
I
have
an
idea,
they've
all
sort
of
been
related
to
performance.
B
We
already
know
that
we
have
some
improvements
to
make
in
the
vulnerabilities
model.
We
already
have
some
an
epic
with
some
issues.
That
is,
it's
going
to
be
done
in
1304
to
clean
that
up
a
little
bit
but
from
the
team.
If
anyone
has
feedback
to
to
improve
how
we
handle
these
either
in
terms
of
communicating
or
having
zendesk
accounts
or
know
what
knowing
where
to
find
stack
tricks
for
these
things,
I'm
all
years
and
the
s1
that
I
raised
yesterday,
I
actually
did
downgrade
it
because
it
didn't
affect
everyone.
B
It
was
a
very
specific
if
you
have
more
than
12
jobs
or
something
like
that
running
that
generated
security
report
it
times
out.
So
we
started
to
see
these
performance
related
things,
which
is
probably
a
good
indicator
that
people
using
our
features
yay,
but
now
we
have
to
go
and
pay
special
attention
to
to
cleaning
up
those
performance
bugs
and
and
having
will
help
us
with
those
end-to-end
tests
and
figure
out
how
we
can
do
load
testing
would
be
very,
very
handy
anyway.
Just
just
an
awareness
thing.
A
And
to
add
to
that
diego,
I
think
some
of
the
bugs
we've
seen
have
been
less
about
performance
and
more
about
edge
cases.
You
know,
I
know
you
saw
one
about
when
you
move
issues
from
one
project
to
another,
that
the
dashboard
was
timing
out
loading
because
it
wasn't
able
to
find
that
issue
or
something
along
those
lines.
So
yeah.
B
A
I
was
gonna,
I
was
gonna,
speak
up
and
nominate
philippe
because
he's
told
me
a
number
of
times
that
he's
really
good
at
catching
these
kind
of
things.
So,
if
you're
developing
something
that
you
feel
like,
maybe
you
don't
know
all
of
the
corner
cases
of
the
edge
cases,
because
you
know
we're
relatively
new,
I
encourage
everyone
to
mention
him
and
say:
hey
felipe,
take
a
stab
at
testing
us
somewhere.
I
know
you're
great
at
breaking
things.