Metrics

오픈 소스 메트릭 분석

드론 센서 데이터부터 CPU 사용량에 이르기까지, Elasticsearch는 처음부터 우수한 텍스트 검색 기능을 다양한 메트릭에 반영해왔으며, 그 능력은 지금도 계속해서 발전하고 있습니다.

Elastic의 메트릭 분석을 경험하세요. 지금 사용해 보세요.

새 기능 인프라 UI와 데이터 롤업에서부터 Functionbeat와 Beats 중앙 관리까지, 인프라 메트릭의 세계에는 기대되고 설레이는 것들이 많이 있습니다.
자세히 보기

여러 데이터 소스 분석을 한 곳에서

Docker 컨테이너, 데이터 센터, 차량단, 또는 화성의 표면 온도 등 무엇을 모니터링하든 Elastic Stack에는 모든 것을 한꺼번에 처리하기 위한 Beat, 모듈, 플러그인이 있습니다.

검샌 엔진이 이러한 데이터 소스를 모두 처리할 수 있다는 사실을 모르셨나요? 그럴 수 있답니다. 이제는 아셨죠?
이후 내용은 건너뛰고 바로 시작하기

원하는 방식으로 자유롭게 수치 데이터를 탐색하세요.

다양한 차원과 태그, 카디널리티, 필드를 넘나들며 자유롭게 데이터를 탐색하세요. Elastic은 데이터 탐색 방식을 제한하지 않으며, 호스트명과 IP 주소, 배포, 색상 같은 속성을 규모나 순서에 관계없이 계속해서 빠르게 탐색하고 원하는 방식으로 시각화할 수 있습니다. 아울러, Beats와 그 모듈은 수집, 구문 분석, 태깅 작업을 합니다. 대시보드와 머신 러닝 작업도 생성할 수 있습니다.

여러분이 찾고 있던 바로 그 속도와 스케일.

그 목표를 달성하기 위해서는 역색인을 뛰어넘는 성능이 필요했습니다. 이에 Elastic은 BKD tree를 상속받는 새로운 자료구조와 column store를 추가하는 작업을 실시했고 이러한 작업을 통해 매우 효율적인 구조의 데이터를 확보하고 검색 속도 향상과 메모리 및 디스크 사용량 감소의 결과를 이끌어 낼 수 있었습니다. 이것은 페타바이트 규모의 데이터에서 아주 빠른 속도로 필드값에 접근이 가능하다는 것을 의미합니다.

정확한 롤업

Elastic Stack을 떠나지 않고서도 메트릭을 다운샘플링하세요. Elasticsearch와 Kibana의 강력한 롤업 지원은 정확도를 희생하지 않고도 공간을 절약하고 쿼리를 더 빨리 처리할 수 있게 해줍니다.

지금 사용해 보세요.

이제 최신 버전을 설치하고 바로 시작해 보세요.
  • Register, if you do not already have an account. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Metricbeat

Open terminal (varies depending on your client OS) and in the Metricbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

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

Open Kibana from Kibana section of the Elastic Cloud console (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. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Metricbeat

Open terminal (varies depending on your client OS) and in the Metricbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

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

Open Kibana from Kibana section of the Elastic Cloud console (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. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Metricbeat

Open terminal (varies depending on your client OS) and in the Metricbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

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

Open Kibana from Kibana section of the Elastic Cloud console (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. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Metricbeat

Open terminal (varies depending on your client OS) and in the Metricbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

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

Open Kibana from Kibana section of the Elastic Cloud console (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. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Metricbeat

Open terminal (varies depending on your client OS) and in the Metricbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

From your machine or wherever you run kubectl:

env:
  - name: ELASTIC_CLOUD_ID
    value: <cloud.id>
  - name: ELASTIC_CLOUD_AUTH
    value: <cloud.auth>
				

Optionally, you can enable kube-state-metrics for more detail.

Open Kibana from Kibana section of the Elastic Cloud console (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. Free 14-day trial available.
  • Log into the Elastic Cloud console
To create a cluster, in Elastic Cloud console:
  • Select Create Deployment, and specify the Deployment Name
  • Modify the other deployment options as needed (or not, the defaults are great to get started)
  • Click Create Deployment
  • Save the Cloud ID and the cluster Password for your records, we will refer to these as <cloud.id> and <password> below
  • Wait until deployment creation completes

Download and unpack Heartbeat (Beta)

Open terminal (varies depending on your client OS) and in the Heartbeat install directory, type:

Paste in the <password> for the elastic user when prompted

Paste in the <cloud.id> for the cluster when prompted

Open Kibana from Kibana section of the Elastic Cloud console (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.

In Elasticsearch install directory:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Metricbeat install directory:
Ctrl + C to Copy

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

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:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Metricbeat install directory:
Ctrl + C to Copy
Ctrl + C to Copy

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

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:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Metricbeat install directory:
Ctrl + C to Copy
Ctrl + C to Copy

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

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:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Metricbeat install directory:
Ctrl + C to Copy
Ctrl + C to Copy

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

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:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Filebeat install directory:
Ctrl + C to Copy
Ctrl + C to Copy
From your machine or wherever you run kubectl:
  • Download metricbeat-kubernetes.yml
  • Edit metricbeat-kubernetes.yml and specify the host for your Elasticsearch server (If you are connecting back to your host from kubernetes running locally then set ELASTICSEARCH_HOST to host.docker.internal). There is a DaemonSet and a singleton, edit the HOST for both:
  - name: ELASTICSEARCH_HOST
    value: host.docker.internal
			

Optionally, you can enable kube-state-metrics for more detail.

Ctrl + C to Copy
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:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Heartbeat install directory:
Ctrl + C to Copy
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의 머신러닝 기능은 어떤 규모에서나 이상 징후 탐색을 자동화하여, 데이터에서 정상값과 비정상 값을 스스로 구분하여 알려 줍니다.

수퍼컴퓨터도 Elastic을 사용합니다.

160GB에 이르는 12억 개의 문서. 미 국립 에너지 연구 과학 컴퓨팅 센터(NERSC)가 하루에 수집하는 데이터의 양입니다. 이 센터는 끊임 없는 과학 발전을 위해 변전소 전력 소비량의 KPI부터 건물의 공기 및 물 온도, 컴퓨터 디스크 및 네트워크 I/O, 시스템 부하까지 모든 유형의 메트릭을 색인합니다.

Elastic으로 로그 데이터를 다루는 곳은 NERSC 뿐만이 아닙니다. 더 많은 고객 사례를 직접 확인해 보세요.

메트릭은 더 큰 여정을 위한 하나의 시작점일 뿐입니다.

네트워크 데이터가 있습니까? 인프라 로그를 사용하고 계신가요? 수많은 텍스트 문서를 처리해야 하나요? 이 모든 것을 메트릭과 함께 Elastic Stack으로 통합하여 분석을 확장하고 워크플로우와 아키텍처를 단순화할 수 있습니다.

로그분석

빠르고 확장 가능하며 중단되지 않는 실시간 로깅.

더 보기

사이트 검색

손쉽게 만들고 추가하는 사이트 검색의 경험.

더 보기

보안 분석

빠르고 확장 가능한 상호 교환형 정보 수색.

더 보기

APM

애플리케이션 성능에 대한 통찰력 강화.

더 보기

앱 검색

문서, 위치정보 및 그 이상의 검색.

더 보기