Investigate code
Find specific objects, inspect them, trace their relationships, and track what changed between analyses
Overview
This section is about drilling into the detail of your application: locating the specific objects, transactions, or nodes you care about, inspecting them, following the relationships between them, and understanding how they have changed over successive analyses. Pick the task that matches what you need to do.
Find what you’re looking for
- Search for an object - find objects across the whole application, within the current view, or inside a transaction or saved view.
- Explore a transaction - select a transaction or data call graph and navigate it end to end.
Inspect an object
- View source code - read an object’s source code in the viewer.
- Inspect object properties - review an object’s characteristics, associations, and metadata.
- Explore links - show, hide, and inspect the links between objects.
Trace relationships
- Trace a path - find the paths between two objects with the Path Finder.
- Callers and callees - see what calls an object and what it calls.
- Highlight dependencies - add an object’s direct and indirect dependencies to the view.
- Find start and end points - identify the entry and exit points of a transaction.
Track change
- Compare versions - compare two analyses to see what was added, deleted, or modified.
- Track history - review the history of an object or link across analyses.
The Compare and history features require at least two analyses (or result imports) of the application.