• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

• There are 37 files with 5,462 lines of code.
• 1 very long files (1,279 lines of code)
• 0 long files (0 lines of code)
• 9 medium size files (2,893 lines of codeclsfd_ftr_w_mp_ins)
• 4 small files (548 lines of code)
• 23 very small files (742 lines of code)

There are 20 files with lines longer than 120 characters. In total, there are 96 long lines.

File	# lines	# units	# long lines
app.py in load_tests/create_testing_resources/kinesis_s3_firehose	75	1	18
run-integ.ps1 in integ	489	-	12
build_windows_image.ps1 in scripts	139	-	9
build_windows_fluent_bit.ps1 in scripts	243	-	8
fluent_bit_init_process.go in init	282	15	6
fluent-bit.yaml in use_cases/k8s-metadata-customize-cw	354	-	5
fluent-bit.yaml in use_cases/k8s-metadata-customize-tag	361	-	5
manage_test_resources.ps1 in integ/resources	103	-	4
resource_resolver.py in load_tests/create_testing_resources/kinesis_s3_firehose	26	7	4
entrypoint.ps1 in scripts	46	-	4
fluent-bit.yaml in troubleshooting/tools/color-logger	343	-	4
validate-and-clean.go in integ/s3	191	7	3
cloudwatch.yaml in load_tests/daemonset	236	-	3
publish_windows_images.ps1 in scripts	341	-	3
MultithreadApp.java in troubleshooting/tools/log4j-tcp-app/src/main/java/com/mycompany/app	77	4	2
acutest.h in troubleshooting/resources/vscode/scripts	1279	5	2
log_generator.c in load_tests/logger/stdout_logger	48	3	1
validation_bar.py in load_tests	14	1	1
App.java in troubleshooting/tools/log4j-tcp-app/src/main/java/com/mycompany/app	86	3	1
log4j2.xml in troubleshooting/tools/log4j-tcp-app/src/main/resources	23	-	1