►
From YouTube: 2023-03-20 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
A
A
B
No
in
town
for
srecon
and
I
came
a
day
early
to
cause
trouble
for
people
at
the
servicenow
offices.
So
that's
where
I
am
there's
like
a
zoom
thing
in
here.
I,
don't
know
how
to
use
it.
D
E
Good
good,
it's
first
time
on
joining
this.
This
group,
but
I
just
wanted
to
stop
by
and
say
hello,
welcome,
awesome.
D
F
D
F
Probably
probably
not
too
much
to
cover,
but
Martin
is
able
to
join
us,
which
is
really
nice,
he's
a
developer
from
light
staff
that'll
be
helping
out
on
the
front
end,
which
I
think
we
all
appreciate.
Yes,
very
much
so
Giuliano
I'm,
not
sure.
If
you
have
anything
top
of
mind
on
the
front
end
I
know
you
have
that
issue
and
and
he'll
be
making
some
some
progress
on
that.
If
there's
anything,
if
you
have
a
wish
list,
Now's
the
Time.
C
Okay,
well
I
I
I
have
actually
the
I
have
one
issue
that
I
linked
all
the
issues
that
I
found
when
I
was
like
navigating
through,
but
from
the
top
of
my
head
things
that
I
I
noticed
like
whenever
I
run.
The
demo
is
so
whenever
we
add
item
to
the
cart,
when
we
go
to
the
checkout
page,
we
have
the
the
shipping
cost
that
that
works.
C
A
F
C
A
B
So,
on
that
note
like,
if
you
go
to
the
demo
and
then
filter
to
1.4
I
did
go
through
this
yesterday
and
unless
there's
something
that
I'm
missing
or
something
that
someone
else
feels
is
like
super
important
I
feel
like
this
is
this
is
our
slate,
so
there's
actually.
B
Issues
right
now
that
are
front
end
I,
think
327
is
where
the
most
is
is
a
big
gnarly
one
with
a
ton
of
like
Little
Things
616
is
pretty
straightforward
and
710
is
pretty
straightforward.
With
the
dependency
update,
I,
don't
know
this
792
feels
like
it
might
be
pretty
straightforward.
B
B
B
B
This
just
seems
like
gonna,
be
dragons
here
and
then
749.
E
D
E
A
E
I
guess
here
like
if,
if
that
request
fails
like
does
the
UI
need
to
respond
to
that
somehow,
like
yeah.
B
Yeah
there
might
be
something
like
I,
don't
actually
feel
like
if
this
is
a
way
like
because
there's
the
the
failures
would
be.
What
in
this
ad
item,
get
cart
and
so
like
those
could
fail
independently
and
I
would
still
expect
this
to
succeed,
this
post
succeed,
but
that
also
sort
of
feels
like
a
HTTP
200
return
to
error,
successfully
type
shut,
which
yeah
I
don't
know.
C
I
think
the
issue
there
is
that
online
50
well
I,
think
I
I
can
share
here
on
the
on
the
chat,
foreign
so
line
51
and
lines
58.
They
have
the
status
set
there
yeah,
so
it
it
returns,
200
and
204.
Even
if
the
get
carton
fails
or
something
like
that.
B
E
B
D
C
Four
yeah:
there
is
a
lot
of
small.
F
E
Yeah
I
think
I
think
so
so,
like
it's,
it's
a
lot
of
small
things
like
is
there
I?
Guess
if
I
understand
what
you
want,
you
want
everything
all
of
these
to
be
addressed
for
the
1.4
race.
F
D
B
That
big,
the
big
Omnibus
one
like
if
it
helps
you
can
always
split
that
out
into
more
issues
like
there's,
something
that
is
just
thornier
than
yeah.
That's
super
thorny!
You
can
just
split
it
out
and
we
can
go
from
there.
C
Also
in
the
in
this
one
that
I
have
a
list
of
things.
If
you
wanna
split
and
say
hey
this
one
and
this
one
are
actual
bugs
and
the
other
ones
are
Improvement
that
I
I
wouldn't
mind.
If
we
push
the
improvements
through
later
because
it's
like
image
resizing
and
whatever,
like
yeah.
B
D
E
C
F
F
Is
yeah
we'll
get
there?
I
guess
one
thing:
they
call
out
so
I
open
a
pull
request
to
reduce
the
capca
memory
print
to
512
from
750.
I'm,
not
sure
I
need
computer
test
it
on
his
cluster,
but
I'm
not
sure
we'll
put
it
Go
much
further
below
that.
I
did
just
some
basic
Google
research
and
it
seemed
like
512
was
kind
of
the
minimum
memory
requirement
unless
I
don't
know,
there's
another
image
out
there.
That's
that's
more
efficient.
F
B
I
mean
I
feel
like
this
needs
to
be
flying
the
issues
needing
a
film
update.
A
B
I,
don't
know
why
okay.
D
B
B
I
saw
like
292,
but
I
see
well,
it's
like
this
actually
explains
it
is
the
span
metrics
it
up,
which
is
understandable,
I'm
inclined
to
I'm
inclined
to
pull
it
to
to
pull
it
in
as
a
base,
just
because
I
think
that
it's
good
to
have
stuff
that
helps,
explain.
I.
Think
it's
good
to
have
signed
posting
for
people
right.
B
C
Yeah
I
just
didn't
comment
anything
yet
because
I
haven't
tested
out,
but
I'm
I
like
it
like
the
the
screenshots
and
stuff
so.
F
C
Well
for
art
service
I
think
he
just
adds
the
environment.
B
F
Yeah
I
mean
I
think
we
have
to
have
it,
but
we
should
probably
talk
about
how
we
want
to
use
it,
but
at
the
same
time,
just
like
adding
basic
support
can
be
altered.
You
know
down
the
road
too,
so.
F
C
I
would
love
to
discuss
with
you
guys
what's
up
the
the
log
back
end,
what.
C
C
B
C
C
I
think
at
the
moment
we
do
not
have
I,
don't
think
open
search
actually
supports
otopia
at
the
moment,
so
it.
B
A
B
E
B
C
To
to
to
have
in
mind
because
yeah
it
as
soon
as
we
start
getting
more
logs,
more
otlp
logs
into
the
services,
we
want
to
show
this
somehow
somewhere.
B
I
think
we
can
yeah
I
would
feel
comfortable,
saying
like
we're
not
until
there
was
a
open
source
logging
DB,
slash
whatever
that
natively
supports
otlp
ingest,
then
we're
not
going
to
bundle
one
in,
but
if
you
want
to
like,
but
we
are
going
to
collect
the
logs
via
otlp
and
be
a
scrapers
and
whatever
put
them
into
a
collector
and
create
a
logging
Pipeline.
And
then
you,
you
know:
here's
how
you
connect
it
to
Blue
right
yeah,.
A
B
B
B
B
To
be
some
confusion
around
it,
but
if
that's
the
flip
side
of
it,
then
we
should
just
bundle
low
key
and
be
done
with
it
right,
because
Loki
will
handle
trace
and
log.
We
should
bundle
like
Loki
and
Es
and
just
be
like
all
right,
because
that's
from
a
open
source
perspective
like
that
is
the
play.
You
know
that
is
one
of
the
plays
like
that.
Maybe
isn't
yeah
foreign
S
I
guess
is
my
problem
and
there's
no.
It's
the
ncf
thing
that
we
can
just
slot
in
here
to
deal
with
this.
F
F
Yeah
I
think
I'm
fine
with
it
to
figure
out
where,
to
put
it,
put
it
or
put
the
data.
C
Yeah
I
I
already
tried
out
just
yeah
waiting
for
more
than
one
approval.
Yay.
B
I
looked
so
I
looked
at
791
yesterday
as
well.
I
feel
like
the
bug
here.
Is
that
I
don't
think
GitHub.
B
Fine,
like
my
my
supposition,
is
that,
for
whatever
reason
the
yamlet
config
is
not
being
picked
up,
but
when
it's
running
to
GitHub
actions,
and
so
maybe
we
just
need
to
explicitly
spell
out
the
path
of
a
config,
so
I
imagine
Pierre
will
get
the
best
when
he
gets
back.
I
took.
F
F
B
B
It's
kind
of
action
should
get.
Action
should
run
off
of
whatever's
in
the
branch,
so
I
don't
know.
Well,
this
is
Pierre's
baby
and
when
he
gets
back
well,
okay,
yeah
we'll
figure
it
out.
We.
D
B
Right,
the.
A
B
Other
thing
is:
if
you've
been
following
along
in
slack
Martin
Waits
I.
B
Been
talking
about
a
Dev
container
support,
So
code
spaces
I'm
a
little
confused
by
what
exactly.
B
C
B
C
C
Wow
worked
everything.
The
only
thing
that
didn't
work
was
exposing
the
the
exporter,
not
the
exporter.
Sorry
The
Collector,
to
4380
to
my
localhost
port
I.
Don't
know
why
that
would
need
some
investigation,
but.
A
B
D
F
B
F
B
What
might
help
here
is
if
we
put
the
collector
behind
Envoy,
if
we
actually
did
that,
if
we
put
the
hotel
collector
behind
Envoy
as
well,
then
that
might
solve
the
problem
of
exposing
it
for
front
end.
Telemetry
different
I,
don't
know
I'll.
Let
Martin
make
his
PR
and
play
around
with
it,
but
I'm
inclined
to
I
think
that'll,
be
a
I,
think
that'll
be
useful
for
people,
so.
B
How
well
it
works
in
like
a
browser
IDE,
but
that
you.
C
So,
whenever
the,
whenever
the
baby
decides
to
arrive,
the.
C
D
B
And
then
it
gets
harder,
but
in
different
ways,
all
right
well
I
think
we
can
probably
wrap
up
a
little
early
good.
Seeing
everyone
I'll
see
some
of
you,
so
our
next
one
is
and.
B
So,
let's,
let's
just
communicate
to
people,
you
know
try
to
get
stuff
in
before
the
next
meeting.
Yeah.
F
Socket
will
be,
but
cool
have
a
good
day,
guys
Martin.
Thank
you
so
much
for
joining
and
for.