Monitoring de conteneur

Vos applications et votre environnement évoluent. La Suite Elastic aussi. Monitorez, recherchez et visualisez tout ce qui se passe au niveau de vos applications, de Docker et de Kubernetes, le tout depuis un seul et même emplacement.

Faites l'expérience du monitoring de conteneur avec Elastic. Allez-y, essayez !

Unifiez

Affichez vos logs et vos indicateurs sur une seule et même plateforme

Monitorez vos applications, gardez un œil sur vos événements et indicateurs Kubernetes, et analysez la performance des conteneurs Docker. Visualisez-les et analysez-les dans une interface utilisateur construite pour les opérations d'infrastructure qui regroupe tous vos indicateurs et vos logs.

Déployer

Faire du monitoring une réalité avec Beats

Commencez à transférer des logs et des indicateurs à partir de vos applications, conteneurs Docker et orchestrations Kubernetes avec Filebeat, Metricbeat et plus encore. La configuration ne prend qu'une ou deux minutes, et la fonction Autodiscover prend ensuite le relais. Lisez cet article et consultez le référentiel GitHub pour découvrir un exemple détaillé de la collecte de logs et d'indicateurs depuis votre application, Docker et k8s.

Icon

Gardez un œil sur Kubernetes et les applications qui y sont exécutées.

Icon

Gérez vos applications et votre infrastructure Docker.

Icon

Vous souhaitez déployer la Suite Elastic dans Docker ? Utilisez nos conteneurs officiels.

Autodiscover

Les agents Beats réagissent à la nature dynamique de vos plateformes

La fonctionnalité Autodiscover de Metricbeat et Filebeat vous permet de vous tenir au courant des changements de votre environnement. Automatisez l'ajout de modules et de chemins de logs et adaptez vos paramètres de monitoring de manière dynamique grâce aux hooks d'API Docker et Kubernetes. Ensuite, il vous suffit d'ajouter les métadonnées afin de savoir d'où viennent toutes ces données.

Un suivi en direct

Visualisez vos données et soyez informé des modifications

Tournez à plein régime avec les tableaux de bord Kibana préconstruits. Puis créez des alertes et des tableaux de bord personnalisés pour garder un œil sur les indicateurs les plus importants. Votre système intègre de nouveaux conteneurs ? Vous voulez connaître l'état de votre application, Docker et Kubernetes ? Visualisez les changements, identifiez les problèmes, prenez le contrôle et soyez informé. Aucun problème.

Prêt en quelques minutes

Intégrez vos données à la Suite Elastic et gardez un œil sur vos déploiements en quelques étapes.
  • 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.

Rejoignez le club

Ne vous contentez pas de nous croire sur parole.

Découvrez comment eBay collecte des logs et des indicateurs à partir de ses applications dans Kubernetes.

Les conteneurs ne sont qu'un point de départ

Vous avez des données réseau ? Des logs d'infrastructure ? Des documents texte ultra-volumineux ? Centralisez le tout dans la Suite Elastic : enrichissez vos analyses, rationalisez vos flux de travail et simplifiez votre architecture.

App Search

Recherchez à travers tous vos documents.

En savoir plus

Security Analytics

Analyse interactive rapide et évolutive.

En savoir plus

Metrics

Supervisez processeur, mémoire, et bien plus.

En savoir plus

Site Search

Créez facilement une excellente expérience de recherche.

En savoir plus

APM

Obtenez un aperçu de la performance de vos applications.

En savoir plus