컨테이너 모니터링

애플리케이션과 시스템 환경의 변화에 발맞추어 Elastic Stack 역시 진화합니다. 이제 애플리케이션과 Docker, Kubernetes의 데이터를 한곳에서 모니터링하고 검색하고 또 시각화할 수 있습니다.

Elastic을 이용한 컨테이너 모니터링을 지금 체험해 보세요. 체험하기

통합

하나의 플랫폼에서 로그와 메트릭을 확인하세요

애플리케이션 모니터링부터 Kubernetes 메트릭 및 이벤트 감시, Docker 컨테이너 성능 분석까지 모든 것을 하나의 플랫폼으로 간편하게 처리할 수 있으며 실시간 데이터 시각화와 검색 기능까지 지원됩니다.

배포

Beats와 함께라면 모니터링이 더욱 간편해집니다

Filebeat, Metricbeat 등을 이용해 애플리케이션과 Docker 컨테이너, Kubernetes의 로그메트릭을 수집하세요. 1~2분만에 설치가 가능하며 자동 검색 기능으로 더욱 손쉽게 모듈을 가동할 수 있습니다. 애플리케이션, Docker, Kubernetes의 로그와 메트릭 수집에 관한 자세한 예시는 이 블로그GitHub 리포를 통해 확인하실 수 있습니다.

Icon

Kubernetes와 Kubernetes에서 작동하는 애플리케이션을 모니터링하세요

Icon

애플리케이션과 Docker 인프라를 관리하세요

Icon

Docker에 Elastic Stack을 배포하고 싶으신가요? Elastic 컨테이너를 이용해 보세요!

자동 검색

역동적인 플랫폼에 신속히 대응하는 Beats

Metricbeat와 Filebeat의 자동 검색 기능을 통해 환경의 변동을 실시간으로 확인할 수 있습니다. 이 자동 검색 기능은 모듈과 로그 경로 추가를 자동화하고 Docker와 API 후크를 이용해 모니터링 설정을 자동으로 변경하며 데이터의 출처를 확인할 수 있도록 메타데이터를 추가하는 역할을 합니다.

자유로운 구성

데이터를 시각화하고 변경 사항에 대한 알림을 받으세요

미리 구성된 Kibana 대시보드를 이용하여 대시보드와 알림 기능을 자유롭게 구성하고 가장 중요한 메트릭을 실시간 모니터링할 수 있습니다. 시스템의 새로운 컨테이너 상태부터 애플리케이션, Docker, Kubernetes의 성능까지 감시할 수 있으며 변경 사항 시각화와 문제 파악, 기능 통제, 알림 받기까지 설정이 가능합니다.

지금 시작하세요

Elastic Stack으로 데이터를 전송하여 배포 상태를 간편하게 확인할 수 있습니다.
  • 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 Filebeat

Open terminal (varies depending on your client OS) and in the Filebeat 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>
				
Open Kibana from Kibana section of the Elastic Cloud console (login: elastic/<password>)
Go to Discover to search your logs
What just happened?
Filebeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start exploring your logs from your app and services running in Kubernetes.
Didn't work for you?

Filebeat module assumes default log locations, unmodified file formats, and supported versions of the products generating the logs. See the documentation for more details.

  • 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 Filebeat

Open terminal (varies depending on your client OS) and in the Filebeat install directory inside a Docker container, type:

As a user that has read access to /var/lib/docker/containers (usually root) modify filebeat.yml to send logs enhanced with Docker metadata to Elastic

filebeat.inputs:
     - type: docker
       containers.ids:
         - '*'
       processors:
       - add_docker_metadata: ~
				

As a user that has read access to /var/lib/docker/containers (usually root) run:

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>)
Go to Discover to search logs for your application or service running in Docker
What just happened?

Filebeat created an index pattern in Kibana with defined fields for logs residing in the default directory where Docker puts logs from your applications (/var/lib/docker/containers/*/*.log), and enhanced them with Docker container metadata. You can now look at logs from Docker in one central place in Kibana.

Didn't work for you?

Filebeat Docker metadata processor can be tuned further for your use case. See the documentation for more information.

  • 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.

In Elasticsearch install directory:
Ctrl + C to Copy
In Kibana install directory:
Ctrl + C to Copy
In Filebeat install directory:
Ctrl + C to Copy
From your machine or wherever you run kubectl:
  • Download filebeat-kubernetes.yml
  • Edit filebeat-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):
  - name: ELASTICSEARCH_HOST
    value: host.docker.internal
			
Ctrl + C to Copy
Open browser @
Go to Discover to search your logs
What just happened?

Filebeat created an index pattern in Kibana with defined fields, searches, visualizations, and dashboards. In a matter of minutes you can start exploring your logs from your app and services running in Kubernetes.

Didn't work for you?

Filebeat module assumes default log locations, unmodified file formats, and supported versions of the products generating the logs. 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 Filebeat install directory on your Docker Host:

As a user that has read access to /var/lib/docker/containers (usually root) modify filebeat.yml to send logs enhanced with Docker metadata to Elastic

filebeat.inputs:
     - type: docker
       containers.ids:
         - '*'
       processors:
       - add_docker_metadata: ~
			

As a user that has read access to /var/lib/docker/containers (usually root) run:

Ctrl + C to Copy
Open browser @
Go to Discover to search logs for your application or service running in Docker
What just happened?

Filebeat created an index pattern in Kibana with defined fields for logs residing in the default directory where Docker puts logs from your applications (/var/lib/docker/containers/*/*.log), and enhanced them with Docker container metadata. You can now look at logs from Docker in one central place in Kibana.

Didn't work for you?

Filebeat Docker metadata processor can be tuned further for your use case. See the documentation for more information.

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.

Elastic이 함께합니다

더 많은 것을 기대하세요

eBay가 Kubernetes를 이용해 어떻게 애플리케이션의 로그와 메트릭을 수집하는지 자세히 알아 보시기 바랍니다.

컨테이너는 더 큰 여정을 위한 하나의 시작점입니다

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

앱 검색

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

더 보기

보안 분석

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

더 보기

메트릭

CPU, 메모리 및 그 외의 다양한 수치 분석.

더 보기

사이트 검색

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

더 보기

APM

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

더 보기