agile-metric-dependency-tracing

Metric field dependencies are traced across IDEASRapidIQ, NitroPF, DORA, and NitroUMDP CUUD by mapping field lineage through external data sources. The process identifies every contributing field, classifies sources as internal or external, and outputs an ExternalRawFieldList.

Data lineage tracing for Agile metrics maps how fields flow from external sources through intermediate repos to a final metric. You need it when you must audit which raw fields drive a specific metric value across a multi-repo pipeline.

Yes, an SVG dependency diagram is generated to visualize metric dependencies and data flow. This diagram illustrates the traced lineage across IDEASRapidIQ, NitroPF, DORA, and NitroUMDP CUUD, showing how fields connect through the pipeline.

Yes, the dependency tracing enforces multi-repo lineage rules and explicitly handles nested properties and intermediate variables. This ensures that complex field mappings within IDEASRapidIQ, NitroPF, DORA, and NitroUMDP CUUD are accurately resolved.

External raw fields are extracted by tracing a given metric upstream through the pipeline until external data sources are reached. The process classifies these sources as external and compiles them into an ExternalRawFieldList for reference.

The best way to map upstream field lineage is to trace the metric through IDEASRapidIQ, NitroPF, DORA, and NitroUMDP CUUD sequentially. This identifies every contributing field and classifies whether the source is internal or external to the pipeline.