►
From YouTube: 2021-07-22 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
C
C
Probably
remembered
it
yeah,
it
could
be:
oh
yeah
yeah,
it's
got
displayport
one,
two
three!
Those
are
the
speakers
that
it
shows
yeah
nothing's
plugged
in
though
all
right
so
yeah.
A
C
B
Okay,
cool
yeah-
I
was
just
poking
through
it
the
other
day,
because
I
was
like
all
right.
I
might
have
a
little
bit
of
time
to
start
helping
on
that,
and
so
I
was
just
going
through
the
spec
and,
like
it
didn't,
seem
like
drastically
off
at
all.
There's
like
some
minor
things
like
being
able
to
like
ask
for
an
instrument
or
stuff
like
that.
I
think
we're
maybe
added,
but
I
guess,
like
the
one
thing
I
was
going
to
ask
about
that,
didn't
dig
into
was
the
actual.
C
B
C
C
My
understanding
and
yeah
I
haven't
looked
at
the
spec
since
they
did
more
work
on
it
for
months,
the
well
that
histograms
are
available
like
they're
supposed
to
be
available,
but
you
can
push
it
off.
I
I
I
would
hope
that's
the
case
because
yeah
I
wouldn't.
I
do
well.
C
Yeah,
those
are
bad,
the
am
I
what
I
figure
we
should
do
for
those
is
one
they
wouldn't
be,
bundled
in
the
main,
open,
telemetry
sdk,
because
I
think
they
should
just
be
c
or
rust
and
let
that
do
it.
So
if
people
want
it,
they
pull
it
in
and
they
get
good
performance
out
of
it,
but
not
wanting
to
require
you
know,
building
c
code
or
rest
code
by
default,
okay
and
maybe
offering
an
erlang
histogram
by
default,
but.
B
C
C
A
B
C
I
think
so
so
I
guess
they
yeah.
If
they
don't
have
one
today,
then
they
have
one
next
week
so
they'd
be
able
to
approve
it.
Next.
B
B
C
B
C
A
I
mean
I'm
interested
in
in
helping
out
to
get
this
working
because
I
have
had
no
luck
any
other
way
getting
getting
spans
into
honeycomb
from
a
phoenix,
app,
well
phoenix
absent
that
and
well
okay,
I
have
the
basics
phoenix
span,
but
I
want
like.
I
want
function
level
ones
and
I
haven't
figured
out
how
to
do
that
yet,
and
I
thought
well,
maybe
opens
one
or
two
will.
Let
me
do
this
and
it's
like:
oh
wait,
that's
not
pretty
yet
and
anyway.
C
I
wonder
what
the
state
of
the
phoenix
example
is
that
needs
to
be
checked
on,
because
there
is
an
example,
phoenix
project
with
open
telemetry
that
should
have
instrumentation
with
inside
it
as
well
like
you
mentioned,
for
functions,
but
it
might
still
be
out
of
date
and
need
to
get
that.
I
don't
think
anybody's
done
it
to
one.
A
I
don't
feel
like
there's
some
automatic
spans
with
the
like
having
the
here's,
how
long
this
here's,
how
long
each
request
took
to
finish,
but
you
can't
see
like
if,
if
fulfilling
a
request
took
several
function,
calls
where
the
slowdown
happened,
like
you
can't
tell
why
it
requested
slow.
A
B
B
So
if
you
want
to,
let's
say
like
you,
have
a
call
and
it
comes
in
your
controller
and
then
that
controller
has
some
information
like
at
that
point
within
like
that
handler.
B
B
If
you
wanted
to
see
what
was
going
on
in
that
particular
what
the
time
was
on
that
next
thing,
you
would
then
do
like
a
tracer
dot
with
span
and
provide
that
information.
So
it's
not
like
completely
automatic.
The
only
thing
that
we
can
do
automatically
when
it
comes
to
telemetry
is
things
that
we
know
about
ahead
of
time,
and
there
is
another
part
of
the
ecosystem,
the
telemetry
registry.
B
That
has
the
capability
to
to
do
that,
along
with
the
open,
telemetry
telemetry
bridge
library,
but
it
requires
people
to
add
module
attributes
that
had
define
what
the
what
the
telemetry
events
are
ahead
of
time.
B
C
A
And
the
telemetry
decorator
package
is
based
on
the
built-in.
Oh,
it's
like
the
built-in
beam
telemetry
and
it's
you
put
a
decorator
on
your
function,
and
that
makes
it
the
same
as
putting
a.
B
A
Yeah
yeah
that
that
didn't
work
with
the
built-in
using
telemetry
decorator,
with
the
built-in
thing,
and
so
I
was
like
okay,
maybe
I
need
to
try
a
different,
a
different
protocol,
and
so
I
was
like
okay,
maybe
try
doing
open
telemetry,
but
I
asked
on
I'd
asked
in
the
slack
about
whether
there
was
1.0
open,
telemetry
support
yet
for
doing
stuff
with
phoenix,
and
the
answer
was
no,
and
so
I
was
like.
Okay,
can
I
help.
C
Okay
yeah,
so
there
is,
I
mean,
there's
1.0
the
release
candidate,
which
is
pretty
much
1.0.
I
might
as
well
cut
1.0,
but
with
phoenix,
I'm
pretty
sure.
That's
just
that
works
and
is
basically
I
mean
1.0
the.
So
it's
just
a
matter.
I
think
there
is
just
some
miscommunication,
but
you
can
use
the
open.
Telemetry
function,
calls
directly
in
your
application
code
to
add
additional
spans
to
to
your
phoenix
project.
Yeah.
B
We
have
to
know
like
what
those
are
and
we
have
to
like
do
all
this
wiring
up
that
like
listens
for
those
events
and
then
like,
starts
and
stops
spans
on
behalf
of
the
user.
So
if
you
look
at
like
the
source
code
for
the
open,
telemetry,
phoenix
library,
if
you
look
in
there,
you'll
see
how
how
that
kind
of
works
of
like
listening
for
events
and
then
like
how
we
start
and
then
span
based
on
them.
But
that's
all
that
wiring
up
is
necessary.
B
C
Yeah
the
examples
on
the
open,
telemetry
website
definitely
need
more
docs.
So
if
you,
if
you
start
going
through
things
and
find
things
that
don't
work
or
confusing
a
huge
help,
would
just
be
even
letting
me
know
or
or
requests
of
but
yeah,
so
my
suggestion
yeah,
I
think
you
were
going
in
the
right
direction
of
open,
telemetry
trying
and
calling
it
directly
after
you.
You
said
you
had
the
integration,
the
open,
telemetry
phoenix
working
like
you
get
spans
for.
A
No
so
I
had
I
had
the
the
theme
telemetry
built-in
default
thing
that
phoenix
has.
C
C
A
When
I
tried
to
use,
I
attempted
to
use
cylindrical
decorators
to
get
more
specific
stuff
from
that
that
didn't
work.
So
I
started
looking
around
for
one
of
the
other
options
and
hemophone
open
telemetry,
and
I
was
like
okay,
maybe
this
thing
and
then
saw
that
it
had
that
1.0
for
the
protocol
had
just
been
announced
at
that
point.
Okay
and.
C
Yeah
names
are
confusing
now
I
now
I
understand
where
now
I
understand
the
progression:
okay,
yeah
so
yeah.
There
is
open
telemetry
support
for
phoenix
for
turning
those
phoenix
beam,
telemetry
events
into
spans-
I
don't
know
we.
I
don't
think
we
have
a
guide
for
that.
Really
though,
but
it's
technically
exists
in
the
library,
so
I
think
that
I
guess
would
be
the
first
place
and
I
can
link
to
that
library
in
slack.
I
haven't
used
it
myself,
but
there's
other
people
in
there
that
have
so.
B
Yeah,
all
you
have
to
do
is
include
the
library
and
then
in
your
application
file
in
the
top
of
the
supervision
tree
on
start,
you
would
just
say
open,
telemetry,
phoenix,
dot
setup
and
for
a
knit
it's
one
of
the
two.
It's
just
an
ecto
does
the
same
thing,
so
you
have
to
like
kind
of
just
call
for
them
to
set
up
and
when
you,
when
you
do
that,
it
will
automatically
wire
everything
up
for
you.
B
As
far
as
collecting
the
spans.
You
still
need
to
do
like
the
normal
stuff
for
like
setting
up
an
exporter
and
whatnot
and
there's
a
base
basic
guide
on
the
open,
telemetry
telemetry.io
site
for
the
erlang.
That
has,
you
know
like
a
very
basic
like
here's.
How
to
export
to,
like,
I
think,
to
sdd
out,
probably
or
pid.
A
Hopefully,
we'll
talk
more
on
slack
about
how
this
stuff
works.
Yeah.
B
Awesome
all
right
see
you
later,
hey
tristan.
I
still
did
you
see,
I
put
the
thing
up
for
the
contrib
library
or
the
repo
just
like
come
up
with
a
convention
and
then
start
migrating
everything
over.
B
Do
you
have
do
you
know
if
you're
they
put
the
approvers
as
the
as
approvers
still
but
there's
like
and
earlying
maintainers,
and
then
some
of
the
other
languages
have
also
done
like
a
contrib,
maintainers
sub
team.
Okay,.
B
B
Library
for
no
but
like
say
like
for
rabbit
mq,
there
might
be
a
rabbit
and
q
propagator,
because
the
headers
are
custom
right,
okay,
yeah
but
like
it
seems
like
the
instrumentation
tended
like
in
the
other
languages,
particularly
like
javascript,
to
be
one-to-one
with
certain
frameworks
and
plug-ins
and
stuff
so
happy
year
express
or
something
like
that,
and
so
it
seemed
like
our
bridges
would
kind
of
fit
that
mold
yeah.
B
C
C
B
But
yeah
I
was
looking
at
the
other
day,
just
because
I
was
gonna,
put
some
propagators
in
for
like
rabbit
and
then
just
to
start
getting
it
all
under
one
spot
and
make
it
a
little,
maybe
start
getting
this
on
a
path
to
like
for
it
to
be
a
little
bit
less
confusing
for
folks
as
to
like
what
what
each
thing
actually
does.