Metrics

メトリックス分析

ドローンセンサーのデータからCPUの使用率まで、Elasticsearchの優れたテキスト検索機能により、メトリック情報を収集しつづけます。

どんな数値でも収集、分析、異常を検知。 今すぐトライ

ディメンション、タグ、ユニークな数、フィールドなどを自由に検索。ホスト名やIPアドレス、デプロイメント、カラー配色など、好みに合わせてカスタマイズできます。

検索エンジンは数値にも応用できます。
まずは、はじめてみましょう。

転置インデックス以上の性能を得るため、新しいデータ種類を作成し、BKDツリーの実装、カラムストアの追加を行うことで、さらに高速な検索、メモリやディスク使用量の削減、より効率的なデータの構造化を実現しました。ペタバイト規模のデータフィールドや値へ高速にアクセスできるのです。

お試しください

最新バージョンをインストールして開始する。
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:
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 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>"
				

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.

データ量が大きくなるほど、ストリーミングの平均値や測定値、合計値の異常を発見するのがむずかしくなります。常に全てのデータを監視するのは不可能でしょう。

Elastic StackのMachine Learning機能は、膨大なデータの中から通常と異常を学習し、自動的に異常を検知します。

国立エネルギー研究科学コンピューティングセンター (National Energy Research Scientific Computing Center(NERSC))では、一日に12億ドキュメント、160GBのデータをElastic Stackを利用し分析しています。変電所の電力使用率のKPIから建物の空気や水の温度、コンピューターディスク、ネットワークI/O、システム負荷まで、あらゆる種類のメトリックをインデックス化して、科学的発見の進歩を保とうとしています。

Elastic Stackの導入事例はこれだけではありません。 他ユーザーの事例も併せてご覧ください。

ネットワークデータ、インフラログ、テキスト量が膨大なドキュメントをElastic Stackで一元化すると、分析の幅が拡がり、ワークフローの合理化、アーキテクチャをシンプルにすることができます。

ログ

高速でスケーラブルなログをリアルタイムに分析。

詳細

Swiftype Site Search

ウェブサイトの検索機能を大幅に向上。

詳細

セキュリティ分析

高速かつ大規模な、リアルタイムの異常検知。

詳細

APM

パフォーマンスメトリックを収集し、分析。

詳細

アプリ検索

ドキュメント、地理データなどを検索。

詳細