recon_gen.apps.l2_flow_tracing.app

L2 Flow Tracing — exercise every L2 primitive on a runtime dashboard.

M.3.4 ships the skeleton: 4 sheets (Getting Started + Rails + Chains + L2 Exceptions), description-driven prose on Getting Started, placeholder prose on the other three. M.3.5+ populates each tab with its real visuals + datasets.

The app is L2-instance-fed via the same M.2d.3 prefix pattern the L1 dashboard uses: cfg.db_table_prefix is set on the cfg yaml directly (no auto-derivation needed), so dashboard ID, analysis ID, dataset IDs, and tag-based cleanup all key off the per-deploy prefix.

Build pipeline:

build_l2_flow_tracing_app(cfg, *, l2_instance=None) -> App

Default L2 instance is the persona-neutral spec_example.yaml (M.3.2 repointed away from sasquatch_ar so production library code carries no implicit Sasquatch flavor); callers MAY override (tests, alternative-persona deployments) via the kwarg.

Substep landmarks (each tab gets its own substep):

  • M.3.4 — package skeleton + Analysis + Dashboard + 4 placeholder sheets (this commit)

  • M.3.5 — Rails tab — per-Rail row table with declared + runtime columns

  • M.3.6 — Chains tab — Sankey + parent-firing-count edges

  • M.3.7 — L2 Exceptions tab — 6 KPI + drill sections

  • M.3.8 — Auto metadata-driven filter dropdowns

Functions

build_analysis(cfg, *[, l2_instance])

Build the complete L2 Flow Tracing Analysis resource via the tree.

build_l2_flow_tracing_app(cfg, *[, l2_instance])

Construct the L2 Flow Tracing App as a tree.

build_l2_flow_tracing_dashboard(cfg, *[, ...])

Build the L2 Flow Tracing Dashboard resource via the tree.
recon_gen.apps.l2_flow_tracing.app.build_analysis(cfg, *, l2_instance=None)[source]

Build the complete L2 Flow Tracing Analysis resource via the tree.

Parameters:
recon_gen.apps.l2_flow_tracing.app.build_l2_flow_tracing_app(cfg, *, l2_instance=None)[source]

Construct the L2 Flow Tracing App as a tree.

M.3.4: registers Analysis + Dashboard + 4 placeholder sheets (Getting Started + Rails + Chains + L2 Exceptions). No datasets, no visuals beyond the description prose. M.3.5+ populates each placeholder one substep at a time.

Dashboard ID convention: <deployment_name>-l2-flow-tracing — the per-deploy prefix the L1 dashboard also uses, so N apps can deploy against the same L2 instance AND the same app can deploy against N L2 instances without QS resource collisions. cfg.deployment_name is set on the cfg yaml directly, no auto-derivation from the L2 yaml.

Return type:

App

Parameters:
recon_gen.apps.l2_flow_tracing.app.build_l2_flow_tracing_dashboard(cfg, *, l2_instance=None)[source]

Build the L2 Flow Tracing Dashboard resource via the tree.

Parameters: