The AppMap extension for your editor automatically displays AppMap files as beautiful diagrams you can interact with.
Use the navigation bar for quick navigation to items of interest, for example, HTTP routes, labels, packages, classes, functions.
The Dependency Map diagram shows all the code that’s relevant to what you’re working on and how it’s connected. Here you can search and navigate through web services, code, libraries, dependency services, and SQL, all in the context of a specific feature.
The dependency map is fully interactive. You can:
The Sequence Diagram view shows an application’s behavior in a linear chronological layout. Function calls are shown as horizontal arrows, ordered from top to bottom as they occurred at runtime. The elements in the sequence diagram are interactive and can be selected, collapsed, and hidden.
Sequence diagrams can also be exported as SVG files for easy sharing and collaboration. Similar AppMaps can also be compared in a sequence diagram “diff” to reveal changes in runtime behavior caused by a code update.
For more information, see the Sequence Diagram reference.
Flame Graphs visualize the performance of your application’s code, and show how long each function call or database query takes to execute. Flame Graphs make it easy to reveal and investigate performance and latency issues in your code.
For more information, see the Flame Graph reference.
The Trace diagram shows all the details of how a feature works. Here you can navigate forward, backward, up, and down through a detailed execution trace. See the call tree starting with web service endpoints going through function calls all the way to SQL operations. At any point, you can move quickly back and forth between the Trace view and your source code.
The Trace is fully interactive. You can:
This video demonstrates how to use AppMap Diagrams when learning how unfamiliar code works:
The AppMap extension for your editor displays SQL commands in AppMap Diagrams so you can understand how your application logic interacts with the database. You can quickly discover SQL inefficiencies and anti-patterns that pose hidden scalability and reliability risks even if your application seems to be working well.
With the AppMap extension, not only are trips to database logs no longer required to see the SQL commands, but the SQL commands are also directly linked to the code that initiates their execution, helping developers understand the direct impacts of their code updates on database operations and performance.
When you open an AppMap, the navigation bar lists all captured SQL commands. This is a great starting point for your SQL investigation:
Use the search box in the Navigation bar to select for a specific subset of SQL Commands:
When you click on a dependency link in the Dependency Map, the navigation bar will list events specific to that relationship.
When investigating how efficiently the application code or the ORM utilizes the database, it’s helpful to see whether multiple SQL commands are clustered together and whether they form any specific (anti-)patterns. The Trace view is a great visual tool for spotting clusters and repetitions of SQL commands enveloped by code that are difficult to discover using database logs or other simple tools.
SELECTs fetching single records using a specific ID
In this video example, you can learn how to optimize Django ORM by seeing how it makes SQL queries under the hood. The video explains the role of ORM in modern applications, SQL efficiency challenges, and how to use AppMap for uncovering and fixing the infamous N+1 anti-pattern