Logs for Assets Created Using an SaaS

The system generates 3 log files when you use the encoding using an SaaS procedure:

•	pub-asset-encoder.log—Captures the completion status of SFAssetGenerator.py.

•	pub-asset-polling.log—Captures the multiple transaction ID’s provided by encoding.com, and associates them with unique keys generated by SFAssetGenerator.py.

•	pub-asset-segmenter.log—Captures the completion status of the SFSegment.py script.

pub-asset-encoder.log Fields: Unique-Key, Date, Time, Publishing-Type, Service Provider,  User-ID, FTP-Source, FTP-Dest,  Video-FileName, Num-Profiles,   Bit-Rates (kbps),  Time-To-Upload, Time-To-Encode,  Completion-Time, Success-Status AX-001, MM/DD/YYYY, HH:MM:SS, Smoothflow/iPhone, encoding.com,  xyga,  username@ip:/in-path, username@ip:/out-path, foo.flv, 2, 500; 1000,  HH:MM:SS, HH:MM:SS, HH:MM:SS,  PASS

pub-asset-polling.log Unique-Key, Date, Time, Num-TxID’s, Tx-ID’s (semi-colon delimited string) AX-001, MM/DD/YYYY, HH:MM:SS, 2, 123432;21300

pub-asset-segmenter.log Fields: Unique-Key, Date, Time, Time-To-Segment, Num-Objects/Chunks,  Origin-Path, Success-Status AX-001,  MM/DD/YYYY, HH:MM:SS, 00:02:40,  2039,  ip:/path, Error (Code:093)