Merge pull request #579 from mulesoft/W-21199271-Fix-troubleshooting-info-ie

W-21199271 update troubleshooting info

Author: IsaacEldridge

modules/ROOT/pages/af-troubleshoot-agent-networks.adoc

@@ -17,39 +17,23 @@ Enable logging and log levels from CloudHub 2.0 or Runtime Fabric:
 * xref:runtime-fabric::deploy-to-runtime-fabric.adoc#configure-logging-and-log-levels[Runtime Fabric]
 . Set the log level to Debug for these classes:
 +
-* `com.mulesoft.modules.agent.broker`
-* `org.mule.service.http.impl.service.HttpMessageLogger`
+* `com.mulesoft.modules.agent.broker` (For agent broker)
+* `INSECURE-LOGGING` (For content that can potentially contain sensitive information, such as LLM reasoning, and inputs and outputs from agents and assets defined in `tools` and `links`)
 
 [IMPORTANT]
-HTTP wire logging displays HTTP headers and payload in plain text. Avoid leaving it enabled indefinitely or unsupervised, as it can negatively impact API performance.
+`INSECURE-LOGGING` is very likely to contain sensitive information, such as personally identifiable information (PII). Make sure to disable it after troubleshooting is completed.
 
 [[enable-message-logging]]
 == Enable Message Logging Policy
 
-Use API Manager or manually edit the agent network file to add a message logging policy. 
+Edit `agent-network.yaml` to set message logging for MCP servers and agents. 
 
-=== Using API Manager
-
-. In API Manager, select the API, agent, or MCP server instance for which you want to apply the policy. 
-. Follow the steps in xref:gateway::flex-managed-message-log.adoc#configure-message-logging-in-connected-mode[Configure Message Logging in Connected Mode] and add these settings:
-+
-* In the Messages field, enter `#[attributes]`.
-* Select the checkboxes for **Before Calling API** and **After Calling API**.
-. Click **Save**.
-
-Afterward, you should see a Message Log option for the API, agent, or MCP server.
-
-[NOTE]
-If you redeploy the network, this policy is deleted.
-
-=== Using the Agent Network File
-
-In the `connection` section of the API, agent, or MCP server instance you want to log, add the following inside `policies`:
+Message logging uses the xref:gateway::policies-included-message-logging.adoc[Flex Gateway Message Logging policy]. In the `connection` section of the agent or MCP server instance you want to log, add the following logging policy inside `policies`:
 
 [source,yaml]
 ----
 
-  policies: ## add the following inside the policy setting
+policies: ## add the following inside the policy setting
     - ref:
         name: message-logging
         namespace: business_group_UUID
@@ -83,14 +67,6 @@ If Anypoint Monitoring isn't showing traces for agents and MCP servers, check th
 * In API Manager, verify you've enabled the tracing policy for all brokers and agents. 
 * In the managed Flex Gateways, verify that you've enabled Distributed Tracing for ingress and egress.
 
-=== Issue: Agent Visualizer Shows Disconnected Nodes
-
-If Agent Visualizer shows disconnected nodes with no edges, delete the `extensions` from the `spec.capabilities` section in `agent-network.yaml`.
-
-=== Issue: Null Response from Broker
-
-If your agent network broker returns a null response, restart the broker.
-
 === Issue: No Agent Network Commands in Anypoint Code Builder
 
 If you installed Anypoint Code Builder successfully, but you don’t see agent network commands in the interface, verify that you have the latest version of the Anypoint Extension Pack. Then, restart VS Code.