The AppMap framework specifies a simple-to-work-with data format that can be readily visualized in popular OSS libraries such as the D3. This example demonstrates how to programmatically parse an event stream in a recorded AppMap JSON file and how to visualize the dynamic dependencies between classes in a D3 force-directed graph.
Continue reading »Code gallery
See how people in the open source community are using AppMaps to record, analyze, and optimize end-to-end code and data flows.
-
AppMap as a D3 Force-Directed Graph
-
Querying data in AppMaps
This example shows how to import AppMap data into neo4j where it can be queried using the neo4j query language.
Continue reading » -
Auto-generated component diagram
The AppMap framework includes JavaScript code which can automatically render visual depictions of AppMap data. This example shows how AppMap data can be displayed as a C4 component diagram.
Continue reading » -
Diff of a program execution trace
Let’s look at a core capability of the AppMap framework: execution traces. What if we could tell how a specific patch affects the execution before even reading and understanding the change?
Continue reading » -
View SQL dependencies of a class
When you are working on a particular class, you can use this applet to figure out which SQL (and which tables) are used to implement the behavior of that class.
Continue reading » -
AppMap data inspector
This proof of concept analyzes data snapshots captured in an appmap file. It surfaces useful insights about how the data is used, where it’s stored and what it may contain. In short, it shows you how you’re handling various kinds of data within your application.
Continue reading » -
AppMap Auto-configuration
A Ruby script that automatically adds the required dependencies to your Ruby project so you can begin AppMapping right away. Check out an example of using this script with the
Continue reading »appmap-rubyclient andappland-clitool to map and visualize a project from scratch in just a few minutes.