Troubleshoot a trace connection

Identify why a trace connection is not collecting data by reviewing its execution log and error messages.

Before you begin

Role required: sn_ai_governance.ai_steward

About this task

Each trace connection record shows an execution log with the result of every collection attempt. When a connection shows an Error execution status, you can select the connection to view the log and read the error message.

Procedure

1. Navigate to All > AI Control Tower > Home > Settings > Integrations > Traces.
2. Select the Established sub-tab.

   Each connection card shows its State and Processing state. A Processing state of Error indicates that the last collection attempt did not complete successfully.

3. Select the connection you want to investigate.
4. In the Execution logs section, review the log entries.

   Each log entry shows the following information.

   Table 1. Execution log fields

   Field	Description
   Start time	Date and time the collection attempt began.
   End time	Date and time the collection attempt ended.
   Traces collected	Number of traces collected during the attempt.
   Execution status	Result of the collection attempt. A status of Success means traces were collected. A status of Error means the attempt failed.
   Error message	Details about a failed collection attempt. Review this message to identify the cause of the error.

Result

You have reviewed the execution log and identified the cause of the collection error. Common causes include invalid or expired credentials, an inactive or unvalidated MID Server, and incorrect region or resource ID values.

What to do next

To update the connection configuration, see Edit a trace connection.