►
From YouTube: 2023-08-01 Product Analytics Group Sync
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
Hello,
everyone
and
welcome
to
the
August
1st
edition
of
the
product
analytics
group.
Sync
I
will
go
ahead
and
share
my
screen
and
we
will
start
with
the
Board
review.
A
Cool
so
getting
into
it,
we've
got
the
most
important
issue
and
then
adding
product
analytics
to
experiment
features
list.
This
one
need
a
bit
of
I'm
assuming
because
it's
open
there's
no
workflowable.
We
still
need
to
Define
exactly
how
this
one's
going
to
work,
James
or.
A
B
I,
don't
think
we
had
a
chance
for
buying
this
before
the
Milestone
kicked
off
yeah.
But
we
want
to
put
this
behind
the
beta
opt-in
for
the
rest
of
the
experiments
just
because
it
gets
up
the
teeth
and
see.
If
that
we
need.
A
Okay
got
it
and
we
should
work
to
Define
that
that
notes
lays
before
the
next
group.
Sync
we've
got
a
issue
in
design
for
creating
a
custom,
dashboard
flow
MVC.
Anything
you
can
share
on
this
one.
B
He's
also
got
the
regular,
bigger
Vision
in
there
as
well,
just
so
that
we
can
kind
of
see
where
we
want
to
get
to
longer
term
with
things
like
other
data
inputs
or
defining
a
visualization,
creating
a
visualization
as
a
part
of
the
flow,
but
the
MVC
is
going
to
be
pretty
straightforward
of
Navy
dashboard
drop
off
visualizations
into
it,
and
it's
all
within
the
project
that
you
want
to
the
dashboard
and
the
data
are
coming
from.
Okay,.
A
Got
it
cool
then
moving
on
nothing
in
blocked
plenty
breakdown
or
ready
for
development,
but
lots
of
stuff
in
Dev?
Oh
and
you've
got
the
first
issue
here.
C
A
Gotcha
well,
thanks
for
working
through
this
conflicts,
we've
got
the
usage
view
user
scoring
map
and
change
anything
you
want
to
update
on
here.
B
Oh
I
I'm
getting
close
to
having
that
wrapped
up
and
should
be
able
to
start
creating
the
MVC
issue
for
that
I'm
gonna
put
together
a
really
rough
wireframe
based
on
existing
usage
quota
screens
and
we'll
just
reuse.
Those
kinds
of
crap
for
this
so
stood
up
that
wrapped
up
within
this
Milestone.
Hopefully
early
in
the
milestones,
we
can
start
discuss
some
implementation
issues.
A
Awesome
cool
I've
got
the
next
one
for
the
customer
facing
infrastructure
release,
so
this
is
kind
of
the
source
of
Truth
for
everything
that
has
to
happen
as
far
as
what
infrastructure
and
security
have
suggested
or
recommended.
Rather
in
order
for
us
to
kind
of
really
do
this
canonical
Security
review.
A
That
said
right
now,
I
just
merged
in
some
configurator
changes,
I've
been
resolving
some
deployment
issues
just
with
our
move
to
Vault
and
things
like
that.
There's
a
just
kind
of
ironing
out
some
bugs,
but
that's
we're
making
good
progress
there.
My
goal-
and
so
my
goal
is
to
get
to
the
point
where
we've
made
all
the
security
changes
that
have
been
recommended
to
us
and
what
I
hope
to
do
is
actually
just
see
if
we
can
get
that
reviewed
since
that's
effectively
just
a
different
environment.
A
That's
just
not
actively
management
infrastructure
so
that
we
could
at
least
get
the
permission
to
onboard
a
some
external
customers.
While
we
continue
to
work
on
you
know
doing
whatever
packaging
or
whatever
needs
to
be
done
in
terms
of
actually
getting
deployed
to
a
an
infrastructure
managed
environment
just
so
we
can
kind
of
make
some
some
more
movement
there
without
holding
this
up
any
further.
So
that's
my
goal.
There
are
more
issues
that
are
actively
assigned
to
me,
but
they're
in
a
different
group
and
project.
So
that's
why
you're
not
seeing
it
here.
A
That
said,
you
can
go
from
this
issue
into
others
to
see
what
exactly
has
to
be
done,
but
a
lot
of
it
is
just
in
review,
and
so
just
a
little
bit
of
a
merge
train
that
I'm
kind
of
sorting
through
right
now,
I
realized
I
was
also
a
confidential
issue,
but
I
think
it's
just
the
nature
of
security
issues
and
then
nothing
particularly
at
least
in
this
issue
that
I
showed
that
was
sensitive.
A
So
no
video
editing
for
me
today,
all
right,
we've
got
admissing
trailing
breadcrumbs
for
analytics
dashboard
Pages,
that's
assigned
to
Rob,
as
well
as
the
cube
clickhouse
driver
up
screen
fix
so
that
we
can
actually
fill
dates
with
mole
values
or
zero
values.
A
Rob
it's
not
on
the
call.
So
we
can
go
ahead
and
move
on
same
thing
for
Yan
as
well,
for
adding
a
retry
button
to
analytics
dashboard
panel
errors,
something
that's
related
to
the
fact
that
we
have
some
query.
Timeouts
I
know
there's
some
issues
that
have
been
created
due
to
some
memory
limits.
Things
like
that,
so
we
can
continue
to
hopefully
investigate
those
at
least
give
the
opportunity
to
retry
queries.
There.
A
We've
got
some
security
improvements
to
make
in
relation
to
the
clickhouse
cluster,
just
trying
to
think
of
what
we
can
share
there,
basically
just
making
sure
that
it's
only
accessible,
Within,
the
same
environment,
but
nothing
more
between
like
just
what
clusters
need
access
to
it.
Directly
Ellen
you've
got
the
loading
State
for
the
shared
dashboard
listing.
C
Yeah
this
one
is
reviewed
now
couldn't
be
merged
because
there
was
a
master
broken
thing
going
on
about
that.
One
should
be
three
Zone.
A
Plus
and
then
Alia's
got
removing
initialized
analytics
worker
class
file
in
review.
This
is
the
old
Jitsu
worker
that
is
no
longer
used,
so
it's
just
a
little
bit
more
of
that
cleanup
there,
which
I
am
very
keen
on
applying
to
our
stack
as
well,
but
that
will
come
later
and
then,
as
far
as
verification
I
want.
You
also
have
the
issue
here.
C
Yeah,
so
the
project
settings
page
for
analytics
merged
last
night,
so
I'll
go
through
and
verify
that
this
morning,
yeah
nice
to
have
that
one
through.
Finally,.
A
Awesome
yeah
that
one's
no
one's
been
in
the
oven
for
a
while.
So
thanks
for
your
patient
patience
and
effort
on
that
cool
last
week,
I
believe
the
bookmark
was
the
designer
outputting
incorrect,
visualization
definitions.
So
we've
got
eight
issues
was
closed
since
then,
which
is
great
to
see
starting
with
removing
just
related
backing
code
from
product
analytics
feature
that
allele
has
done
as
well
as
hiding
analytics
dashboards
for
users
without
access,
as
well
as
a
follow-up
related
to
the
just
related
cleanup.
A
C
The
IR
estate,
one
is
pretty
nice
because
we
can
actually
see
which
things
are
failing
now
and
we'll
be
building
on
top
of
that
for
some
validation
stuff.
That's
coming
up.
Oh
that's!
Really:
cool
nice
and
the
hiding
configured
custom
dashboards
Banner.
There
was
a
change
happening
as
well
from
Valley
Streams
analytics.
They
were
trying
to
hide
that
for
all.
B
C
So
that's
been
done
as
part
of
this
as
well.
That's
yeah
completely
disabled
for
groups
now
until
they're
ready
for
that
this
last
one
was
just
a
little
follow-up,
not
too
much.
So
then.
A
Great
and
then
Alan
had,
let's
close
the
issue
for
product
analytics,
queries
failing
to
load.
I
know
there
were
some
other
related
issues
there
regarding
query
performance,
but
I.
Think
there's
a
little
bit
of
a
follow-up
here
looks
like
it's
related
to
the
memory
issue,
so
we'll
investigate
that
great.
B
B
Figure
everything
out,
keep
yourselves
there.
We
go.
Making
that
bigger
the
release.
Product
analytics,
open
Beta
is
our
big
objective
or
the
big
objective
that
I'm
targeting
for
the
quarter.
Sorry,
that's
the
key
result.
There
we
go.
The
objective
complete
the
product,
analytic,
beta,
epic
and
open
the
beta
program
for
customers
so
obviously
relate
the
product
analytics
beta
for
me,
delivering
a
blog
post
about
product,
analytics
data
and
Direction.
B
That's
kind
of
our
go
to
market
root
motion
here,
we're
not
going
to
be
actively
marketing
the
open
Beta,
but
a
little
bit
of
kind
of
underground
marketing
when
we
say
release
it's
more
of
a
it's
now
available,
but
isn't
going
into
the
release
post
we're
not
necessarily
going
to
be
providing
a
bunch
of
extra
collateral
to
the
Salesforce
I'm
going
to
go
out
and
delete,
but
we
will
be
looking
for
customers
to
help
with
stress
test
the
thing
and
then
holding
some
number
of
customer
feedback
calls
with
those
experiment,
participants
so
I'm,
reaching
back
out
to
both
folks
who
were
interested
thinking
if
they're
still
interested
so
as
soon
as
we
can
get
them
on,
boarded
wrapping
up
that
infrastructure
work
that
we
talked
about
earlier.
B
We
can
get
them
in
and
get
feedback
we're
having
great
feedback
sessions
with
our
internal
users
already
so
really
excited
to
get
outside
of
gitlab
intra
as
well.
Keep
looking
at
those
videos
sharing
them
with
the
team
and
understanding
where
there's
opportunities
for
us
to
develop
more
pain,
points
with
product
analytics
for
those
first
customers.
B
So
I
want
to
open
it
up.
For
questions
comments
concerns
we
kick
off
the
new
fiscal
year
quarter
today,
it's
August
September
October,
so
this
will
be
definitely
a
big
stretch
to
get
into
beta,
but
I
think
it's
something
that
we
can
do
based
on
what
right
now
we
know
about
the
work.
That's
in
the
beta
epic
anyway,.
A
Yeah
I
mentioned
it
before
it's
it's
ambitious,
but
it's
achievable.
So
you
know
I
think
that's
the
right
kind
of
okay.
B
I
think
the
the
biggest
problems
that
we're
facing
are
that
are
in
the
way,
are
the
infrastructure
work
that
you
have
experiments
started
and
then
some
of
those
known
unknowns
around
pardoning
the
stack
and
a
little
bit
of
resiliency
and
so
I
think
it'll
be
a
great
opportunity
for
us
to
be
creative
around
what
are
ways
that
we
can
get
to
Beta
that
aren't
necessarily
going
to
scale
the
ga
for
reliability,
resilience
of
the
product
analytics,
backup
like
where
we
put
our
rate
limits.
B
What
those
rate
limits,
look
like
I
think
it'll
be
a
great
opportunity
for
the
team
to
brainstorm.
Really.
How
can
we
get
to
that
objective
within
the
time
frame.
A
Yeah
for
sure,
not
for
the
intention
of
conflating
the
terms,
but
data
will
kind
of
really
be
an
experimental
base
for
us
in
terms
of
trying
what
works
as
far
as
weight
limits
and
scaling
strategies.
Not
that
we
expect
to
really
treat
data
as
an
experiment.
But.
B
A
It's
a
little
bit
different
in
terms
of
us
figuring
out
how
we
want
to
actually
scale
for
for
GA,
but
I
think
it'll
be
good
to
explore
that
as
far
as
the
feed.
So
obviously
we
want
to
get
feedback
from
external
customers
as
well,
but
have
there
been
any
common
themes
from
internal
customers,
at
least
so
far
from
your
conversations.
B
Nothing
big
yet
I
have
a
session
tomorrow
morning
with
the
design
team.
Let's
talk
about
pajamas
I
asked
Jeremy
specifically
to
try
to
go.
Look
at
visualization
designer
and
I
know
that
he's
had
some
questions
around
the
page
we
used
to
I
know
we
worked
through
the
unique
user
problem
with
them
already
and
that
they're
good
there.
B
What
we're
finding
so
far
is
that
these
teams
are
interested
in
the
product,
but
they
don't
have
specific
product
problems
to
solve
or
problems
to
solve
that
the
features
address
so
could
they,
it
hasn't
been
a
main
thing
for
them
to
go.
Look
at
yet
so
the
data
is
interesting,
but
it's
not
as
useful
as
it
could
be.
Just
because,
if
they're
not
trying
to
solve
it
like
it's,
not
the
right
tool
for
them
yet
so
yeah,
that's
kind
of
been
the
feedback
so
far.
A
Gotcha
yeah,
and
especially
if
it's
in
the
context
of
pajamas
I,
think
one
thing
that
I
created
an
issue
for,
but
I,
don't
think
we've
yet
prioritized
like
the
what
we
discussed
at
least
some
discussions
about
or
yeah
discussion
discussions
we'll
be
just
discussed
regarding
being
able
to
filter
out
the
user,
ID
type
that
that
we
were
having
that
return
to
reach
decision
on,
because,
for
example,
for
pajamas
there's
a
lot
of
CI
pipelines
running
that
aren't
actually
running
in
production,
so
being
able
to
filter
that
noise
out.
A
Well,
not
noise,
but
filtering
out
that
those
those
domains
to
see.
What's
the
authentic
production
traffic
will
be
useful
and
actually,
when
they
do
have
questions
answering
those
so
yeah,
yeah
yeah.
B
And
one
thing
that
Jeremy
shared
this
morning
was
around
their
top
page
views:
I
mean
they're
interested
in
the
top
pages.
How
many
are
what
are?
What
are
the
top
pages
that
are
showing
up
we're,
counting
an
anchor
link
as
a
separate
page?
So
there's?
If
you
look
at
right
now,
they're
dashboard,
it
looks
like
there's
only
two
pages
visited.
B
Duplicate
and
if
you
look
at
the
URL
that
it
would
link
to
it's
an
anchor
on
that
page
somewhere,
but
I
think
that'll
be
a
user
experience
thing
that
we
got
to
get
sorted
out
and
that's
on
my
agenda
to
talk
with
him
tomorrow.
What
would
you
expect
to
see
like
what
would
be
useful
when
you
click
on
that
not
just
going
to
where
it
is,
but
maybe
some
more
details
about
it.
So.
A
Yeah
for
sure
it'd
be
it'd,
be
interesting,
also
to
see
I
mean
technically
I.
It
could
be
a
preference
thing
right.
Like
you
know,
some
people
would
want
to
see.
You
know
well,
I
I
get
that
they're
going
to
this
page,
but
they're
looking
for
one
specific
thing
or
do
they
want
it
Consolidated,
but
then
you
could
segment
it
later
on
where
it's
like.
Yes,
you
have.
You
know,
here's
all
the
total
visits
to
this
page,
but
it's
it's
more
nuanced
than
that.
So
yeah
I.
C
A
B
I
was
going
to
go
start
scraping
through
department
okrs
and
see
if
product
analytics
could
be
a
tool
that
helps
somebody
achieve
their
okrs
for
the
quarter
and
I.
Think
that's
going
to
get
us
if
we
can
get
in
to
some
of
those
projects
and
help
them
look
at
usage
of
a
project
that
might
be
helpful
for
us,
because
those
are
the
kind
of
users
that
we
want.
That's
where
we
can
provide
a
lot
of
value
with
the
product
analytics
feature
set,
so
some.
A
One
thing
that
might
be
useful
as
well
and
I
think
this
would
also
support
analytics
instrumentations
okrs
in
terms
of
their
unified
API
and
at
some
point
they
want
to
start
sending
events
to
our
snowplow
collector
for
the
usage
within
product
analytics
dashboard.
So
I'm
just
making
a
note
for
myself
to
kind
of
check
in
to
see
where,
if
we
can
potentially
dovetail
there
yeah
but
yeah
I'm,
still
working
on
the
engineering
okrs.
So
we'll
see
if.
B
I
could
start
to
count
unique
active
users,
dashboards
in
product
analytics,
yeah,
yeah.
A
Awesome
I
guess
the
only
other
thought
yeah
we've
been
yeah,
we've
been
struggling
a
little
bit
with
infra,
but
I
think
once
we
get
out
yeah
once
we
get
into
the
official
experiment,
phase
I
think
you
know
with
once
we
figure
out,
or
at
least
have
some
ideas
for
rate
limiting
for
beta.
It
wouldn't
be
that
much
more
difficult
from
a
complexity
scale
to
like
just
open
it
up
to
more
people,
so
yeah
just
need
to
make
that
First
Progress
of
being
able
to
host
Red
Data.
So
yeah.
B
Owen,
did
you
have
any
questions
we
touched
on
this
briefly
in
the
section
call
earlier
this
week,
but
wanted
to
make
sure
that
we
got
some
engineering
questions
in
there
too.
B
Sorry
Skip
and
write
over
things.
Yeah
just
wanted
to
talk
about.
B
How
do
we
balance
that
availability
and
making
sure
that
we're
not
well
and
when
I
say
we
I
mean
y'all,
aren't
constantly
getting
paged
or
have
alerts
going
off,
trying
to
keep
this
back
up
and
running,
seeing
if
we
can
start
to
maybe
get
stats
from
the
folks
running
some
of
those
AI
experiments
and
see
what
kind
of
volumes
they're
getting,
and
is
that
even
something
that
would
translate
into
the
kind
of
event
volume
that
we
would
get
that
we
want
to
set
thresholds
around
and
then
the
other
thing
was
with
this
being
behind
the
experiment.
B
Toggle
are
we
we
reasonably
expect
folks
to
onboard
quickly
or
is
it
going
to
be
hey
if
they
happen
to
run
across
that
they're
going
to
join,
we've
only
had
two
or
three
other
companies
that
are
interested
or
customers
that
are
interested
so
without
a
big
push
from
us
into
the
failed
force
or
into
the
field
teams
to
say,
hey,
go,
get
everybody
working
on
the
beta
I,
don't
know
that
we're
going
to
see
a
ton
of
playing
to
start.
So
this
might
be
a
problem
we
don't
necessarily
have
to
solve.
Very.
A
No
for
sure
I
think
it
just
comes
down
to
what
we
think
is
a
sensible
set
of
of
a
sensible
strategy
for
for
how
I
want
to
roll
this
out
and
then-
and
you
touched
on
this
yesterday
during
the
section
meeting
as
well.
It's
like
there's
the
difference
between
we've,
achieved
the
release
and
we're
actually
pushing
the
release
like
in
terms
of
marketing
and
field
like,
like
you
just
mentioned,
I
I.
Think
if-
and
this
is
I'm
glad
this
is
gonna-
be
recorded,
because
my
third
review
remember
it
later.
A
But
if
we
do
something
like
I,
don't
want
to
over
optimize
and
say
like
oh,
we
have
to
put
really
low
limits
just
because
we're
gonna,
we
don't
know
how
many
people
will
opt
in
I.
Think
if
we
do
something
like
okay,
the
experiment,
toggle
is
still
behind
a
feature
flag
and
then
we've
set
sensible
limits
and
have
a
general
idea
of
like
how
many
people
we
could
potentially
get
then
I.
A
Think
that's
enough,
because
if
we
see
that
things
start
to
immediately,
let
me
back
up
a
little
bit
in
the
context
of
like
some
of
the
AI
experiments.
You'd
run,
we
have
run
into
cases
where,
like
we've
launched
it
more
than
100
people
start
using
it
at
the
same
time,
and
it
just
immediately
goes
down.
So
there
is
the
potential
for
that,
but
I
think.
A
If
we
do
get
a
sense
of
that,
then
we
can
just
say:
hey:
let's
shut
off
the
experiment,
toggle
for
now,
we've
we've
we've
kind
of
closed
the
door
on
the
beta.
For
now,
as
we
work
to
iron
out
the
issues,
and
then
we
can
use
that
to
just
generally
have
a
stable
set
of
users
and
events
coming
in
to
figure
out
what
we
need
to
change
to.
Do
that,
so
I
don't
want
to
I,
don't
want
it!
A
I
don't
want
us
to,
like
imagine
all
the
edge
cases
that
could
happen
or
things
that
could
go
wrong
or
you
know
in
in
reality.
Maybe
there's
only
a
handful
of
people
that
actually
do
opt
into
it
until
we
actually
start
making
a
big
push
for
it.
So
I
think
yeah,
just
putting
the
toggle
behind
a
feature
flag
and
doing
some
level
of
rate
limiting
just
enough
for
us
to
like
we're.
A
Gonna
have
to
start
building
that
Foundation
anyways
for
you
to
view
and
like
billing
and
purposes,
anyways
I
think
that's
a
good
enough,
like
iteration
or
MDC
to
say,
hey,
there's!
This
will
get
us
the
majority
of
the
way
there
to
have.
You
know
a
decent
level
of
confidence
that
this
can
handle.
You
know
people
opting
into
it
without
us,
paying
too
much
attention
to
it
and
if
we
need
to,
we
have
a
fail
safe
and
just
we
can
shut
off
the
toggle
for
at
that
point,
so
I.
A
Because,
based
on
how
things
are
going,
it's
it's
probably
just
going
to
be
like
myself
and
and
Nell's
like
being
paged.
So
you
know
we
have
to
keep
bear
that
in
mind
as
well.
So
yeah.
A
A
Cool
did
that
answer
your
questions,
or
was
there
anything
else?
You
wanted
to
look.
B
Up
that
covers
it,
I
think
for
me.
I
just
want
to
make
sure
we
had
some
space
and
time
to
talk
about
that.
So
cool.
A
A
Cool,
then,
for
me,
it's
just
a
little
bit
of
a
read-only
but
I'll
verbalize
It
Anyways.
There
was
a
engineering
as
a
whole
wants
to
just
make
sure
all
Engineers
are
aware
of.
You
know
the
required
stops,
which
is
basically
an
upgrade
path
in
order
to
run
certain
migrations,
and
it's
could
arguably
more
backend
Centric,
but
it
can
influence
the
front
end
as
well
with
certain
changes.
But
in
some
cases
we
do
have
upgrade
paths
where
it's
not
easily.
A
It's
not
super
easy
to
just
go
from
any
version
to
another,
and
you
have
to
actually
make
required
stops
to
go
from,
let's
say,
for
example,
like
14.2.1
to
14.3.6
I'm,
making
these
numbers
up
these
doc
there's
documentation
on
it,
but
it's
just
as
a
refresher
to
everyone.
We
want
to
try
to
avoid
that.
We
also
want
to
avoid
you
know,
making
migrations
that
require
downtime,
and
things
like
that.
So.
B
A
Included
a
couple
links
here
just
for
the
engineers
to
kind
of
take
a
look
to
look
at
in
terms
of
required,
stops
and
avoiding
downtime
and
how
we
generally
approach
breaking
changes.
It's
a
good
refresher
for
myself,
because
I
totally
forgot
that
sometimes
we
have
required
stops
in
the
upgrade
path,
which
is
not
ideal.
A
A
You
have
to
run
these
five
versions
first
before
you
actually
get
to
the
version
you
want
to
go
is
not
ideal,
so
it's
good
to
think
of
more
Creative
Solutions
if
we
can-
and
it
talks
about
which
we've
done
in
the
past,
with
our
existing
columns,
for
example,
for
credentials
and
things
like
that,
as
we
just
got,
got
started
with
product
analytics
using
Jitsu
and
things
like
that,
where
we
ignore
columns
and
then
one.
C
A
Two
Milestones
later
we
eventually
remove
it.
So
there's
there's
definitely
ways
to
approach
this,
but
yeah
not
prepared
in
time,
but
I
wanted
to
call
this
out
since
James
Sam
and
the
rest
of
product
management
had
gotten
there.
Okay
I
was
done
on
time,
but
I
just
want
to
kind
of
thematically
highlight
what
we're
thinking
for
as
far
as
engineering,
which
I
think
is
mostly
in
line
with
what
James
is
thinking
so
just
calling
out
you
know,
of
course
we
want
to
get
out
to
customers.
A
We
want
to
figure
out,
what's
necessary,
to
actually
get
out
to
Beta
in
terms
of
performance
and
logging
and
making
sure
that
we're
able
to
have
the
Baseline
level
of
monitoring
to
be
able
to
say.
Okay,
things
are
going
down.
We,
the
health
checks
for
family.
We
need
to
shut
off
the
opt-in,
for
example,
as
well
as
the
cost
and
performance
analysis,
and
so,
as
I
may
have
mentioned,
to
some
on
privately,
but
I've
become
a
designated
Insider.
A
So
I
can
be
able
to
see
some
of
the
more
sensitive
information
to
help
out
to
see
the
costs
in
terms
of
like
being
able
to
help
James
and
Sam
out
with
the
pricing
strategy,
and
things
like
that,
but
as
well
was
being
able
to
see
how
much
we
can
squeeze
out
in
terms
of
once
we
actually
get
to
like.
A
As
we
went
through
the
billboard
review,
we
have
encountered
some
performance
issues,
but
then
how
can
we
balance
that
versus
you
know
the
performance
per
dollar
that
we're
spending
in
terms
of
cost
to
make
sure
that
we're?
You
know
when
we're
pricing
it
correctly,
but
two
we're
running
as
efficiently
as
we
can
and
of
course
it's
not
going
to
be.
We
we're
not
at
that
point
yet
where
we
would
want
to
want
to
over
optimize
on
performance
per
dollar.
A
But
you
know
we
definitely
want
to
keep
it
in
mind,
so
just
to
kind
of
laying
the
down
the
groundwork
in
terms
of
what
what
that
would
entail.
A
At
the
same
time,
we've
got
a
number
of
issues
outlined
in
the
beta
and
the
ga
epics,
but
you
know,
as
we
discussed
and
figure
things
out
as
we
meet
with
more
and
more
customers,
I
think
there's
going
to
be
a
general
sense
of
adding
more
filters,
adding
improvements
to
what
we've
built
so
far
and
how
we
can
you
know
optimize
in
terms
of
the
custom,
dashboard
experience
and
things
like
that,
so,
whatever,
whatever
polish
we
can
add,
as
we
kind
of
just
try
to
catch
up
on
the
infrastructure
side
of
things
but
yeah,
hopefully
we'll
have
those
okrs
later
this
week,.
B
All
right,
it
seems
so
good,
I'm
interested
or
excited
to
see
the
okrs
and
the
numbers
attached
to
the
cares.
A
Yep
sweet
me
too.
Awesome
then
show
and
tell
we
haven't
done
that
in
a
while
I
mean
I,
guess
you
know
it's
just
Ellen
not
to
put
you
on
the
spot
and
I
can't
I.
Don't
think
anyone
wants
to
watch
any
just
hit
play
on
a
CI
pipeline
to
see
a
environment
deployment
fail,
but
I
want
you
anything.
You
want
to
show
off
or
yeah
no
worries
cool
yeah.
We
should
we
should.
We
should
open
open
encouragement
to
anyone
watching.
A
You
know
record
a
demo,
maybe
see,
let's
see
what
you're
working
on
I
know.
We
talk
about
a
lot
of
the
issues,
but
it
might
be
good
to
see
you
know
when
we
got
error
States
into
the
panel
is
we're
adding
retries
to
to
panel
errors.
I
think
it'll
be
good
to
kind
of
help
demo
and
show
off,
and
we
can
use
that
to
eventually
generate
some
excitement.
A
Once
customers
are
able
to
get
their
hands
on
it,
but
yeah
cool,
then
we've
reached
the
end
of
the
agenda
we're
at
time,
but
is
there
anything
else
anyone
wants
to
cover
all
right?
Then
James
Owen
good,
to
see
you
too
and
good
rest
of
your
days
rest
your
week
and
thanks
for
whoever's
watching
the
recording.