Agent Platform Tracing

Set Up Agent Platform Tracing

To generate Data 360 reports for Session and Platform Traces, users must first enable Data 360 and Platform Tracing.

1. In Setup, use the Quick Find Box to search for Einstein Generative AI.
2. From Einstein Generative AI, click Einstein Audit, Analytics, and Monitoring Setup.
3. Confirm that Agentforce Session Tracing is turned on. See Set Up Agentforce Session Tracing.
4. Scroll to the Agent Platform Tracing toggle and turn it on.

Your data model is provisioned in just a few minutes. Data collection then starts immediately and recurs at five-minute intervals. Note that turning data collection increases your org’s credit consumption rate.

Suspending data collection keeps your data so that you can resume later. Any reports show a gap between the time you turn it off and turn it back on.

Data 360 Reports for Service Rep Sessions and Platform Traces

To gain insights into KPIs and trends, create a single Data 360 report that integrates both Agent Session traces and End-to-End Platform traces. This report can be run for near real-time data, allows for grouping, filtering, and summarizing records, and can be shared with others.

Agent Tracing includes spans from the following services:

• Apex
• Flows
• Prompt Builder
• Invocable Actions
• Planner
• AI Gateway
• LLM Gateway
• DC Query Federator

Generate a Data 360 Report

Create reports on specific Data Model Objects (DMOs), such as Telemetry Trace Span and AI Agent Interaction, to analyze and learn from unified data.

1. Navigate to the Reports tab in Salesforce and click New Report. The Report Types page is displayed.
2. In the search bar, type the name of the Data Model Object (DMO) you want to report on. In this case, you would select Telemetry Trace Span or AI Agent Interaction.
3. Create a new field relationship within the relevant data model objects. In this instance, you could select Telemetry Trace Span -Telemetry Trace → ManyToOne → AI Agent Interaction - Telemetry Trace.

   In Data 360, relationships between DMOs are established by defining a connection from a "Source DMO" to a "Target DMO" using key fields. The most frequent type of relationship is Many-to-One, where multiple records from the Source DMO correspond to a single record in the Target DMO. Refer to Data Model Object Relationships for more information.

4. Within the DMO's detail page, there is a Relationships tab. This tab provides a visual and structured view of all the relationships that exist for this DMO. Verify the new DMO relationships through the Relationships tab.

   Telemetry Trace Span Example

   AI Agent Interaction Example

5. Create a custom report type.
6. Click New Custom Report in Setup underneath New Custom Report. Fill out the fields to create a new custom report type. In this case, you would create a Session & Platform Traces report type.
7. Go to the Data Cloud App and select the Reports tab.
8. Create a Data 360 Report. Click New Report and select the desired report type (i.e. Session Traces and Platform Traces).
9. Click Start Report.

Once the report is initiated, you should be able to visualize correlated platform telemetry trace spans logged as part of each Agent Session.

Note Data 360 reports display a maximum of 2,000 rows in run mode. You can export up to 50,000 rows. For more information, see Data 360 Reports and Dashboards and Data Cloud Reports and Dashboards: Limits and Limitations.

Data Model for Agent Platform Tracing

Enabling these features automatically generates a Data 360 data stream, a Data Lake Object (DLO), and a Data Model Object (DMO). This data is created within the data space specified in Auditing & Monitoring.

Observability Spans Data Stream

The Observability Spans Data Stream is automatically created to capture the trace data:

Observability Spans Data Lake Object

A new DLO called ObservabilitySpans is created with the following fields: