Merge pull request #97115 from eromanova97/manual-cp-97059-to-4.18

[enterprise-4.18] OBSDOCS-2252: Vale dita compatibility assessment - verify assemblies

Author: eromanova97

observability/monitoring/about-ocp-monitoring/key-concepts.adoc

@@ -71,6 +71,7 @@ include::modules/monitoring-understanding-metrics.adoc[leveloffset=+1]
 * xref:../../../observability/monitoring/accessing-metrics/accessing-metrics-as-a-developer.adoc#accessing-metrics-as-a-developer[Accessing metrics as a developer]
 
 include::modules/monitoring-controlling-the-impact-of-unbound-attributes-in-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-adding-cluster-id-labels-to-metrics.adoc[leveloffset=+2]
 
 //About monitoring dashboards
@@ -102,15 +103,17 @@ include::modules/monitoring-about-managing-alerts.adoc[leveloffset=+1]
 include::modules/monitoring-managing-silences.adoc[leveloffset=+2]
 
 include::modules/monitoring-managing-core-platform-alerting-rules.adoc[leveloffset=+2]
+
 include::modules/monitoring-tips-for-optimizing-alerting-rules-for-core-platform-monitoring.adoc[leveloffset=+2]
 
 include::modules/monitoring-about-creating-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-managing-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-optimizing-alerting-for-user-defined-projects.adoc[leveloffset=+2]
 
 include::modules/monitoring-searching-alerts-silences-and-alerting-rules.adoc[leveloffset=+2]
 
-
 // Overview of setting up alert routing for user-defined projects
 include::modules/monitoring-understanding-alert-routing-for-user-defined-projects.adoc[leveloffset=+1]
 

observability/monitoring/about-ocp-monitoring/monitoring-stack-architecture.adoc

@@ -25,10 +25,12 @@ endif::openshift-dedicated,openshift-rosa[]
 
 //Components for monitoring user-defined projects
 include::modules/monitoring-components-for-monitoring-user-defined-projects.adoc[leveloffset=+1]
+
 include::modules/monitoring-targets-for-user-defined-projects.adoc[leveloffset=+2]
 
 //The monitoring stack in high-availability clusters
 include::modules/monitoring-monitoring-stack-in-ha-clusters.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../../operators/operator_sdk/osdk-ha-sno.adoc#osdk-ha-sno[High-availability or single-node cluster detection and support]

observability/monitoring/configuring-core-platform-monitoring/configuring-performance-and-scalability.adoc

@@ -8,6 +8,9 @@ toc::[]
 
 You can configure the monitoring stack to optimize the performance and scale of your clusters. The following documentation provides information about how to distribute the monitoring components and control the impact of the monitoring stack on CPU and memory resources.
 
+[role="_additional-resources"]
+.Additional resources
+
 * xref:../../../observability/monitoring/about-ocp-monitoring/key-concepts.adoc#about-performance-and-scalability_key-concepts[About performance and scalability]
 
 [id="controlling-placement-and-distribution-of-monitoing-components_{context}"]

observability/monitoring/configuring-core-platform-monitoring/preparing-to-configure-the-monitoring-stack.adoc

@@ -1,6 +1,5 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
-
 [id="preparing-to-configure-the-monitoring-stack"]
 = Preparing to configure core platform monitoring stack
 :context: preparing-to-configure-the-monitoring-stack
@@ -35,5 +34,6 @@ include::modules/monitoring-granting-users-permissions-for-core-platform-monitor
 * xref:../../../observability/monitoring/accessing-metrics/accessing-monitoring-apis-by-using-the-cli.adoc#cmo-services-resources_accessing-monitoring-apis-by-using-the-cli[CMO services resources]
 
 include::modules/monitoring-granting-user-permissions-using-the-web-console.adoc[leveloffset=+2]
+
 include::modules/monitoring-granting-user-permissions-using-the-cli.adoc[leveloffset=+2,tags=**;CPM;!UWM]
 

observability/monitoring/configuring-user-workload-monitoring/preparing-to-configure-the-monitoring-stack-uwm.adoc

@@ -50,6 +50,7 @@ include::modules/monitoring-enabling-the-platform-alertmanager-instance-for-user
 endif::openshift-dedicated,openshift-rosa[]
 
 include::modules/monitoring-enabling-a-separate-alertmanager-instance-for-user-defined-alert-routing.adoc[leveloffset=+2]
+
 include::modules/monitoring-granting-users-permission-to-configure-alert-routing-for-user-defined-projects.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -67,6 +68,7 @@ include::modules/monitoring-granting-users-permission-to-monitor-user-defined-pr
 * xref:../../../observability/monitoring/configuring-user-workload-monitoring/preparing-to-configure-the-monitoring-stack-uwm.adoc#granting-users-permission-to-configure-alert-routing-for-user-defined-projects_preparing-to-configure-the-monitoring-stack-uwm[Granting users permission to configure alert routing for user-defined projects]
 
 include::modules/monitoring-granting-user-permissions-using-the-web-console.adoc[leveloffset=+2]
+
 include::modules/monitoring-granting-user-permissions-using-the-cli.adoc[leveloffset=+2,tags=**;UWM;!CPM]
 
 // Excluding a user-defined project from monitoring

observability/monitoring/getting-started/maintenance-and-support-for-monitoring.adoc

@@ -18,6 +18,7 @@ Installing another Prometheus instance is not supported by the Red Hat Site Reli
 endif::openshift-dedicated,openshift-rosa[]
 
 include::modules/monitoring-support-considerations.adoc[leveloffset=+1]
+
 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/monitoring-support-policy-for-monitoring-operators.adoc[leveloffset=+1]
 endif::openshift-dedicated,openshift-rosa[]

observability/monitoring/managing-alerts/managing-alerts-as-a-developer.adoc

@@ -46,9 +46,10 @@ When you create silences, they are replicated across Alertmanager pods. However,
 * xref:../../../observability/monitoring/configuring-core-platform-monitoring/storing-and-recording-data.adoc#configuring-persistent-storage_storing-and-recording-data[Configuring persistent storage]
 
 include::modules/monitoring-silencing-alerts.adoc[leveloffset=+2,tags=**;DEV;!ADM]
+
 include::modules/monitoring-editing-silences.adoc[leveloffset=+2,tags=**;DEV;!ADM]
-include::modules/monitoring-expiring-silences.adoc[leveloffset=+2,tags=**;DEV;!ADM]
 
+include::modules/monitoring-expiring-silences.adoc[leveloffset=+2,tags=**;DEV;!ADM]
 
 [id="managing-alerting-rules-for-user-defined-projects-uwm_{context}"]
 == Managing alerting rules for user-defined projects
@@ -63,6 +64,7 @@ In {product-title}, you can create, view, edit, and remove alerting rules for us
 * xref:../../../observability/monitoring/about-ocp-monitoring/key-concepts.adoc#optimizing-alerting-for-user-defined-projects_key-concepts[Optimizing alerting for user-defined projects]
 
 include::modules/monitoring-creating-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-creating-cross-project-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -71,6 +73,7 @@ include::modules/monitoring-creating-cross-project-alerting-rules-for-user-defin
 * link:https://prometheus.io/docs/practices/alerting/[Alerting (Prometheus documentation)]
 
 include::modules/monitoring-accessing-alerting-rules-for-your-project.adoc[leveloffset=+2]
+
 include::modules/monitoring-removing-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
 
 [role="_additional-resources"]

observability/monitoring/managing-alerts/managing-alerts-as-an-administrator.adoc

@@ -46,9 +46,10 @@ When you create silences, they are replicated across Alertmanager pods. However,
 * xref:../../../observability/monitoring/configuring-core-platform-monitoring/storing-and-recording-data.adoc#configuring-persistent-storage_storing-and-recording-data[Configuring persistent storage]
 
 include::modules/monitoring-silencing-alerts.adoc[leveloffset=+2,tags=**;ADM;!DEV]
+
 include::modules/monitoring-editing-silences.adoc[leveloffset=+2,tags=**;ADM;!DEV]
-include::modules/monitoring-expiring-silences.adoc[leveloffset=+2,tags=**;ADM;!DEV]
 
+include::modules/monitoring-expiring-silences.adoc[leveloffset=+2,tags=**;ADM;!DEV]
 
 [id="managing-alerting-rules-for-core-platform-monitoring_{context}"]
 == Managing alerting rules for core platform monitoring
@@ -68,6 +69,7 @@ For example, you can change the `severity` label for an alert from `warning` to
 * xref:../../../observability/monitoring/about-ocp-monitoring/key-concepts.adoc#tips-for-optimizing-alerting-rules-for-core-platform-monitoring_key-concepts[Tips for optimizing alerting rules for core platform monitoring]
 
 include::modules/monitoring-creating-new-alerting-rules.adoc[leveloffset=+2]
+
 include::modules/monitoring-modifying-core-platform-alerting-rules.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -90,6 +92,7 @@ In {product-title}, you can create, view, edit, and remove alerting rules for us
 * xref:../../../observability/monitoring/about-ocp-monitoring/key-concepts.adoc#optimizing-alerting-for-user-defined-projects_key-concepts[Optimizing alerting for user-defined projects]
 
 include::modules/monitoring-creating-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-creating-cross-project-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -99,7 +102,9 @@ include::modules/monitoring-creating-cross-project-alerting-rules-for-user-defin
 * link:https://prometheus.io/docs/practices/alerting/[Alerting (Prometheus documentation)]
 
 include::modules/monitoring-listing-alerting-rules-for-all-projects-in-a-single-view.adoc[leveloffset=+2]
+
 include::modules/monitoring-removing-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
+
 include::modules/monitoring-disabling-cross-project-alerting-rules-for-user-defined-projects.adoc[leveloffset=+2]
 
 [role="_additional-resources"]

observability/monitoring/sd-accessing-monitoring-for-user-defined-projects.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/attributes-openshift-dedicated.adoc[]
 [id="sd-accessing-monitoring-for-user-defined-projects"]
 = Accessing monitoring for user-defined projects
-include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: sd-accessing-monitoring-for-user-defined-projects
 
 toc::[]

observability/monitoring/sd-disabling-monitoring-for-user-defined-projects.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
+include::_attributes/attributes-openshift-dedicated.adoc[]
 [id="sd-disabling-monitoring-for-user-defined-projects"]
 = Disabling monitoring for user-defined projects
-include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: sd-disabling-monitoring-for-user-defined-projects
 
 toc::[]