azure / jaeger-kusto
Components

An overview of source code logical components.

Intro

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 5 components.
  • 23 files, 1,440 LOC (100.0% vs. main code).
  • "store" is biggest, containing 56.04% of LOC.
  • "ROOT" is smallest, containing 2.57% of LOC.


store807 LOC (56%) 6 files
config256 LOC (17%) 6 files
build222 LOC (15%) 7 files
runner118 LOC (8%) 3 files
ROOT37 LOC (2%) 1 file
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
store63 commits (45%)
ROOT31 commits (22%)
config22 commits (15%)
runner16 commits (11%)
build2 commits (1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024 2023 2022 2021 2020
store
6
8
35
41
9
37
build
6
6
config
2
6
26
ROOT
1
2
23
1
4
runner
28


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report...

G store store store--store 2 build build build--build 1


2025-05-06 22:36