►
From YouTube: Extensions and Telemetry WG - 2021-05-05
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
So
yeah
hey,
I
was
on
mute.
I
did
so.
I
just
had
a
guy
who
keeps
pestering
about
how
to
use
a
envoy
extension
in
istio,
and
I
realized
we
have
no
a
very
limited
documentation
for
the
envoy
filters
and
if
we
I
mean
we
need
to
get
people
to
try
these
envoy
things.
So
we
know
which
enway
things
to
make
apis
for.
B
A
B
Yeah,
so
there
is
a
wiki
page
devoted
to
envoy
filter
examples-
oh
great,
oh
and
quite
just
listed
it
there.
Let
me
add
that
to
the
notes.
Thank
you.
B
So
I
I
don't
know
if
there's
one
for
direct
response
there,
but
that
is
the
place
we
should
probably.
A
B
I
think
that
that
wiki
page
probably
needs
to
be
cleaned
up,
because
I
think
there's
probably
tracing
and
logging
examples
there
that
need
to
be
updated
too,
but,
but
I
think,
you're
right.
So
we
should.
We
should
make
that
more
findable,
but
that's
the
place
to
put
it.
A
I
I
have
one
more
thing
I
want
to
mention.
Okay
short,
so
I've
been
getting
more
into
the
tracing
stuff.
I
the
our
example
for
how
to
set
up
jager,
doesn't
use
correct
for
jaeger
which
confused
me,
although
you
don't
really
need
to
do
it.
So
I
mean
it
probably
was
operator
error,
but
part
of
it.
A
Was
this
confusing
thing
and
also
I
looked
at
the
latest
jager
and
it
doesn't
work
I'm
following
up
on
that
with
the
jaeger
people,
but
so
anyway,
I
guess
I'm
trying
to
make
myself
more
of
the
distributed
tracing
guy
and
I'm
gonna
be
making
a
couple
doc
prs
to
fix
that.
B
A
A
But
the
instructions
for
an
external
yeager
are
wrong
and
that
they
define
a
jaeger
that
uses
the
the
spans
delivered
by
thrift
and
not
the
jaeger
that
for
spans
delivered
by
zipkin,
so
that
that
documentation,
piece
that
installs
jager
is
as
a
service
is
wrong
and
we
need
to
fix
it.
A
But-
and
I
also
wanted
to
upgrade
to
the
latest
release
jaeger
and
that
also
doesn't
work
so
we're
using
120
121
works.
122
does
not-
and
I
am
in
communication
with
the
some
jaeger
folks
at
redhead
about
that.
B
Okay,
yeah
I'm
interested
in
the
results
of
why
122
does
not.
I
had
noticed
that
we
were
a
couple
releases
behind
in
our
samples,
but.
A
Myself
and
I
think
jersey
from
the
red
hat
team
found
the
commit
and
it's
a
bunch
of
command
line,
change,
option
changes
like
I
don't
know
if
it's
for
a
good
reason,
but
they
changed
their
flag
format.
So
it's
it's
likely
that.
B
Okay,
well,
thank
you
for
owning
that.
That's
a
big
help.
I
think
I
think
we
have
tested
tests
with
zipkin
end
to
end,
but
I
don't
think
we
we
did
both
and
so
maybe
it's
time
we
have.
B
A
B
Just
amplify
that
and
also
put
a
jager
in
so
if
you
already
have
an
issue
for
that,
maybe
we
can
add
that
to
that
work.
Maybe
this
is
something
for
the
roadmap
discussion
too,
which
is.
A
B
B
Okay,
I
had
after
last
time's
discussion
about
host
header
fallback.
I
wrote
up
this
this
doc.
You
can
open
it.
I
think,
let
me
see
if
I
can
share
it.
I
was
just
trying
to
sum
up
our
conversation
in
you
know,
sort
of
a
one
or
two
page
format.
I
think
we
have
general
agreement
on
disabling
it,
but
I
think
we're
preferring
doing
it
for
ingress.
Only
so
I
know
jay.
B
Maybe
this
is
something
that
might
impact
you
know
just
in
terms
of
things
users
might
see,
so
we
have
to
come
up
with
a
good
set
of
release,
notes
explaining
the
difference.
I
think
this
is
something
we're
going
to
move
forward
with.
So
I
just
wanted
to
mention
that
here
follow
up
on
our
discussions
from
last
week.
Okay
I'll
take
a
closer
look
at
this
one
and
see
what
I
see
great
okay,
yeah
and
the
only
deadline
on
that.
B
Isn't
I'd
like
to
get
it
in
before
the
cut
off
on
the
11th,
so
it
gets
into
the
110
release,
but
that's
a
couple
days
away
and
then
the
other
thing
that
we
have
to
present
next
week
is
just
our
the
roadmap
things
we'd
like
to
get
done
in
the
next
release.
B
These
are
the
ideas
that
came
up
last
week,
so
I
just
wanted
to
circulate
them
again
and
see
if
there's
anything
else,
that
people
believe
we
should
be
working
on
or
fleshing
out
or
addressing
you
know,
ed
you're
mentioned
in
testing,
I
think
is,
is
important.
So
I
put
that
down
here
now,
but
but
are
there
other
telemetry
related
issues?
I
know
for
the
telemetry
api
right.
We
want
to
include
metrics
and
logging
potentially.
B
B
Okay,
well,
I
guess
if
there
are
no
items
that
are
that
are
burning,
then
we
should
maybe
just
adjourn,
and
I
will
type
that
up
into
a
more
cool.
You
know
more
filled
out
bit
of
information
for
the
toc
and
then
present
them
on
monday.
B
So
I
guess
that's
it!
That's
that's
all!
I
really
wanted
to
discuss
as
a
group
unless
there's
anything
else.
Maybe
we
should
just
adjourn.