ETL Stages - Revision history

Sam: /* Simple Exploitation Walk Through */

2023-05-25T10:16:08Z

Simple Exploitation Walk Through

2023-05-25T10:14:16Z

Simple Exploitation Walk Through

2023-05-25T10:13:46Z

Simple Exploitation Walk Through

2022-07-25T17:53:11Z

ETLs and Their Stages

2022-07-13T12:20:25Z

Stages and Status Monitoring

2022-07-13T12:20:04Z

Simple Exploitation Walk Through

2022-06-03T13:17:01Z

ETLs and Their Stages

2022-05-25T14:55:07Z

Linear

2022-05-25T14:53:46Z

Note: Stage Value Behavior

2022-05-25T14:53:20Z

Semi-Chaotic

@@ Line 24: / Line 24: @@
 # Retrieve the contents of the file referenced in the message
 # Report status to the Load Status Monitor ([[Les]])
-# Exploit those contents to produce more files, or entities, or messages, etc.
+# Exploit those contents to produce more files, or [[Entity Types|entities]], or [[Message Types|chat messages]], etc.
 # Files produced by one ETL can be sent to another
 When all ETLs have finished, the load is complete.

@@ Line 19: / Line 19: @@
 # Puts meta data into the database
 # Identifies the file's contents
-# Based on the [[File Types Supported|file's type]], the file is routed to the ETL process by putting a message into that ETL's [[Message Bus Messages | message queue]].
+# Based on the [[File Types Supported|file's type]], the file is routed to the exploitation process by putting a message into that ETL's [[Message Bus Messages | message queue]].
 The ETL process will:
 # Wait until a message arrives for it to process

@@ Line 16: / Line 16: @@
 The first stage is [[Load]]. It performs the following tasks:
 # Navigate the source media (disk image, folder or file)
-# Puts contents into [[Depot|depot]] files
+# Puts file contents into [[Depot|depot]] files
 # Puts meta data into the database
 # Identifies the file's contents

@@ Line 238: / Line 238: @@
 |-
 | Maintenance
-| <code>[[Maintenance|Maintenance.exe]]</code>
+| <code>[[Maintenance ETL|Maintenance.exe]]</code>
 | style="text-align:center;" | 255
 | style="text-align:center;" | 100%

@@ Line 36: / Line 36: @@
 This is ignored in the Chaos region, becomes relevant in the Semi-Chaotic region and becomes law in the Linear.
-It is the job of the Load Status Monitor (Les) to watch all of the ETLs and advance the media through the stages of exploitation.
+It is the job of the Load Status Monitor ([[Les]]) to watch all of the ETLs and advance the media through the stages of exploitation.
 ==Chaos==

@@ Line 216: / Line 216: @@
 | <code>[[Finished|Finished.exe]]</code>
 | style="text-align:center;" | 240
-| style="text-align:center;" | 94-100%
+| style="text-align:center;" | [[Media Load Percentage|94-100%]]
 | finished
 |-
@@ Line 471: / Line 471: @@
 | <code>[[Finished|Finished.exe]]</code>
 | style="text-align:center;" | 240
-| style="text-align:center;" | 94-100%
+| style="text-align:center;" | [[Media Load Percentage|94-100%]]
 | finished
 |-

@@ Line 89: / Line 89: @@
 ETLs in this stage execute one after another.
 For example, Alerts (stage 128) is executed before Reports (stage 160) because any alerts that were generated need to be included in reports.
 While earlier stages were mainly concerned with producing files and artifacts, Linear and later stages are concerned with Media processing.

@@ Line 82: / Line 82: @@
 [[Stitch|Stitching]] (fragmented file carving) is another semi-chaotic ETL.
 [[Poly]] is stage 32 while Stitch is stage 40.
-This means that [[Stitch]] will not start until Poly is completely finished.
+This means that [[Stitch]] will not start until [[Poly]] is completely finished.
 If [[Stitch]] was stage 32, it would be told to execute at the same time as [[Poly]] and miss any data produced by poly file expansion.

@@ Line 80: / Line 80: @@
 ===Note: Stage Value Behavior===
-Stitching (fragmented file carving) is another semi-chaotic ETL.
+[[Stitch|Stitching]] (fragmented file carving) is another semi-chaotic ETL.
-Poly is stage 32 while Stitch is stage 40.
+[[Poly]] is stage 32 while Stitch is stage 40.
-This means that Stitch will not start until Poly is completely finished.
+This means that [[Stitch]] will not start until Poly is completely finished.
-If Stitch was stage 32, it would be told to execute at the same time as Poly and miss any data produced by poly file expansion.
+If [[Stitch]] was stage 32, it would be told to execute at the same time as [[Poly]] and miss any data produced by poly file expansion.
 ==Linear==