►
From YouTube: Full Stack Visibility with Elastic: Logs, Metrics and Traces - Carlos Pérez-Aradros, Elastic
Description
Full Stack Visibility with Elastic: Logs, Metrics and Traces - Carlos Pérez-Aradros, Elastic
"With microservices every outage is like a murder mystery" is a common complaint. But it doesn't have to be! This talk gives an overview on how to monitor distributed applications. We dive into:
System metrics: Keep track of network traffic and system load.
Application logs: Collect structured logs in a central location.
Audit info: Watch for user and processes activity in the system.
Uptime monitoring: Ping services and actively monitor their availability and response time.
Application metrics: Get metrics and health information from for application via REST or JMX.
Request tracing: Gather timing data by using tools like Zipkin to retrieve and show call traces.
About Carlos Pérez-Aradros
Carlos is a software engineer at Elastic, working on Beats. With love for distributed systems, he has experience in many container technologies and focuses on bringing the right tools to monitor them. When he is not coding you may find him playing with home automation and all kinds of gadgets.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 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.
A
A
We
used
to
call
this
the
ELCA
stock,
but
then
bits
came
into
a
position,
so
now
we
usually
prefer
to
call
it
the
elastic
stack
cause.
You
know
bulk
or
lqb
suns
will
and
we
just
released
6.0
a
couple
of
weeks
ago
and
I
really
love
this
nice
animation,
because
somehow
it's
it
shows
how
the
elastic
stock
is
made
of
many
pieces,
but
when
you
put
all
of
them
together,
they
work
really
great
and
I
like
that.
Really
much
so
today
will
be
mostly
speaking
about
beets
and
kubernetes,
of
course.
A
So
let's
get
started
with
that.
So
what
sweets
bits
a
family
of
lightweight
zippers
that
collect
and
see
all
kinds
of
operational
data
to
elasticsearch.
What
do
we
mean
by
lightweight?
Well,
this
may
have
many
meanings,
but
for
us
is
everything
is
given
in
go.
We
see
everything
in
a
single
binary
that
doesn't
require
any
external
library
yeah,
the
CPU
and
memory
consumption.
It's
usually
low,
depending
on
your
race,
so
meet
the
big
family,
the
beets
family.
A
A
Maybe
there
is
an
community
bit
supporting
your
use
case,
I'm,
going
to
go
quickly
over
all
of
them,
a
step
for
window
bit
which
is
for
windows,
event
locks,
but
as
I'm
doing
a
demo
later
on
I'm
going
to
try
to
do
this,
quick,
okay,
so
loss.
How
do
we
get
loss
which
we
have
something
called
file
bit?
It
tells
some
ships
logs
for
you.
It
does
a
lot
of
things
like
back
pressure
control.
A
We
can
do
a
structure
login,
and
that
means
we
can
first
parse
the
lock
lines
and
strat
method
from
them,
for
you
also
multi-line
for,
for
instance,
if
you
lock
contain
I,
don't
know,
stick
three
stack
traces.
We
are
able
to
compact
all
the
different
lock
lines
and
put
them
together,
and
we
do
many
other
scenes
for
metrics
and
events.
We
have
many
different
bits.
The
main
one
to
me
will
be
met
with
it:
Paul's
API
for
the
API
of
different
services.
A
It's
a
common
use
case
for
a
monitoring
agent,
so
it
talks
normally
to
the
service
you
want
to
monitor
and
takes
the
metrics
from
it
for
you,
each
store
since
in
elasticsearch
in
an
efficient
way
and
actually
we're
still
improving
this
and
with
six
zero.
It
went
down
by
a
lot
and
it's
also
supports
application
metrics
from
from
other
protocols
or
standards
like
getting
metrics
from
job
application
with
MX
or
promise
use,
for
instance,
a
packet
bit.
You
can
think
of
it
as
a
like
a
distributed.
A
Wireshark
it
taps
into
the
network,
speaks
different
protocols
and
can
instruct
what's
going
on
for
you.
Basically
it
it
understands
protocols
like
HTTP
MySQL,
whatever
it
reads
for
all
the
packets
in
the
network
and
then
a
struct
like
address
a
transaction
from
them
so
creates
an
events
in
elastic
shirts.
Recently
we
added
TLS
handshake
versions.
So
this
that's
really
cool
for
security
use
cases,
so
you
can't
get
what's
going
on
and
your
users
are
using
SSL
herb.
It
is
like
uptime
monitoring.
It
can
talk
to
your
services
from
time
to
time.
A
You
can
schedule
checks
and
check
that
everything
is
available
and
running
how
did
beat.
This
was
the
last
one
added
to
the
list
basically
connected
to
the
Linux
audit
framework.
It
can
work
with
Audi
G,
as
said
car
or
or
standalone,
and
something
cool
that
it
does.
Is
you
know,
lineage
how
the
framework
gives
you
a
lot
of
events
on
on?
A
What's
going
on
with
the
security
on
with
on
your
system,
what
how
did
big
does
is
read,
hold
at
events
and
correlate
the
ones
that
are
correlated
and
create
a
single
event
in
your
elastic
search,
and
it
also
does
file
integrity
monitoring.
So
you
can
check
if
someone
changed.
Some
of
your
files,
for
instance
binaries
for
Tricia's
recently
up
beat
a
company
that
was
working
on
a
p.m.
joining
forces
with
elasticsearch.
It
was
it
it.
A
It
went,
acquired
by
drastic
and
and
since
then
they
have
been
working
on
open
sourcing,
a
lot
a
lot
of
issue
of
their
code.
It's
in
alpha
state,
as
of
now
I'm
so
in
later
on,
but
just
taking
the
contents
in
alpha,
but
yeah
they
are
doing
really
great
stuff
on
on
APM.
By
the
moment,
there
are
no
da
some
Python
agents
with
support
for
scenes
like
flask
or
Django,
and,
of
course,
more
coming.
A
So
today,
I
came
here
to
talk
about
the
kubernetes
and
and
docker
in
this
case
this
year,
we'll
have
been
working
a
lot
on
supporting
this.
Well,
using
bits
I
want
to
thank
you
especially
BJ
Samuel.
He
worked
for
eBay
and
they
contributed
a
lot
of
code
here.
They
use
bits
internally
and
we
are
really
grateful
for
that.
Several
media,
if
you
are
watching
thank
you,
so
what's
all
about
a
with
containers,
infrastructure
with
micro
services.
Basically,
when
you
are
using
this
kind
of
architecture,
every
scene
is
a
moving
target.
A
The
static
static
configurations
that
are
not
valid
anymore
I
mean
you:
can
you
can
expect
everything
to
be
in
place
and
not
moving,
so
we
need
the
specific
type
specific
tools
to
track
things
down,
and
we
have
implemented
a
few
primitives
that
you
can
use
to
monitor.
What's
going
on
with
containers,
first
of
all,
we
added
docker.
We
have.
We
have
it
already
actually,
and
we
recently
added
that
kubernetes
one.
So
you
can
monitor
the
others.
A
The
overall
state
of
you
of
your
kubernetes,
so
I
think
we
saw
that
we
also
added
metadata
processors
that
help
you
enrich
your
events.
Anything
that
is
coming
out
of
your
beads
can
be
enriched
with
information
that
gives
you
context
on
where
it
came
from.
That's
really
useful.
When,
then,
you
want
to
navigate
that
data
that
matrix
that
locks
whatever
or
even
correlate
them.
A
So
we
have
something
to
add
information
about
what
cloud
you
are
running
on
Suns
into
what
information
from
docker
and
something
to
add
information
from
kubernetes
I
will
show
all
this
in
the
demo.
This
is
an
example
of
how
an
event
that
comes
from
file
bit.
So
this
a
lot
looks
when
you
are
using
the
different
processors
and,
of
course
you
can
use
all
of
them
or
any
or
only
the
ones
that
you
are
interested
on.
So
what
you
are
seeing
here
is
a
lock
line
from
valve.
A
It
actually
is
telling
that
it's
connected
to
elastic
shirts,
but
then
you
get
a
lot
of
metadata
of
where
this
line
this
line
came
from,
so
I
know
the
pot
name
the
container
within
that
pot,
the
name
space
and
even
the
labels,
and
also
I
get
information
from
the
cloud
it's
running
on.
So
in
these
cases
Google
Cloud,
as
you
can
see-
and
this
is
how
it
works.
Basically,
we
are
pulling
the
cue
Burnitz,
API
constantly
and
every
time
that
a
new
post
is
launched
it.
A
So
when
we
resell
of
line
from
docker
or
whatever
we
parse
that
get
the
container
ID
and
then
use
that
container
ID
to
check
on
this
table,
and
normally
you
find
about
and
getting
the
metadata
information
for
for
that
for
that
container,
then
we
get
that
metadata,
put
it
with
event
and
ship
it
to
elastic
shirt
lobster.
So.
A
Let's
talk
now
what
autodiscover?
This
is
not
yet
release,
but
it
will
be
really
really
soon
it's
already
in
the
release
branch,
so
you
can
expect
it
in
the
follow
with
we
in
the
following
weeks.
We
are
get
out
of
this
cover.
What
is
this
about
its
we
watch
for
documents,
and
we
have
two
changes
so
allow
you
to
define
a
set
of
predefined
templates
to
apply
when
something
goes
on.
For
instance,
in
this
case,
we
have
a
condition
which
is
it
image.
The
docker
image
is
etcd.
A
We
want
you
to
launch
this
configuration
on
metric,
mid,
launch
this
module
to
monitor
it
and,
as
you
can
see,
we
get
the
host
the
IP
address
of
the
or
that
container
from
the
front
out
of
this
cover.
So
we
just
put
that
in
the
template
and
it
will
automatically
spawn
the
right
IP.
So
this
is
how
it
works
more
or
less
beats
watching
for
the
docker
events
API.
A
When
you
launch
a
new
container
or
kubernetes
task,
you
get
an
event
with
all
and
we
create
like
an
internal
structure
with
all
the
information
about
what
happened
what's
different
about.
Then
we
take
your
configuration
and
do
condition
matching
in
this
case
the
condition
of
etcd
matches,
so
this
is
bound
at
a
new,
a
module.
A
We
take
the
template
that
you
gave
us
in
the
configuration
and
do
the
bar
expansion
so
from
the
autodiscover
event,
with
the
word
bar
expansion
to
the
configuration
that
you
gave
us,
and
you
end
up
with
the
final
that
we
launched
for
you
in
the
same
way,
the
container
goes
out
a
we
do
the
same
thing,
but
the
other
way
around.
We
attack
that
and
stop
the
module.
A
So
when
you
are
running
bits
on
docker
host,
we
normally
run
them
from
a
container.
Do
you
cool
do
that
also
from
the
host
itself?
So
it's
up
to
you,
but
we
provide
both
documentation
and
docker
images
on
how
to
do
it
and,
depending
on
what
you
are
doing,
we
will
like
to
want
a
scene
from
the
host,
for
example,
on
metric
bid.
We
want
the
proc
file
system,
so
we
got
good
access
to
all
the
a
hot
prop
proc
information.
So
we
can
monitor
that
with
the
system
model.
A
We
will
see
that
in
a
while
and
for
the
per
file
bit
case
to
strap
the
logs.
We
do
it
in
the
similar
way.
We
want
barley,
docker
containers
and
read
a
lot
from
there
long
as
I
said
when
you
are
reading
the
log,
then
hundreds
start
with
information
from
kubernetes.
Oh
look
then,
which
enters
into
elastic
search,
and
you
can
see
it
in
Capernaum.
A
A
Basically
this
is
the
Des
Moines.
So
in
that
URL
you
can
visit
already
it's
a
really
simple
application,
written
in
python,
with
django
WSGI
with
engines.
Front-Ends
just
be
careful,
it's
not
elastic.
It's
like
an
internal
URL,
so
easy
l
SDC.
So
the
idea
of
the
application
is
that
you
can
submit
questions
out
this
talk.
If
we
get
the
right
questions,
I
can
answer
from
there.
You
can
also
bolt
them.
So
the
questions
you
want
to
get
answer
you
about
them.
This
is
how
the
application
is
running.
We
have
on
MySQL
pot
single
one.
A
This
is
pretty
simple,
deploy
it's
just
for
testing
just
for
so
cashing
this
and
a
couple
of
pots.
I
think
it's
three
running
the
application
itself
with
an
engine
front
ends.
So
what
we
are
doing
and,
of
course,
a
lot
balance
around
the
public
IP.
What
we
are
doing
here
is
getting
the
logs
getting
matrix
method
from
this.
You
see
no
to
discover
to,
for
instance,
detect
that
my
SQL
data,
endings
and
monitored
am
also
doing
network
analysis
using
packet
with
and
application
performance
metrics
using
the
elastic
APM
okay.
So
this
is
the
demo
application.
A
A
Don't
have
file
bit
deployed
yet
so
I
don't
have
logs
here
but
I'm
about
to
deploy
it
so
I
kind
of
start
getting
the
logs
into
my
elasticsearch
instance.
This
one
is
running
in
elastic
cloud,
but
elastic
cloud
runs
the
same
elastic
search
that
you
will
download
from
our
page
it's
open
source,
so
it
could
be
running
anywhere.
A
A
B
A
Okay
and
after
a
Buddhist
wrapping
everything,
it's
able
to
talk
everything
with
the
proper
metadata.
So,
as
you
can
see
here,
I
can
get
information
from
the
pot
name
or
the
container
name
for
everything,
and
maybe
you
just
saw
that
it
back
filled
the
whole
last
fifteen
minutes.
This
is
because
we
are
extracting
the
time
stamp
from
the
docker
law,
so
we
get
that
time
stamp
and
submit
event
with
the
current
time
stamp.
A
So
now,
I
got
lost
from
everything
that
happened
before
I
deploy
this,
which
is
cool
and
the
important
thing
about
metadata's
that
allows
you
to
navigate
everything
on
your
infrastructure.
So
if
I'm
watching
logs
here
I,
maybe
want
to
watch
loss
for
all
the
engines
that
I
have
deploy
and,
as
you
can
see
in
the
pot
name,
I
have
different
names
around.
A
A
Forgot
to
say
that
we
are
also
using
auto-discover
here.
Can
you
read
the
text?
Okay?
So
if
you
see
these
lines,
I'm,
detecting
the
endings
container
and
I'm
passing
the
ending
model
for
file
bit
what
the
engines
module
does
is
do
all
the
handling
of
the
logs
for
you
and
instruct
information.
So
you
have
metrics
stuff
instead
of
the
lock
lines.
So
this
way
I'm
getting
both
and
getting
the
logs,
but
also
getting
a
matrix
from
from
file
from
file
bit
for
for
endings.
A
So
I
can
go
and
open
the
endings
dashboard
for
file
bit,
and
this
gives
you
an
overview
of
all
the
visits
I'm
having
and
we
have
people
from
other
sites
role
in
the
streaming.
Hello
and
a
lot
of
information
on
you
know,
usual
agents.
What
you
are
visiting,
what
you
are
quoting
actually
and
volume
data.
So
this
is
really
cool.
This
is
coming
from
all
the
lofts,
and
now
we
can
jump
to
do
matrix.
A
So
metal
bit
can
monitor
both
your
host
system
also,
the
kubernetes,
linear
and
everything
that
you
are
running
on
top
of
them.
So
I
enabled
system
module
here,
Kuban
at
this
module
here
and
I'm,
using
autodiscover
to
monitor
the
differences
that
I
know
that
will
be
in
the
system
and,
for
instance,
MySQL
I'm
matching
the
condition
here.
So
if
you
see
a
MySQL
module
launch
this
sorry
I'm
a
nice
cool
container
launch
this
module
to
monitor
it.
You
can
do
a
lot
of
tricks
here
cause
at
the
end.
A
We
get
an
auto,
discover,
module,
sorry,
an
auto
discovery
event
and
can't
react
to
that
and
do
whatever
we
want.
So
in
this
case
we
could
be
doing
something
based
on
annotations
on
that
on
that
pot.
So,
if
I
see
this
annotation
like
I,
don't
know
promise
you
scrape
I
can
launch
the
promise
you
smuggle.
So
you
don't
need
to
hard
code
things
here.
This
is
just
an
example,
MySQL
and
also
engines,
so
I'm
launching
this
now.
A
A
I'm
opening
first
the
system
overview
that
gives
me
an
overview
of
the
hosts
that
are
running
these
kubernetes
instance.
As
you
can
see,
I
had
three
hosts
sorry.
This
is
because
of
the
resolution
and
I
get
an
idea
of
the
CPU
on
the
different
hosts,
as
you
see
from
the
name,
I'm
running
them
on
Google
cloud
and
I
get
an
overall
idea
of
the
CPU
memory
disk
network.
So,
as
you
can
see,
here
are
the
histogram
on
host
CPU.
A
A
So
this
is
for
the
system
module
on
metric
elite.
Let
me
open
now
the
Kuban
Etta's
overview
dashboard.
As
I
say,
this
is
directly
set
up
by
a
metric
bit.
So
when
you
deploy
with
the
manifest
all
these
dashboards
come
not
come
with
it
metric,
it
takes
care
of
deploying
them.
So
here
we
are
seeing
that
we
have
three
notes
across
the
three
notes.
With
90
points
going
on,
everything
looks
good.
A
A
A
We
are
also
monitoring
MySQL.
Thank
you
to
the
autodiscover
features,
so
we
detect
that
MySQL
is
running
and
launched
it,
the
MySQL
module
for
it
and
there
it
is.
We
get
an
idea
of
the
different
queries
that
are
happening
now
on
MySQL
active
connections
or
this
kind
of
matrix
that
you
may
be
interested
on.
As
we
said,
I
just
launched
this,
so
we
don't
have
much
history
on
this,
but
you
will
see,
therefore,
the
graph
for
it.
A
Let's
now
take
a
look
to
packet,
it
as
I
said
packet,
beat
Lisa
taps
into
the
network
and
understands
what's
going
on
on
the
different
protocols.
I
configure
it
this
one
to
understand.
Dns,
HTTP
and
MySQL
and
I
tell
it's.
The
pore
diameter
stayed
on
because
it's
too
expensive
to
listen
in
too
many
ports,
so
I'm
listening
only
in
the
port
I'm
interested.
A
So
this
is
the
plugin
packet
bit
for
me
and
we
should
start
having
some
information
from
it
and
I
will
like
this
because
it
gets
you
a
lot
of
insights
from
what
you
normally
don't
see.
It
may
be
CPU
intensive,
depending
what
you
are
doing,
but
I
think
it's
really
cool
for
some
cases.
For
instance,
this
is
what
I
get
using
packet
with
for
MySQL.
It's
able
to
understand
the
MySQL
protocol
and
tell
you
what
are
the
queries
that
are
being
run.
So
these
are
the
queries
that
are
happening
as
we
speak.
A
Release
or
the
traffic
generated
part
by
you
and
yeah
I
get
a
lot
information
that
I
cannot
so
get
with
metric
bit.
So
you
too,
sis,
depending
of
your
needs.
Of
course,
we
also
have
with
packet
beads
the
HTTP
parsing.
So
this
is
how
it
looks.
I
mean
packet
bit,
doesn't
know
anything
about
this
web
server,
it's
agnostic,
but
it's
able
to
understand.
What's
going
on
so
actually
I
get
information
not
only
for
my
my
application
demo
application,
but
for
other
services.
A
But
this
is
a
cool
just
case
actually
because,
as
I
said,
everything
gets
stuck
with
metadata,
so
I
can't
filter
to
the
name.
Is
Paige
I'm
interested
on
so
I'm?
Getting
all
the
metrics
from
PAC
a
bit
from
all
the
club
board
for
the
whole
cluster
and
Ike
I
can
decide
to
to
listen
only
or
to
watch
only
the
ones
for
my
default
namespace
I
can
add
this
filter
here.
Also.
A
So
it
already
gets
me
debating
the
possible
values
from
from
the
documented
existing
documents,
but
I
can
add
that
filter
and
then
I'm
only
watching
the
the
their
request,
HTTP
request
for
for
my
name's
place,
where
the
application
is
running.
So
this
is
thank
you
to
having
all
these
processors
with
metadata
information.
We
think
they
are
released
for
and
they
are
available
in
all
the
different
bits
and
let's
check
a
p.m.
I
I
did
to
click
with
this.
One
I
will
let
it
run
for
the
whole
for
the
whole
demo.
A
So
it's
already
running
I
know
deployed
unit
now,
as
I
said
a
bit
just
in
alpha
status,
but
it's
already
working
and
it's
really
great,
so
it's
open
source.
So
you
can
have
a
look
to
it
in
this
case
I
instrument.
In
my
jungle
application,
you
can
see
that
once
I
open
the
repo,
but
it's
really
easy
to
instrument
and
it's
getting
information
about
all
the
abuse
that
are
available
and
that
you
are
hitting
in
the
webpage.
A
It
is
speaks
jungle
I,
get
the
exact
name
of
the
view
from
the
angle
and
asked
for
now.
I
can
see
the
trace
is
using
this,
so
you
say
you
see
the
response
times
and,
and
the
results
of
the
HTTP
request
in
in
the
dashboard
I
can
also
see
the
traces
for
any
specific
bill.
So
in
this
case,
I
get
information
on
time
in
our
hood.
They
my
squad,
police
and
so
on.
Alpha
state,
it's
already
released
and
really
cool,
so
get
data.
Try
I
created
a
dashboard
I
created
a
dashboard
for
for
cube
con.
A
So
what
I'm
trying
to
show
is
the
power
of
having
everything
in
one
place
are
having
the
court
metadata
to
navigate
all
that
uncorrelated.
That
I
think
is
really
cool
when
you
can
do
that,
so
this
dashboard
was
created
for
this
demo.
Basically,
the
only
filter
I
have
here
is
using
this
coronet
as
metadata
and
instructing
qivana
to
filter
only
to
the
default
name
is
page,
but
this
could
be
everything.
A
I
mean
I
can
even
disable
this
and
I
get
information
for
my
whole
cluster,
which
is
probably
too
much,
but
for
this
demo,
as
you
can
see,
you
can
see,
as
you
can
see,
we
will
have
order
running.
Let
me
do
this.
Bigger,
maybe
all
the
running
pots
with
the
containers
inside
I
can
I
have
here
this,
so
I
can
see
that
there
is
a
my
squared
with
a
MySQL
container
on
it.
This
is
a
the
application
path
with
a
both/and,
the
application
container
and
the
engines
container,
and
this
other
two
are
all
supports.
A
I
get
the
logs
for
everything
here,
so
everything
in
this
namespace
locks
are
here:
I
get
CPU
usage
per
pot,
I
get
memory
usage
purpose.
Also
I
took
the
file
bit
view
from
the
logs
from
the
engines
locks,
as
you
can
see.
I
can
focus
on
starting
to
see
what's
going
on
in
these
errors,
so
the
whole
dashboard
changed
for
it.
So
I
went
here
and
then
I
can
check.
Maybe
the
logs
for
what's
going
on
and
I
can
see
here.
Something
is
going
on
we'll
check
later.
A
A
Yeah
the
same
way,
I
drilled
down
to
some
time
range
I
can
do
it
for
a
specific
port,
so,
for
instance,
I
have
all
the
logs
here
for
all
my
applications
in
this
namespace,
but
I
may
want
to
watch
only
the
ones
from
MySQL.
Well,
in
this
case,
MySQL
doesn't
have
any
logs.
It's
not
logging
anything,
so
let
me
focus
on
and
if
you
want
so
maybe
only
this
pot
I
get
the
logs
for
these
pots
only
and
in
this
port
I
have
both
engines
and
application.
A
So
these
are
the
HTTP
requests
that
are
being
answered
by
this
pot
and
only
this
pot
and
the
same
for
APM.
So
if
only
one
of
the
pots
is
that
what
you
are
interested
in
this
sound
way
to
use
in
metadata
to
to
navigate
that
and
within
this
path,
I
have
two
containers
or
engines
on
the
application
itself.
I
can
focus
in
one
of
them,
so
logs
for
engines
differ.
So
this
will
be
the
exit
law
that
we
will
be
seen
with.
A
What
in
the
garage
for
that
container
and
I
can
watch
all
the
system
usage
for
it.
So
I
think
this
is
everything
I
wanted
to
show
today.
Thank
you
for
coming,
and
maybe
you
have
some
interesting
questions
here.
I
can
also
take
questions
from
the
milk
if
you
want
Ward.
Oh
thank
you.
Okay,
yeah,
I'm,
publishing
the
slides,
so
yeah
give
me
a
couple
of
I.
Don't
know,
I
will
publish
them
during
today.
So
if
you
go
back
to
the
cube
cone,
it
said
these
lights
would
be
published
there.
A
Non-Standard
log
formats,
hi
Vijay,
so
yeah
we
are
working
on
some
things,
but
always
you
can
use
the
ingest
pipeline
or
lobsters
to
do
the
heavy
lift
in
there.
If
you
need
to
process
a
some
format
of
of
your
rocks,
you
can
use
both
elasticsearch
and
unlock
stuff
to
process
them
and
we
achieve
them.
A
Is
beat
an
alternative
to
Prometheus?
Well,
I'm,
not
sure
I,
don't
think
so,
maybe
depending
on
your
use
case,
but
we
can
work
together
with
promises
or
we
can
make
get
metrics
from
Prometheus.
We
speak
that
promises,
protocol
and
I
think
we
are
doing
different
things.
We
are
sending
metrics
for
later
analysis.
So
can
you
compare
file
bit
versus
24?
Well,
this
is
I.
Guess
this.
This
is
a
long
comparison.
I,
don't
know
I
I
invite
you
to
test
it
and
see
what
you
think,
and
maybe
someone
can
do
the
comparison
for
me.
A
A
A
A
B
Yeah
things
on
right
now,
yeah.
So
if
it
works
very
closely
with
the
Pitts
team
to
contribute
a
lot
of
stuff,
we
recently
also
open
source
to
collect
feet,
which
is
one
of
the
community
plugin
to
make
it
easier
for
I.
Think
our
vision
is
the
as
a
developer
and
the
PT
developer
when
they
deploy
the
application
on
top
of
kubernetes
right.
So
all
they
need
to
do
is
define.
Where
is
my
metrics?
What
type
from
tears
drop
wizard?
B
A
B
The
thing
that
I'd
like
to
you
know
pleat
is
that
so
there
is
this
thing,
a
community
about
using
prom
tears,
they
use
honor
right
and
then
they
use
lots
and
analytics
they
use
kupuna.
So
one
of
the
thing
that
EP
has
been
trying
to
twist
can
be
actually
try
to
unify
those
two
so
that
we
have
like
one.
You
know
kind
of
open
source
console
to
actually
look
at
both
and,
to
be
honest
with
you,
we
actually
invested
heavily
in
Cabana,
so
we
actually
have
country.
B
We
added
a
lot
of
plugins,
even
stuff
that
were
not
natively,
supported
by
Cabana.
We
actually
intercepted
the
call
tapana.
We
created
the
cube
watch
so
that
we
can
actually
get
all
the
API
servers
that
somebody
in
my
team
actually
presented
yesterday
right,
but
I
think
one
of
the
thing
that
we
could
work
together
as
part
community
is
there.
Can
that
be
one
potentially
way?
Let's
say
Capanna
right
so
because
you
have
the
timeline
support
as
well.
B
You
can
actually
pull
the
you
know,
metrics,
one
of
the
things
that
I
feel
Kalpana
is
much
more
adopted
on
the
operational.
You
know
team.
You
know,
but
this
I
don't
know
the
answer,
but
this
is
something
that
we
could
work
together.
Potentially
making
keep
an
eye
can
support
a
much
better
visualization
on
the
air
time
series
there
as
well
yeah.
A
For
sure
this
is
something
we
are
targeting
all
the
time
like
improving
Capanna
to
to
see
to
what
time
serious
information
we
actually
have
something
called
the
time
serious,
visual
builder,
which
is
an
easy
interface
to
watch
for
time-series,
metrics
and
yeah
totally
agree
with
you,
I
mean
you
have
been
doing
great
work
and
it
has
been
really
cool
journey,
working
together
and
putting
everything
in
bits
and
yeah.
There
are
still
many
scenes
we
want
to
do
on
that.
We
are.
Thank
you,
so
thank
everyone.