►
From YouTube: 2021-06-30 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
A
I
always
had
this
interesting
idea
that
we
should
have
like
working
minimal
agent
without
any
instrumentation,
so
lie
like
the
very
bond,
the
bare
bone
of
machinery
and,
right
now,
it's
not
actually
possible.
For
example,
agent
tooling,
comes
to
the
agent
only
through
instrumentation.
B
A
A
So
I
might
try
looking
in
into
that
a
little
bit
yeah.
My
my
my
starting
point
was
that
I
was
trying
to
understand
how
to
convert
splunk
distribution
to
using
extensions,
not
repackaging.
B
And
extension,
api
is
relatively
new
by
matthias
recently,
I
think,
as
far
as
I
remember,
java
agent
api
is
for
when
you're
is
the
components
used
from
instrumentation
modules,
so
like
the
matchers
and
stuff
and
then
extension
api
is
only
really
for
custom.
Distro
type
of
things
so
not
related
to
instrumentation.
B
Yeah
yeah,
I
remember
in
that
sense
there
doesn't
seem
a
put
to
have
a
point
for
this
yeah.
B
A
B
B
B
It
depends
on
what
we
want
to
test,
so
we
can
test
the
published
agent
in
one
way.
That's
not
going
to
be
the
same
as
published
testing
a
custom
distro,
but
if
it's
so
just
one
example,
this
isn't
even
agent
or
anything
but
indexed
sdk.
We
recently
did
one
add
tests
for
the
published
artifacts.
A
B
B
B
A
B
B
B
But
yeah,
so
I
think
I'm
going
to
make
it
less
concrete,
just
try
to
focus
more
on
the
features
rather
than
on
code
examples.
I
think
that
can
be
more
helpful
and,
like
I
think,
actually,
your
comment
was
the
most
important
one.
I
don't
think
I
resolved
it
well
enough
yet,
but
there
are
so
many
things
like
one
I
didn't
remember
yet,
but
mapping
http
status
code,
error
status,
that's
also
something
instrumentation
has
to
deal
with
and
it's
very
annoying.
If
we
don't
have
an
instrumentation,
you
guys
so
there's
a
huge
list
of
these.