fake anchors for xlinks

Author: shainaraskas

deploy-manage/monitor/logging-configuration.md

@@ -25,7 +25,7 @@ The following logging features are available:
 
 * **Application and component logging**: Logs messages related to running {{kib}}. 
 
-  You can [configure the log level for {{kib}}](/deploy-manage/monitor/logging-configuration/kibana-log-levels.md), and, in self-managed clusters, [configure underlying settings](/deploy-manage/monitor/logging-configuration/kib-self-managed-logging.md) to customize logging behavior.
+  You can [configure the log level for {{kib}}](/deploy-manage/monitor/logging-configuration/kibana-log-levels.md), and, in self-managed, ECE, or ECK deployments, [configure advanced settings](/deploy-manage/monitor/logging-configuration/kib-self-managed-logging.md) to customize logging behavior.
 
 * [Audit logging](/deploy-manage/security/logging-configuration/enabling-audit-logs.md): Logs security-related events on your deployment.
 

deploy-manage/monitor/logging-configuration/kib-self-managed-logging.md renamed to deploy-manage/monitor/logging-configuration/kib-advanced-logging.md

@@ -4,9 +4,11 @@ mapped_pages:
 applies_to:
   deployment:
     self: 
+    ece:
+    eck:
 ---
 
-# {{kib}} logging settings in self-managed clusters
+# Advanced {{kib}} logging settings
 
 You do not need to configure any additional settings to use the logging features in {{kib}}. Logging is enabled by default, and will log at info level using the `pattern` layout, which outputs logs to `stdout`.
 

deploy-manage/monitor/logging-configuration/kibana-logging.md

@@ -11,12 +11,18 @@ applies_to:
 
 # Kibana logging [logging-configuration]
 
+$$$pattern-layout$$$
+$$$time-interval-triggering-policy$$$
+$$$size-limit-triggering-policy$$$
+$$$logging-appenders$$$
+$$$dedicated-loggers$$$
+
 You do not need to configure any additional settings to use the logging features in Kibana. Logging is enabled by default.
 
-In all deployment types, you might want to change the log level for {{kib}}. In a self-managed cluster, you might want to further customize your logging settings to define where log messages are displayed, stored, and formatted, or provide granular settings for different loggers.
+In all deployment types, you might want to change the log level for {{kib}}. In a self-managed, ECE, or ECK deployment, you might want to further customize your logging settings to define where log messages are displayed, stored, and formatted, or provide granular settings for different loggers.
 
 * [](/deploy-manage/monitor/logging-configuration/kibana-log-levels.md)
-* [](/deploy-manage/monitor/logging-configuration/kib-self-managed-logging.md)
+* [](/deploy-manage/monitor/logging-configuration/kib-advanced-logging.md)
 
 You can also configure [{{kib}} task manager health monitoring](/deploy-manage/monitor/kibana-task-manager-health-monitoring.md) using logging settings.
 

deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md

@@ -11,6 +11,9 @@ applies_to:
 
 # Update Elasticsearch logging levels [logging]
 
+$$$deprecation-logging$$$
+$$$_deprecation_logs_throttling$$$
+
 Log4j 2 log messages include a *level* field, which is one of the following (in order of increasing verbosity):
 
 * `FATAL`

redirects.yml

@@ -27,6 +27,7 @@ redirects:
   'deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md': '!deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md'
   'deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md': '!deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md'
   'deploy-manage/deploy/kibana-reporting-configuration.md': '!deploy-manage/kibana-reporting-configuration.md'
+  'deploy-manage/monitor/logging-configuration/kibana-logging-cli-configuration.md': '!deploy-manage/monitor/logging-configuration/kib-advanced-logging.md'
 
   ## audit logging movement to security section
   'deploy-manage/monitor/logging-configuration/configuring-audit-logs.md': 'deploy-manage/security/logging-configuration/configuring-audit-logs.md'