​
Introduction

The Agentforce Context Protocol (ACP) Management UI includes an Activity Log that provides a chronological record of significant events within the ACP system. This log is an invaluable tool for monitoring tool usage, diagnosing issues, and understanding how ACP is being utilized in your Salesforce org.

This guide explains how to access and interpret the Activity Log.

​
Prerequisites

  • Access to the ACP Manager Lightning App in Salesforce.
  • ACP has been active, meaning tools have been called, connections tested, or other relevant operations performed.

​
Accessing the Activity Log

  1. Navigate to the ACP Manager App:

    • Open the App Launcher in Salesforce.
    • Search for “ACP Manager” and select it.

  2. Go to the “Activity Log” Tab:

    • Within the ACP Manager app, click on the Activity Log tab. This tab displays a list of recent ACP activities.

    (Placeholder: Screenshot of the ACP Manager UI, Activity Log tab)

​
Understanding the Activity Log Entries

The Activity Log typically displays the following information for each entry, often in a table format:

  • Timestamp: The date and time the activity occurred.
  • User: The Salesforce user who initiated the action or the context in which the action ran (e.g., “Automated Process” for system-driven events).
  • Action/Event Type: The type of activity, for example:
    • Tool Execution
    • Connection Test
    • Configuration Change
    • Error
  • Status: The outcome of the activity:
    • Success
    • Failure/Error
    • Warning
  • Details/Summary: A brief summary of the activity. This might include:
    • For Tool Execution: Tool name, key input parameters (non-sensitive).
    • For Connection Test: Connection name.
    • For Error: A brief error message.
  • Related Record (Optional): A link to a related Salesforce record if applicable (e.g., the Lead that triggered a Flow which called an ACP tool).
  • View Details (Action): Often, there’s an option to view more detailed information about a specific log entry, which might open a modal or a separate page.

​
Information Available in Detailed View

When you view the details of an Activity Log entry, you might find more comprehensive information, such as:

  • Full Request Payload: For tool executions, the complete input data sent to the tool (care should be taken with sensitive data logging, which might be configurable).

  • Full Response Payload: The complete response received from the tool.

  • Detailed Error Messages: Stack traces or more verbose error descriptions if an error occurred.

  • Correlation ID: A unique identifier that might link related log entries across different systems or components.

  • Duration: How long the operation took to complete.

    (Placeholder: Screenshot of a modal or detail view for an Activity Log entry)

​
Using the Activity Log for Monitoring and Troubleshooting

  • Monitoring Tool Usage:
    • See which ACP tools are being used most frequently.
    • Understand who or what processes are invoking these tools.
    • Identify patterns of usage.
  • Diagnosing Errors:
    • When a tool execution fails or a connection test is unsuccessful, the Activity Log is often the first place to look for error details.
    • The log can help pinpoint whether the issue was with the input data, the connection itself, the external service, or the ACP tool’s logic.
  • Auditing Changes:
    • Track configuration changes made within the ACP system (if logged).
  • Performance Analysis:
    • If execution times are logged, identify slow-performing tool calls.

​
Filtering and Searching the Activity Log

Most Activity Log implementations offer ways to filter and search entries to help you find specific information quickly:

  • Date Range: Filter entries by a specific time period.
  • User: Filter by the user who initiated the action.
  • Action/Event Type: Show only tool executions, errors, etc.
  • Status: Filter by success or failure.
  • Search Text: Search for keywords within the log details (e.g., a specific tool name, connection name, or error message).

​
Log Retention and Configuration

  • Log Retention Policy: Be aware of how long Activity Log data is stored. Older data might be archived or deleted based on system settings. This is often configurable.
  • Logging Levels: The ACP system might have configurable logging levels (e.g., DEBUG, INFO, WARN, ERROR). A more verbose logging level will capture more detailed information but can also consume more storage and potentially impact performance slightly. Adjust this based on your monitoring and troubleshooting needs. These settings might be found in the “Settings” tab of the ACP Manager.

The Activity Log is a powerful resource for maintaining the health and efficiency of your ACP integrations. Regularly reviewing it, especially when troubleshooting or monitoring new deployments, can provide critical insights.