Trace is Potpie’s incident investigation agent. It uses your knowledge graph as the structural model of expected system behavior and investigates failures against that model. When a failure surfaces, Trace uses the encoded structure of your codebase to define the investigative scope immediately, rather than reconstructing it through manual exploration.Documentation Index
Fetch the complete documentation index at: https://docs.potpie.ai/llms.txt
Use this file to discover all available pages before exploring further.
What Trace does
| Call graph traversal | The call graph is traversed from the affected service outward. Every upstream caller and downstream dependency is mapped before a single log is read. |
| Contract validation | Logged requests are validated against API and schema contracts defined in code. A changed response shape or a silently diverged API surfaces as a contract violation with the affected path. |
| Historical baseline | The current repository state is compared with earlier states to identify structural changes and dependency regressions from the last stable version. |
| Log analysis | Provide a log snippet or file. Trace cross-references it against the knowledge graph and constrains the relevant entries to the call paths and services already in scope. |
contract compliance, dependency health, scaling policies, and recent diffs in a single view. Deviations surface as contract violations, dependency regressions, or invalid execution paths, expressed in terms of impact and causality. Teams move directly from detection to remediation.