Product Documentation

Limelight

Type of Data

CDN Bandwidth, CDN Usage

Description

  • Limelight portal account URL: http://control.llnw.com/
  • API Usage Metrics Reporting URL: GET /traffic-reporting-API/v2/usage?shortname=cedexis&service=http,https,hls,mss&reportDuration=month&sampleSize=daily
  • API Bandwidth Metrics Reporting URL: GET /traffic-reporting-API/v2/livestats?shortname=cedexis&service=http,https,hls,mss&displayPopData=false&startDate=${unixTime5MinutesAgo}&endDate=${currentUnixTime}
  • API Docs URL: https://control.llnw.com/acontrol/#/helpdoc

Data Feed Format

If there is an error retrieving bandwidth:

  {
    "usage": {
      "unit": "GB",
      "value": "7447.00"
    }
  }

If bandwidth can be retrieved:

  {
    "bandwidth": {
      "unit": "Mbps",
      "value": "272.45"
    }
    "usage": {
      "unit": "GB",
      "value": "7447.00"
    }
  }

Implementation Notes

Usage

  • Shows monthly usage metrics from beginning of month to current day (always based on the current month).
  • By default, http and https reporting metrics are captured. Additional services may be entered in the Fusion Limelight UI installation.
  • Daily sample size allows to get stats aggregated for each day as opposed to each hour in the day which is the default.
  • Basic logic is to iterate the usage metrics for each day reported via Limelight API in Mbps, convert to GB, sum all the days of the month, and return just the total usage for the OM data feed.
  • Usage will always be retrieved, even if bandwidth data retrieval fails.

Bandwidth

  • Shows most recent fully aggregated bandwidth for all configured services at a particular point in time.
  • Usually the value will be about 3 to 4 minutes stale or at the most 5 minutes stale.
  • The most current data points from the live stats endpoint for the current minute, or a few minutes before that may not be completely totaled and maybe inaccurate
  • If bandwidth cannot be retrieve the feed will return a payload with only usage metrics

Reconciliation Steps

How to reconcile Limelight Networks Usage reporting with Fusion OM Data Feeds

  • In the Limelight Networks portal, select Report → Usage.
  • The default view should display the data transferred.
  • This should match Report → Monthly Summary.
  • The default “Monthly Summary Report Filters” view should have rows labeled “Master”. The “Total” in the feed and usage report should match the total “GB Transferred” for all “Master” rows.

How to reconcile Limelight Networks Bandwidth reporting with Fusion OM Data Feeds

  • In the Limelight Networks portal, select Report → Live Stats.
  • Hover over the “Live Stats Aggregate Data” on the far right.
  • Look for the 3-4 minute old data point.
  • The bandwidth data should match the total Mbps for all services.

Why Fusion and Limelight portal metrics might not match

There are 2 main reasons why the usage or bandwidth metrics reporting by Fusion might not exactly match the Limelight Networks portal reporting:

  1. Verify that the services (HTTP, HTTPS, etc.) match with what is entered in Fusion available services. If HTTP and HTTPS are the only 2 services, there is no need to enter additional services in the Fusion Limelight recipe install.
  2. Timing
  • For Usage: The Limelight Networks is real time and so is Fusion. But, there may be a few minutes off between comparing Fusion metrics with Limelight Networks. The best thing to do in order to verify is to grab the metrics reported by Fusion and then immediately run the Limelight Networks Traffic Summary report. Things should match up using this scenario.
  • For Bandwidth: The result should generally closely match the feed data. Look for results within 1-2 minutes of the date and time the feed data was created.

Limelight Networks Portal Traffic Summary (Monthly Usage)

  • The “Usage” report has default filters.

  • Usage value should match the “Data Transfer” total.

  • This value should match the “Master” values in the “Monthly Summary Report”.

Setup in Fusion

You can access Fusion Data Feeds from the left navigation pane, under Openmix. For initial steps please refer to the Fusion Integration Documentation.

When you get to the service-specific configuration dialog box, enter the following:

  • Name: The name given to the data feed. This will default to “Service - Platform Name” if not specified.
  • Run Every: The frequency with which the data feed is updated from the service.
  • Platform: The Platform that is associated with the data feed.
  • API Username: API credentials created in the Limelight Networks portal.
  • PI Shared Key: API credentials created in the Limelight Networks portal.
  • CDN Account Shortname: In the Limelight Networks portal, the Shortname is shown in the left navigation under Select Account.
  • Additional Services (Optional): By default, the Fusion recipe selects http and https Limelight services for metrics reporting. Some customers have traffic under different services which may need to be entered in order for the usage metrics between Fusion and LLNW to match. The additional services valid for traffic reporting (usage) are: hls, mss, hds, flash, dynamicorigin, windowsmedia, redirector, quicktime, flash, shoutcast, shoutcastnative, realmedia, parenthttp. The additional service valid for bandwidth retrieval are: hls, hds, mss, flash. Separate each additional service with a comma.

Once the installation is complete, it will be listed on the Fusion data feeds home page with a green status and monitoring metrics in the log history.

To edit a Fusion data feed click on the data feed in the list and then click the Edit button. Once you have changed the configuration, click Save. This will bring you back to the data feed list with your changes saved and applied to the data feed.