monitor.md

mapped_pages	applies_to
https://www.elastic.co/guide/en/elasticsearch/reference/current/monitor-elasticsearch-cluster.html https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html	deployment ess ece eck self all all all all

Monitoring

Keeping on top of the health of your cluster or deployment, as well as your orchestrator, is an important part of maintenance. It also helps you to identify and troubleshoot issues. When you move to production, detecting and resolving issues when they arise is a key component of keeping your deployment highly available.

Depending on your deployment type, you can use a variety of solutions for monitoring your Elastic components.

Monitoring your cluster or deployment

Depending on your deployment type and context, you have several options for monitoring your cluster or deployment.

AutoOps (recommended)

deployment:
  ess:

:::{include} /deploy-manage/monitor/_snippets/autoops.md :::

Stack monitoring

deployment:
  ess:
  ece:
  eck:
  self:

:::{include} /deploy-manage/monitor/_snippets/stack-monitoring-def.md :::

In {{ece}} and {{ech}}, Elastic manages the installation and configuration of the monitoring agent for you, simplifying the stack monitoring setup process.

:::{include} /deploy-manage/monitor/_snippets/stack-monitoring-prod.md :::

Cluster health and performance metrics

deployment:
  ece:
  ess:

{{ece}} and {{ech}} provide out of the box tools for monitoring the health of your deployment and resolving health issues when they arise:

• Cluster health information, including health warnings
• A JVM memory pressure indicator

{{ech}} only:

• Cluster performance information
• Preconfigured logs and metrics

{{ece}} only:

• Platform monitoring, including logs, metrics, and proxy logs

:::{tip} Out of the box logs and metrics tools, including ECH preconfigured logs and metrics and ECE platform monitoring logs and metrics, are useful for providing information in a non-production environment. In a production environment, it’s important set up either AutoOps or stack monitoring to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to contact our support team, they can use the retained data to help diagnose any problems that you may encounter. :::

To learn more about the health and performance tools in {{ecloud}}, refer to .

{{kib}} task manager monitoring

stack: preview

The {{kib}} task manager has an internal monitoring mechanism to keep track of a variety of metrics, which can be consumed with either the health monitoring API or the {{kib}} server log. Learn how to configure thresholds and consume related to {{kib}} task manager.

Monitoring your orchestrator

deployment:
  ece:
  eck:

In addition to monitoring your cluster or deployment health and performance, you need to monitor your orchestrator. Monitoring is especially important for orchestrators hosted on infrastructure that you control.

Learn how to enable monitoring of your orchestrator:

• ECK operator metrics: Open and secure a metrics endpoint that can be used to monitor the operator’s performance and health. This endpoint can be scraped by third-party Kubernetes monitoring tools.
• ECE platform monitoring: Learn about how ECE collects monitoring data for your installation in the logging-and-metrics deployment, and how to access monitoring data.

:::{admonition} Monitoring {{ecloud}} Elastic monitors {{ecloud}} service metrics and performance as part of our shared responsibility. We provide service availability information on our service status page. :::

Logging

You can configure several types of logs in {{stack}} that can help you to gain insight into {{stack}} operations, diagnose issues, and track certain types of events. Learn about the types of logs available, where to find them, and how to configure them.