Understand MSL 4 billing model
When you use Media Services Live, you pay a fee corresponding to your usage and can choose ingest bytes or ingest minutes as the billing unit for your contract.
MSL 4 provides a flexible pricing model that consists of:
Included usage - Akamai provides you the number of included ingest minutes or bytes.
Overage - If your usage exceeds the included minutes, then your bill will include an overage fee that is calculated by multiplying the price per ingest per minute by the overage.
Ingest minutes billing or ingest bytes billing
Ingest minutes billing
In the ingest minutes billing model, your usage is tracked per month based on the active minutes per unique stream ID and the event name. You will be billed based on the number of active minutes you publish a specific content into Akamai. The specific content is unique to you and is identified based on your publishing URL. Granularity for billing is a minute - if a source is active in the path for at least 1 second in the last 60 second interval then it is counted as 1 full minute.
For example, let's assume you have purchased MSL 4 and Akamai included 1000 ingest minutes for signing up for the product. If your account ingests 10,000 minutes of streaming content for the month, your bill would be calculated as follows:
10,000 input minutes - 1,000 included input minutes = 9,000 minutes of overage.
The exception to this rule is DVR. DVR is turned on by default, and is charged based on NetStorage usage. Akamai does not charge for DVR as part of MSL.
Ingest bytes billing
If you choose ingest bytes billing, your invoice will be generated based on the number of active bytes you publish a specific content into Akamai.
Billing log collection criteria
You will be billed based on the amount of content published to your account, identified based on the publishing URL.
Only rlines (request log lines) with 2xx responses will be considered for billing. Ingest HTTP access logs are used for billing and reporting. Successful r lines or request lines are used to process the billing. r lines' success is indicated by a successful HTTP POST 200 response to the encoder by the ingest server.
Only bytes coming into Akamai will be billed. Response bytes will not be billed.
All incoming bytes in a 2xx request will be billed, irrespective of the media object type such as Audio, Video, or Subtitle, master playlist, bitrate playlist or any other metadata objects such as JSON, XML, or JPEG posted to the ingest server.
Primary and backup
streamIDswill continue to be treated as separate inputs and hence the bytes for primary and backup for billing.
Updated over 1 year ago