►
From YouTube: Fluent Community Meeting March 10th, 2022
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
Right
welcome
to
the
apac
emea
community
meeting
for
fluent
right.
Let
me
dig
out
this
one:
that's
not
what
you
guys
want
to
see,
but
there
we
are
so
brought
this
up
a
few
weeks
back
saying.
A
Maybe
we
should
have
a
more
more
friendly
time
zone
for
people
who
can't
make
it
so
I
I've
been
volunteered
to
to
lead
this
one
in
instead
of
annual
egg,
and
so
today,
we'll
probably
go
over
a
little
bit
of
the
1.9
release
stuff,
any
other
community
things
I
can
think
of
which
is
not
many
at
the
moment
and
then
dennis
is
going
to
do
a
demo,
not
entirely
sure
what
dennis
what?
What
exactly
are
you
going
to
demo.
A
A
So
yeah
we'll
start
with
the
the
1.9
release
update,
so
that
should
be
imminent.
The
cars
can
probably
dive
into
the
details,
but
I
think
we're
waiting
on
there's
some.
A
Last
minute
changes
to
to
go
in
just
to
resolve
a
couple
of
minor
things.
I
think
there
might
be
the
is
it
the
hotel
input
as
well.
That's
that's
looking
to
to
go
into
1.9
as
well,
but
otherwise
we've
cut
four
rc's
and
everything
seems
good
at
the
moment.
So
hopefully
it
won't
be
too
long
jose.
Do
you
want
to
touch
on
anything
there.
C
Okay,
okay,
so
yeah,
as
you
said,
we
are
waiting
on
the
on
some
last
minute
fixes
there
and
we
are
trying
to
to
have
a
very
stable
release
of
it.
As
you
said,
we
are
still
working
on
open
telemetry,
but
we
have
tagged
the
release
candidate
number
four
for
1.9,
I'm
not
sure
if
we
mentioned
this
on
the
in
the
past
community
call,
but
we
are
releasing
release
candidates
starting
in
1.9.
C
So
if,
if
anyone
in
the
community
wants
to
test
them,
make
sure
you
go
to
github
discussions
and
and
look
into
that
post
where
we
are
announcing
these
new
release,
candidates.
C
C
It's
still
for
logs
and
matches,
I
think,
but
traces
is
something
that
we're
working
on.
I'm
not
sure
if
you
will
be
out
now,
but
yeah.
It's
something.
A
C
C
B
In
the
initial
release,
okay,
because
that
that,
for
me,
is
the
thing
that
keep
the
one
thing
that
we're
not
shoving
through
fluent
bit.
Yet
is
some
logs
where
we
have
a
homegrown
logging
demon
that
generates
traces
based
on
log
data.
I
was
planning
to
implement
something
in
fluent
bit
myself,
but
if
you
guys
are
already
doing
that
thumbs
up.
C
Yeah,
it
is
on
the
roadmap
and
we
are
very
excited
to
work
on
that,
but
still
not
ready
for
release
yeah
and
what
we
have
new.
In
there
we
have
engine
plus
metrics,
for
example,
in
the
plug-in
side,
a
windows
metric
collector
that
we
have
seen
some
community
asking
for
for
that.
C
C
As
you
may
know,
we
have
a
partnership
with
amazon,
so
this
is
something
that
we're
doing
as
part
of
this
partnership
and
also
contributions
from
the
community,
the
apache
sky,
walking
and
can't
remember
anyone
where
groundbreaking.
I
think
it
is
a
jamal
support.
C
A
There's
there's
initial
yeah
yeah,
so
the
idea
of
the
animal
support
is
using
the
conflict
file
in
the
animal
format.
Still,
I
think,
that's
still,
there's
still
some
work
to
do
in
that,
but
it's
it's.
The
intention
is
to
deliver
that.
Isn't
it
I
think.
A
Community
dish
contribution
was
there
was
there
was
a?
Was
it
a
nightfall
plug-in?
Something
like
that.
I
think
that
for
like
log
sanitization,
oh
yeah,
which
might
be
useful
and
the
other
big
one
that
eduardo
mentioned
the
other
day
was
the
default
workers
setting,
which
I
think
has
been
tested
quite
a
bit
by
aws
setting
some
default
workers
for
for
the
plugins
by
default
now
and
just
to
improve
the
performance
which
sounds
like
it
would
be
pretty
good,
particularly
for
something
like
the
default
deployments
on
kubernetes.
A
A
Come
quite
useful
but
yeah
they're
all.
A
Quick
look
and
hopefully
it'll
be
out
soon.
I
don't
think
there's
much
else
on
the
community
side
to
cover
obviously
fluent
con
eu's
coming
up.
The
schedule,
hopefully,
will
be
announced
soon
for
that
I'll,
be
there
in
person
doing
kubecon
as
well.
I.
A
B
Okay,
if
you
were.
C
Just
just
one
clarification
on
the
default
workers:
it's
something
that
is
actually
part
of
the
latest
one
point
pain
release
as
well,
so,
okay.
B
A
B
B
B
So
I
made
fluent
actually
read
the
thing
directly
and
so
I'll
do.
A
quick
output
of
this
is
what
the
varnish
ncsa
would
look
like
if
you
just
run
it,
and
this
is
on
a
live
server
and
it's
basically,
you
get
a
tail
of
your
access
logs
and
this
is
not
any
kind
of
sensitive
data.
This
is
all
public
and
this
is
all
anonymous
requests.
B
So
what
I've
added
to
fluent
bit
is
a
new
input
called.
Where
is
it
here
called
coproc,
which
runs
a
process
as
a
kind
of
sidecar?
It
just
runs
a
program,
another
program
along
with
it,
and
it
reads
the
standard
out
of
that
process.
It
is
different
from
the
exec
input,
because
exec
waits
for
a
application
to
finish
and
then
spits
the
log
and
then
absorbs
its
logs.
This
actually
runs
side
by
side.
So,
if
you
look
at
systemctl
yeah.
B
Doesn't
work
in
the
container?
This
is
only
run
under
systems
systemd
in
on
normal
hardware.
This
does
not
run
in.
C
B
Cluster,
at
least
I
haven't
tried
it
in
the
cube
cluster,
but,
as
you
can
see
in
the
system
output
here,
you
see
that
fluent
is
running
and
it's
running
varnish
and
csa
and
we
told
furnish
ncsa
to
spit
its
output
in
a
specific
format.
So
we
can
actually
parse
it
as
standard
log
format,
and
this
is
how
it
would
look.
B
A
B
That's
going
to
go
in
a
pr
yeah.
I
need
to
make
sure
that
well,
I
know
it
works
because
we've
been
running
this,
for
I
think
close
to
three
months
now
yeah,
so
it
works,
it
doesn't
crash,
but
I
want
to
make
sure
it
meets
the
standards
of
contributions.
A
Yeah
yeah,
so
it
sounds
pretty
good.
I
mean
I'd,
be
quite
keen
to
I've
definitely
had
some
use
cases
for
that
in
the
past,
so
it'd
be
quite
useful
too.
To
have
it
because
I
think
I
ended
up
doing
it
in
golang
and
I
had
a
golang
watcher
anyway.
So
I
was
just
executing
the
other
stuff
through
that,
rather
than
through
this
and
yeah.
A
A
Yeah,
okay,
that'll
be
useful
cool.
That
sounds
good.
Let
me
go
back
to.
Is
there
other
stuff
you
wanted
to
cover.
B
A
Yeah
sounds
good
anything
else
you
want
to
cover
talk
about
discuss,
if
not
I'll
bring
it
to
an
end.
B
A
Nothing
on
my
side,
cool
thanks,
guys
and
hopefully
catch
more
people
for
the
next
one.