►
From YouTube: Building API Endpoints (CHAOSS Workshop Part 1)
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
All
right,
so
this
is
building
api
endpoints
and
the
first
part
is
you're
developing
a
query.
That'll
produce
data
needed
to
deliver
the
endpoint,
usually
that's
parameter
parameterized
by
a
repo
id
and
then
determining
if
the
endpoint.
A
A
Essentially,
I'm
just
doing
this
to
remind
myself
how
how
markdown
syntax
works
all
right,
so
the
our
endpoints
are
located
under
the
auger
directory
in
your
agar
repo,
and
so
where
are
the
endpoints.
A
C
A
Metrics,
that's
the
folder
that
they
are
in
and
inside
of
there
there
are
metrics
that
that
are
organized
by
the
kind
of
information
that
they
find.
A
A
All
right,
so
these
are
the
existing
metrics
for
that
return,
json
as
its
product,
so
we
also
have
existing
metrics
that
return
visualizations.
A
A
Contributor
contributor
reports,
dot,
pi
and
pull
request
reports,
dot,
pi
and
the
fundamental
difference
is
between
these
metrics
and
others
is
that
they
deserve
to
deliver
a
visualization.
So
if
I
was
to
give
you
an
example
of
what
that
means,
I'll
stop
the
share
here,
a
minute
and
I'll
share
a
firefox
screen.
A
A
A
C
A
A
A
C
A
Unexpected
character?
Okay,
so
I
don't
have
a
working
example
of
that
right
now
we
are
actively
developing
those,
but
let's
see
if
I
can
get
one
to
work,
I
had
a
bunch
of
ones
that
were
ready
to
demo
and
then
I
had
a.
B
A
A
For
those
I
know
andrew
is
working
on
a
better
error
message
so
and
also
optimizing
those
I
did
have
a
bunch
that
I
had
that
I
knew
were
working,
but
one
of
my
servers
went
down,
and
so
I
don't
have
a
super
good
demo
for
that
right
now,
apparently
so
the
contributor
reports
that
pi
and
pull
request
reports
dot
pi
are
the
ones
that
deliver
contributor
so
like
this
is
basically
it
imports
a
lot
of
things,
but
then
it
also
imports
these
visualization
libraries
and
that's
good
to
know.
A
I
will
I
will
come
back.
Let
me
let
me
pause
resume.
Recording,
so
visual
and
ap.
The
visualization
apis
have
have
different
routes.
If
it's
quarters
month
year,
the
specified
new
contributor
data
collection
gets
all
the
new
contributor
data.
That's
a
method,
months,
data
collection.
This
is
a
query
and
then
this
is
a
method
for
the
server
app
route
of
new
contributors,
and
if
I
make
this
a
little
smaller-
and
I
do
a
few,
if
you
can
wrap
text.
A
You
can
sort
of
see
the
whole
thing
and
it
basically
delivers
a
visualization
bar
chart
and
looks
like
it's.
A
A
A
A
Have
like
for
the.
A
Yeah,
for
some
reason,
I'm
I'm
issuing
it
wrong.
So
I'm
not
not
getting
the
endpoint
to
return
right
now,
but
it
I
will
have
demos
of
it.
Returning
very
shortly.
A
Yeah
well
we'll
move
on
from
there,
so
the
commit
the
existing
metrics
are
in
these
files.
A
For
so
the
routes
directory
contains
the
contributor
reports,
the
pull
request
reports,
and
then
we
do
have
non-standard
metrics,
which
give
essentially
licensing
information
that
are
used
by
the
licensing
pages
so
license
id
spdx
boundary
repo
id,
and
so
this
is
for
the
risk.
That's
mostly
what
our
non-standard
metrics
are.
We
also
have
some
pull
request:
collection,
status.
A
So
these
are
good.
These
are
good
examples.
Like
the
issue
message,
there
isn't
a
one
for
messenger
platform
yet,
but
pull
request.
These
repos
will
return
the
json
that
you
could
then
build
front,
end
information
off
of
or
reports
off
of
and
as
we
perfect
our
visualization
api
and
I
think,
there's
just
a
deployment
issue
that
I've
created.
A
I
haven't
set
boca
to
a
specific
version,
so
I
may
be
using
the
wrong
version
of
bokeh.
I
need
to
make
a
note
of
that
for
myself.
A
A
A
A
A
A
A
A
A
Standard
metrics
also
generally
include
default,
setting
in
blocks,
so
in
the
event,
parameters
are
not
passed
so.
A
There's
a
little
bit
of
a
there's
some
documentation
here,
but
the
default
settings
are
essentially
this,
so
it
sets
the
begin
date
to
the
beginning
of
time
and
it
sets
the
end
date
to
the
end
of
time.
If
no
date
window
is
passed
so.
A
Yeah
and
then
it
they
typically
so
default
setting
blocks
for
date
range
in
the
event.
Parameters
are
not
passed,
so
it
gives
you.
You
know,
if
not
begin
date.
It
does
that
and
then
I
don't
know
why
it's
being
bad
to
me
right
now,.
A
And
then,
typically
the
you
can
get
that
you
can
get
the
metrics
for
a
repo
group
or
a
repo,
but
more
and
more
we
just
rely
on
calling
a
repo.
A
However,
so
there
is
also
generally
a
block
and
a
standard
metric
for.
A
A
A
A
A
Yeah
it
is,
it
was
just
the
word
wrapping
and
so
else
so
you
can
see
if
repo
id,
then
it
does.
This.
A
A
And
then
else,
if
this
would
be
the
case
where
it's
not
the,
so
this
is
what
gets
returned
if,
if
the
repo
id
is
specified.
A
Else
it
does
it
it
does
this
query
and
I'll
truncate
that
one.
A
And
then
it
turns
that
returns
those
results.
So
that
gives
you
an
idea,
there's
just
basically
a
strategy
that
we
use
for
writing
the
query
so,
and
the
visualization
metrics.
A
A
So,
let's
see
all
standard
metrics
include
shares
definition,
method,
signature.
A
Imports,
and
so
those
are
at
the.
C
A
C
A
A
So
if
you
want
to
know
what
the
register
metric
is
actually
doing,
that's
that's
where
you
can
find
it
so
does
that
make
sense,
yeah.
B
A
So
essentially,
this
kind
of
explains
like
what's
there
where
they
are,
what
kinds
of
structure
they
follow.
These
are
the
visualization.
C
C
A
A
A
A
And
so
now,
I'm
in
the
directory
for
doing
for
doing
this,
I'm
in
the
wrong.
B
A
A
B
A
A
There's
always
some
errors
in
the
make
development,
because
we
have
oops,
we
have
some
documentation
partially
developed
that
we
don't
publish
just
yet
so
development
guide
create
a
metric
parts
of
an
auger
endpoint,
and
so
this
is
what
we
were
just
editing.
A
A
All
standard
metric
share
declaration
and
a
method,
signature
and
standard
metrics
also
generally
include
a
default
setting
blocks
and
it
includes
default,
setting
blocks
for
date
range
and
the
event
parameters
are
not
passed.
So
something
like
this.
A
Oh,
oh,
thank
you.
Thank
you.
Do
this
all
the
time,
so
all
right
going
back,
so
you
can
see
what
we
built
is.
If
I
go
back
home
to
auger
under
the
development
guide,
I
have
now
a
create
a
metric
section
and
parts
of
an
api
endpoint,
so
developing
the
query
that
will
produce
data
needed
to
deliver
the
endpoint,
usually
parameterized
by
repo
id
and
then
determining
if
the
endpoint
will
be
a
standard,
endpoint
or
a
custom
endpoint.
A
So
where
are
the
endpoints
there's
the
json
metric
json
metrics
are
here.
These
are
metrics
that
return
json
data,
auger
home
metrics
and
visualization
metrics
are
here
the
existing
json
metrics
are
in
these
files
and
these
are
standard
metrics.
All
the
standard
metrics
generally
share
this
set
of
imports,
and
you
can
see
that
one
of
the
imports
is
our
standard
metric
import
from
the
util
file,
which
is
located
under
auger
home
auger
routes.
Util.Pi
all
standard
metrics
also
share
a
declaration
and
a
method
signature
as
we
said,
register
metric.
A
This
is
the
method
signature
that
they
share,
and
then
they
also
include
the
default
setting
block
for
date
range
and
the
event
that
event
parameters
are
not
passed
basically
from
the
beginning
of
time
to
this
moment
in
time,
1970
being
the
beginning
of
time
for
computers-
and
here
is
an
example,
a
truncated
example
of
a
block
of
of
how
the
queries
are
written
in
this
is
from
the
contributor.pie
endpoint.
A
A
A
The
files
all
together
are
not
intended
to
be
to
be
all
inclusive,
rather
they're.
What
we've
developed
or
imagined,
based
on
existing
chaos
metrics
to
date,
nucleus
metrics,
are
likely
to
result
in
the
inclusion
of
new
files
under
metrics
or
routes
depending
if
they
are
standard
metrics
or
not.
So
we
generally
put
standard
metrics
under
the
metrics
folder
and
non-standard
metrics
under
the
routes
folder.
B
C
A
This
is
parts
of
an
auger
api
endpoint.
I
probably
want
to
create
a
file
called
how
to
you
know,
steps
for
creating
a.
A
A
A
C
C
C
A
A
A
Which
is
true
and
and
so
then
the
question
is.
A
A
A
A
Metrics
steps-
I
don't
remember
if
that's
what
I
called
it
in
the
table
of
contents,
so
I
will
go
back
and
look.
I
did
call
it
metric
steps.
How
about
that?
I
also
noticed
notice
that
I
put
metric
steps
ahead
of
api
development
steps
to
create
a
metric
api.
Endpoint
is
probably
what
I
want
to
call
that
and
then
I
probably
want
to
have
a
line.
A
A
A
C
A
I
I
called
it
slightly
a
different
name,
and
so
the
build
didn't
pick
it
up.
So
I'm
just
gonna
do
this
one
more
time.
I
won't
bother
showing
you
the
construction,
but
restructured
text
is
okay,
restructure
text.
I
didn't.
I
used
an
s
in
one
in
the
document,
but
not
in
the
table
of
contents.
So
steps
to
create
an
api
endpoint
are
listed
here.
A
And
I
thought
I
deleted
that,
but
maybe
I
didn't
so
what
do
we
want
to
develop?
Sometimes
there
are
metricon
points
that
integrate
provisionalized
metrics
several
metrics
determine
the
tables
construct
a
very
basic
query
that
does
the
work
of
joining
those
tables
in
some
minimum
ways.
You
have
a
baseline
query
and
then
refine
the
query
so
that
it
takes
standard
inputs
for
a
standard
metric
and
then
the
next
page
is
parts
of
an
auger
api
endpoint.
A
A
A
A
A
A
Oh
sorry,
thank.
A
You
so
I'm
just
looking
at
other
examples
of
indentation
and
a
lot
of
it
just
isn't
too
terribly
straightforward.
So
what
tables
we
might
use.
A
B
A
B
A
A
So
create
a
metric
steps
that
actually
worked.
So
this
is
like
a
first
cut
at
building
that
that
query.
But
what
does
that
query
do
well
find
that
out?
We
would
go
to
some
kind
of
query
tool.
I
use
navicat
premium
and
say
connect
to
a
lot
of
databases.
This
is
that
exact
query,
and
if
I
run
it,
what
I
get
is
for
each
repository.
A
A
Fifty
dollars
an
hour,
so
you
can,
you
could
parameterize
like.
If
I
was
going
to
make
this
into
an
end
point
and
somebody
should
you
could
make
labor
cost
a
parameter
that
you
put
in
and
you
could
also
make
minimum
labor
hours
a
parameter.
So
I
take
the
average
code
complexity
times.
The
sum
of
code
lines
plus
20.,
the
average
code
complexity
is
seldom
zero.
A
So
and
we
don't
have
that
problem,
but
we
want
to
make
sure
that
basically,
we
don't
have
a
zero
value,
so
the
code
complexity
will
ratchet
up
or
down,
and
we
may
look
at
the
metric
as
it's
defining
chaos
and
decide
that
there's
different
calculations
that
we
want
to
use
right.
This
is
just
the
current.
A
This
is.
This
is
like
my
current
first
cut
right
at
a
metric,
all
right
and
so
over
time,
because
there
isn't
one
for
labor
cost
in
chaos
right
now.
So
over
time,
oops.
B
A
Yep
and
then
once
we
then
the
next
next
thing
we
do
is
we
will
fit
this
metric
into
one
of
the
different
types
of
metric
api
endpoints
discussed
in
the
next
section,
so
it
kind
of
it
starts
with.
What
do
you
want
to
build
a
metric
for?
Is
there
a
chaos
metric?
A
Are
you
going
to
integrate
several
metrics?
Then?
What
are
the
tables
involved
and
you
construct
a
basic
query
that
joins
those
tables
and
then
refine
it
so
that
it
takes
the
standard
inputs
for
a
standard
metric?
If
that's
what
people
are
looking
for-
and
I
might
say
this
step
is
explained
in
the
next
section.
C
A
So
obviously,
compiling
and
going
through
the
effort
of
making
an
endpoint
isn't
something
that
we
can
do
in
in
two
hours,
because
there's
going
to
be
a
lot
of
back
and
forth
and
debugging.
But
this
gives
you
all
of
the
steps
that
you
would
require
to
create.
That
end.
Point.
B
A
B
B
A
And
I
think
it'll
help
a
lot
of
other
people
who
want
to
create
metrics
in
the
future
as
well.
Do
you
have
I'm
gonna
stop
recording
right
now,
just
so,
you
can
ask
whatever
questions
you
might
have
and
it
doesn't
have
to
be
recorded.