Once MLP completes the log processing operation, logs are delivered to the customer’s respective OSP (osp_origin) account.
The logs are placed in the customer’s OSP account under the /logs directory. Subdirectories are created that follow a date/primary alias naming convention of:
Note: Only primary aliases are used for naming purposes (directory, file name). Data from other aliases will be included in the same directory/file.
The log file uploaded to the customer’s OSP account follows a primary alias/date naming convention of:<primary alias>_<year><month><day><hour><minute><second><CosID>.log[.gz]
Note: The log file name represents the time the file was created by the MLP, it does not represent the time the log entries were created. Typically, the log timestamps will be several minutes earlier than the timestamp in the file name.
Log files are compressed by MLP using GNU Zipped Archive (.gz) compression when sending to a customer’s OSP account, and log files can be retrieved in the customer’s OSP account and managed through a variety of means. For further information, please see Origin Storage Service Information.
Please note that OSP Storage consumed by log data will be billed as part of the customer’s OSP usage at their contracted storage usage rate. The customer is responsible for purging log data from OSP when it is no longer required, otherwise they will continue to be charged for all logs’ data stored, on a monthly basis.
Lumen can also deliver CDN Log Files to our customer’s Amazon Simple Storage Services (Amazon S3) endpoint. Click here to learn more.