►
From YouTube: 2020-05-21 meeting
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
B
I'm
I'm
Dave
from
Google
I'm,
actually
coaching
two
summer
interns
with
Google
to
work
on
the
open,
telemetry
collector
related
to
metrics.
So
that's
kind
of
why
I'm
trying
to
just
sort
of
catch
up.
My
main
work
at
Google
is
actually
a
UI
development
for
the
visualizations
of
our
metrics
and
some
like
schema
review
so
familiar
at
the
metric
space.
But
you
know
want
to
help
our
customers
get
metrics
into
our
system
better
and
they
can't
do
that
without
something
like
open,
telemetry,
yeah.
A
C
So
I
mean
so
I
came
from
Amazon
AWS
cloud
watching
so
actually
yeah
Mikey
its
basically
provide
yeah.
We
actually
devoted
to
clock
watch
agent.
So
that's
why
we
also.
We
are
trying
to
see
this
open
energy
community
for
the
metrics
part
to
see
how
we
can
migrate
or
help
our
customer
onboard
the
open
elementary
cool.
C
Actually
I
got
a
problem
I,
you
know,
I
have
a
question.
I
wanna,
ask
you
know
in
the
today's
meeting,
but
I
don't
know
so
in
cloud
watch.
We
also
support
a
format
called
so
you
know
we
can
put
the
metrics
into
the
structure,
lock
call
the
EMF.
So
basically
we
don't
want
that
measure
could
be
aggregate
and
you
know-
and
we
can
put
all
the
ROI
vents
into
the
structure
log
structure
to
log,
so
our
back-end
can
do
aggregation
or
customer
or
kind
of
stuff.
C
So,
from
the
current
thing,
I
know
we
we
have
the
review
API
that
is
ongoing,
but
I'm
looking
for
since
we're
in
the
POC
some
kind
of
prototyping
we
wanted.
I
won't
probably
want
to
see.
If
there's
a
way
I
can
send
a
data
over
to
front
SDK
without
doing
the
aggregation.
If
they're,
you
know
it's
not
possible
to
do
that
right.
Now.
We
without
a
view
API
supporting.
C
A
B
So
I
know
I've
been
thinking
about
that
a
little
bit
in
some
other
context
like
one
would
be
something
like.
Let's
say
you
have
a
lambda
function
or
a
web
browser.
That
is
really
only
writing
single
points
and
you'd
want
to
say
the
collector
to
act
as
a
source
of
aggregation
yeah
throughout
time,
and
you
know
it
gets
a
thousand
writes
in
a
minute-
writes
one
counter
for
all
thousands.
You
know
things
added
together.
Is
that
your
use
case?
Are
you
aggregating
away
a
field
like
you're?
C
B
C
Yeah,
the
lock
connections
are
purely
for
log
yeah,
it's
kind
of
similar,
but
we
put
a
metrics
into
logs
so
so
yeah,
even
without
considering
the
it's
a
login
equation
right
now,
I
I
want
you,
you
know,
I
see
you
know
in
matches
data
model,
if
I
can
just
put
all
the
wrong
event
into
the
current
match
within
a
model
and
I,
don't
do
I,
don't
I,
don't
generate
those
histogram
points
or
some
reports.
I
just
put
it
into
T
single
point
data
point
in
in
the
past
or
the
event
over
to
the
exporter.
C
B
C
So
we
don't
write
box,
we
still
want
those
a
mattress
event,
so
further
SDKs
I,
when
we,
when
the
customer
they
instrumented
it
generates
a
lot
of
the
metrics
raw
events.
We
want
to
keep.
We
don't
want
to
aggregate
them.
Just
have
all
those
metrics
then
come
all
the
way
to
the
collector
in
the
in
the
in
the
collector.
We
can
put
our
own
exporter
in
the
we
assemble.
We
assemble
those
relevant
in
our
own
way
in
in
the
Senate
to
our.
It
allows
to
again.
Yes,.
A
So
look
looking
at
the
spec
there's
two
types
of
instruments:
one
is
additive
and
one
is
non
additive.
So
if
you
want
to
send
raw
metrics,
you
use
the
non-additive
instruments
to
come
to
to
write
that
down
consent.
You
would
like
to
be
exactly
where
it
talks
about
that
yeah.
What's
it
looks
like
it
shouldn't
be
completely
fine
to
do
that.