Remove section about turning on agent monitoring in cloud for Fleet S…

…erver (#1286) (#1296)

docs/en/ingest-management/fleet/fleet-server-monitoring.asciidoc

@@ -1,51 +1,36 @@
 [[fleet-server-monitoring]]
-= {fleet-server} monitoring
+= Monitor a self-managed {fleet-server}
 
-Monitoring {fleet-server} is key since the operation of the {fleet-server} is
-paramount to the health of the deployed agents and the services they offer. When
-{fleet-server} is not operating correctly, it may lead to delayed check-ins,
-status information, and updates for the agents it manages. The monitoring data
-will tell you when to add capacity for {fleet-server}, and provide error logs
-and information to troubleshoot other issues.
+For self-managed {fleet-server}s, monitoring is key because the operation of the
+{fleet-server} is paramount to the health of the deployed agents and the
+services they offer. When {fleet-server} is not operating correctly, it may lead
+to delayed check-ins, status information, and updates for the agents it manages.
+The monitoring data will tell you when to add capacity for {fleet-server}, and
+provide error logs and information to troubleshoot other issues.
 
-To enable monitoring for {fleet-server}, turn on agent monitoring in the agent
-policy. For self-managed clusters, monitoring is on by default when you create a
+For self-managed clusters, monitoring is on by default when you create a
 new agent policy or use the existing Default {fleet-server} agent policy.
-However, it is off by default in the {ecloud} agent policy because monitoring
-requires additional RAM.
 
-To turn on {fleet-server} monitoring in the agent policy:
+To monitor {fleet-server}:
 
-. In {fleet}, go to *Agent Policies* and click on the *{ecloud} agent policy*.
-+
-[role="screenshot"]
-image::images/fleet-policy-page.png[Fleet Policy Page]
+. In {fleet}, go to *Agent Policies* and click the {fleet-server} agent policy.
 
-. Click the *Settings* tab and notice that Agent monitoring is
-off by default.
+. Click the *Settings* tab and verify that *Collect agent logs* and
+*Collect agent metrics* are selected.
 
-. Under *Agent monitoring*, select *Collect agent logs* and
-*Collect agent metrics*.
-+
---
-[role="screenshot"]
-image::images/elastic-cloud-agent-policy-page.png[{ecloud} Policy Page]
-
-The agent will now be able to collect logs and metrics from the {fleet-server}.
-
-NOTE: The {fleet-server} is deployed as yet another agent in the system.
---
-
-. Next, set the *Default namespace*.
+. Next, set the *Default namespace* to something like `fleetserver`.
 +
 Setting the default namespace lets you segregate {fleet-server} monitoring data
 from other collected data. This makes it easier to search and visualize the
-monitoring data. By default the monitoring data is sent to the *default*
-namespace.
+monitoring data.
++
+[role="screenshot"]
+image::images/fleet-server-agent-policy-page.png[{fleet-server} agent policy]
 
 . To confirm your change, click *Save changes*.
 
-To see the metrics collected for {fleet-server}, go to *Analytics > Discover*.
+To see the metrics collected for the agent running {fleet-server}, go to
+*Analytics > Discover*.
 
 In the following example, `fleetserver` was configured as the namespace, and
 you can see the metrics collected: