►
From YouTube: Ops Backend Group Conversation
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
A
C
C
That
was
really
really
appreciated,
not
very
much
in
the
comments.
Although
there
were
some
really
good
comments
that
helped
drive
good
conversation,
so
I
encourage
everyone
to
put
in
comments
because
there
they
make
it
easier
to
relate
to
the
rating.
The
reading
itself
has
like
we've
been
in.
You
know
the
the
upper
of
the
range,
which
is
fantastic,
I'm
very
happy
with
with
the
result,
I
would
just
like
to
see
a
bit
more
comments
so
that
it's
easier
to
get
a
sense
of
what
what
particular
things
the
team
may
need.
C
I
use
them
very
much
as
a
tool
as
a
skip
level
tool.
I
would
like
to
get
back
into
a
cadence
of
doing
regular
skip
levels,
and
hopefully
that
will
be
that
will
happen.
As
you
know,
Tod
on-boarded,
taken
on
secure
and
defend
and
Jim
is
helping
with
the
ICD,
so
I'm
hoping
on
that
front
will
will
have
more
face-to-face
time,
but
this
is
very
much
an
acing
tool
and
a
good
gauge
for
me
to
know
how
the
team
is
doing.
Does
that
answer
your
question,
sir
yeah.
D
A
A
What
we
would
call
pass
in,
monitor
I
know:
Sara
has
been
heavily
focused
on
instant
management
and
starting
that
MVC.
So
we
can
start
closing
the
loop
of
in
in
a
DevOps
life
cycle
on
APM
I'm,
really
focused
on
ensuring
that
we
are
making
continuing
to
make
metrics
viable
and
I
really
want
to
improve
upon
the
ability
for
developers
to
instrument
their
applications
with
custom
code,
and
then
us
create
alerts
for
them.
That
then,
get
fed
into
instance
when
they
go
beep
in
the
night.
A
E
So,
while
we're
waiting
for
similar
questions,
I
do
want
to
point
out
that
we
are
working
to
rename
pass
to
the
native.
The
first
proposed
name.
We
had
was
application
development
platform.
That
may
not
be
the
final
name,
because
we're
trying
to
position
get
lab
kind
of
in
the
platform
for
you
all
of
your
DevOps
needs,
delivered
in
a
single
app
and
a
may
or
may
not
be
final,
so
we're
working
through
naming
right
now.
If
you
have
any
thoughts
on
that,
we
welcome
them.
We
have
a
channel
for
naming
so
feel
free
to
join.
A
E
C
F
C
I'm
happy
to
give
you
a
little
bit
of
insight.
We,
we
reviewed
these
metrics
weekly
with
the
managers
and
it's
it's
something
that
you
know
we're
constantly
learning
from.
Definitely
the
like
I'll
start
with
monitor
so
monitor
is
a
brand
new
team.
Most
of
the
engineers
are
new
to
get
lab
and
they've
had
a
chance
to
onboard
and
get
familiar
as
well.
As
you
know,
execute,
and,
and
have
you
know
you
know
just
going
through
the
lifecycle
doing
the
reviews
putting
em
ours
going
through
the
transition
of
breaking.
C
You
know
large
deliverables
into
smaller,
M
R.
So
that's
that's
been
a
really
good
journey.
I
also
think
that
you
know
seth
has
done
a
fantastic
job.
You
know
taking
the
team
and
figuring
out
how
to
execute
it,
so
being
the
first
engineering
manager
there
and
then
to
add
to
that.
You
know
with
the
our
phone
and
manage
and
the
partnership
and
and
those
relationship
and
how
to
work
collaboratively
has
also
improved.
So
a
lot
of
these
things
line
up
and
we're
just
getting
better
at
it.
So
my
hope
is
to
continue
to
see
that.
C
Definitely
you
know
when
you
go
from
you
know.
One
engineer
to
you
know
a
large
team
and
actually
monitor
is
now
four
teams
to
back
in
teens
to
front-end
team.
It
is
natural
to
see
that
trend
of
I'm,
hoping
that,
with
with
these
throughput
charts,
one
of
the
things
that
I'd
like
to
see,
maybe
as
we
move
it
to
periscope,
is
the
ability
to
get.
C
Contributors,
so
we're
able
to
see
how
does
that
throughput
line
up
with
you
know
the
number
of
contributors
for
the
months
or
the
week
for
the
configure
a
similar
story
that
team
broke
off
of
CI
CD
was
seeded
by
two
fantastic
folks,
Myra
and
Dylan.
We
started
to
hire
and
grow
that
team
as
well
from
the
backend.
We
started
to
a
line
dedicated
front-end
engineers
with
it.
So
again,
it's
non
boarding
successfully
having
these
multiple
months
of
you
know
going
through
the
process
and
now
I
see
that
team
executing
very
well,
and
you
know
they've.
C
They
fine-tune
how
they
work
together,
especially
through
the
configure
team,
is
spread
across
very
wide
time
zones.
So
that
was
also
another
thing
that
I've
seen
them
work
through
and
kudos
to
the
individuals
on
the
team
on
both
teams.
They've
really
figured
out
a
good
working
relationship,
so
anything
else
on
this
believe
I'm
happy
to
fill
you
in
that's.
A
A
And
returning
the
best
practices
for
how
we
monitor
get
lab
both
Griffin
and
then
at
monitor,
AMA
Andrew
nearly
gave
a
talk
about
how
how
we
do
anomaly
detection
on
get
lab,
comm
metrics.
It's
important,
though
I
want
to
make
sure
we're
making
a
distinction
there,
because
the
what
we
call
the
monitor
stage
is
really
about
the
tooling
that
we
enable
our
users
to
instrument
and
then
respond
to
their
applications
in
production
environments,
and
so
I'll
give
this
other
little
bit
of
context
and
call
out
for
some
work.
A
The
monitor
group
is
doing
because
the
monitor
group,
also
in
owns
this
part
of
the
product,
called
gate
lab
self
monitor
which
we're
working
to
transform.
Essentially,
we
have
some
out-of-band
admin
panels
that
show
monitoring
related
information
for
the
health
of
your
gate.
Lab
instance
itself.
It's
kind
of
like
using
get
lab
to
get
a
view
of
how
gate
lab
itself
is
performing
and
we're
working
to
move
that
into
its
own
project,
so
that
actually,
then
it
utilizes
the
same
native
capabilities.
A
We
would
give
a
customer
to
monitor
their
own
application,
so
if
they
created
their
own
rails
application,
they
were
instrumented
and
have
these
dashboards,
and
we
would
use
much
of
those
same
tools
on
get
lab
itself,
and
that
also
gives
us
the
opportunity
to
expose
users
and
administrators
to
oh,
here's
kind
of
like
best
practices
for
how
to
instrument
and
use
our
monitoring
capabilities
as
they
would
live
in
a
complex
application
like
get
lab.
So
I'm
really
excited
about
that
initiative.
A
That's
part
of
our
get
lab
self,
monitor
initiative
that
we
have
going
on,
but
that
often
times
we
people
hear
the
word
monitor
or
monitoring
at
get
lab,
and
they
think
it's
about.
How
do
we
monitor
get
lab
itself
but
remember
we're
building
a
extensive
set
of
functionality
that
enable
our
customers
to
monitor
their
own
applications.
A
G
A
I
And
try
and
just
maybe
come
in
here
a
little
bit
I'm,
not
sure
if
your
question
was
around
the
tools
that
we
use
mine
are
get
calm
today,
like
that
dashboard,
we
actually
ship
a
fully
functional
monitoring
suite
with
omnibus
today
in
get
lab.
So
if
you
install
on
to
us
in
a
single
node,
you
will
get
many
theists
hooked
up
as
been
mentioned.
I
You'll
also
get
Griffin
I've
hooked
up,
you'll
have
some
dashboards
baked
in
and
I
think,
hopefully
this
summer
I
get
Spurgeon
will
actually
give
you
a
link
to
that
dashboard
in
the
instance
panel,
and
so
you
can
click
on
that
and
get
taken
into
a
full
dashboard
telling
you
how
your
higher
instances
doing
so
I
sent
a
lot
of
work.
Martin's
been
doing
and
Drew's
also
doing
some
great
work
to
even
have
it
to
get
set
up
out
of
the
box
with
service
discovery
for
multi
node
get
up
instances
as
well.
I
So
if
you
deploy
ten
nodes,
you'll
get
those
ten
nodes
being
scraped
and
pulled
for
for
your
dashboards
across
all
done
automatically
as
they
come
up
and
down,
which
is
super
exciting.
So
and
then,
hopefully
we
can
transition
this
to
end
product
here
soon
as
well.
But
does
that
help
answer
your
question
but
I
mean
today
I
think
we
have
a
great
monitoring
story
out
of
the
box.
Yeah.
G
G
C
C
We
are
really
excited
for
him.
He
is
transferring
to
the
infrastructure
team
will
be
closely
aligned
to
you,
know
continuing
to
work
on
monitoring
but
from
infrastructure,
so
Ben.
Thank
you
so
much
for
everything
you've
done
for
the
Deb
and
it's
this
is
not
like
a
goodbye
or
anything.
We
are
so
excited
to
continue
to
partner.
Ben
is
leading
a
working
group
for
self.