►
From YouTube: Opening Remarks + Project Updates - Bartek Płotka, Open Observability Day Program Co-Chair
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Opening Remarks + Project Updates - Bartek Płotka, Open Observability Day Program Co-Chair
A
Hello,
everyone
and
welcome
to
the
open
observability
day,
co-located
event
during
kubecon,
my
name
is
bartek
and
together
with
Eduardo,
we
are
co-chairs
of
this
event
and
in
the
next
25
minutes,
I
would
like
to
share
with
you
some
important
information
about
logistics,
acknowledgments
and
some
initial
contacts
about
this
event.
A
So
yeah,
let's,
let's
start
so
in
terms
of
logistics.
Two
simple
rules,
you
know
code
of
conduct
applies
so
be
you
know
nice
and
friendly
to
each
other,
respectful
because
we
want
to
make
sure
this
space
is
just
safe
and
and
and
harassment,
free
and
masks
are
acquired.
Still,
we
have
coffee
times,
so
please
make
sure
we
have
them
on
unless
you
are
actively
eating
or
talking
for
the
social
media
and
and
other
information.
A
Please
use
this
hashtag
open
observability
day
and
and
also
make
sure
that
I
mean
to
understand
that
the
dogs
are
alive
and
kind
of
visual
attendees
are
watching
them
and
there
will
be
kind
of
uploaded
two
days,
at
least
after
the
event.
There
is
Wi-Fi
as
well,
so
feel
free
feel
free
to
use
it
for
virtual
discussions
and
any
questions
any
any.
A
You
know
anything
you
would
like
to
share
with
others
and
maybe
not
on
the
scene
or
during
you
know,
networking,
but
just
virtually
we
have
a
daily
slack
Channel
or
actually
it's
not
dedicated
it's
dedicated
for
today.
For
this
talk
it's
generally
a
slack
channel
of
TAC
observability
I
will
explain
to
you
what
DAC
observability
is
later
but
feel
free
to
really
use
it,
and
even
if
you
are
in
person,
just
really
help
virtual
attendees
to
understand
what's
happening
and
just
answer
the
questions
or
even
ask
questions
right.
A
So
we
will
prioritize
the
questions
from
the
audience
here
just
in
person,
but
we
would
love
to
kind
of
take
a
couple
of
questions
from
virtual
attendees
as
well,
so
we'll
be
monitoring
this
channel
and,
first
of
all,
let's
have
some
acknowledgments.
Let's
thank
everyone
who
make
this
even
happen.
A
So,
first
of
all
program
committee,
there
were
like
a
bunch
of
people
who
were
like
very
hard
working
on
reviewing
those
stocks.
There
were
lots
of
them
and
yeah.
Thank
you.
Thank
you
to
them.
Finally,
I
mean
not
finally,
but
a
second
thanks
to
just
cncf
staff
and
venue
staff.
They
are
doing
very
hard
work
to
make
this
happen.
So
thank
you
so
much
for
all
of
this,
and
you
know
sponsors,
of
course,
without
the
sponsors
we
wouldn't
be
able
to
meet
here.
A
So
thank
you
for
Diamond,
Sports
sponsors,
caliptia
and
chronosphere
and
platinum,
open
source,
and
we
have
also
thank
you
to
two
gold
sponsors.
Okay.
So,
let's
share:
let's
spend
a
couple
of
minutes
to
really
understand
where
we
are
like
why
we
are
even
here
what
we
are
doing
here
and
by
the
way
this
is
my
own
cat.
I
really
wanted
to
have
my
card
being
a
mem,
a
meme,
so
yes
I
finally
get
opportunity
to
do
so.
A
So
what's
observability
right,
like
generally,
we
are
here
for
observability,
but
what
it
really
means
why
it's
so
popular
nowadays.
So
my
definition
is
very
clear.
You
know
it's
the
ability
to
understand
the
current
or
past
states
of
your
application
or
process
running
on
your
machines
or
multiple
machines,
one
or
maybe
thousands
processes,
and
you
know
understanding
like
what
it
is
actually
doing
right,
because
we,
maybe
you
know,
program
it
in
some
way,
but
we
have
to
you
know,
make
sure
it's
actually
running
as
we
expected.
A
So
the
second
definition
is,
you
know
it's
observability
is
answering
unknown
unknowns.
What
it
means
is
that
we
are
shipping
this
this
application
somewhere
and
it's
kind
of
complex
environment,
and
we
would
like
to
we.
We
know
certain
known
unknowns
like
it
can
be
down.
There
might
be
some
errors
on
HTTP
and
there
might
be.
A
You
know
this
memory
usage
roughly
or
we
will
know
what
is
the
memory
usage,
so
those
are
known
unknowns
and
we
can
cover
those
and
and
unveil
those
who
using
standard
traditional
monitoring,
but
observability
goes
even
even
further
right.
We
really
want
to
know
the
unknown
unknown.
So
perhaps
the
questions
that
we
don't
know
we
will
be
asking
in
future.
For
this
we
need
a
really
good
observability
to
be
able
to
navigate
through
the
states
for
the
events
that
application
is
is
performing.
A
So
we
mentioned
that
observability
kind
of
allows
us
to
in
first
state
of
application,
using
certain
signals
using
external
signals,
and
this
is
where
it
comes
to
free,
observability,
pillar
signal
signal
pillars,
and
you
know,
traditionally,
probably
you
are
aware
we
really
were
talking
about
metrics,
so
some
aggregate
numbers
that
aggregate
certain
events
tracing
which
is
kind
of
request,
transaction
based
information
about
you
know
even
that
happen
across
different
transactions
and
and
logging,
which
is
really
some
kind
of,
like
you
know,
simple
observability
for
for
for
scoping
that
you
know
putting
information
about
the
events
that
were
happening
in
our
system.
A
So
all
of
this
is
great
I-
think
it's
already
kind
of
expensive
and
sometimes
difficult
to
set
up
all
those
things.
But
we
are
not
stopping
here,
like
recently
we're
adding
more
signals
right-
and
this
is
where
I'm
you
know.
I'm
super
fan
of
experiment
experimenting
in
this
space
and
recently
we
have
grow
in
profiling
and
particularly
in
continuous
profiling,
because,
as
as
our
application
is
sitting
there
and
and
Performing
some
work,
we
want
to
kind
of
go
past
into
what
profiles
have
been.
A
You
know
one
hour
ago,
and
this
allows
us
to,
for
example,
find
the
performance
issues.
You
know
that
happened
one
hour
ago,
for
example,
you
have
a
memory
leak.
It's
to
enter
your
application,
crashed
it's
too
late
to
get
per
profile.
Now
you
want
to
get
a
profile
just
before
the
memo
leak.
So
this
is
where
can
to
your
continues
providing
shines
and
we
can
in
some
way
put
it
as
a
as
another
observability
signal,
but
we
are
not
stopping
even
there
right.
A
Like
recently,
we
have
an
amazing
blog
post
from
Yuri,
and
that
mentioned
there
are
actually
six
signals
right:
six
yeah
I'm,
counting
it
right,
so
he
mentioned
profiling
on
top
of
like
free
basic
signals,
but
also
exceptions,
but
also
events.
A
So
it's
amazing
to
be
open-minded
here
and
just
learn
about
different
profits
of
categorizing
certain
data
differently,
so
observability
is
easier,
but
I'm
not
sure.
Yet,
if
this
is
like
a
correct
categorization,
there
has
to
be
balance
between.
You
know
clear,
categorization
of
certain
signals
we
observe,
but
also
like.
We
don't
want
to
have
them
too
many.
A
It's
just
too
complex
right,
so
I
would
I
would
argue
with
some
of
this,
but
it's
amazing
to
have
to
see
people
experimenting
and
innovating
in
the
space
to
make
things
easier
in
the
long
run
so
be
mindful
like
check
this
blog
post.
It's
it's
super
super
useful,
so
we
of
course,
in
the
cncf
space.
We
have
some
projects
that
helps
in
this
observability
mission
right.
A
A
So
graduated
are
those
the
most
major
projects
and
we
have
on
the
left
fluenty
as
the
first
one,
which
is
I
mean
we
have
maintainers
here
on
this
on
this
in
this
room
like
we'll,
be
speaking
about
that
for
sure,
but
generally
it's
just
like
you
know,
just
collector
and
pipeline
for
for
logs
and
analyzing
those
we
have
hiager,
which
is
kind
of
API
and
a
bit
of
storage
and
like
really
patterns
for
distributed
tracing,
we
have
Prometheus,
which
is
like
a
metric
system,
but
it's
much
more
than
this.
A
Actually,
it's
just
gives
you
know,
monitoring
patterns
that
allow
you
to
alert
and
monitor
in
a
very
reliable
way,
in
your
infrastructure,
with
prom,
ql
and
so
on.
Then
we
have
incubated
projects,
we
have
cortex
and
then
I
will
take
like
the
the
latter
tunnels
as
well
as
one
because
they
are
really
solving
similar
problems.
They
are
essentially
databases
for
distributed
metric
ingestion
and
storage,
so
you
can
think
of
it
about
like
Prometheus,
but
putting
in
scalable
kind
of
environments
right
just
you
know
to
have
like
billions
of
metrics.
A
Not
only
10
Millions
like
less
single
Prometheus
can
can
handle
right,
but
it's
kind
of
forming
the
same
family
or
Prometheus
ecosystem
that
I'm
personally
in
as
well
and
kind
of
maintainer
of
Prometheus
and
Thanos.
We
have
open
metrics
and
open
Telemetry.
Those
are
kind
of
similar.
So
start.
Let's
start
with
open
metrics
open
metric
is
just
a
standard
or
protocol.
You
could
say
for
ingesting
scraping
metrics
from
your
application.
It's
born
from
from
Prometheus
Exposition
format.
Open
Telemetry
is
much
much
more.
A
It
has
some
standards
for
metrics
logs
profiles,
recently
profiles
and
then,
and
then
traces
well,
I
said
that
right,
tracings,
Matrix,
logs
and
profiles.
Some
of
them
are
maybe
still
in
progress,
but
generally
does
the
mission,
and
but
that's
not
all,
they
have
also
SDK.
They
have
also
collector
application
that
you
can
just
put
and-
and
it
understands
those
protocols
and
can
pipeline
to
your
storage
or
render
of
your
choice,
and
we
have
actually
a
couple
of
new
projects
down
there
with
sandbox
level
and
they're
pretty
amazing.
It's
good
to
kind
of
see.
A
You
know
where,
where
things
are
evolving
so
fonio
is
security.
Monitoring
agent
based
on
ebpf
Cube
healthy,
is
an
operator
that
allows
you
to
just
you
know
very
easily
and
like
in
a
standard
way
check
your
kubernetes
system.
So
if
your
notes
are
healthy,
if
your
apis
are
healthy
and
you
just
run
it
in
periodically
checks
and
produce
some
metrics
open
course,
which
is
like
amazing
framework
and
UI
to
you
know,
just
just
monitor
your
performance,
metrics
or
different
features.
A
A
We
have
Pixi,
which
is
another
ebpf
agent,
but
it's
also
kind
of
like
bigger
framework
for
taking
observability
and
security
kind
of
information
from
ebpf
and
kind
of
put
that
into
into
some
database.
We
have
Schooner,
which
is
open
source
UI
for
kubernetes.
And
so,
if
you
are
bored
of
cube
cattle
you
can
you
can
try
that
it
actually
has
a
monitoring
built
in.
So
there
are
some
dashboards,
and
so
it's
pretty
sweet
and
trickster,
which
is
like
a
cache
for
web
services.
A
But
it's
cached
primarily
for
time
series,
applications
or
databases,
so
so
you
could
use
it
with
grafana
to
like
make
your
girlfriend
a
much
faster
by
you
know,
because
it
caches
some
stuff.
So
generally,
all
of
it
is
open
source.
All
of
it
is
apache2.
So
this
is
what
we
are
doing
in
the
cncf.
We
are
trying
to
kind
of
maintain
those
communities
unhealthy
healthy
projects,
healthy
software
really
right.
A
A
You
know
you
have
to
have
or
like
find
someone
who
will
do
operations
of
your
pro
of
your
software.
You
know
Community
Building
education,
you
know
just
agreeing
on
apis
and
standards
and
it's
just
critical
parts.
So
code
is
just
one
thing
right.
For
this
reason
we
have
various
Tools
in
in
the
cncf
ecosystem,
so
one
of
them
are
those
interests,
groups,
special
interest
groups
which
are
tied
to
communities,
and
there
are
advisory
technical
advisory
groups,
tag
which
are
generally
for
all
the
projects,
not
only
kubernetes.
A
So
we
have
two
groups
for
monitoring
or
observability
kind
of
case.
First,
we
have
like
tied
to
kubernetes
seek
instrumentation,
but
it's
actually
much
more
like
it's,
essentially
how
to
instrument
kubernetes,
but
actually
how
to
how
to
monitor
kubernetes
and
observe
kubernetes
in
a
in
an
efficient
way.
So
if
you
are
interested
into
contributing
into
the
space
or
maybe
ask
questions,
for
example,
how
do
I
monitor
my
kubernetes?
Like
that's
the
space
you
should?
You
should
go?
There
are
periodic
meetings,
there
are
kind
of
slack
channels,
so
that's
Community
around
exactly
that
right.
A
Second
group.
We
have
and
we
have
tag
observability
and
I'm
kind
of
tackled
there,
and
you
are
welcome.
We
are
meeting
you
know,
B
weekly
as
well,
and
this
is
more
kind
of
overreaching
the
kubernetes,
because
we
really
try
to
unify
the
space
of
observability
and
educate
others
on
on
higher
level.
A
So
yeah,
you
are
also
welcome
to
join
us
really
talk
about.
You
know
your
usage
perspective,
what
you
are
missing
and
what
do
you
don't
know
or
like
you
want
to
look
like
what
would
you
like
to
know
so
so
I
recommend
like
just
visiting
this
space.
So
if
you
want
to
learn
more
on
kubecon,
there
are
two
talks
about
that.
On
Wednesday
we
have
attack
observability
update
and
on
Friday
we
have
seek
instrumentation.
A
A
Then
there
will
be
like
building
observability
pipelines
so
something
about
fluency.
Then
they
will
have
break
we'll.
Have
then
two
talks,
two
main
talks,
then
two
lighting
talks.
Then
lunch
and
free
lighting
talks
two
talks
around
open,
Telemetry.
Actually,
then,
the
coffee
break
and
finally
free
free
livestocks
around
distributed
web
assembly
or
distributed
training
in
webassembly,
yeah
observability,
introduction
again
and
yeah
more
observability
in
kubernetes
networking.
So
it's
it
looks.
A
Pretty
sweet,
so
thank
you
for
those
who
propose
talks
and-
and
it's
kind
of
first
first
I-
think
Event
open
up
service
day
ever
so.
Hopefully,
if
you
would
like
it,
if
you
could
give
feedback
that
we
will
kind
of,
you
want
us
to
do
those
more
like.
Please
give
that
feedback
and
we'll
continue.
Okay,
as
a
last
kind
of
piece
of
this
talk,
I
would
like
to
we.
A
We
have
this
idea
to
kind
of
share
awareness
of
what
those
projects
are
doing
so
the
project
you
saw
on
the
landscape
and
we
will
talk
about
essentially
graduated
and
incubated,
so
those
two
first
rows
and
I
will
have
some
some
updates
from
each
of
those
projects.
A
Just
might
give
you
awareness
like
what
they
do
and
where
they
are,
if
you
are
really
using
them
already.
So
let's
go
so.
Let's
start
with
fluency
and
I
will
ask
Eduardo
to
come
and
help
me
with
that.
B
Thank
you
well,
first
of
all,
thanks
for
coming
to
the
first,
a
open
observability
day
and
just
a
quick
update
of
the
project.
Fluid
was
born
many
years
ago,
10
years
and
it's
a
really
stable.
We
found
it
that
it's
working
in
major
Cloud
providers
and
in
hundreds
and
hundreds
of
companies
and
as
part
when
we
created
fluency,
we
started
iteration
with
the
new
generation
of
fluency,
which
is
called
fluent
bit,
which
is
a
sub-project
of
the
flu
in
the
ecosystem,
and
this
week
we
are
announcing
the
launch
of
flu
and
bit
2.0.
B
So
I'm
with
fluent
b2.0,
the
first
major
change
and
vision
in
the
project
it
used
to
be
just
for
lock,
lock
type
of
data,
and
now
we
switch
all
the
project
to
support
multiple
type
of
signals.
So
now
we
fully
support
locks,
metals
and
traces
right.
That
means
full
compatibility
with
Prometheus,
open
metrics
and
open
telemetry
with
film
b2.0
also
comes
with
higher
performance.
Initially,
the
project
at
the
beginning
didn't
support
any
threading.
It
was
just
a
single
process
used
doing
asynchronous
a
asynchronous
events,
doing
a
synchronous
Connection
in
just
one
thread.
B
B
One
of
the
other,
a
community
asks
is
like.
Okay,
me,
Agent
is
working,
but
how
can
I
see
the
data
that
is
flowing
through
the
agent
before
it
hits
the
destination
right?
And
why?
Because
sometimes
things
go
wrong
in
the
network
or
sometimes
the
data
that
arrives
to
my
back
end
like
a
database,
elastic
or
Amazon
E3
doesn't
have
the
format
that
it
was
expecting.
B
So
how
do
I,
troubleshoot
and
debug
that
tap
tap
is
a
new
feature
that
allows
you
to
talk
to
flow
embed
over
an
https
endpoint
and
tell
it
a
send
me
a
snapshot
of
the
data
that
is
flowing
through
this
input
plugin
right
now,
and
it
will
send
you
a
sample
for
a
couple
of
seconds,
so
you
can
inspect
live.
What's
going
on
with
the
agent.
B
For
the
other
side,
we
didn't
support
in
the
beginning,
a
TLS
for
the
input
plugins,
because
we
were
doing
networking,
but
most
of
the
security
side
was
for
the
output
side
of
the
agent.
Now
in
the
input
side,
if
you
wanted
to
use
this
as
a
collector
aggregator,
you
will
have
all
these
capabilities
and
if
you
are
Developer
that
is
looking
to
put
your
business
logic
into
the
agent
we.
We
support
this
Lua
scripting
a
couple
of
filters
also
to
do
enrichment,
but
now
we
have
extended
this
for
golang.
B
A
All
right,
let's
quickly,
move
over
other
projects,
so
I
asked
kind
of
community
members
of
of
other
projects
to
like
bring
give
me
some
slides
of
updates.
So
it's
kind
of
fresh
for
you.
Some
of
them
are
on
this
conference,
but
still
traveling,
so
we
couldn't
have
them
in
today,
but
let
me
kind
of
go
through
roughly
for
the
Jagger.
So
Jagger
as
a
reminder
is
a
distributed
tracing
system-
and
you
know
it's,
it
seems
like
there
are
lots
of
updates
recently
seen
since
since
kind
of
last
last
kubecon.
A
So
they
have
this
monitoring
Tab
and
I'm,
using
jagers,
I'm
kind
of
like
a
user
as
well.
They
have
monitoring
tabs,
so
they
have
finally
some
connection
with
monitoring
information,
not
only
tracing,
so
it's
pretty
sweet.
Finally,
they
have
otlp
support,
which
means
like
a
native
open,
Telemetry
standard
and
they
actually
dropping
their
own
protocols
like
Jagger
protocols.
A
So
if
you
still
use
them
make
sure
you
you
switch
to
the
new
otlp
with
shiny
new
features,
and
there
is
other
they
added
adaptive
sampling
so
so
seems
like
you
can
control
your
sampling
much
more
granularly
and
dynamically,
which
is
which
is
super
sweet
because,
as
you
know,
tracing
can
be
expensive
if
you
sample
every
event
in
your
system.
A
So
making
sure
you
make
right
decision
is
really
important
and
yeah
flying
graphs
for
traces,
which
is
amazing
again,
like
it's
a
specific
kind
of
view
that
you
could
use
actually
for
profiling
as
well
and
yeah.
The
note
of
deprecation,
Prometheus
and
open
metrics
a
reminder,
a
metric
monitoring
system
and
I'm.
Maintaining
that
and
we
are
moving
as
well
a
lot.
We
are
adding
new
service
discoveries
so
essentially
like
how
you
can
integrate
with
the
system.
A
You
are
using
to
to
to
add
your
scrape
jobs
to
really
like
control
your
monitoring
metric
pipeline,
so
we
added
new
Cloud
providers,
but
actually
Nomad
as
well,
which
is
like
super
popular
orchestration
system
alternative
to
kubernetes.
A
Additionally,
we
have
a
special
long-term
support
kind
of
version.
It's
kind
of
like
very
special
I.
Think
I
was
even
surprised
that
this
thing
can
can
exist.
So
you
know
we
have
a
version
every
six
weeks
and
some
of
them
like
we
are
trying
to
be,
you
know,
compatible
and
so
on,
but
we
decided
to
have
one
version
being
special
and
having
this
for
longer,
so
people
can
use
it
in
more.
A
You
know
different
systems
that
are
not
as
dynamic
as
Cloud
native.
You
know.
Cloud
native
you
know
communities,
for
example
like
communities,
so
so
having
this
LTS
version
is
kind
of
super
useful,
so
we'll
make
sure
it's
stable
make
sure
the
security
fixes
and
boxes
are
patches.
Are
there
lots
of
optimizations
and
kind
of
formatting
for
and
pretty
pretty
printing
for
prom
ql,
which
is
super
nice?
You
don't
need
to
manually
kind
of
format,
those
in
the
UI
and
finally
out
of
order.
A
What
it
means
is
that
promoters
were
never
capable
of
appending
all
samples.
So,
for
example,
you
have
a
metric
that
you
scrape
and
it
is
kind
of
from
current
time-
and
you
know
you
want
to
scrape
you
actually
forgot
to
scrape
you
know-
let's
say
a
period
of
two
hours
before
that
like
if
you
would
like
to
backfill
that
and
append
in
some
way
VIA
programmatic,
API
or
via
remote
right
You
users
just
fail
without
or
their
error
now
prompt
use,
appends
that
it
has
some
cost,
of
course,
so
be
careful.
A
But
it
will
just
accept
this.
If
you
configure
Prometheus
properly
open
Telemetry,
we
like
lots
of
lots
of
changes.
It's
a
big
project
as
well.
A
So
you
know
logging
work,
open,
metric
and
pro
materials
compatibility,
work,
tracing,
General,
availability,
Telemetry
locks
being
improved,
there's
client
instrumentation,
there
are
end
working
groups
or
more
groups
as
well.
Metrics
GA,
which
is
kind
of
sweet,
so
kind
of
their
metric
protocol
and
sdks
are
available,
and
finally
they
start
working
on
profiling.
A
So
that's
pretty
pretty
sweet,
so
we
can
have
like
those
four
signals
for
now
being
supported
by
open
telemetry
and
two
more
projects
cortex,
which
kind
of
gets
better
scalability
with
with
with
new
versions,
adding
more
maintainers
and
and
the
newest
release,
have
vertical
question
sharding,
so
kind
of
improvements
on
query
layer
and
and
some
open
Telemetry
support.
Oh,
like
no
sorry,
it's
a
it's
just
for
tracing
of
Cortex
itself.
A
They
support
open,
Telemetry
and
then
compaction
is
more
scalable
as
well,
and
finally,
last
project
I'm,
maintaining
I
kind
of
co-founded
this
project
as
well,
and
we
are
moving
as
well
with
scalability
and
we
have
katama
hash
ring.
We
have
ingestion
rate
limiting
so
kind
of
like
lots
of
performance
fixes,
and
we
are
a
rewriting
prompt
well
recently.
So
if
you
want
to
learn
more
visit
us
in
prom
con
or
maybe
talks
in
this
this
this
event
so
yeah,
that's
all
from
all
from
my
side.
Thank
you
very
much
and
enjoy
today's
event.