►
From YouTube: 2023-03-06 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
A
B
A
Awesome,
okay,
I,
recently
moved
to
Ubuntu
and
now
my
oh,
my
microphone
and
headset
is
like
a
mess.
B
It's
actually
really
annoying
with
the
hotel
calendars,
because,
like
the
only
the
best
way,
I
figured
out
to
subscribe
to,
it
is
create
like
a
new
Google
account
pointing
to
my
servicenow
email
address
and
then
it
sends,
but
because
of
the
way
Outlook
works
with
recurring
meetings
and
Google
Calendar.
It
sends
me
like
a
single
like
every
time.
There's
any
change
to
any
meeting.
I
get
one
email
for
each
like
recurrence,
so.
C
B
C
It's
just
about
right,
then
you
get
the
signal.
Noise
ratios
off
and
your
email
inbox
is
useless.
B
I
switched
actually
I
know
I
switched
to
as
long
as
we're
kind
of
I'm,
starting
to
use
superhuman.
Now,
because
I,
just
like
the
Outlook
stuff
is
just
like
I
can't
I
can't
deal
with
Theology
and
superhero
is
pretty
good,
though
it's
I'm
still
kind
of
getting
it
getting
used
to
it.
But.
B
B
B
D
B
Honestly,
yeah
I'm
trying
to
pull
up
get
up.
D
D
D
There
are
some
season,
I,
don't
know
someone
created
an
issue
essentially
offering
to
write
docs
for
us
or
something
like
that.
D
D
A
D
Patrice
or
something
like
that,
and
that
should
at
least
Point
them
in
the
right
direction
and
maybe
I'll
maybe
I'll
talk
to
Ted
about
it
too,
because
I
think
you're
right.
The
project
in
general
could
probably
use
some
documentation.
B
D
D
What
else
raise
it
I
mean
I
think
there
might
be
some
cigs
that
maybe
are
willing
to
write
some
content,
but
not
do
a
lot
of
polishing,
and
so
that
might
be
beneficial
to
them,
but
cool
yeah
anyways
subscribe.
My
eye
I
wanted
to
kind
of
bring
it
up
as
a
group
and
see
if
you
wanted
to
do
anything
with
it.
D
So
I
think
we
have
some
big
open
questions
around
1.4
in
general.
It's
kind
of
a
grab
bag
of
small
paper
cuts,
but
if
anyone
wants
to
speak
to
the
specific
items
already
listed,
that
would
be
great.
E
I
think
it's
not
listed
there
for
one
four,
but
do
we
have
do
we?
Can
we
confirm
we're
even
able
to
build
arm
images.
E
E
B
E
D
B
A
We
were
discussing
last
week,
I
think
Josh
was
in
the
car
as
well
that
now
that
we
have
the
docs
on
the
on
the
open,
Telemetry
IO
repo,
it
would
be
awesome
if
we
had
some
actions
that
actually,
whenever
someone
merged
a
merge,
a
PR
with
a
specific
label
on
it
like
required,
docs
update
or
something
like
that,
then
we
open
our
issue
right
away
into
the
open
Telemetry
I
o
and
assign
to
that
person.
A
This
ticket
kind
of
automatically
I
played
around
I
was
able
to
to
create
the
issue
on
my
own
repo.
So
now
I
would
need
to
investigate
how
like,
depending
on
the
on
the
tag
I,
can
create
the
issue
on
my
own
repo.
Now
I
just
need
to
figure
out
how
to
do
that
in
a
in
a
my
external
repo,
and
for
that
I
think
you
mentioned
Pierre.
That
I
would
need
some
some
tokens
to
to
be
shared
between
the
two
repos
and
for
that
case,
I'm
not
sure
how
to
proceed
here.
E
Yeah
I
I
I'm
not
sure
what
would
be
needed
to
make
that
work
exactly.
But
you
know
when,
when
an
issue
is
created,
there's
an
author
for
that
issue.
Yes,
so
who's!
The
author
here
it'd,
probably
be
some
kind
of
cncf
bot.
If
you
will,
and
with
that
cncf
bot
have
the
tokens
I'm
thinking
of
in
my
and
I'm
imagining
things
I'm,
not
even
sure
if
this
exists,
but
that's
how
I
would
imagine
it
would
work
yeah.
A
B
B
That's
something
else,
so
there
is
just
as
an
aside
there's
a
tcgc
meeting
this
week
tomorrow
and
Wednesday
I'll
be
at
so
one
of
the
things
I
was
going
to
bring
up
as
like
a
project
need
is
like
it's
kind
of
this,
of
like
service
accounts
passwords
like
sort
of
the
technical
aspect
of
doing
stuff
like
this,
because
right
now
it's
it's
sort
of
pain
in
the
butt
and
I,
don't
think,
there's
a
single
source
of
Truth.
So
hopefully
that
will
also
help.
E
And
for
white
sports
I've
also
experimented
with
creating
GitHub
action,
except
back
with
the
chat
GPT
and
then
some
secret
limited
co-pilot
to
help
write
it
for
me,
but
basically,
I'm
gonna
write
a
GitHub
action,
so
if
you
create
a
a
PR
that
touches
dockercompose
dot,
EnV
anything
within
the
grafana
folder
that
we
provision,
basically
anything
that's
part
of
the
helm
chart
that
we
have
to
kind
of
replicate
back
over
you're,
going
to
get
a
Helm
required
label
automatically
slapped
onto
your
PR.
E
That
way
there.
If
and
when
we
merge
that
thing
and
if
we
carry
over
the
the
version
number
of
PR
as
well,
it's
I
find
myself
spending
a
lot
of
time.
Looking
at
a
lot
of
code,
a
lot
of
PR's,
because
I
can't
look
at
every
single
one
of
them
to
figure
out.
Does
this
thing
require
a
Helm
update
and
I
would
rather,
this
be
automated
in
some
way.
E
So
we
could
use
a
few
actions
here
to
help
yeah
it's
it's
now
that
we
have
a
lot
of
people
writing
PR
from
all
over
the
place.
It's
hard
to
create
consistency.
E
E
C
Yeah
I'll
be
there.
My
experience
last
time
was
that
the
project
was
really
unstable
in
the
days
following
that,
and
there
was
a
lot
of
excitement
so
I
don't
know
what
we
can
do
to
just
I'll
limit
limit
the
the
last
minuteness
of
it
yeah.
B
To
put
some
color
on
this
I
think
we
should
announce
1.4
at
open
observability
day.
I
think
we
should
from
observability.
D
B
Dropped
the
open
I
was
very
insistent
of
it.
We
should
announce
1.4,
then
we
should
release
it
like
the
week
before
and
like
really
make
sure
that
everything's
cooked.
B
E
Something
done
by
midday
or
like
April,
5th
or
April
4th.
B
Yeah,
that
sounds
good.
That's
a
lot
that
we,
that
is
a
okay,
something
is
actually
like.
Super
wrong.
B
B
A
E
Well,
if
you
haven't
booked
your
Logistics,
yet
everybody
on
this
call,
please
book
them
now,
at
least
from
the
the
US
I
like
I,
could
not
believe
how
much
my
airfare
cost.
It
was
really
through
the
roof
and
hotels
were
kind
of
reasonable,
but
they're
definitely
booking
up
in
their
locking
down
quick,
so
Kevin.
E
E
Walking
in
Amsterdam
is
definitely
fun.
I
I
grab
the
hotel
by
where
all
the
canals
are
we're
really
in
the
center
of
the
area
and
I
just
plan
taking
the
public
transportation
to
Rai
daily.
E
A
I
I
love
how
how
we
evolve
a
society,
but
some
things
are
really
a
pain
and
they
continue
to
be.
B
B
E
That
one's
A2,
a0bc
I
mean
and
four
E
Yeah.
B
E
Oh,
go:
releaser
probably
takes
care
of
all
your.
Your
different
manifests
at
honeycomb
used
Carol
for
this,
and
it
takes
care
of
all
your
manifest.
B
B
B
I
can
look
at
this
like
after
this
call
and
see,
and
just
I
mean
if
nothing
else,
I
can
try
to
replicate
the
actions
environment
somehow
or
like
try
to
do
I.
Don't
know
I'll
figure
it
out,
but.
B
Yeah
I
guess
I
can
just
change.
E
E
I
am
sometime
later
this
afternoon
today,
but
I
will
make.
B
It
work
okay,
yeah,
I,
think
my
day
is
somewhat
free-ish
today,
so
I
can
I
can
look
at
this
today
to
get
back
to
one
four
in
general,.
E
Yeah
he
wrote
down
April
6,
which
is
a
Thursday
okay
about
10
day
or
it's
12
days
before
observability
day.
D
B
E
E
E
One
thing
I
did
write
up
in
slack
is
I.
Did
the
investigation
on
memory?
Okay,
we
do
have.
We
have
four
Services
I'm,
not
sure
I,
gotta
recheck
on
fraud
detection
service
to
make
sure,
but
we
have
for
sure
at
least
three
things
that
leaked
memory.
The
email
service
is
a
real
serious
memory,
leak,
load,
generator
and
redis.
E
Both
have
a
moderate
league
as
well
I'm,
not
sure
why
Reddit
has
a
leak,
maybe
you're
not
specifying
time
to
live
and
Reddit
is
just
cache,
is
infinitely
growing
there,
but
I
feel
like
that
might
be
a
simple
fix
that
we
have
to
do
in
the
cart
service.
Just
to
make
sure
we
specify
the
proper
time
to
live.
E
E
So
and
I
documented
them
in
slack
at
least
like
charts
and
pictures
and
whatnot
I,
think
the
the
Ruby
issue
for
the
email
service.
If
I'm
not
mistaken,
that's
actually
a
problem
with
the
grpc
library
for
Ruby.
E
If
I'm
not
mistaken-
or
maybe
not,
the
jrpt
library,
I
think
it's
the
grpc
protobuf
library
to
get
really
specific
I
can't
remember,
I
I
seem
to
remember
digging
up
in
this
stuff
and
I
got
myself
into
a
a
hole.
I
did
not
want
to
get
myself
into,
but
there
was
references
to
open,
Telemetry
and
leaking
memory,
and
there
was
you
know,
arguments
of
why
it
was
done
the
way
it
was
done.
E
D
E
Load
generator
that
would
baffles
me
a
lot
it's
Locust
and
Locust
is
known
for
to
just
be
able
to
run
now.
I,
don't
know
if
I
care,
if
low
generated,
restarts
itself,
it's
the
low
generator.
E
Do
we
even
care
if
it
restarts,
should
we
just
document
that
we
know
that
there's
a
restart
in
here
and
just
walk
away
and
call
it
a
day?
Is
it
worth
the
effort?
I
don't
know,
but
that's
that's
the
other
one.
So
so
that's
just
kind
of.
B
I
feel
like
Lucas
is
probably
us
holding
it
wrong.
I
just
looked
at
redis
card
store.
Yes,
we
are
not
setting
a
TTL.
So
that's
why
redditism
really.
A
Just
one
quick
question:
there
wouldn't
be
nice
to
maybe
actually
document
that
in
our
docs
and
just
leave
it
not
for
readies
and
locals
Locust,
but
for
the
other
two
Services,
maybe
just
say,
hey.
We
intentionally
left
a
memory
leaking
here
and
yeah
like
just
to
that's.
E
E
Well,
the
email
service
you
catch
right
away.
That's
why
I'm
like
the
email
service
has
got
a
serious
leak,
redis
and
low
gender.
You
catch
up
there,
two
days
yeah
like
if
variety
attacks
has
been
running
for
three
weeks
and
it
hasn't
blown
up
yet
so
I'm
less
inclined
to
give
a
yeah.
My.
B
My
I
guess
my
problem
is
I.
Think
we
should
like
I
want
I
mean
just
from
a
design
point
of
view,
I
think
it's
important
that
failures
have
to
be
deterministic
to
the
operator
from
a
like,
make
it
a
good
demo
and
I
think
if
we
have
failures
that
impact
like
not
like
determine
this,
like
based
off
of
you
know
like
oh
it's
running
for
a
week
or
two
like
that,
only
really
hurts
people
that
are
trying
to
run
like
a
stable
version
of
this
or,
like
a
you,
know,
they're.
A
D
B
E
Sense
so
yeah,
so
fraud
detection,
probably
doesn't
matter,
is
what
we're
saying
I
mean
we
probably
like
I
said:
I,
wouldn't
I
wouldn't
care
if
we
fix
the
low
generator
and
I,
don't
think
it.
B
I
feel
like
that's,
probably
something
that's
also
simple.
What
would
help
immediately
so
I
think
everyone
is
just
like
when
we
see
things
like
this,
let's
make
issues
for
them
and
tag
them
with
one
four.
B
This
homework,
maybe
can
we
spend
this
week
like
everyone
kind
of
independently
going
through?
You
know,
getting
your
issues
that
you
want
in
for
one
for
tagging
them
and
then
next
week
we
can
do
go
through
and
like
make
a
and
do
a
pass
just
to
groom
the
back
law
groom
the
stuff-
that's
tagged,
one
for
say
like
okay.
This
is
what
we
actually
think
we
can
do
and
we'll
we'll
figure
that
out
I.
Think.
E
I
made
in
two
weeks
and
commit
to
getting
it
done.
B
D
It
sounds
generally
good
to
me.
I
think
we
do
need
to
clean
up
some
of
these
kind
of
lingering
issues
like
update
copyright,
notices,
I
know
someone
put
like
the
resource,
detection
and
they're
I
think
we're
about
like
half
half
coverage
of
those,
so
we
should
probably
start
closing
some
of
these
out
but
Pierre.
What
do
you
think
about
the
license?
Checks,
I,
know:
I,
think
you
were
the
one
who
created
the
issue
originally.
E
I
think
it's
just
another:
linter
yeah
license
center.
So
any
code
file
s.
E
B
Think,
let's
not
make
a
decision
about
what's
in
or
out
right
now,
let's,
let's
do
our
ideation
and
then
we'll
make
that
call
like
based
on
what
we
see
next
week.
B
Yeah
I'll
put
a
note
in
the
demo
Channel
telling
people
that
are
just
in
the
demo
channel.
It's
like
hey
if
you've
got
stuff
that
you
really
want
in
the
next
release
like
that
are
related
to
maintainability,
whatever
then
create
an
issue
label
it
with
one
for
and
we
will
like
evaluate
them
next
week.
Basically,.
B
B
Just
do
we'll
do
it
async,
perfect.
B
B
E
Well,
if
we
want
to
meet
next
week,
I
won't
be
around
anyways.
I
will
be
on
PTO
next
week,
but
I
will
get
some
issues
in
tomorrow
on
things.
Today's
got
a
few
things
in
my
play,
but
tomorrow,
when
things
clear
up,
we'll
give
you
more
issues
in
there
and
I
may
also
just
lob
a
quick
fix,
at
least
in
a
card
service,
to
fix
the
redis
memory
League
before
it's
worth,
I
just
checked
again.
The
fraud
detection
service
now
running
for
28
days
is
slowly
still
climbing.
E
It's
up
to
89
memory
used
this
rate's,
probably
gonna
bail
in
10
more
days
or
so
I
don't
know,
but
it's
not
something
I
would
be
concerned
with
I.
Don't
think
anybody
outside
of
vendors
would
run
this
thing
for
long-running
the
way
I'm
running
it
right
like
I'm
running
it.
So
you
could
go
to
hotel,
mli.honeydemo.io,
yeah.
B
E
B
Yeah
I
mean
I
said
that
that's
really
cool
and
I
think
that's
a
like
I
want
us
to
be
able
to
take
that
use
case
and
support
it
right.
If
someone
else
wanted
to
do
the
similar
thing
like
I
think
it
should
be
like
oh
yeah,
you
can
run
this
because
I
think
there's
there's
been
discussions
about
like
load,
testing
or
sort
of
like
profiling.
B
You
know
utilization
over
time
or
whatever
and
like
that's
something
that
we
should
be
able
to
support
with
the
demo
project,
and
to
do
that,
we
need
to
make
sure
that,
like
any,
that
usage
is
fairly
deterministic.
You
know
so
that
someone
could
run
this
for
like
a
month
at
and
give
it
various.
You
know
like.
Okay,
we're
gonna
run
this
for
30
days
and
we're
gonna.
You
know,
give
it
maybe
different
different
Locus
profiles
or
whatever
and
like
adjust,
how
much
load
it's
getting
blah
blah
blah
blah.