elastic / apm-aws-lambda
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 10 components.
  • 55 files, 3,510 LOC (98.2% vs. main code).
  • "testing" is biggest, containing 23.42% of LOC.
  • "version" is smallest, containing 0.14% of LOC.


testing822 LOC (22%) 20 files
logsapi652 LOC (18%) 9 files
apmproxy598 LOC (16%) 5 files
app446 LOC (12%) 4 files
accumulator362 LOC (10%) 4 files
ROOT204 LOC (5%) 3 files
e2e-testing195 LOC (5%) 5 files
extension167 LOC (4%) 2 files
logger59 LOC (1%) 2 files
version5 LOC (<1%) 1 file
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
ROOT32 commits (9%)
app20 commits (6%)
apmproxy18 commits (5%)
logsapi15 commits (4%)
testing12 commits (3%)
accumulator11 commits (3%)
e2e-testing5 commits (1%)
extension4 commits (1%)
logger2 commits (<1%)
version1 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
testing
21
7
17
logsapi
1
11
4
28
app
8
5
19
ROOT
2
5
13
16
apmproxy
6
9
24
accumulator
5
6
7
e2e-testing
1
2
6
logger
2
2
extension
1
1
3
version
1


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...

No temporal dependencies found.


2025-05-13 19:56