Beats

Open Source Metrics Analysis

From drone sensor data to CPU usage, Elasticsearch has been taking what you love about its text search superpowers and applying them to metrics since the beginning. And it keeps on getting better.

Experience metrics analysis with Elastic. Try It Out

Freely Explore Your Numbers Your Way

Run wild with dimensions, tags, cardinality, and fields. Elastic doesn't limit or dictate how you explore your data. Instead, you can continuously and quickly explore attributes — host name, IP address, deployment, color — at scale in any way you like, in any order you like, in the visualization you like.

Didn't know a search engine could be so good with numbers? That's alright. You do now.
Skip ahead to get started.

It's Got the Sort of Speed and Scale You Notice

And to make that happen, we went beyond the inverted index. We created new data types, implemented BKD trees, and added a column store — all of which leads to more efficiently structure data for faster searches, and less memory use, and less disk use. In other words: you can access fields and values across petabyte-scale data at remarkable speeds.

Try It Out

Grab a fresh installation and get started.
In Elasticsearch install directory:
Once Elasticsearch starts, in Elasticsearch install directory (separate window):

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Kibana install directory:

Modify config/kibana.yml to set credentials for Elasticsearch

elasticsearch.username: "kibana"     
elasticsearch.password: "<kibana_pw>"
			
In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
			

To modify defaults, edit modules.d/system.yml.

Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
Open dashboard:
"[Metricbeat System] Overview" and click on your host.
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing CPU and memory utilization, and process-level statistics.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

In Elasticsearch install directory:
Once Elasticsearch starts, in Elasticsearch install directory (separate window):

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Kibana install directory:

Modify config/kibana.yml to set credentials for Elasticsearch

elasticsearch.username: "kibana"     
elasticsearch.password: "<kibana_pw>"
			
In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
			

To modify defaults, edit modules.d/apache.yml.

Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
Open dashboard:
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing connection statistics and HTTP worker details.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

In Elasticsearch install directory:
Once Elasticsearch starts, in Elasticsearch install directory (separate window):

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Kibana install directory:

Modify config/kibana.yml to set credentials for Elasticsearch

elasticsearch.username: "kibana"     
elasticsearch.password: "<kibana_pw>"
			
In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
			

To modify defaults, edit modules.d/mongodb.yml.

Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
Open dashboard:
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing data statistics, health and status information about your MongoDB deployment.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

In Elasticsearch install directory:
Once Elasticsearch starts, in Elasticsearch install directory (separate window):

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Kibana install directory:

Modify config/kibana.yml to set credentials for Elasticsearch

elasticsearch.username: "kibana"
elasticsearch.password: "<kibana_pw>"
			
In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
			

To modify defaults, edit modules.d/docker.yml.

Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
Open dashboard:
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing data statistics, health and status information about your Docker deployment.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

In Elasticsearch install directory:
Once Elasticsearch starts, in Elasticsearch install directory (separate window):

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Kibana install directory:

Modify config/kibana.yml to set credentials for Elasticsearch

elasticsearch.username: "kibana"
elasticsearch.password: "<kibana_pw>"
            
In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
From your machine or wherever you run kubectl:
env:
  - name: ELASTICSEARCH_USERNAME
    value: elastic
  - name: ELASTICSEARCH_PASSWORD
    value: changeme
Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can monitor your Kubernetes cluster.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

In Elasticsearch install directory:
In Kibana install directory:

Note the password for elastic user as <es_pw>

Note the password for kibana user as <kibana_pw>

In Heartbeat install directory:

Modify heartbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<es_pw>"
			
Open browser @
http://localhost:5601 (login: elastic/<es_pw>)
Open dashboard:
What just happened?

Heartbeat is designed to do distributed uptime checks from each of your hosts to ensure that they can each reach every endpoint they are supposed to. This is amazing for service oriented architectures. In this case, you’ve asked Heartbeat to check the uptime for the two local ports corresponding to the Elasticsearch and Kibana defaults. Heartbeat then sends this data to Elasticsearch and you can see the data in the Kibana dashboard.

Didn't work for you?

Heartbeat was set to use the default ports for Elasticsearch and Kibana in this example. See the documentation for configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Metricbeat

In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
				

To modify defaults, edit modules.d/system.yml.

Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Metricbeat System] Overview"
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing CPU and memory utilization, and process-level statistics.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Metricbeat

In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
				
class="p-t-20"To modify defaults, edit modules.d/apache.yml.
Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Metricbeat Apache] Overview"
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing connection statistics and HTTP worker details.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Metricbeat

In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
				

To modify defaults, edit modules.d/mongodb.yml.

Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Metricbeat MongoDB] Overview"
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing data statistics, health and status information about your MongoDB deployment.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Metricbeat

In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
                
Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Metricbeat Docker] Overview"
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start viewing data statistics, health and status information about your Docker deployment.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Metricbeat on your local machine

In Metricbeat install directory:

Modify metricbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
                

From your machine or wherever you run kubectl:

env:
  - name: ELASTICSEARCH_USERNAME
    value: elastic
  - name: ELASTICSEARCH_PASSWORD
    value: changeme
                
Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Metricbeat Kubernetes] Overview"
What just happened?

Metricbeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can monitor your Kubernetes cluster.

Didn't work for you?

Metricbeat modules have defaults and configurations for each system they connect to. See the documentation for supported versions and configuration options.

  • Register, if you do not already have an account
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Cluster, leave size slider at 4 GB RAM, and click Create
  • Note the Cloud ID as <cloud.id>
  • Note the cluster Password as <password>
  • In Overview >> Endpoints section note Kibana URL as <kibana_url>
  • Wait until cluster plan completes

Download and unpack Heartbeat (Beta)

In Heartbeat install directory:

Modify heartbeat.yml to set credentials for Elasticsearch output

output.elasticsearch:
  username: "elastic"
  password: "<password>"
				
Open browser @
http://<kibana_url>:5601 (login: elastic/<password>)
Open dashboard:
"[Heartbeat] HTTP Monitoring"
What just happened?

Heartbeat is designed to do distributed uptime checks from each of your hosts to ensure that they can each reach every endpoint they are supposed to. This is amazing for service oriented architectures. In this case, you’ve asked Heartbeat to check the uptime for the two local ports corresponding to the Elasticsearch and Kibana defaults. Heartbeat then sends this data to Elasticsearch and you can see the data in the Kibana dashboard.

Didn't work for you?

Heartbeat was set to use the default ports for Elasticsearch and Kibana in this example. See the documentation for configuration options.

Run Machine Learning Jobs to Spot Anomalies

As data scales, it's easy to lose errant data points among the streaming averages, measurements, totals. And it's impractical to analyze all your visualizations all the time.(Hey we're all human here.)

The machine learning capabilities for the Elastic Stack automates anomaly detection at scale. It learns what's normal in your data to indentify what isn't, and then alerts you to it.

Even Supercomputers Use Elastic

1.2 billion documents, 160 GB. That's how much data the National Energy Research Scientific Computing Center (NERSC) collects on any given day. From substation power usage KPIs to building air and water temperature, computer disk and network I/O, and system load, they index all kinds of metrics to keep scientific discovery moving forward.

They're not the only ones doing the numbers with Elastic. Explore more customer examples.

Metrics are Just One Place to Start

Have network data? Infrastructure logs? Documents with tons of text? Centralize it all into the Elastic Stack with your metrics and enrich your analyses, streamline your workflows, and simplify your architecture.

App Search

Search across documents, geo data, and more.

Learn More

Security Analytics

Interactive investigation at speed and scale.

Learn More

Logging

Fast and scalable logging, that won't quit.

Learn More

Site Search

Easily create a great search experience for your site.

Learn More