►
From YouTube: Fluent Community Meeting Sept 30th 2021
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
And
awesome:
well:
yeah,
hey
thanks
thanks
for
everyone
for
joining.
So
this
is
the
september
fluent
community
meeting
and
if
folks
haven't
seen
there
is
a
google
doc,
it's
fully
public.
So
it
goes
over
a
bit
of
an
agenda
what
we
have
for
today.
We
have
a
pretty
light
agenda.
You
know
it's
everyone's
mainly
focusing
on
on
fluentcon
north
america,
which
is
in
in
about
two
weeks.
So
you'll
see
many
of
us
there.
A
If
you
have
any
questions,
thoughts
or
ideas,
we'd
love
to
hear
them,
and
then
of
course
this
is
another
great
forum
where
you
can
share
things
that
you,
you
found
cool
to
be
working
on
things
you
want
to
share
with
the
community
and
we're
you
know
very
supportive
of
you
know,
helping
helping
you
get
that
out.
So
today's
main
topic
is
proposal
for
the
fluent
road
map,
and
I
don't
know
you
know
we
have
some
new
folks
joining
if
shanthanu,
mateo
or
jeff.
A
If,
if
you
have
any
agenda
items
as
well
we'd
love
to
see,
you
know
how
we
can
also
incorporate
those
as
well,
but
maybe
patrick,
I
could
switch
it
over
to
you.
Just
a
quick
run-through
of
the
florida
roadmap.
B
Yeah
yeah,
I
can
do
that
yeah.
I
should
be
able
to
share
screen
and
just
find
it
so
something
we
discussed.
I
think
was
it
two
meetings
ago
there
was
a
little
bit
of
a
chat
about
it,
so
I
just
I've
had
a
little
play
around
and
wanted
to
bring
a
little
proposal
together
that
maybe
we
can
bring
up
at
fluentcon
to
see
what
what
people
think
as
well.
B
So
one
of
the
problems
I've
had
as
an
end
user
certainly
has
been
just
knowing
what
is
going
on
with
like
fluent
organization,
with
flint
d
flat
bit
who's
doing
what
what's
coming
up.
You
know,
particularly
initially
when
I
was
doing
a
park
and
saying
you
know,
does
it
do
this?
Oh
it's
about
to
do
this
or
you
know,
do
I
need
to
do
any
extra
work
and
those
kind
of
questions
as
well.
B
So
so
that's
why
I
sort
of
sort
of
proposed
it
from
I'm
doing
this
more
from
an
end
user
perspective
rather
than
a
dev
perspective,
but
I
imagine,
there's
probably
a
few
other
use
cases
as
well.
So
so
what
why?
Why
do
we
want
this?
You
know
I
touched
it
briefly,
you
know,
is
there
a
feature
influence,
or
is
it
coming
soon
what's
being
worked
on?
If
I
wanted
to
help
out,
do
some
testing
maybe
or
do
some
more
dev,
you
know?
B
Is
there
a
way
who
do
I
contact
to
find
out
that
kind
of
stuff?
Where
do
I
get
a
bit
more
detail?
Those
kind
of
things,
and
also
I
wanted
to
touch
on
like
I
know,
1.8
there's
like
this
new
multi-line
parcel,
that's
come
in
and
there's
there
seems
to
be
a
lot
of
work
at
the
moment
on
like
improving
it
and
resolving
a
few
issues
and
stuff
like
that.
So
it's
not
just
for
like
new
stuff,
but
it
could
be
for
like.
Oh,
we
want
to.
B
We
want
to
improve
this
area
or
we
want
to
do
you
know
fluidcon
or
something
like
that.
You
know
stuff.
That
may
not
be
pure.
You
know
new
feature
stuff
and
yeah
and
it
might
help
you
know
people
if
they
want
to
contribute
they.
You
know
they
can
see.
What's
going
on,
it's
a
bit
more
visible
and
also
yeah.
B
B
We
can
provide
some
resources,
those
kind
of
things
so
that's
kind
of
the
the
stuff
I
I
was
sort
of
focusing
on
basically
the
the
more
end
user
stuff,
the
other
the
other
bit
as
well
was
like
there's
a
lot
of
issues,
and
some
of
them
are
all
kind
of
the
same
issue
at
a
higher
level
or
part
of
a
feature.
Can
we
like
bring
those
together?
It's
really
difficult.
B
If
you
look
at
like
the
issues,
certainly
for
me
like,
what's
you
know,
what's
being
actively
worked
on
what
all
these
things
that
you
know
how
people
report
stuff
is
quite
different
as
well
right
yeah,
so
so
those
are
the
kind
of
things
I
was
trying
to
bring
together.
B
So
I
looked
at
a
few
options
and
how
we
might
do
it.
So
one
of
the
one
of
the
the
things
yeah
we're
based
on
github
already
it's
kind
of
roadmap
stuff,
that's
in
there
github
used
it
themselves
and
we
sort
of
discussed
it.
B
Those
couple
of
meetings
ago,
it's
in
it's
in
the
in
the
minutes
which
are
in
that
google
doc
about
what
we
can
do
and
kind
of
some
of
the
decisions
where
you
know
we
want
one
sort
of
top
level
for
the
whole
fluent
organization
being
able
to
filter
on.
Oh,
is
this
a
bit
thing?
Is
this
a
fluent
d
thing?
Is
this
a
fluent
operator
thing?
You
know
those
those
kind
of
areas
as
well
and
then
yeah
bring
that
associate
those
those
tasks
together.
B
So
you've
got
a
lot
of
jiras
at
the
moment
on
some,
you
know
dns
error.
Maybe
we
can
have
a
high
level
action
that
we
need
to
improve
dns
and
we
just
put
that
on
the
roadmap,
and
then
people
can
see
it's
being
worked
on.
One
thing
as
well:
I
wanted
to
to
make
sure
is
you
know
it's
great
having
like
wonderful
visibility
and
all
that
stuff?
B
But
you
know
people
actually
need
to
do
the
work
as
well
and
if
you
give
them
another
thing
to
to
to
manage
and
and
keep
up
to
date
and
and
all
that,
you
know
that
that's
a
bit
of
a
nightmare.
So
how
can
we
keep
that
overhead
to
a
minimum
and
also
don't
change
the
current
process
because
yeah
this
is
a
proposal?
Maybe
it's
not
going
to
work,
we
don't
really
want
to
stick
a
load
of
stuff
in.
I
don't
have
to
take
it
out
again.
B
So
that's
what
I
was
looking
at
and
then
when
I
started
looking
into
it
as
well.
You
know
github
roadmaps
seem
to
have
like
this
kind
of
triage
board
as
well,
which
might
be
useful,
for
you
know,
there's
other
options
as
well.
You
could
have
a
road
map
board
you
could
have.
These
are
the
bugs
we've
triaged
them
and
kind
of
prioritize
them
and
maybe
allocate
them
to
certain
people
or
or
whatever
those
kind
of
things,
there's
a
few
other
options
as
well.
B
You
know
you
can
have
they
call
it
a
project,
you
know,
but
it
is
essentially
you
could
have
a
board
per
feature.
You
could
have
a
board
per
repo,
so
yeah
well
just
one
for
fluentd,
once
it's
a
little
bit
that
kind
of
stuff
or
one
for
organization,
but
the
organization
seemed
to
fit
fit
a
bit
nicer
and
certainly
seemed
to
be
what
people
wanted
a
few
weeks
a
few
months
ago.
B
So
that's
what
I
was
trying
to
keep
on
oh
yeah,
and
I
was
thinking
as
well.
You
know
like
things
like.
If
you
have
a
feature,
if
you
have
something
on
that
roadmap,
maybe
you
could
have
a
a
dedicated
slack
channel
for
that,
rather
than
just
all
in
the
same
room
and
stuff
like
yeah,.
C
B
You
want
to
communicate
and
people
can
get
a
bit
more
information
and
and
interact
as
well
might
be
might
be
a
good
one
too.
There's
there's
some
questions
about
you
know
if
people
are
doing
stuff
commercially
or
helping
out,
and
maybe
they
don't
want
it
visible
on
the
open
source
stuff
or
how
do
we?
How
do
we
tie
that
in
you
know,
if
aws
is
doing
some
work
to
help
improve
a
bit?
B
How
can
you
show
that
when
they
might
not
want
to
commit
to
oh
we're
going
to
do
it
by
x,
state
or
whatever,
and
we
certainly
covered
that
last
time
as
well,
making
making
the
road
map
a
bit?
You
know
not
a
we're
going
to
deliver
this
feature
on
this
day,
it's
more
just
a
a
high
level.
This
is
kind
of
where
we
see
it
fitting.
There's
no
guarantees
that
it'll
be
done,
but
that's
that's
kind
of
the
relative
priority
of
it.
A
Yeah,
I
I
think
you
know
even
one
thing
I
was
thinking
as
well.
Is
you
know
some?
Sometimes
we
release
features
just
as
soon
as
we
have
at
least
the
basic
thing
working
and
then
we'll
find
edge
cases,
and
then
we
have
to
go
fix
those
and
and
so
on
and
so
forth.
A
a
maturity,
kind
of
exactly
yeah.
That's
a
better
way
to
describe
it.
So
we
could
say
like
multi-line.
Is
this
new
multi-line
mode
is
in
preview?
Okay,
it's
reached
beta,
it's
now
ga
as
we
get
into
yeah
specific
features
as
well.
I
think
that
could
be
could
be
helpful
for
folks.
C
I
have
a
question
so
what's
the
sort
of
how
much
wider
you
think
you
are
going
to
incorporate
within
this
roadmap,
meaning
if
we
are
to
talk
about
fluent
of
lin
a
kind
of
core,
I
think
we
could
write
a
road
map
about
it.
C
But
companies
like
us
having
things
like
you
know
the
plugins
that
help
people
to
operate
their
fluency
a
little
bit
a
little
bit
easier
or
you
know,
security
plug-in
that
can
mask
data
on
the
fly
and
in
a
pipeline
it
will
be
actually
completely
contributed
as
we
go,
but
these
are
actually
happening
within
the
community
and
this
roadmap.
B
I
mean
that's
a
that's
a
tricky
question
to
answer
directly
and
it
sort
of
touches
on
that
kind
of
aspect
of
yeah
people
want
to
contribute,
but
they
don't
want
to
be
saying.
B
You
know
this
is
this
is
when
it
will
go
in
and
maybe
being
tied
to
it,
making
it
too
public,
but
but
also
making
it
visible.
That
people
know
that
you're
working
on
this
yeah,
someone
else
isn't
also
working
on
it
and
there's
that
kind
of
competition.
When
you
could
be,
you
know,
you
know,
sharing
those
resources,
I
don't
know
I
mean
the
other
thing
I
was
thinking
as
well
is
so
here.
So
I
followed
sort
of
the
the
github
public
roadmaps,
one
which
you
can
see
here.
B
That's
bloody
massive
and
they've
got
loads
of
math
yeah
yeah,
that's
yeah,
there's
like
dependency,
bot,
stuff
and
yeah.
The
the
good
thing
is,
you
can
kind
of
you
can
start
small
and
maybe
explode
it
as
as
you
go
and
and
add
things,
and
then
they
sort
of
get
into
the
kind
of
future
future
stuff.
B
So
maybe
we
could
have
something
like
that
where
we
we
put
in
you
know
kind
of
contribution
that
isn't
specific
but
yeah
or
long-term
stuff
as
well,
because
there's
there's
stuff
that's
in
the
future,
but
it's
kind
of
ongoing
as
well,
maybe
and
things
like
that
perpetual
kind
of
tasks
as
well
security
analysis,
those
kind
of
things.
Maybe
so
I
don't
know
what
I
mean.
What
would
you?
What
would
you
suggest
would
be
my
my
question.
C
I
think
we
can
focus
on
really
fluent
different
as
a
it's
hard
to
define
this
language
if
it's
cool
or
not,
but
I
think
we
can,
I
would
say
the
core
features
of
fluent
differently.
For
example,
fluent
bit
is
gonna,
let's
say:
implement
metrics
capability
for
windows,
that's
a
big
thing
right
and
then
we
should
be
aware
as
a
community
roadmap,
but
the
plugins
that
can
help
you
know
the
people's
daily
operation
or
some
security
improvement.
Addition,
you
know,
doesn't
have
to
be
kind
of
roadmap.
C
People
contribute
everyday.
So
that's
I
would
think
we
can
kind
of
tell
people
this
modern
math
is
about
core
or
major
kind
of
road
map
that,
where
we
tell
people
where
we
are
heading,
you
know,
rather
than
you
know,
bitty
backlog,
the
feature
you
know
featured
back
yeah
yeah.
I.
B
See
I
see
what
what
you're
you're
meaning
yeah
and
I
I
certainly
agree
with
that.
I
I
wasn't
thinking
we'll
put
like
every
single
issue
or-
or
you
know,
contribution
on
here.
It's
it's
more
those
kind
of
high
level
things
that
that
can
yeah
that
people
are
willing
to
share,
but
also
you
know,
there's
little
things
as
well.
You
know
like
I've,
updated,
you
know,
dependency
or
stuff
like
that.
You
know.
Maybe
that
doesn't
make
it
onto
the
road
map.
It's
it's!
It's
yeah!
A
Think
of
the
rag
yeah
I
I
completely
agree
with.
We
could
even
use
labels
to
to
help
separate.
Oh,
I
see
eyeshadow.
You
have
your
your
hand
raised
any
comment
here
as
well.
D
Yes,
so
is
documentation
planned
in
the
roadmap.
Somehow
because
special
case
I
have
recently
discovered
fluent
bit.
It's
been
a
breath
of
fresh
air
compared.
C
D
Other
stuff,
what
happened
is
I
set
it
up
very
quickly
and
when
I
hit
some
nuance,
things
which
I
was
looking
for,
I
ended
up
going
to
github
going
through
issues
discovering
some.
You
know,
lua
thing
that
I
had
to
add
to
the
log,
and
now
it
is
working
so
my
take.
Is
that
often
what
happens
is
the
documentation?
Is
there
but
examples
are
missing
so
examples.
C
D
From
yeah
and
specifically
around
debugging,
the
log
pipeline
yeah.
A
D
D
So
my
recent
question,
on
the
top
of
my
mind,
is
how
do
I
up
sort
of
p
print
the
record?
You
know
the
incoming
record.
I
want
to
discover
something
from
the
record,
because
a
lot
of
examples
assume
kubernetes.
I
am
not
using
kubernetes.
I
still
need
to
do
something.
What
do
I
am?
What
am
I
doing
like?
What
do
I
have
to
do?
You
know
stuff
like
that.
A
Yeah,
I
I
totally
agree,
I
think,
there's
a
lot
of
like
I
would.
I
would
consider
this
part
of,
like
the
developer
or
even
practitioner
experience
that
we
want
to
give
with
flipbit.
I
I
I'm
fully
supportive
of
like
more
examples
and
ways
to
to
show
off
those
examples.
A
We
created
the
fluent
discuss
forums
probably
about
three
four
months
ago.
They
have
some
decent
use
with
fluentd,
but
to
be
honest,
it's
a
bit
it's
a
bit
underwhelming,
and
so
we
have
like
it's
kind
of
caused
more
problems
than
I
think
it
helped
where
there's
a
new
place,
that
people
are
sending
data
and
it's
siloed
from
stack
overflow.
A
It's
siloed
from
the
slack
it's
siloed
from
the
google
groups,
and
I
I
almost
feel
I
know
we're
taking
this
in
a
tangent,
but
maybe
we
just
use
github
discussions
or
something
and
github
discussions
are
like
meant
to
be
that
type
of
here's
an
example.
Here
I
have
a
question
about
like
how
do
I
get
this
example
and
we
deprecate
all
the
other
groups
so
that
it's
very
simple
to
say.
If
I
have
a
long-standing
question,
I
go
to
discussions.
A
D
I'm
I
am
for
reducing
things
personally
and
I
think
cross
linking
with
the
fluent
bit.
Docs
project
might
also
just
work,
so
it
might
be
like
the
same
border
yeah.
So
I
mean
I
submitted
one
a
pr,
so
I
tested
it
to
work
and
it's
like
a
one-liner
fix.
D
A
Yeah,
that's
I.
I
think
I
would
agree
with
that,
because
right
now,
there's
like
jumping
between
like
five
different
places,
wow
almost
like
another
proposal,
but
I
I
think
it's
maybe
it's
for
the
benefit
right.
We
just
redirect
discuss
that
fluent
d
to
github
discussions.
Maybe
we
migrate
everything
from
google
groups
into
github
discussions.
D
The
way
I
use
instant
communication
things
usually
is
like.
I
ask
a
question.
Sorry.
If,
if
I'm
answering
a
question,
if
somebody
knows
I
say
point
to
the
github
issue
or
point
to
the
github
thing,
so
the
instant
communication
channel
remains,
but
because
it's
such
a
high
traffic,
quick
moving
thing,
it
becomes
difficult
to
catch
up
on,
so
it
has
its
use.
But
over
time
we
I
mean
I
mean
you
guys
can
decide
but
deprecating.
It
is
fine.
I
mean
yeah
anyway,
I'm
new
here.
A
So
no,
no,
that's
I'm
really
happy
yeah!
You
joined
we,
we
love
all
opinions,
so
I
I
think
yeah
I've
had
this
idea
of
reducing
more
like
there's
this
art
of
subtraction,
and
how
can
we
subtract
more
places?
I
think
some
places
like
stack
overflow.
We
just
will
never
be
able
to
subtract
because
it's
its
own
community
essentially
and
we
just
are
a
participant
in
there
but
other
places
where
we
do
own
the,
how
the
community
interacts
and
everything
like
with
google
groups
and
and
other
places.
A
If
we
just
move
it
to
github.
Maybe
it
creates
a
better
area
for
how
to
get
more
examples
out
to
to
the
masses
right,
here's,
five
or
six
lua
scripts.
Here's
how
you
can
do
a
grep.
You
know,
I
see
all
the
time.
How
do
I
search
my
blogs
and
only
include
the
following?
If
it
contains
how
do
I
exclude
debug
logs
right
like
those
come
up
frequently?
How
can
we
make
that
so.
C
Yeah
yeah,
I
think
that's
the
communication
channel
is
one
and
then
so
back
to
chantal's
original
comment
about
documentation
with
examples.
C
This
is
this
is
a
very
missing
area,
but
of
the
fact
that
we
we
did
provide
commercial
services
around
food
and
nuclear,
but
we
write
some
blogs
about
how
people
can
utilize
how
people
can
configure
things
and
then,
once
in
the
past,
we
wrote
about
how
they
can
configure
fluent
for
kafka
with
rd
kafka
and
kerberos
authentication,
which
is
very
simple
example
right,
but
has
the
most
access
on
this
website,
because
the
community
document
you
know
doesn't
have
that
kind
of
example.
There
yeah
there's
no.
C
Yeah
and
then
also
tips,
debugging
tips
is
something
we
develop
as
well,
but
it's
it's
not
a
yet
publicly
documented
in
you
know,
organizations,
but
people
like
us,
the
first
adapter
to
this
community
yeah.
We
should
have
better
resource
or
easier
access
to
those.
I
really
agree
with
that
program
statement.
A
Yeah-
and
one
thing
I
saw
digitalocean
had
done,
and
maybe
we
can
ask
cncf
for
help
on
this-
is
like
they
would
almost
build
this
fund
for
people
to
write
blogs
and
example,
use
cases,
and
so
you
know
like
it's
not
like.
You
have
to
spend
all
the
time,
but,
okay,
here's
it's
not
a
super
meaningful
amount,
but
like
hey,
here's
100
bucks,
so
you
know
it
gets,
gets
folks
excited
about
making
making
the
content.
So
maybe
that's
something.
C
C
Yeah
that
fan
can
be
also
utilized.
For
example,
if
you
have
a
you
know,
just
a
working
configuration
and
a
set
of
instructions.
C
D
But
that
type
of
content
I
mean
this
is
far
away,
but
it
there
would
be.
It
would
be
an
awesome
way
if
it
was
like
multiple
setups
could
be
configured
like
one
with
css
log
output,
one
with
say,
loki
output.
D
You
know
where
there
are
four
or
five
variations
like
say
incoming
syslog
with
some
filters
and
then
outgoing
loki.
That's
one
example.
You
know.
D
D
A
D
A
Yeah
but
more
kind
of
community
tooling
around
around
this-
I
I
I
tend
to
agree.
I
know
I
know
we've
kind
of
drifted
a
little
bit
from
from
the
roadmap
side,
patrick,
but
I
I
think
yeah
this
is.
This
is
a
really
good
topic
about
almost.
C
A
B
A
A
B
Anyway,
yeah,
that
was
the
roadmap
proposal.
The
main
thing
on
the
last
slide
was
what
github
do
is
they
put
it
in
a
separate
repo,
and
it
makes
a
lot
of
sense
because
then
you
have
your
separate
issues
and
you
can
just
link
all
the
other
ones
and
then
there's
no
impact,
and
if
we
decide
we
don't
want
to
do
this,
we
just
delete
that
repo
and
everything
everything
goes
as
well.
B
So
that
was
just
an
awesome
but
yeah.
I
think
the
documentation
one's
a
good
one
and
those
worked
examples
as
well.
If
they
can
be
built
and
tested.
You
know
as
part
of
the
release,
then
that
that's
something
it's
a
hard
thing
to
do
to
do
well
and
and
make
sure
it's
consistent.
You
know
like
how
do
you
test
that
things
are
going
into
low-key
and
in
a
way,
that's
you
know,
yeah
changes,
the.
A
Api
or
whatever
we
do
have
end-to-end
tests,
we
do
with
splunk
and
elasticsearch
and
google
services.
Today
we
need
to
expose.
A
Yeah
yeah
almost
like
it's
all
open
source,
but
like
here's,
the
examples
we're
using
for
the
end-to-end
test
and
maybe
folks
want
to
play
around
with
it,
go
ahead
right.
You
know
you
want
to
adapt
it
for
their
own
use
great.
So
I
think
I
think
that
would
be.
That
would
be
really
really
good.
A
Okay,
I
think
we're
we're
at
the
end
of
time
here,
so
I'm
going
to
go
ahead
and
pause.
The
record.