Stay organized with collections
Save and categorize content based on your preferences.
By default, the Trace Explorer page only searches your selected
project for trace data. When a trace has data stored in multiple projects,
as might occur when an application in one project makes a call into
an application hosted by another project, you need to perform
the following steps to view all spans in the trace:
Create a trace scope that
lists the Google Cloud projects that store the spans in a trace.
For information about trace scopes, see
Create and manage trace scopes.
Your Identity and Access Management (IAM) roles on the projects listed in the
trace scope and the
time-range setting determine what data is displayed. The trace scope
only specifies which resources are searched.
When the Trace Explorer page opens, it searches the
resources listed in the default trace scope,
provided that scope is accessible. When that scope isn't accessible,
your Google Cloud project is searched. You can set which
trace scope is the default trace scope.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-17 UTC."],[],[],null,[]]
