►
From YouTube: 2020-10-07 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
A
Apparently,
something
happened
with
opened,
lengthy
calendar
and
this
meeting's
event
disappeared
from
the
calendar.
So
I
guess
people
are
going
to
miss
the
meeting,
probably
because
of
that
anyway,
let's
wait
a
couple
minutes
and
see.
A
A
A
B
B
So
we're
going
to
go
about
making
our
own
api,
and
one
of
the
things
we
need
to
do
is
figure
out
exactly
which
formats
of
logging
we
need
to
support.
So
we
made
this
rfc
just
so.
People
can
comment
like
different
like
ways
they
want
to
write
logs
like
if
they
want
to
just
write
a
string
or
like
a
structured
map.
A
B
Yes,
so
we
shared
it
with
riley
and
max
and
alelita
and
they're
all
good.
With
this.
A
Okay,
so
yeah.
Okay,
that's
good
from
the
format's
perspective
for
open
telemetry,
I'd
say:
two
formats
are
very
important:
one
is
json
and
json
as
it
is
described
in
the
overview
overview
vlogging
with
supposedly
with
trace,
ids
and
spam
ids
included.
If
they
are
available,
we
don't
have
a
precise
definition
of
in,
particularly
in
that
document
we
don't
have
precise
definition
of
what
keys
to
using
the
json.
What
how?
What?
What
exactly
is
the
structure
expected
structure
of
json?
A
But
I
think
it's
it's
very
natural
to
expect
it
to
look
like
the
json
encoding
of
open,
telemetry
protocol
or
tlp
protocol,
so
that
that's
a
very
specific
thing.
I
would
default
to
that
right
that
that's
obviously
that
matches
the
data
model
of
intelligent
trees
model.
It's
it's
well
defined.
It
exists
today.
I
would
aim
to
make
that
the
default
for
the
laundry
library
right.
B
A
I
I
I
I
don't
think
so.
Right.
C
Go
ahead
david,
you
want
to
add
something
so
so
I
think
what
I
would
really
suggest
is
making
sure
that
kind
of
internally
in
the
library
you
do
look
use
something
that's
kind
of
similar
to
the
the
log,
libra
or
lug
model
that
tigran
has
but
you're
kind
of
looking
at
three
different
levels:
right
you're.
Looking
at
the
user
interface
of
how
do
I
log
a
statement
you're
looking
at?
How
do
I
represent
that
internally
and
then
you
you've
got
some
way
of
getting
it
out
into
the
outside
world.
C
I
think
you
really
want
to
have
all
of
those
be
somewhat
distinct
and
modular,
so
when
it
comes
to
because
I
think
like
even
here,
I
think
we're
maybe
conflating
the
inside
input
and
the
output
so
in
the
output
definitely
model
on
kind
of
the
rest
of
the
open,
telemetry
stuff,
which
is
you've,
got
exporters,
and
so
that
exporter
will
take
the
the
internal
universal
format
and
we'll
translate
that
into
splunk
or
json
or
whatever
else,
and
that
that
makes
that
very
flexible
and
easy
to
change.
C
As
far
as
the
input,
if
you
have
somebody
build,
you
know
basically
an
hotel
struct
for
every
time
they
want
to
log
something
that's
going
to
suck
right,
yeah
like
that
yeah
and
and
so
for
that,
look
at
something
that
that's
more
ergonomic,
and
this
is
where
I'm
really
talking
about.
C
You
know
separating
these
three
things
right,
because
what
you
want
is
an
ergonomic
module
that
lets
you
do
the
things
you
expect
to
do
like
log.debug
string
and
then
that's
going
to
build
that
into
the
internal
logging
record
format
and
pass
that
off
to
an
exporter
conceptually
that's
kind
of
the
flow
that
we're
going
to
go
through
right,
and
so
that
way
you
can
overload
on
the
the
the
user
side,
because
we
kind
of
expect
to
be
able
to
say
log.debug
and
log.warn,
but
inside
the
actual
library,
that's
processing
it.
C
What
we're
actually
doing
is
we're
setting
a
flag
right
like
it's,
not
a
different
function.
It's
just
setting
something
up
in
a
convenient
way,
and
so,
like
definitely
think
about
those
three
things
in
different
ways.
You
know
just
put
on
different
hats
as
you
go
through
them
as
far
as
what
I
would
suggest
for
the
ergonomic
side
of
it.
C
Definitely
do
you
look
at
some
lugging
library
see
what
makes
sense
to
you,
but
open
telemetry
supports
a
rich
data
model
and
that's
actually
going
to
be,
in
my
opinion,
where
we
get
the
most
power
from
this.
C
So,
although
you'll
probably
want
to
have
a
log.debug
string,
also
make
sure
you
have
a
log.debug
string
map
or
you
know
like
an
attribute
set
right,
so
you
can
pass
in
the
attributes
that
are
then
going
to
get
put
into
the
right
place
in
the
structure
and
come
up.
So
you
know
that
again,
like
that's
a
little
bit,
why
we
want
to
look
at
it
in
different
hats
right.
C
A
Description
david.
Thank
you.
What
david
has
been
describing
the
structure
with
the
api
internal
representation
and
exporters
which
are
responsible
for
the
format,
is
how
today
open
chemistry,
sdks
are
done
for
this
for
the
traces
and
metrics
as
well.
So
that's
that's
a
very
good
advice.
Yeah.
D
C
So
I
I
wouldn't
so
as
soon
as
you
get
into
custom,
encoding
and
decoding
and
that
stuff
you're
gonna
start
pulling
your
hair
out.
So
I
wouldn't
start
there
like.
I
think
you
start
simple.
You've
got
some
sort
of
you
know
what
well,
what
I
would
do
is
I
don't
know
c
plus
plus
very
well,
I'm
afraid.
C
So
you
know,
if
you
take
a
look
at
what
the
protocol
buffers
is
going
to
generate
for
c
plus
and
you
build,
you
know
it's
going
to
be
kind
of
an
ugly
c
plus
plus
you
know,
because
it's
trying
to
do
something
for
everybody
right,
so
take
a
look
at
what
that
is
and
turn
it
into
something
that
makes
sense
in
c,
plus
plus,
and
so
you
know
some
sort
of
interface
there
and
then
use
that
as
kind
of
your
your
model
and
then
in
your
ergonomic
sides.
C
You
know
it
could
be
key
value
pairs.
You
have
a
var
sort
of
thing
where
you
can
pass
in
a
bunch
of
key
value
pairs
and
that
gets
because
that's
that's
going
to
be
the
most
common
use,
but
definitely
target
the
most
common
things.
First
and
then
kind
of
start,
adding
on
the
more
complicated
things
as
people
want
them
right.
C
You
know.
One
thing
you
you
definitely
should
should
think
about
is
some
way
to
to
fall
through
to
the
more
complex
cases.
So
if
that
means
that
you've
got
a
log
internal
struct,
that
means
that
somebody
can
always
do
whatever
they
need
to
do
they're
not
having
to
go
around
and
redo
everything,
so
so
definitely
have
back
doors
for
some
of
these
things.
But
you
know,
because
when
you're
trying
to
make
things
easy,
it's
really
easy
to
make
something.
A
Much
and
to
continue
on
the
formats,
so
one
is
the
json,
and
I
highly
highly
recommend
that
this
json
looks
like
whatever
otlp
protocol
would
output.
If
you,
if
you
encode,
if
you
travel
to
marshall,
to
reason
the
second
would
be
the
binary
for
above
right
and
then
you
would
obviously
want
to
have
a
network
exporter,
which
then
also
would
do
the
both
binary
and
json
formatted.
B
A
Is
also
completely
uniform
with
how
we
do
things
for
traces
and
metrics
today
for
for
network
network
exporting,
we
don't
really
write
traces
and
metrics
to
files.
If
we
wanted
to,
this
would
be
the
obvious
choice
for
us
as
well.
If
we
wanted
to
output
traces
in
amazing
format,
then
we
would
obviously
choose
this
and
in
fact
we
have
for
just
for
troubleshooting
and
for
debugging
purposes.
In
the
open
climate
collector,
we
have
what
we
call
file
exporter,
which
is
only
used
for
diagnostic
and
for
troubleshooting,
and
it
does
just
that.
A
It
outputs
traces
and
metrics
in
json
that
js
the
structure
of
the
json
comes
directly
from
the
open
to
entry
protocols,
diffusion
protocol.
C
A
Okay,
anything
we
can
help
you
with
or
anyone
else
in
other.
E
Topics:
hey
it's
ron
again,
I've
been
lurking
a
lot
just
I.
I
asked
a
couple
questions
and
I
just
wanted
a
real,
quick
kind
of
fix
on
it.
I
understand
this
stuff
is
baking
somewhat
slowly
in
some
areas
and
we're
very
willing
to
poc
and
test
as
a
kind
of
an
end
user.
E
You
know
whatever
you
do
have
one
question
I
asked
was
about
mobile
support
and
I
don't
know
how
much
that
science
fiction
it
does
seem
possible.
A
Mobile
support,
meaning
ability.
E
For
for
one
platform
for
android
or
android,
android,
yeah,
yeah,
android
and
ios
clients
to
send
traces
and
logs
via
a
gateway
into
some
in
internal
collector
or
something
else,
probably
probably
a
collector.
A
C
Yeah,
I
think
so
yeah
I
don't.
I
don't
think,
there's
anything
technically
yeah.
I
mean
obviously
you're
you're
sending
a
lot
more
network
stuff
whatever,
but
I
don't
think
there
would
be
anything
precluding
you
from
doing
that.
You
know
I
think
the
library
should
work
yeah,
I
know
go
ahead.
I
know
that
on
the
the
tray
side
we
have
kept
with
java
7
in
a
lot
of
ways
so
that
it
is
compatible
with
with
android.
I
also
know
that
we
don't
really
know
of
anybody.
That's
actually
doing
that
at
the
moment,
right
so
yeah.
C
So
it's
theoretically
supported
you
know,
I'm
not
the
one
that
is
in
any
way
an
expert
on
this
but
yeah.
I
believe
it's
theoretically
supported,
but
we
don't
really
have
anybody.
That's
that's
actively
doing
it.
E
C
My
next
step
is
building
an
otlp
exporter.
You
know
I've
got
some
other
priorities
at
the
moment,
so
it's
a
little
bit
slow,
but
I'm
gonna
be
trying
to
make
some
progress
in
the
next
next
spring.
Here,
okay,
great.
E
No
objective
c
support:
there
is
a
there
is
a
contrib
sdk
for
swift
and
yeah
and
the
guy
the
guy
even
said
that
he
intended
it
should
work
for
client
side
and
that
you
know
they
said
somebody
had
asked
a
question
like
well,
there's
a
bug,
I'm
not
it's
not
working
for
me
on
coin
on
client
side,
and
he
said:
oh,
that
was
an
oversight.
Here's
a
fix,
okay,.