►
From YouTube: 2022-03-31 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
B
A
A
About
like
needing
to
know
variables,
no
yeah
having
to
have
the
entire
instrument
variable,
instead
of
just
the
name
like
in
most
metrics,
libraries
like
prometheus
statics
and
all
those
people
are
used
to
just
putting
counter
add
and
then
the
name
of
a
like
an
atom
right.
A
And
I
don't
know
if
it's
worth
doing,
that
to
and
adding
like
a
sort
of
registry
or
just
requiring
that
you
have
the
instrument.
B
A
A
B
A
A
It's
a
superset
that
includes
instrumentation
library,
and
so
we
should
be
changing.
Everything
to
like
variable
name
usually
will
be
scope,
but
the
what
it
all
the
automatic
stuff
that
we
currently
use
remains
an
instrumentation
library.
So
it
doesn't
really
change
anything
for
a
user
except
they
we
I
get.
I
guess,
want
to
do
some
more
documentation
because
now,
as
like,
before
pretty
much
users,
never
needed
to
bother,
in
our
case
thinking
about
the
instrumentation
libraries,
because
it's
just
using
the
application
and
registered
forum,
but
now
with
scope.
A
B
A
Yeah
the
scope
for
will
usually
be
the
instrumentation
library.
It's
just
that
now
it
can
be
anything
okay
and
which
will
make
it
will
be,
could
be
used
for
for
a.
B
B
Isaac
was
messaging
me
the
other
day,
basically
about
making
hotel
telemetry
1-0.
B
B
B
A
I
mean,
I
think
it's
supposed
to
be
part
of
the
sdk,
but
not
necessarily
I'm
not
sure
if
it's
supposed
to
be
enabled
by
default,
that
I
need
to
check,
but
the
yeah
it
definitely,
I
think,
should
be
in
the
sdk.
So
people
don't
have
to
use
a
another
library
for
it,
and
I
suggested
the
existing
one
going
contrib
just
to
like
have
something
get
get
started
with,
but
that
ultimately
it
should
be
provided
by.
A
B
B
That
same
process,
it
would
apply
to
all
log
messages,
but
it
does
bring
up
the
thing,
though,
of
if
you
propagate
it
across
boundaries,
then,
when
you
attach
context,
I
think
you
would
need
to
oh
right
said
it
again:
yeah,
maybe
it's
in
like
it.
Maybe
it's
in
the
context
library,
whenever
we
attach,
because
we
do
that
in
this
with
span
right,
there's
like
a
there's.
A
A
A
A
To
another
I'd,
say
it's
more:
it's
more
whether
or
not
it
should
always
be
doing
that,
like
a
enabled
by
default
or
not.
I
think
that's
an
easy
answer.
If
it's
in
the
spec
and
it's
a
more
of
a
probably,
we
should
make
it
a
default.
If
it's
not,
I
mean
it's
not
specified
in
the
spec
like
it's
more
most
people
are
going
to
want
this
yeah,
so
we
should
probably
make
it
default,
and
I
mean
I
can't
think
of
reason.
I.
A
A
B
A
B
B
B
Basically,
having
some
macros
that
when
basically
like
do
like
a
not
over,
I
mean
we
talked
about
wrapping
gen
server
in
total,
but
even
just
to
have
like.
B
B
B
A
B
A
Yeah,
this
should
be
bad
technically,
we
could
tell
people
they
can.
If
they
really
wanted
to
go
crazy,
they
can
have,
we
could
name
it
gen
server
and
they
can
just
replace
the
one
that
doesn't
propagate
context
in
their
release.
B
I'm
not
sure
how
angry
anybody
would
be
that
we're
over.
No,
I
mean
they
would
have
to.
B
B
B
Okay,
I
will
try
to
read
more
just
so
I
can
be
cool,
I
don't
know,
provide
some
kind
of
feedback
and
then.
B
Try
to
get
some
of
those
other
things
kind
of
wrapped
up
to
1.00
yeah
and
then
the
filter
thing
that
you
brought
up.
I
think.
B
B
Okay,
I
mean
it
would
need
some
modification,
because
I
think
in
the
end
we'd
want
to
accept
and
they
would
need
to
define
like
what
it
is
or
provide.
Yeah
like
is
this
a
regex.
Are
we
doing
an
exact
match?
Is
it
a
function?
Call
because
we
should
probably
be
able
to
support
each
of
those,
and
then
people
can
get
as
non-performant
as
they
want
right,
because
that
thing
is
not
going
to
be.