►
From YouTube: Grafana Agent Community Call 2021-12-15
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
All
right
this
is
the
griffin
agent
community
call
on
the
15th
of
december
and
yeah.
This
is
our
second
one.
So
awesome,
hopefully,
as
always,
we
appreciate
any
questions.
Anybody
making
time
to
come
here
and
we've
got
some
topics
here,
but
feel
free
to
add
your
own
or
if
you
have
any
questions
have
brewing
through
feel
free
to
bring
them
up.
A
B
C
Sure
no
problem,
so
this
is
just
a
really
simple
implementation
that
allows
the
enabling
of
an
experimental
feature
that
allows
you
to
fetch
the
agent
configuration
over
http
or
https.
So
really
it's
pretty
simple.
I
think
the
plan
is
in
the
future
to
extend
this
to
have
more
providers
than
http
and
https,
but
for
now
it
allows
you
to
pass
a
flag
where
you
can,
instead
of
passing
a
path
to
a
file,
you
can
pass
a
url
to
your
file.
B
Yeah
I
mean
so.
This
is
kind
of
the
counterpart
that
we
talked
about
last
week
with
everyone.
We're
we're
well,
okay,
so,
like
I've
been
slowly
considering
a
way
to
like
have
a
ubiquitous
format
for
saying
when
you
refer
to
a
file
you
might
like
that
file
might
be
not
on
your
disk
so
like
that
file
might
be
involved
or
whatever
it's
going
to
be
really
small
baby
steps
to
get
to
that
final
vision
of
like
this.
B
Like
naming
convention,
I
guess
we
can
call
it,
but
the
first
step
is
having
the
agents
config
file
itself,
like
the
core
config
file,
might
not
be
on
disk.
It
might
be.
Https
probably
did
great
work
with
that.
B
I
used
it
for
something
which
I
don't
think
I
can
talk
about
yet,
but
I
think
I
think,
like
it's
an
exciting
future
and
there's
a
lot
you
could
do
even
with
with
like
what
it
does
now,
for
example
like
just
because
https
doesn't
mean
like
it
has
to
serve
a
file
from
some
other
machine
like
it
could
generate
things
on
the
fly
and
that's
kind
of
neat.
B
Try
it
out
it's
hidden
behind
a
a
feature
flag
which
kind
of
goes
into
the
next
topic,
but
once
once
like,
we
have
more
confidence
in
what
we're
doing
it'll
be
enabled
by
default.
But
for
now
you
have
to
explicitly
say
like
yeah.
I
want
to
opt
in
to
this
weird,
this
new
weirdness
that
might
break.
A
Sounds
like
we're
good
on
it,
nice,
so
dead
branch
of
the
future
flags.
B
Yeah,
so
we
kind
of
agreed
and
turned
we
kind
of
agree
like
between
the
team
that
it's
best
for
everyone
if
the
agent
can
be
released
at
any
time
like
there's
so
many
places
in
grafana
that
use
the
agent
and
it's
hard
for
us,
it's
hard
for
them.
If,
like
we
can't
release
for
any
reason.
So
what
we
started
doing
was
this
dev
branch
idea,
where
we
have
dev
branches
that
hold
work.
That's
not
finished
yet
so
like.
B
B
I
think
I've
done
it
a
few
times.
I
think
the
the
biggest
drawback
is
that
it
like
kind
of
separates
the
community
like
it's.
Essentially,
the
dev
branch
is
for
developers,
it's
not
for
users,
so
it
makes
it
hard
to
get
feedback
on
what
we're
doing
with
a
dev
branch.
B
B
We
are
doing
this
with
what
robbie
implemented
with
the
remote
urls
and
we
are
going
to
also
do
it
for
this
pr.
I
have
open
for
improving
how
integrations
function-
and
you
know,
scraping
and
stuff,
we'll
probably
keep
doing
it
for
more
things,
but
we'll
be
we'll
try
to
be
well.
I
think
I'll
recommend
everyone
that
we
don't
have
a
million
future
flags,
but
I
feel
like
we
might
we'll
see.
C
And
a
quick
question,
slash
comment:
I
think
this
is
pretty
interesting
and
I
think
it
may
be
maybe
interesting
how
this
could
shake
out
for
features
that
exist
upstream
and
prometheus.
For
example,
I
know
there
was
a
prometheus
feature
flag
for
enabling
extra
scrape
metrics
that
I
would
like
to
see
us
enable
in
the
agents
as
well.
So
I
think
we
could
take
some
of
these
features.
That
prometheus
is,
you
know,
hiding
behind
feature
flags
and
bring
them
down
into
the
agent.
A
Yeah
I
mean,
I
think,
feature
flags
are
pretty
common
usage
pattern,
so
I
think
this
just
allows
us
to
move
quicker.
Try
out
more
things.
B
I
was
struggling
to
find
a
way
to
do
feature
flags.
I
opened
a
pr
last
night.
I
think,
gives
us
a
good
way
to
set
up
this
pattern
of
like
there
might
be
many
of
these
things.
B
So
I
I
guess
I
should
say:
like
all
you
know,
these
things
are
happening
in
maine,
we're
coming
towards
the
end
of
the
year,
so
we're
kind
of
we're
gonna,
probably
avoid
releases
so
like
if
you're
looking
toward
or
if
you're
looking
like.
If
you're
excited
about
any
of
that
you're
gonna
have
to
wait
till
mid-january,
probably
after
after
everyone's
back
from
holidays,.
A
All
right
that
leads
to
the
agent
security,
patch
and
I'll
kind
of
set
the
stage
a
little
bit
just
to
give
robert
a
little
bit
of
chance
before
speaking
so
back
in
14.0,
we
released
some
features
to
let
you
see
the
configuration,
the
scrape
targets,
this
inadvertently
ex
could
have
exposed
some
secrets
if
you
had
any
there
on
the
config
endpoint
and
the
targets
endpoint
right,
and
we
recently
patched
our
two
most
recent
minor
versions
or
was
that
last
week
yeah
to
not
only
try
to
replace
those
security
settings
with
placeholders,
but
also
to
disable
the
exposing
of
those
endpoints
by
default.
A
You
can
re-enable
them
the
flag
and
they
would
come
back
if
you've
got
it
behind.
You
know
some
kind
of
secure
network
or
anything
like
that.
Yeah
robert,
you
got
any
anything
you
want
to
add
to
that.
B
Yeah
like
this
is
something
we
found
internally
right.
You
know
I,
I
kind
of
found
this
on
a
call
helping
someone
internally,
and
I
was
like,
oh
that
shouldn't
that
shouldn't
be
happening.
That's
not
right,
so
we
don't
think
this
has
been
exploited
like
the
the
most
kind
feedback
I
found
on
twitter
about
this
was
like
someone
saying
I
don't
think
I
don't
think
that's
a
vulnerability.
B
I
mean
I
disagree
with
them,
but,
like
that's
the
feedback
I
want
and
not
like
this
is
as
bad
as
log
for
j.
Like
you
know
the
I
mean
not
this
okay,
I'm
not
not
not
poo
pooing
blog
for
jay,
but
you
know
what
I
mean
like
it
seems
like.
B
Maybe
the
cve
score
I
assigned
it
was
a
little
bit
higher
than
it
should
have
been,
but
I
do
think
it's
important
for
people
to
understand
that
it
was
a
vulnerability,
so
they
can
patch
and
avoid
accidentally
leaking
secrets
to
people
on
the
same
network.
B
With
that
in
mind,
like
I
think
this
we're
gonna
have
to
do
a
postmortem
on
this,
that
we
released
everyone.
I
think
there's
gonna
be
a
lot
of
interesting
procedure
changes
around
how
we
deal
with
security
for
like
open
source
prs
and
just
kind
of
being
more
conscious
about
that
going
forward,
instead
of
instead
of
just
like
you
know,
base
checks
but
stay
tuned
for
the
postmortem
and
how
we
plan
to
avoid
attempts
to
avoid
security
problems
going
forward.
You
know
it's
never
to
be
perfect.
A
Yeah-
and
I
think
definitely
we're
as
a
company
we're
going
to
have
more
focus
on
that.
Given
we
had
some
other
issues
last
week,
so
definitely
going
to
be
a
company
push.
Do
we
have
any
questions
on
the
security
patch.
D
D
It
is
like
the
feature
mainly
is
you
can
automatically
tag
traces
with
certain
labels
by
using
the
kubernetes
api
to
get
metadata
for
parts
and
name
spaces
and
such
and
in
order
to
do
that,
previously,
we
relied
on
spans
to
be
tagged
with
a
very
specific
tag.
I
think
it
was
net
host
ip
and
now
we've,
I
included
other
methods
of
making
this
part
association.
D
So
now,
like
you,
don't
have
to
rely
on
having
those
like
that,
all
the
time
stacked
with
with
that
specific
label,
which
was
something
very
specific
of
certain
exporters
and
not
all
of
them
did
now.
There
are
other
labels
that
you
can
check,
also
the
host
name
so
yeah
like
you,
can
check
the
host
name
and
finally,
you
can
use
also
the
connection
so
for,
like
http
and
grpc
based
exporters.
D
The
receiver
will
essentially
like
extract
the
ip
off
of
the
sender,
and
you
can
make
the
pod
association
through
that
and
yeah.
You
can
use
all
of
them
any
of
them
like
any
combination
of
them
or
yeah
and
origin
them
in
whatever
priority
you
like
fits
the
best,
your
instrumentation,
so
yeah.
B
Might
have
already
said
this
night,
I'm
sorry
if
you
did,
but
I
think
there
were
some
cases
where
we
couldn't
associate
at
all
for
spans.
Coming
from.
I
think
the
java
client
library
for
hotel
is
that.
Does
that
sound
right.
A
Okay,
any
questions
about
that
all
right,
so
we're
kind
of
open.
Does
anybody
have
anything
they
want
to
bring
up
or
just
questions
or
just
comments,
pretty
free
form.
A
So
if
nobody
has
anything
else,
we
can
end
early
and
give
you
all
some
time
back.
A
All
right
nobody's
anything
else
we
will
depart
and
then
I
will.
It
generally
takes
a
few
hours
for
this
to
somehow
record
and
then
we'll
post
it
up
on
the
youtube
all
right,
happy,
holidays.