[Fleet] Agent status alerts for monitoring

Author: karenzone

reference/fleet/agent-health-status.md

@@ -48,12 +48,19 @@ No. The health monitoring of {{agent}} and its inputs, as reported in {{fleet}},
 
 ## If {{agent}} goes down, is an alert generated by {{fleet}}? [agent-health-status-outage]
 
-No. Alerts would have to be created in {{kib}} on the indices that show the total count of agents at each specific state. Refer to [Enable alerts and ML jobs based on {{fleet}} and {{agent}} status](/reference/fleet/monitor-elastic-agent.md#fleet-alerting) in the {{agent}} monitoring documentation for the steps to configure alerting. Generating alerts on status change on individual agents is currently planned for a future release.
+::::{applies-switch}
+:::{applies-item} { "stack": "ga 9.2", serverless }
+Yes. When you install or upgrade {{agent}}, new alert rules are created automatically. You can configure and customize out-of-the-box alerts to get them up and running quickly. 
+Check out [Elastic Agent out-of-the-box alert rules](/reference/fleet/alert-templates) for details.
+:::
+:::{applies-item} { "stack": "ga 9.0" }
+No, not without additional configuration. For releases earlier than 9.2, alerts must be created in {{kib}} on the indices that show the total count of agents at each specific state. Refer to [Enable alerts and ML jobs based on {{fleet}} and {{agent}} status](/reference/fleet/monitor-elastic-agent.md#fleet-alerting) in the {{agent}} monitoring documentation for the steps to configure alerting.
+:::
+::::
 
 
 ## How long does it take for {{agent}} to report a status change? [agent-health-status-report-timing]
 
 Some {{agent}} states are reported immediately, such as when the agent has become `Unhealthy`. Some other states are derived after a certain criteria is met. Refer to [View agent status overview](/reference/fleet/monitor-elastic-agent.md#view-agent-status) in the {{agent}} monitoring documentation for details about monitoring agent status.
 
 Transition from an `Offline` state to an `Inactive` state is configurable by the user and that transition can be fine tuned by [Setting the inactivity timeout parameter](/reference/fleet/set-inactivity-timeout.md).
-

reference/fleet/monitor-elastic-agent.md

@@ -241,11 +241,20 @@ To do so, follow the steps in [Remote {{es}} output](/reference/fleet/remote-ela
 
 ## Enable alerts and ML jobs based on {{fleet}} and {{agent}} status [fleet-alerting]
 
-You can access the health status of {{fleet}}-managed {{agents}} and other {{fleet}} settings through internal {{fleet}} indices. This enables you to leverage various applications within the {{stack}} that can be triggered by the provided information. For instance, you can now create alerts and machine learning (ML) jobs based on these specific fields. Refer to the [Alerting documentation](/explore-analyze/alerts-cases.md) or see the [example](#fleet-alerting-example) on this page to learn how to define rules that can trigger actions when certain conditions are met.
+:::{admonition} Built-in alert rules for {{agent}}
+:applies_to: stack: ga 9.2.0
+
+As of 9.2.0, {{agent}} provides out-of-the-box alert rules to help you simplify monitoring the health of agents.
+Built-in alerts are the best approach for many monitoring use cases, and offer a quicker and easier alternative to manual configuration required in earlier versions.  
+
+Check out [Elastic Agent out-of-the-box alert rules](/reference/fleet/alert-templates) for more information. 
+:::
+
+You can access the health status of {{fleet}}-managed {{agents}} and other {{fleet}} settings through internal {{fleet}} indices. This enables you to leverage various applications within the {{stack}} that can be triggered by the provided information. For instance, you can now create alerts and machine learning (ML) jobs based on these specific fields. Refer to the [Alerting documentation](/explore-analyze/alerts-cases.md) or check out the [example](#fleet-alerting-example) on this page to learn how to define rules that can trigger actions when certain conditions are met.
 
 This functionality allows you to effectively track an agent’s status, and identify scenarios where it has gone offline, is experiencing health issues, or is facing challenges related to input or output.
 
-The following data streams and fields are available.
+These data streams and fields are available.
 
 Data stream
 :   `metrics-fleet_server.agent_status-default`
@@ -282,7 +291,7 @@ Data stream
 
 
 
-### Example: Enable an alert for offline {{agent}}s [fleet-alerting-example]
+Example: Enable an alert for offline {{agent}}s [fleet-alerting-example]
 
 You can set up an alert to notify you when one or more {{agent}}s goes offline: