►
From YouTube: 2022-04-19 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
B
A
B
B
A
B
A
Yeah
that'll
work
thanks
for
helping
helping
me
track
down
who
to
talk
to
about
the
hotel
crystal
stuff.
B
Yeah
no
problem-
I
I
found
another
page
actually
that
I
can
send
you
a
link
to
that
was
addressing
donations,
specifically,
it
yeah.
I
think
it
just
had
a
little
bit
more
information
about
the
process.
A
I
think
I
think
maybe
I
have
that
one
and
yes
sure
I
don't
know
if
you
know
shark
feed
and
she
does
a
lot
of
the
hotel
stuff
for
new
relic
she's.
A
Our
director
over
the
you
know
like
like
jack
berg
and
ellen
west,
and
a
bunch
of
the
other
folks
that
are
involved
in
in
implementations,
she's
their
director
and
she
helped
me
chase
down
a
couple
of
the
like
the
the
contributions
page,
which
I
think
is
probably
what
you're
referring
to.
A
B
I'm
starting
to
suspect
it's
just
going
to
be
us
so
yeah
and
I'm
just
here
to
lurk
so
all
right.
Anything
on
your
mind,
while
we're
here
or.
A
I
mean
not
not
really.
Actually,
I
do
have
a
question
because
I
just
haven't
looked
at
the
the
code
recently,
you
know
a
few
weeks
ago.
The
metrics
stuff
for
ruby
was
still
very
much
just
sort
of
laying
out
the
code
framework,
but
there
was
not
any
real
implementation
there.
Has
it
progressed
from
there
or
or
not?
Do
you
know.
B
It's
a
good
question.
I
know
robert
was
working.
It's
still
all
right.
So
there's
this
there's
a
work
in
progress
here.
B
There's
still
the
whip,
so
there's
there's
an
api,
and
this
is
the
thing
that
has
kind
of
been
in
progress.
Okay,
yeah
and
my
guess
is,
it
has
been-
maybe
stalled
for
a
minute.
A
Yeah
yeah
that
looks
like
it's
basically
the
same
place.
It
was
when
I
last
looked
at
it
yeah
because
I
was
looking
at
it
for
inspiration
and
yeah.
It
looked
like
it
had
been
kind
of
stalled
because
it's
kind
of
so
you
know.
I
find
that
that
some
of
the
other
implementations
docs
are
helpful,
but
the
code
for
how
other
implementations
do
things
is
largely
not
helpful.
A
So
so
you
know
my
strategy
has
been.
I
look
at
goes
docs.
I
look
at
java's
docs,
I
look
at
ruby's
docs
and
then
you
know
if,
if
I'm
kind
of
wondering
okay,
how
might
I
approach
this?
I
go
and
I
look
at
the
ruby
code
and
I
want
to
gets
get
back
to
implementing
metrics
but
yeah
I
was
hoping
there
was
a
little
bit
more
more
movement
on
the
the
ruby
side
with
metrics,
so
I
can
kind
of
see
which
direction
you
all
are
moving
in
before
I
start
just
doing
things.
B
Yeah,
it
seems
like
the
closer.
The
implementations
are,
maybe
the
easier
it
is
in
the
long
haul,
but
yeah
it
would
be.
It
would
be
nice
if,
if
robert
were
around,
we
could
kind
of
get
an
idea
of
where,
where
this
stuff
is
is
headed.
But
I
I
imagine
that
more
important
stuff
has
fallen
onto
his
plate
to
get
back
to
this
yeah.
B
There's,
definitely
like
a
lot
of
pieces
to
the
metrics
sdk
yeah,
so
I
think
he
was
really
trying
to
get
like
everything
in
place
for
to
be
able
to
kind
of
like
spike
the
instruments
through
like
do
like,
like
one
synchronous
instrument
or
something
and
get
all
the
different
pieces
wired
up
for
that,
and
then
maybe
do
like
one
asynchronous
instrument.
A
A
Yeah
I
mean
yeah,
that's
the
thing
when
I
was
looking
at
the
metrics
sdk,
it's
just
there.
I
mean
the
metrics
docs
the
specification.
That's
just
yeah,
there's,
there's
there's
a
lot
of
moving
parts,
yeah
a
lot
of
details
to
keep
track
of
there.
B
Yeah-
that's
that's
definitely
the
case,
so
so
yeah,
hopefully
you'll
be
back
to
this.
At
some
point,.
A
Yeah
is
anybody
working
on
the
log
log
implementation
at
for
ruby
at
all.
B
It's
another
good
question.
I
know
andrew
said
he
might
come
to
this
meeting
and
oh
quite
a
while
ago.
I
think
he
was
paying
attention
to
the
the
log
spec
and
maybe
even
the
logging
sig
and
was
doing
some
prototyping
around
it.
But.
B
A
A
It's
not
stable.
The
way
tracing
is
and
stuff
like
that.
A
I
think
in
part,
because
logging
has
to
deal
with
a
lot
of
legacy,
logging
concerns,
and
so
there's
there's
a
lot
of
thinking
about
how
to
deal
with
all
of
that.
That's
still
going
on
it's
still
simpler
than
than
say
neometrics,
you
know,
and
so
I
I
actually
started
implementing
implementing
it
in
crystal,
and
it's
just
one
of
those
things
that
it
seems
like
it
should
be.
A
I
don't
know
it's,
it
seems
like
it
should
be
not
as
heavy
of
a
lift
as
as
metrics
to
get.
A
To
get
the
a
spec
conformant
logging
implementation
built,
and
yes,
I
was
just
wondering
if
anybody
was
doing
it
because
you
know
if
I,
if
I
get
it
built
in
crystal,
I
imagine
that
a
lot
of
what
I
do
there
will
be
more
or
less
directly
transferable
to
the
ruby
implementation,
and
so,
if
nobody's
working
on
it,
maybe
I'll
I'll,
try
and
kill
two
birds
with
one
stone
there
and
and
contribute
something
there.
B
B
But
yeah,
I
think
I
think
logging
will
ultimately
be
a
lot
more
straightforward.
It's
I
think,
really
about
getting
a
a
trace
id
and
possibly
a
span
id
into
the
logs
when,
when
applicable,
yeah,
but
as
always
like
the
devil,
is
in
the
details,
and
I
think
that
is.
A
Yeah
see
what
I,
what
I
did,
what
I
ended
up
doing
on
the
crystal
side:
crystal
has
kind
of
like
ruby,
a
standard
log
library
that
pretty
much
everything
uses
and
so
not
having
the
actual
log
signal
implemented.
A
On
the
crystal
side,
since,
since
I
have
you
know
the
current
trace
current
span
readily
available,
you
know
when
I
go
implement
it,
it's
it's
it's
more
or
less.
The
exact
same
logic,
it'll
just
produce
a
log
instead
of
injecting
an
event
into
the.
A
A
B
Yeah
I
wish
I
could
tell
you
what
languages
are
kind
of
ahead
of
the
curve
in
logging.
So
I'm
sure
there
are
some.
A
Yeah
yeah
there's
been
some
discussion
in
new
relic
about
some
of
the
some
of
the
semantics
around
around
logging,
because
it's
like
in
ruby.
You
know
when,
when
we
use
the
logging
library
and
send
a
log
basically
we
assemble
a
complete
log
message
and
send
the
complete
log
message
as
a
log,
but
in
java.net
and
either
one
of
them.
They
do
it
differently.
A
They
send
a
template
of
a
logging
message
and
then
they
send
a
set
of
keys
to
get
merged
into
the
template,
because
it's
you
know,
there's
a
computational
expense
to
merging
both
of
those
things
and
so
what
what
their
logging
standard
logging
library
does?
Is
it
kicks
the
can
on
that
computational
expense
down
to
whoever
is
receiving
the
logs
to
merge
the
two
into
a
completed
message,
and
so
they
were
discussing
okay.
A
How
do
other
languages
do
this?
Because
if
you
have
the
template-
and
you
have
the
keys,
you
can
do
other
sort
of
associations
and
analysis,
and
things
like
that
on
the
back
end
that
you
can't
do
if
you
just
have
the
the
finished
message
and
that's
all
that's
delivered
to
the
back
end-
and
this
was
a
topic
of
discussion
the
other
day,
because
the
java
and
net
back-ends
do
it
this
way
and
so
they're
like
well.
A
So
then
in
our
new
relic
back
end,
we
could
do
certain
things
with
with
that
template
to
make.
You
know
make
dealing
with
with
the
logs
more
useful
in
the
ui.
But
if
say,
ruby
doesn't
do
that,
doesn't
send
a
template
and
you
are
that's
not
the
way.
Ruby's
logging
libraries
tend
to
work
that
wouldn't
work
for
ruby,
and
so
you
know
that's
kind
of
you
know
it's
one
of
the
things
that
has
been
discussed
specifically
because
those
two
languages
have
a
complete
logging
implementation.
So
they
can
start
thinking
about
these
things.
B
Yeah,
no
that's
interesting.
I
didn't
quite
realize
that
java
and
network
that
way,
but
I
could
see
I
can
see
how
it
would
be
super
useful
for
like
back
ends,
if
you
could
just
send
like
the
template
and
the
parameters
rather.
A
A
A
I
don't
know
you
know,
I
think
what
we
have
is.
We
have
a
difference
between
language
philosophies
and
net
and
java
both
fall
on
one
side
and
ruby
falls
on
the
other,
and
you
know
I
think
you'll
find
that
there's
two
camps
and
they
kind
of
associate
with
that
that
dynamic
interpreted
language
camp
versus
the
non-dynamic.
A
B
I'm
pretty
comfortable
with
where
open
telemetry
is
in
the
tracing
realm.
That
makes
a
lot
of
sense.
I
think
metrics,
I'm
I'm
kind
of
where
the
ruby
cig
is
on
this,
like.
I
know
that
they're,
like
I
feel
like
I
have
like
big
picture
but
like
there's,
there's
definitely
a
lot
of
pieces
and
and
a
lot
of
details
that.
B
That
I
I
know,
exists
but
haven't
gone
through
the
exercises
actually
putting
together
myself
and
then
vlogging
is
kind
of
just
something
that
I
know
people
have
been
working
on,
but
I
haven't
really
been
paying
a
whole
lot
of
attention
to,
but
I
think
if,
if
you've
been
paying
attention
to
it,
like,
I
think
it
it's
good
that
we
have
somebody
who
who
knows
something
and
if,
if
at
any
point,
you
are
feeling
like
the
log
expert
and
want
to
start
working
on
an
implementation.
B
I
think
it
would
be
a
good
thing
to
volunteer.
A
For
I
don't
think
yeah,
I
think
what
I'll
probably
do
is
is
get
my
crystal
implementation
finished,
because
then
I
can
also
like
make
sure
that
it
works
with
back
ends,
as
you
know,
make
sure
that
I
understand
everything
and
I'm
delivering.
A
You
know
things
that
actually
work
correctly
and
then,
once
I
have
a
working
implementation
that
you
know
works
correctly
with
the
various
backends,
it
shouldn't
be
too
hard
to
then
port
that
over
to
the
the
ruby
implementation,
because
I
mean
crystal's
so
close
to
ruby
in
so
many
ways
that
a
lot
of
code
is
is
almost
cut
and
pasted.
So.