more fixes

Author: shainaraskas

deploy-manage/monitor.md

@@ -58,7 +58,7 @@ deployment:
 
 {{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](/deploy-manage/monitor/cloud-health-perf#ec-es-cluster-health.md), including [health warnings](/deploy-manage/monitor/cloud-health-perf.md#ec-es-health-warnings)
+* [Cluster health information](/deploy-manage/monitor/cloud-health-perf.md#ec-es-cluster-health), including [health warnings](/deploy-manage/monitor/cloud-health-perf.md#ec-es-health-warnings)
 * [Cluster performance information](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md)
 * A [JVM memory pressure indicator](/deploy-manage/monitor/ec-memory-pressure.md)
 * [Preconfigured logs and metrics](/deploy-manage/monitor/cloud-health-perf.md#ec-es-health-preconfigured)

deploy-manage/monitor/logging-configuration.md

@@ -22,7 +22,7 @@ When shipping logs to a monitoring deployment there are more logging features av
 
 ### For {{es}} [extra-logging-features-elasticsearch]
 
-* [Audit logging](../logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
+* [Audit logging](/deploy-manage/security/logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
 * [Slow query and index logging](elasticsearch://reference/elasticsearch/index-settings/slow-log.md) - helps find and debug slow queries and indexing
 * Verbose logging - helps debug stack issues by increasing component logs
 
@@ -31,7 +31,7 @@ After you’ve enabled log delivery on your deployment, you can [add the Elastic
 
 ### For {{kib}} [extra-logging-features-kibana]
 
-* [Audit logging](../logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
+* [Audit logging](/deploy-manage/security/logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
 
 After you’ve enabled log delivery on your deployment, you can [add the {{kib}} user settings](/deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md) to enable this feature.
 

deploy-manage/toc.yml

@@ -696,7 +696,7 @@ toc:
             children:
               - file: monitor/monitoring-data/beats-page.md
               - file: monitor/monitoring-data/elasticsearch-metrics.md
-              - file: monitor/monitoring-data/kibana-alerts.md
+              - file: /monitor/monitoring-data/configure-stack-monitoring-alerts.md
               - file: monitor/monitoring-data/kibana-page.md
               - file: monitor/monitoring-data/logstash-page.md
               - file: monitor/monitoring-data/monitor-troubleshooting.md

raw-migrated-files/cloud/cloud/ec-monitoring-setup.md

@@ -59,7 +59,7 @@ To learn more about what [Elasticsearch monitoring metrics](/deploy-manage/monit
 :alt: Node tab in Kibana under Stack Monitoring
 :::
 
-Some [performance metrics](/deploy-manage/monitor/ec-saas-metrics-accessing.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
+Some [performance metrics](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md) are also available directly in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu:
 
 :::{image} ../../../images/cloud-ec-ce-monitoring-performance.png
 :alt: Performance page of the Elastic Cloud console

raw-migrated-files/cloud/cloud/ec-planning.md

@@ -44,7 +44,7 @@ Clusters that only have one master node are not highly available and are at risk
 
 ## Do you know when to scale? [ec-workloads] 
 
-Knowing how to scale your deployment is critical, especially when unexpected workloads hits. Don’t forget to [check your performance metrics](/deploy-manage/monitor/ec-saas-metrics-accessing.md) to make sure your deployments are healthy and can cope with your workloads.
+Knowing how to scale your deployment is critical, especially when unexpected workloads hits. Don’t forget to [check your performance metrics](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md) to make sure your deployments are healthy and can cope with your workloads.
 
 Scaling with {{ech}} is easy:
 

raw-migrated-files/toc.yml

@@ -37,17 +37,12 @@ toc:
       - file: cloud/cloud-heroku/ech-delete-deployment.md
       - file: cloud/cloud-heroku/ech-editing-user-settings.md
       - file: cloud/cloud-heroku/ech-enable-kibana2.md
-      - file: cloud/cloud-heroku/ech-enable-logging-and-monitoring.md
       - file: cloud/cloud-heroku/ech-getting-started.md
       - file: cloud/cloud-heroku/ech-manage-apm-settings.md
       - file: cloud/cloud-heroku/ech-manage-kibana-settings.md
-      - file: cloud/cloud-heroku/ech-monitoring-setup.md
-      - file: cloud/cloud-heroku/ech-monitoring.md
       - file: cloud/cloud-heroku/ech-planning.md
       - file: cloud/cloud-heroku/ech-regional-deployment-aliases.md
       - file: cloud/cloud-heroku/ech-restoring-snapshots.md
-      - file: cloud/cloud-heroku/ech-restrictions-monitoring.md
-      - file: cloud/cloud-heroku/ech-saas-metrics-accessing.md
       - file: cloud/cloud-heroku/ech-security.md
       - file: cloud/cloud-heroku/ech-snapshot-restore.md
       - file: cloud/cloud-heroku/ech-upgrade-deployment.md
@@ -64,7 +59,6 @@ toc:
       - file: cloud/cloud/ec-custom-repository.md
       - file: cloud/cloud/ec-delete-deployment.md
       - file: cloud/cloud/ec-editing-user-settings.md
-      - file: cloud/cloud/ec-enable-logging-and-monitoring.md
       - file: cloud/cloud/ec-faq-getting-started.md
       - file: cloud/cloud/ec-faq-technical.md
       - file: cloud/cloud/ec-getting-started-trial.md
@@ -75,13 +69,11 @@ toc:
       - file: cloud/cloud/ec-manage-enterprise-search-settings.md
       - file: cloud/cloud/ec-manage-kibana-settings.md
       - file: cloud/cloud/ec-monitoring-setup.md
-      - file: cloud/cloud/ec-monitoring.md
       - file: cloud/cloud/ec-password-reset.md
       - file: cloud/cloud/ec-planning.md
       - file: cloud/cloud/ec-regional-deployment-aliases.md
       - file: cloud/cloud/ec-restore-across-clusters.md
       - file: cloud/cloud/ec-restoring-snapshots.md
-      - file: cloud/cloud/ec-saas-metrics-accessing.md
       - file: cloud/cloud/ec-security.md
       - file: cloud/cloud/ec-select-subscription-level.md
       - file: cloud/cloud/ec-service-status.md
@@ -112,18 +104,13 @@ toc:
     children:
       - file: elasticsearch/elasticsearch-reference/documents-indices.md
       - file: elasticsearch/elasticsearch-reference/esql-using.md
-      - file: elasticsearch/elasticsearch-reference/how-monitoring-works.md
       - file: elasticsearch/elasticsearch-reference/index-modules-allocation.md
       - file: elasticsearch/elasticsearch-reference/index-modules-mapper.md
       - file: elasticsearch/elasticsearch-reference/ip-filtering.md
-      - file: elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md
-      - file: elasticsearch/elasticsearch-reference/monitoring-overview.md
-      - file: elasticsearch/elasticsearch-reference/monitoring-production.md
       - file: elasticsearch/elasticsearch-reference/recovery-prioritization.md
       - file: elasticsearch/elasticsearch-reference/scalability.md
       - file: elasticsearch/elasticsearch-reference/search-with-synonyms.md
       - file: elasticsearch/elasticsearch-reference/secure-cluster.md
-      - file: elasticsearch/elasticsearch-reference/secure-monitoring.md
       - file: elasticsearch/elasticsearch-reference/security-files.md
       - file: elasticsearch/elasticsearch-reference/security-limitations.md
       - file: elasticsearch/elasticsearch-reference/semantic-search-inference.md

troubleshoot/elasticsearch/high-cpu-usage.md

@@ -46,7 +46,7 @@ To track CPU usage over time, we recommend enabling monitoring:
     * **CPU credits**: Your remaining CPU credits, measured in seconds of CPU time.
 
 
-{{ech}} grants [CPU credits](../../deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md) per deployment to provide smaller clusters with performance boosts when needed. High CPU usage can deplete these credits, which might lead to [performance degradation](../monitoring/performance.md) and [increased cluster response times](../monitoring/cluster-response-time.md).
+{{ech}} grants [CPU credits](../../deploy-manage/monitor/ec-vcpu-boost-instance.md) per deployment to provide smaller clusters with performance boosts when needed. High CPU usage can deplete these credits, which might lead to [performance degradation](../monitoring/performance.md) and [increased cluster response times](../monitoring/cluster-response-time.md).
 ::::::
 
 ::::::{tab-item} Self-managed

troubleshoot/monitoring/unavailable-shards.md

@@ -164,7 +164,7 @@ The response is as follows:
 
 #### Check {{es}} cluster logs [ec-check-es-cluster-logs]
 
-To determine the allocation issue, you can [check the logs](/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-check-logs). This is easier if you have set up a dedicated monitoring deployment.
+To determine the allocation issue, you can [check the logs](/deploy-manage/monitor.md#logging). This is easier if you have set up a dedicated monitoring deployment.
 
 
 ## Analyze unassigned shards using the Kibana UI [ec-analyze_shards_with-kibana]