{"componentChunkName":"component---src-templates-markdown-template-jsx","path":"/guides/oversight/observability/guide/","result":{"data":{"pageMetadata":{"title":"Observability User Guide","path":"/guides/oversight/observability/guide/","sourceCode":null,"metadataParent":{"title":"Observability","path":"/guides/oversight/observability/","sourceCode":null,"hasVersionPicker":null,"metadataChildren":[{"title":"Observability Overview","path":"/guides/oversight/observability/overview/","order":1,"label":null},{"title":"Observability User Guide","path":"/guides/oversight/observability/guide/","order":2,"label":null},{"title":"Observability Troubleshooting Examples","path":"/guides/oversight/observability/trouble-shooting-examples/","order":3,"label":null},{"title":"Observability Span Glossary","path":"/guides/oversight/observability/span-glossary/","order":4,"label":null}],"metadataParent":{"title":"Oversight","path":"/guides/oversight/","metadataChildren":[{"title":"System Alerts","path":"/guides/oversight/system-alerts/","order":1,"label":null},{"title":"Observability","path":"/guides/oversight/observability/","order":2,"label":null},{"title":"Privacy","path":"/guides/oversight/privacy/","order":3,"label":null}],"metadataParent":{"title":"Guides","path":"/guides/","metadataChildren":[{"title":"Platform Overview","path":"/guides/platform-overview/","order":0.5,"label":null},{"title":"Getting Started","path":"/guides/getting-started/","order":1,"label":null},{"title":"mParticle Agent","path":"/guides/mparticle-agent/","order":1.5,"label":null},{"title":"Oversight","path":"/guides/oversight/","order":2,"label":null},{"title":"Data Platform","path":"/guides/data-platform/","order":3,"label":null},{"title":"Data Warehouse","path":"/guides/data-warehouse/","order":4,"label":null},{"title":"Customer 360","path":"/guides/customer-360/","order":5,"label":null},{"title":"Analytics","path":"/guides/analytics/","order":6,"label":null},{"title":"Audiences","path":"/guides/audiences/","order":7,"label":null},{"title":"Settings","path":"/guides/settings/","order":8,"label":null},{"title":"Troubleshooting mParticle","path":"/guides/troubleshooting/","order":10,"label":null},{"title":"Default Service Limits","path":"/guides/default-service-limits/","order":11,"label":null},{"title":"Glossary","path":"/guides/glossary/","order":12,"label":null}],"metadataParent":null}}}},"markdownRemark":{"html":"

The Trace Activity page in the Observability tool is where you can:

\n\n

To learn more about the information that traces that provide, see trace details.

\n\n\n

To navigate to Observability:

\n
    \n
  1. Log in to your mParticle account.
    2. \n
  2. From the overview map, select Observability within the Oversight suite or go to Oversight > Observability > Trace Activity using the left hand nav.
    3. \n
  3. This brings you to the Trace Activity page.
    4. \n
\n

\n

You can also jump directly to Observability by clicking the Search icon in the left nav bar (or entering Cmd+K on MacOS or Ctrl+K on Windows) and searching for “Observability”.

\n

\n \n \n \n \n \n \n \n View all trace activity

\n

The Trace Activity page displays a list of all recent traces for your development data, and any traces you have configured for your production data. All traces are available for up to 14 days.

\n\n

To view the details for a specific trace, click the purple ID under the Trace ID column.

\n

\n \n \n \n \n \n \n \n Trace status

\n

You can access a trace from Observability as soon as mParticle begins receiving and processing data, but it’s important to note that a trace can’t provide complete information about a data flow until all data in the trace has been fully processed. This typically occurs within 30 minutes.

\n

Traces that are ready to be used for troubleshooting will display a “Complete” Trace Status on the Trace Details Page. Traces for data flows that are still being processed have a Trace Status of “In Progress”.

\n

\n \n \n \n \n \n \n \n Sort and filter trace activity

\n

You can filter your results by time frame by clicking the button labeled “Last hour” and selecting one of the predefined date ranges or entering a custom range.

\n

\n

To further sort and filter your results, click Sort and Filters to view the following options:

\n

\n \n \n \n \n \n \n \n Sort traces

\n

Use the Order dropdown menu to sort your traces from most recent to oldest, or oldest to most recent.

\n

\n \n \n \n \n \n \n \n Filter traces

\n

Under Filters, select any of the following criteria to limit the traces displayed:

\n\n\n

After selecting your desired sorting and filter options, click Apply. This refreshes the Trace Activity page to display only filters matching your selected criteria.

\n

\n \n \n \n \n \n \n \n Customize trace activity page

\n

You can configure the columns that are displayed on the trace activity page by clicking the View Columns button.

\n

\"screenshot

\n

To remove a column from the trace activity page, click the toggle switch. Some columns, like “Trace ID”, cannot be removed.

\n

To change the order of the columns, click and drag the handle next to the column name.

\n

\"screenshot

\n

\n \n \n \n \n \n \n \n Trace details

\n

After opening the details page for a specific trace, you will see the following information:

\n

\n \n \n \n \n \n \n \n Trace summary

\n

\n\n

\n \n \n \n \n \n \n \n Setup details

\n

\n\n

\n \n \n \n \n \n \n \n Trace result

\n

For each trace, you will see either Success, Insight, Needs Attention, or Warning displayed under “Result” along with any applicable messages under “Additional information”. You can use this information to determine whether an issue encountered during the trace was intentional or accidental, and what steps you may need to take to resolve any issues.

\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
MessageDescription
SuccessYour data was ingested, processed, and forwarded without encountering any issues.
InsightYour data flow was interrupted due to a configuration setting (such as a Rule or Filter). These interruptions may or may not be intentional, depending on your configuration and desired behavior. Referring to any insights can be helpful in identifying unintended consequences of a configuration setting.
WarningIndicates that an issue was encountered during data processing that could be resolved with a retry.
Needs AttentionAn error was encountered during the trace that cannot be resolved with a retry.
\n

In some cases, you might see additional information with instructions to contact mParticle Support or your mParticle Account Representative, who can help you determine the root cause of an error or issue.

\n

\n \n \n \n \n \n \n \n Related traces

\n

It’s possible for one process to trigger other related processes in the mParticle platform. Any related processes that are traced will be listed here.

\n

For example, when mParticle ingests a batch of event data or a request to make a bulk update to your data, each subsequent data flow will have its own unique trace, which you can find and access here.

\n

\n \n \n \n \n \n \n \n Timeline view

\n

\n

The Timeline View provides a visual picture of how your data flows through the mParticle platform, broken into different spans, with each span representing a different stage of data processing.

\n

Hover your cursor over the span in the timeline to see its exact start and end times.

\n

To view details for a specific span, click on the span within the timeline and review the information panel at the bottom of the UI.

\n

Not all spans will be presented sequentially, and some will appear to occur at the same time.

\n

This is because mParticle executes different processes in parallel to reduce the amount of time it takes to process your data. Most gaps between spans on your timeline are likely due to networking delays or internal processes that are not represented on the trace timeline.

\n

\n \n \n \n \n \n \n \n Span details

\n

\n

The Span Details view provides more granular information about a particular span. The details shown will vary depending on the span category.

\n

To learn more about each span category, view the Span Glossary.

\n

\n \n \n \n \n \n \n \n About trace IDs

\n

Each individual trace is uniquely identified by a 36 character Trace ID resembling 66e0c0cd9bb8998a579595e42bae7077.

\n

Trace IDs are essential for pinpointing specific data processing traces. You can find them in two primary ways:

\n

\n \n \n \n \n \n \n \n 1) Find a trace ID in an API response

\n

Trace IDs are included with all responses to calls to the Events and IDSync APIs.

\n

To find a trace ID in an API response:

\n
    \n
  1. Search your API response for the header titled X-MP-Trace-Id. The value of this header is the trace ID for the corresponding API call.
    2. \n
\n

\n

\n \n \n \n \n \n \n \n 2) Find a trace ID in Live Stream

\n
    \n
  1. Log into your mParticle account and navigate to Activity > Live Stream.
    2. \n
  2. Select any event row.
    3. \n
  3. In the right hand sidebar, you will find the trace ID associated with that event.
    4. \n
\n

\n \n \n \n \n \n \n \n Search for a trace using a trace ID

\n

To search for a specific trace on the Trace Activity page:

\n
    \n
  1. Find and copy the trace ID from an API response or Live Stream as described in About trace IDs.
    2. \n
  2. Log into your mParticle account and navigate to Oversight > Observability > Trace Activity.
    3. \n
  3. From the Trace Activity page, enter your trace ID in the search bar and click Search.
    4. \n
\n

\n

\n \n \n \n \n \n \n \n Open a trace from Live Stream

\n

You can also view trace details for a data flow directly from the mParticle Live Stream.

\n
    \n
  1. Log into your mParticle account and navigate to Data Platform > Live Stream.
    2. \n
  2. Select the event row you want to view the trace for.
    3. \n
  3. In the right hand sidebar, you will find the trace ID associated with that event.
    4. \n
  4. Click on the Trace ID to open up the Trace Details page in the Observability suite.
    5. \n
\n

\n

\n \n \n \n \n \n \n \n Trace configurations

\n

To view your trace configurations, navigate to Oversight > Observability > Trace Configurations in the left hand navigation.

\n

You define what data you want to trace using a trace configuration. A trace configuration initiates an individual trace with a unique trace ID for each request to the Events or Identity API according to the trace configuration settings you specify.

\n

The trace configurations page displays a list of all configurations, sorted from newest to oldest. You can see the start and end date and times for each configuration, the trace configuration ID, the percentage of data that will be traced, and one of the following trace configuration statuses:

\n\n

\"screenshot

\n

\n \n \n \n \n \n \n \n Create a trace configuration

\n

To create a new trace configuration:

\n
    \n
  1. \n

    Navigate to Oversight > Observability > Trace Configurations, and click Create Trace Configuration.

    \n

    \n

    This opens the Add Tracing Configuration window:

    \n

    \n
    2. \n
  2. \n

    Under Inputs, select the connected data input you want to trace.

    \n\n
    3. \n
  3. \n

    Use the date and time picker to select the Start Date & Time and Duration for your trace. Traces will only be generated after the start time and for the duration you specify.

    \n\n
    4. \n
  4. \n

    Select the percentage of your data you would like to be traced using the Sample Size drop down menu. You can select either 1%, 3%, or 5% for small sample sizes, or you can select 10% through 100% in increments of 10 for larger sample sizes.

    \n\n
    5. \n
  5. Use the date and time picker to select the Start Time (UTC) and Duration for your trace. Traces will only be generated after the start time and for the duration you specify.
    6. \n
  6. Click Submit.
    7. \n
\n\n

After clicking Submit, you will see your new tracing configuration listed on the Trace Configurations page.

\n","frontmatter":{"title":"Observability User Guide","order":2,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/oversight/observability/guide/"}},"staticQueryHashes":["2950460867"]}