| Description | Procedure Archive ingester |
|---|---|
| Docstring | Ingest Procedure Archive zipfiles. Documented in [MOF MON] "MTG GS MOD_MME Monitoring ICD", EUM/MTG/ICD/12/0724 Sections 5.9 File format description 5.9.3 File name convention for holding zipfile (although supplied test data does not follow it) For this algorithm we perform a full scan of the .zip file and ingest all likely contents. From the low level files, types are: L1 (Step Event): Domain, Counter, Timestamp, Attribute, Value, Step Identifier L2 (Step List Event): Domain, Counter, Timestamp, State Value, Step List Identifier L3 (Thread Event): Domain, Counter, Timestamp, Attribute, Value, Thread Identifier L4 (Argument): Domain, Counter, Timestamp, Attribute, Value L5 (Variable Event): Domain, Counter, Timestamp, Attribute, Value Sample zipfile name: APEX_history.zip Sample internal name: APEX_history/ProcArchive 2018.05.02 00-00/P7659_7139.txt Sample line (new format, utf-8 encoding): <H>MTI1:¬S=17¬0¬1562934452@174 <L>1¬MTI1:¬12¬1562828931@214¬S=5¬P.1 <L>3¬MTI1:¬20¬1562828931@385¬S=0¬P APEX history consist of 2 types of files: - HLCH files - Procedure Archive (PA) files (what this ingester handles) The ingesters for those 2 types parse the input files, or rather interpret them to extract INSTANCE data and execution LOG data. In the PA files, the ingester extracts occurences of Steps, StepLists and Threads along with their attributes and put them into INSTANCES table, whereas States are stored in the execution log table. Other levels (Argument and Variables), go into execution LOG table. |
| Wiki page | None |
| Activity file | AU_PROCHIST_INGESTER.xml |
| Executable | alg/au_prochist_ingester.py |
| Calling convention | filename |
| Table triggers | None |
| Scheduler triggers |
|
| Output tables | |
| Event raised | None |