orchestrator stuff

Author: shainaraskas

deploy-manage/monitor.md

@@ -81,7 +81,16 @@ deployment:
   eck:
 ```
 
-TODO
+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](/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md): 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.
+* [ECK platform monitoring](/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md): 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}}](/deploy-manage/deploy/elastic-cloud.md) service metrics and performance as part of [our shared responsibility](https://www.elastic.co/cloud/shared-responsibility). We provide service availability information on our [service status page](/deploy-manage/cloud-organization/service-status.md).
+:::
 
 ## Logging
 

deploy-manage/monitor/orchestrators.md

@@ -7,10 +7,17 @@ applies_to:
 
 # Monitoring orchestrators
 
-% What needs to be done: Write from scratch
+Your [orchestrator](/deploy-manage/deploy.md#about-orchestration) is an important part of your Elastic architecture. It automates the deployment and management of multiple Elastic clusters, handling tasks like scaling, upgrades, and monitoring. Like your cluster or deployment, you need to monitor your orchestrator to ensure that it is healthy and performant. Monitoring is especially important for orchestrators hosted on infrastructure that you control.
 
-% GitHub issue: https://github.com/elastic/docs-projects/issues/350
+In this section, you'll learn how to enable monitoring of your orchestrator.
 
-% Scope notes: Landing page to monitoring orchestrators (not deployments)
+* [ECK operator metrics](/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md): 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.
+* [ECK platform monitoring](/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md): Learn about how ECE collects monitoring data for your installation in the `logging-and-metrics` deployment, and how to access monitoring data.
 
-⚠️ **This page is a work in progress.** ⚠️
+:::{admonition} Monitoring {{ecloud}}
+Elastic monitors {{ecloud}} service metrics and performance as part of [our shared responsibility](https://www.elastic.co/cloud/shared-responsibility). We provide service availability information on our [service status page](/deploy-manage/cloud-organization/service-status.md).
+:::
+
+:::{note}
+Orchestrator monitoring can sometimes augment cluster or deployment monitoring, but doesn't replace it. For information about monitoring your cluster or deployment, refer to [](/deploy-manage/monitor.md).
+:::

deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md

@@ -6,52 +6,47 @@ applies_to:
     ece: all
 ---
 
-# Access logs and metrics [ece-monitoring-ece-access]
+# Platform monitoring deployment logs and metrics [ece-monitoring-ece-access]
 
-To access logs and metrics for your deployment:
-
-1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md).
-2. From the **Deployments** page, select your deployment.
-
-    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
-
-3. On the **Elasticsearch** page, the following logs and metrics are available:
-
-    Elasticsearch logs
-    :   Detailed logs related to cluster state
+On the **{{es}}** page, the following logs and metrics are available:
 
-    Elasticsearch metrics
-    :   Detailed metrics for CPU and memory usage, running processes, networking and file system performance, and more
+| Log or metric | Description |
+| --- | --- |
+| {{es}} logs | Detailed logs related to cluster state. |
+| {{es}} metrics | Detailed metrics for CPU and memory usage, running processes, networking and file system performance, and more. |
+| Proxy logs | Search and indexing requests that proxies have sent to the {{es}} cluster. |
 
-    Proxy logs
-    :   Search and indexing requests that proxies have sent to the Elasticsearch cluster
+If a {{kib}} instance exists for the deployment, the following {{kib}} logs and metrics are also available from the **{{kib}}** page:
 
-    If a Kibana instance exists for the deployment, the following Kibana logs and metrics are also available from the **Kibana** page:
+| Log or metric | Description |
+| --- | --- |
+| {{kib}} logs | Detailed logs related to instance state. |
+| {{kib}} metrics | Detailed metrics for CPU and memory usage, running processes, networking and file system performance, and more. |
+| Proxy logs | Requests that proxies have sent to the {{kib}} instance. |
 
-    Kibana logs
-    :   Detailed logs related to instance state
+## Access logs and metrics
 
-    Kibana metrics
-    :   Detailed metrics for CPU and memory usage, running processes, networking and file system performance, and more
+To access logs and metrics for your deployment:
 
-    Proxy logs
-    :   Requests that proxies have sent to the Kibana instance
+1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md).
+2. From the **Deployments** page, select your deployment.
 
+    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
 
-::::{tip} 
-If you have a license from 2018 or earlier, you might receive a warning that your cluster license is about to expire. Don’t panic, it isn’t really. Elastic Cloud Enterprise manages the cluster licenses so that you don’t have to. In rare cases, such as when a cluster is overloaded, it can take longer for Elastic Cloud Enterprise to reapply the cluster license. If you have a license from 2019 and later, you’ll receive a warning only when your full platform license is about to expire, which you’ll need to renew.
-::::
+3. Depending on the logs or metrics that you want to access, click on the **Elasticsearch** or **Kibana** page.
 
+    ::::{tip} 
+    If you have a license from 2018 or earlier, you might receive a warning that your cluster license is about to expire. Don’t panic, it isn’t really. Elastic Cloud Enterprise manages the cluster licenses so that you don’t have to. In rare cases, such as when a cluster is overloaded, it can take longer for Elastic Cloud Enterprise to reapply the cluster license. If you have a license from 2019 and later, you’ll receive a warning only when your full platform license is about to expire, which you’ll need to renew.
+    ::::
 
-1. Select one of the links and log in with the `elastic` user. If you do not know the password, you can [reset it first](../../users-roles/cluster-or-deployment-auth/built-in-users.md).
+4. Select one of the links and log in with the `elastic` user. If you do not know the password, you can [reset it first](../../users-roles/cluster-or-deployment-auth/built-in-users.md).
 
     ::::{tip} 
     The password you specify must be for the `elastic` user on the `logging-and-metrics` cluster, where the logging and metrics indices are collected. If you need to reset the password for the user, make sure you reset for the `logging-and-metrics` cluster.
     ::::
 
 
-    After you select one of the links, Kibana opens and shows you a view of the monitoring metrics for the logs or metrics that you selected.
+    After you select one of the links, {{kib}} opens and shows you a view of the monitoring metrics for the logs or metrics that you selected.
 
 
 If you are looking for an {{es}} or {{kib}} diagnostic to share with Elastic support, go to the **Operations** page for the deployment and download the diagnostic bundle to attach to your ticket. If logs or an ECE diagnostic are requested by Elastic support, please [run the ECE diagnostics tool](../../../troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md).
-

deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md

@@ -18,7 +18,7 @@ You might need to adjust the retention period for one of the following reasons:
 To customize the retention period, set up a custom lifecycle policy for logs and metrics indices:
 
 1. [Create a new index lifecycle management (ILM) policy](../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) in the logging and metrics cluster.
-2. Create a new, legacy-style, index template that matches the data view (formerly *index pattern*) that you wish to customize lifecycle for.
+2. Create a new, legacy-style, index template that matches the data view (formerly *index pattern*) that you want to customize the lifecycle for.
 3. Specify a lifecycle policy in the index template settings.
 4. Choose a higher `order` for the template so the specified lifecycle policy will be used instead of the default.
 

deploy-manage/monitor/orchestrators/ece-platform-monitoring.md

@@ -8,22 +8,25 @@ applies_to:
 
 # ECE platform monitoring [ece-monitoring-ece]
 
-Elastic Cloud Enterprise by default collects monitoring data for your installation using Filebeat and Metricbeat. This data gets sent as monitoring indices to a dedicated `logging-and-metrics` deployment that is created whenever you install Elastic Cloud Enterprise on your first host. Data is collected on every host that is part of your Elastic Cloud Enterprise installation and includes:
+By default, {{ece}} collects monitoring data for your installation using Filebeat and Metricbeat. This data gets sent as monitoring indices to a dedicated `logging-and-metrics` deployment that is created whenever you install {{ece}} on your first host. Data is collected on every host that is part of your {{ece}} installation and includes:
 
-* Logs for all core services that are a part of Elastic Cloud Enterprise and monitoring metrics for core Elastic Cloud Enterprise services, system processes on the host, and any third-party software
-* Logs and monitoring metrics for Elasticsearch clusters and for Kibana instances
+* Logs for all core services that are a part of {{ece}} 
+* Monitoring metrics for core {{ece}} services, system processes on the host, and any third-party software
+* Logs and monitoring metrics for {{es}} clusters and for {{kib}} instances
 
-These monitoring indices are collected in addition to the [monitoring you might have enabled for specific clusters](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md), which also provides monitoring metrics that you can access in Kibana (note that the `logging-and-metrics` deployment is used for monitoring data from system deployments only; for non-system deployments, monitoring data must be sent to a deployment other than `logging-and-metrics`).
+These monitoring indices are collected in addition to the [monitoring you might have enabled for specific clusters](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md), which also provides monitoring metrics that you can access in Kibana. 
 
-In this section:
+The `logging-and-metrics` deployment is used for monitoring data from system deployments only. For non-system deployments, monitoring data must be sent to a deployment other than `logging-and-metrics`.
 
-* [Access logs and metrics](ece-monitoring-ece-access.md) - Where to find the logs and metrics that are collected.
-* [Capture heap dumps](../../../troubleshoot/deployments/cloud-enterprise/heap-dumps.md) - Troubleshoot instances that run out of memory.
-* [Capture thread dumps](../../../troubleshoot/deployments/cloud-enterprise/thread-dumps.md) - Troubleshoot instances that are having thread or CPU issues.
-* [Set the Retention Period for Logging and Metrics Indices](ece-monitoring-ece-set-retention.md) - Set the retention period for the indices that Elastic Cloud Enterprise collects.
+In this section, you'll learn the following about using ECE platform monitoring:
 
-::::{important} 
-The `logging-and-metrics` deployment is for use by your ECE installation only. You must not use this deployment to index monitoring data from your own Elasticsearch clusters or use it to index data from Beats and Logstash. Always create a separate, dedicated monitoring deployment for your own use.
-::::
+* [](ece-monitoring-ece-access.md): The types of logs and metrics that are collected for deployments, and where to find them.
+% where do we find logs and metrics for the installation itself? 
+* [](/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md): The fields that are included in proxy logs. Proxy logs capture the search and indexing requests that proxies have sent to the {{es}} cluster, and requests that proxies have sent to the {{kib}} instance.
+* [](ece-monitoring-ece-set-retention.md): How to set the retention period for the indices that {{ece}} collects.
 
+For information about troubleshooting {{ECE}} using these metrics, and guidance on capturing other diagnostic information like heap dumps and thread dumps, refer to [](/troubleshoot/deployments/cloud-enterprise/cloud-enterprise).
 
+::::{important} 
+The `logging-and-metrics` deployment is for use by your ECE installation only. You must not use this deployment to index monitoring data from your own Elasticsearch clusters or use it to index data from Beats and Logstash. Always create a separate, dedicated monitoring deployment for your own use.
+::::