Container-Überwachung

Ihre Anwendungen und Ihre Umgebung entwickeln sich weiter – wie auch der Elastic Stack. Überwachen, durchsuchen und visualisieren Sie das, was in Ihren Anwendungen, in Docker und in Kubernetes geschieht – und das alles von einem Ort aus.

Lernen Sie mehr über die Container-Überwachung mit Elastic. Probieren Sie es aus

Alles auf einen Blick

Sehen Sie sich Ihre Logs auf einer Plattform an

Überwachen Sie Ihre Anwendungen, behalten Sie die Kubernetes-Kennzahlen und Events im Auge und analysieren Sie die Performance der Docker-Container. Visualisieren und durchsuchen Sie alles ad-hoc. Überwachung von Metriken, Logs und der Anwendungsperformance live hier und auf einen Blick.

Einsetzen

Lassen Sie Monitoring Realität werden – mit Beats

Übermitteln Sie Logs und Metriken aus Ihren Anwendungen, Docker-Containern und Ihrem Kubernetes-Setup mit Filebeat, Metricbeat und vielen mehr. Die Konfiguration dauert nur ein oder zwei Minuten, ab da übernimmt Autodiscover. Ein ausführliches Beispiel für das Erfassen von Logs und Metriken aus Ihrer App, aus Docker und aus k8s finden Sie in diesem Blog und im GitHub-Repository.

Icon

Behalten Sie Kubernetes und die darin ausgeführten Anwendungen im Auge.

Icon

Verwalten Sie Ihre Anwendungen und Ihre Docker-Infrastruktur.

Icon

Sie möchten den Elastic Stack in Docker bereitstellen? Verwenden Sie unsere offiziellen Container!

Autodiscover

Beats reagiert auf die dynamische Natur Ihrer Plattformen

Die Autodiscover-Funktion in Metricbeat und Filebeat informiert Sie über Veränderungen in Ihrer Umgebung. Automatisieren Sie das Hinzufügen von Modulen und Logpfaden und passen Sie Ihre Monitoring-Einstellungen dynamisch mit den Docker- und Kubernetes-API-Hooks an. Hängen Sie dann die Metadaten an, sodass Sie stets wissen, woher all Ihre Daten stammen.

Machen Sie mit

Visualisieren Sie Ihre Daten und lassen Sie sich bei Änderungen benachrichtigen

Mit den vordefinierten Kibana-Dashboards sind Sie sofort voll einsatzbereit. Erstellen Sie benutzerdefinierte Dashboards und Warnmeldungen, um die Metriken zu überwachen, die Ihnen am wichtigsten sind. Gibt es neue Container in Ihrem System? Wie ist der Zustand Ihrer App, von Docker und Kubernetes? Visualisieren Sie Änderungen, identifizieren Sie Probleme, übernehmen Sie die Kontrolle und lassen Sie sich benachrichtigen. Kein Problem.

In Minutenschnelle loslegen

Ziehen Sie Ihre Daten in den Elastic Stack und behalten Sie Ihre Bereitstellungen mit nur wenigen Schritten im Auge.
  • 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.

Sie sind in guter Gesellschaft

Überzeugen Sie sich selbst

Erfahren Sie, wie eBay Logs und Metriken aus ihren Anwendungen in Kubernetes erfasst.

Container sind nur der Anfang

Verfügen Sie über Netzwerkdaten? Infrastruktur-Logs? Dokumente mit enormen Textmengen? Zentrieren Sie alles im Elastic Stack und bereichern Sie Ihre Analysen, optimieren Sie Ihre Workflows und vereinfachen Sie Ihre Architektur.

App-Suche

Suche nach Dokumenten, Geodaten usw.

Mehr erfahren

Sicherheitsanalysen

Interaktive Untersuchung – schnell und skalierbar.

Mehr erfahren

Metriken

Erhalte Einblick in Zahlen: CPU, Speicher, usw.

Mehr erfahren

Website-Suche

Optimiere das Sucherlebnis auf deiner Website.

Mehr erfahren

APM

Erhalte Einblicke in deine Application-Performance.

Mehr erfahren