[8.11] [DOCS] Add solution selection to maintenance windows (#169441)

docs/api/alerting/list_rule_types.asciidoc

@@ -63,9 +63,14 @@ context and state in action parameter templates, and a short human readable
 description. When you create a rule in {kib}, it uses this information to prompt
 you for these variables in action parameter editors.
 
+// `alerts`:: TBD
+
 `authorized_consumers`::
 (object) The list of the plugins IDs that have access to the rule type.
 
+`category`::
+(string) The rule category, which is used by features such as category-specific maintenance windows.
+
 `default_action_group_id`::
 (string) The default ID for the rule type group.
 
@@ -77,6 +82,10 @@ action.
 (boolean) Indicates whether the rule type is enabled or disabled based on the
 subscription.
 
+// `has_alerts_mappings`:: TBD
+
+// `has_fields_for_a_a_d`:: TBD
+
 `id`::
 (string) The unique identifier for the rule type.
 
@@ -121,7 +130,28 @@ the API returns the following:
    {
       "id":"logs.alert.document.count",
       "name":"Log threshold",
+      "category": "observability",
       "producer":"logs",
+      "alerts": {
+        "context": "observability.logs",
+        "mappings": {
+          "fieldMap": {
+            "kibana.alert.evaluation.threshold": {
+              "type": "scaled_float",
+              "scaling_factor": 100,
+              "required": false
+            },
+            "kibana.alert.evaluation.value": {
+              "type": "scaled_float",
+              "scaling_factor": 100,
+              "required": false
+            },
+            ...
+           }
+         },
+        "useEcs": true,
+        "useLegacyAlerts": true
+      },
       "enabled_in_license":true,
       "recovery_action_group":{
          "id":"recovered",
@@ -164,7 +194,10 @@ the API returns the following:
          "logs":{"read":true,"all":false},
          "alerts":{"read":true,"all":false}
       },
-      "does_set_recovery_context":true
-   }
+      "does_set_recovery_context":true,
+      "has_alerts_mappings": true,
+      "has_fields_for_a_a_d": true
+   },
+   ....
 ]
 --------------------------------------------------

docs/management/maintenance-windows/maintenance-windows.asciidoc

@@ -11,7 +11,7 @@ preview::[]
 You can schedule single or recurring maintenance windows to temporarily reduce rule notifications.
 For example, a maintenance window prevents false alarms during planned outages.
 
-Maintenance windows affect all rules in all {kib} apps and spaces.
+By default, maintenance windows affect all rules in all {kib} apps and spaces.
 Alerts continue to be generated, however notifications are suppressed as follows:
 
 - When an alert occurs during a maintenance window, there are no notifications.
@@ -42,6 +42,10 @@ You can optionally configure it to repeat daily, monthly, yearly, or on a custom
 image::images/create-maintenance-window.png[The Create Maintenance Window user interface in {kib}]
 // NOTE: This is an autogenerated screenshot. Do not edit it directly.
 
+By default, maintenance windows affect all categories of rules.
+The category-specific maintenance window options alter this behavior.
+For the definitive list of rule types in each category, refer to the <<list-rule-types-api,get rule types API>>.
+
 A maintenance window can have any one of the following statuses:
 
 - `Upcoming`: It will run at the scheduled date and time.