►
From YouTube: 2021-03-18 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
Hello,
hey
today,
might
be
another
quiet
meeting
day
for
this.
This
working.
A
A
Did
you
get
approved
to
be
a
member
of
open
telemetry.
A
B
Yesterday,
any
robberies
he's
a
penny,
so
that
drives
me
to
double
think
about.
If
you
really
need
open
traditional
repo
in
upstream
yeah,
let
me
share
my
screen.
So
here
is
my
proposal.
My
idea
how
to
show
screen.
I
really
use.
B
B
Okay,
so
go
to
see
that
honeywell
submit
the
java
support
and
I
also
submitted
the
initial
command
for
creator
retention
and
python
cp
I
saw
I
saw
alex
comments
that
I
should
split
for
call
here.
I
think
today
I
can
do
that.
I
think
for
probably
for
python
svk
we
have
we
need
to
discuss
more
discussion,
but
for
characterization
we
can
get
started
right.
A
Yeah,
I
I
reviewed
the
extension
portion
and
it
looked
good,
that's
kind
of
what,
when
I,
when
I
got
to
the
bottom
of
the
collector
extension,
that's
kind
of
why
I
asked.
If
you
could
split
it,
then
we
could
just
get
this
thing
merged
pretty
quickly.
B
Okay,
so
do
you
want
how
I
close
this
pr
and
read
the
new
one.
B
Yeah
and
yeah:
let's
discuss
about
it
if
we
should
leave
this
level
and
how
would
this
level
look
like
so.
B
But
at
that
time
I
still
keep
the
idea
that
it
was
to
have
a
lambda
level,
but
this
lavender
level
might
be
downstream
owned
by
aws
of
mobility.
The
reason
we
need
a
central
report-
that's
because
lambda
project
is
not
only
for
instrumentation,
but
also
because
lambda
is
a
special
environment
right.
We
need
to
figure
out
how
to
launch
it,
how
to
launch
planetary
aid
and
how
to
enable
auto
instrumentation
unit.
So
for
this
part
of
code
we
do
need
a
repo
yeah.
D
B
So
the
thing
is
yesterday,
probably
two
days
ago,
when
I
saw
anyone
here,
I
have
questions
like
why
we
don't
use
some
very
aws,
specific
logic
like
why
we
use
open
telemetry
java
agent,
but
not
aws
style
agent.
So
any
large
idea
is
this
vehicle
should
be
neutral
and
not
database
specific.
I
agree
with
that,
but
the
difference
is.
I
believe
that
we
still
need
at
least
one
sample
for
aws.
B
Second,
not
because
I
intend
to
then,
but
it's
easy
for
user
demo
and
easy
for
our
csv
workflow,
because
we
need
to
use
x-ray
for
validation
and
also
currently
any
route
sample
just
print
as
a
log
in
cloudwatch
log
customers
still
need
to
load,
aws
account
and
go
to
call
the
workflow
to
see
the
print.
B
So
that's
my
point
and
I
list
my
idea
here.
B
B
A
I
mean
I
I
guess
in
my
in
my
opinion,
I
don't
see
the
I
don't
see
there
being
an
issue
if
there
is
sample,
for
example,
configuration
for
specific
vendors
in
the
lambda
repo,
because
you
mentioned
here,
it's
not
really
any
different
than
what
we're
able
to
collect
or
contribute,
though.
C
A
Yeah
sorry,
I
was
just
looking
through
some
of
the
exporters.
You
know
there's
a
little
bit
of
like
vendor-specific
information
there,
but
there's
not
a
ton
of
it
or.
A
And
I
mean
even
in
the
python
contributor,
you
know,
there's
a
datadog
exporter,
there's
some.
Sometimes
that's
amazon
specific.
So
it's
you
know
I
I
guess,
because
the
difference
is
I
don't
imagine
there
should
be
a
like
a
aws
land
that
control
people.
I
kind
of
feel
like
that's
overkill,
because
considering
I
don't
expect
it'll
be
too
much
additional
work
here
once
once
this
is
done
so.
B
I
think
we
have
to
use
unless
we
won't
hold
unless
we
want
to
copy
the
similar
logic.
The
reason
the
reason
we
use
aws
is
for
collector.
There
are
two
reasons.
One
thing
is:
we
know
that
naturally,
aws
is
structured
for
aws
service
right,
so
I
probably
this
is
not
a
good
reason.
The
most
important
thing
is
the
size
of.
B
B
B
C
B
B
A
C
A
C
B
C
B
E
E
B
But
the
aws
return,
the
propagator
is
not
again
core.
That's
not
the
most
important
reason
think
about
the
other
third
party
as
water
are
also
not
incorrect
right,
but.
C
C
Like
we're
not
open
like
so
the
x-ray
id
generator
is
not
open,
tell
me
to
complain,
that's
for
sure,
and
so
if
we
turn
that
on
by
default,
it's
not
on
photometry
layer
anymore.
So
I
think
I
do
agree
a
bit
that
if
it's
enabled
by
environment
variable
yeah
but
not
on
by
default,
then
I
guess
it
would
be
okay.
I.
B
So
so
the
decision,
one
thing
is,
we
don't
use
aws
digital
collector.
B
For
sample
yeah,
I
said
I
want
one
sample
with
aws
patterns.
I
think
yesterday
I
I
gave
my
opinion
to
you.
The
reason
why
I
needed
it.
B
Yeah,
I
don't
think
that
we
have
only
one
level
for
aws.
We
can
have
one
more
record
for
any
other.
Second,
like
I
remember
one
month
ago,
I
verified
the
lifestyle.
Second,
I
register
my
schedule
contact
and
use
otlp
as
possible
as
for
data
tool
as
well,
it
works.
So
I
think
we
can
also
add
this
sample
into
this
local
to
make
sure
it's
neutral,
but
that's
the
reason
why
we
need
aws
background.
That's
because
you
may
use
even
print
a
lot,
because
I
still
need
to
use
cloth
watch
to
check
the
load.
B
C
C
We
can
say
our
current
plan
is
to
not
enable
any
x-ray
features
by
default,
and
but
we
do
want
to
have
samples
for
all
the
vendors
in
this
repo
rather
than
having
them
in
separate
places.
So
that's
what
we're
saying
right
right
and
so
the
I
think
the
configure
it
like
on
off
by
default.
That
should
be
no
problem,
the
sample
app.
We
can
ask
more
people
what
they
think.
I
think
and
see
how
it
goes.
A
C
A
A
B
Yeah,
and
also
one
for
this
plan,
for
I
don't
know
because
of
underlying
that
happen,
the
previous
call
or
threshold
meeting
yeah.
So
I
write
down
the
story,
the
history
here
so
at
the
beginning,
we
really
want
to
follow
the
pattern
of
awg
stroke
character,
just
for
some
reason
like
we
want
to
public
lambda
layering
upstream
for
better
user
visibility,
because
we
don't
want
to
user
go
to
downstream
to
find
what
there
is
public
land
layer,
and
I
think,
if
we
ask
splunk
right
step
to
provide
their
code
to
it.
That's
unfair.
C
B
B
B
B
C
To
this
issue,
so
with
the
we're
all
on
the
same
page
that
we're
going
to
see
if
it's
okay
to
publish
artifacts
based
all
on
the
open,
telemetry
components,
so
we
don't
use
any
aws
components
and
then
we
make
it
opt-in
to
any
vendor
by
the
user,
explicitly:
okay
yeah!
I
guess
that
should
be
okay,.
B
B
C
B
And
what
we
just
planned
is
practical
alex.
So
I
think
I
like
to
know
the
code
of
public
publish
randomly
the
reason
why
here
I
use
aws3,
that's
because
for
a
large
for
a
larger
file,
if
we
don't
use
s3,
sometimes
the
upload
process
will
be
filled
button
for
the
user.
A
F
C
A
B
Yeah,
when
you
talk
about
the
platform
yeah,
that's
a
heavy
problem
for
me.
I
think
we
should
support,
support
both
telephone
and
call
information
right.
C
Yeah
we
can
support.
B
Java
has
the
only
telephone
but
the
other
language
I
believe
we
should
reveal.
We
will
support
the
call
formation
first.
B
Interface
called
common
interface,
as
we
have
called
long
dot
sh.
When
we
call
this
shell
script,
it
will
invoke
the
cloud
information.
It
will
remove
the
same
address
and
deploy
the
compact
application
center
and
the
general
integration
test.
So
I
have
no
idea
how
to
make
it
adapt
to
telephone
and
to
figure
out
how
to
do
that
in
april.
I
think
so.
That's
the
reason.
I
hope
we
can
have
cloud
information
first,
because
it
can
make
sure
that
our
necessity,
public
landmark
layer
works
all
of
language,
can
follow
the
same
thing.
F
B
C
B
B
For
example,
if
you
commit
code
to
java
folder,
it
will
trigger
a
workflow
like
if
you
submit
a
code
to
another
folder
to
trigger
another
workflow.
I
know
we
can
do
that,
but
how
can
I
make
sure
that
if
the
user
commit
code
into
both
python
and
the
java
folder
at
the
same
time,
it
will
trigger
the
same
work
as
it
will
follow
and
it's
the
same
video
currently
I
know
you
create
a
ci
workflow
for
download,
but
I
want
to
also
invoke
the
same
session
before
I
I
haven't
saved
on
how
to
do
that.
C
B
B
Yeah
we
can't
we
can,
but
I
mean
yes,
I
mean
if
here
I
added
the
path
to,
for
example,
to
python.
Only
python
will
trigger
this
code.
How
can
I
make
sure
that
java
can
also
trigger
this
workflow.
B
C
Yeah,
let's
start
with
the
collector,
I
think,
or
I
mean
we
can
do
both.
I
guess,
but
I
think
the
collector
is
easier
because
we're
definitely
using
the
collector
contrib.
So
that's
not.
B
Yeah,
but
currently
my
my
cluster
is
using
aws
stroke
yeah,
I'm
not
sure
if
I
have
a
time
consuming
sub
component
in
several
hours.
I
will
try
to
do
that.
F
C
A
B
A
Oh
all
right,
I'm
I'm
gonna
drop
off
yeah
thanks.
Everybody.