Discover the top benefits of observability
See the research

Content delivery networks, or CDNs, accelerate the transfer of assets necessary to load media and other internet content, including HTML pages, JavaScript files, and style sheets. Many of the largest companies on the internet rely on CDNs because of their ability to deliver efficient, consistent experiences for your end users — regardless of where they’re located. However, by scaling your reach across their widely distributed server infrastructures, using CDNs can make it more difficult to pinpoint the origin of latency issues, anticipate fluctuations in traffic volume, assess the impact of errors, and follow other business-vital performance indicators.

The ability to monitor CDN data can be critical in protecting advertising revenue and customer trust, particularly while delivering real-time content, such as video streaming. Being able to quickly identify and act on CDN-related issues during high-traffic, live events can make the difference between a pleasant viewing experience for users and a disruptive, buffering stream that drives viewers elsewhere. 

CDN performance observability in minutes

We’ve partnered with leading CDN providers Akamai, Cloudflare, and Fastly to create quickstarts that bundle integration instructions, pre-built dashboards, and alerts to help you start monitoring your CDN’s performance in a matter of minutes. By integrating your CDN with New Relic, you can keep tabs on performance metrics such as load balancing, latency, availability, and other information in the context of all your telemetry data.

Akamai integration

Akamai uses its distributed cloud platform to enable users to build, run, and secure applications in one place. Akamai DataStream 2 is a real-time log delivery solution that supports sending log files to New Relic for improved log analytics. 

The Akamai DataStream 2 quickstart comes with a pre-built dashboard and 5XX error alert to let you instantly monitor Akamai performance in New Relic, such as cache-hit ratio, and view client information like browser and browser version.

Demo: Set up and deploy the Akamai DataStream 2 quickstart in minutes.

How to set up the Akamai integration

Watch the video above or follow the instructions below:

  1. Create a job by making a POST request to the Akamai DataStream 2 endpoint.
  • Log in to the Akamai Control Center using an account that has access to DataStream 2.
  • Navigate to Common Services > DataStream > Create stream.
  • Configure your DataStream with a human-readable name, select desired properties, then select Next.
  • Choose the data sets you want to send to New Relic. Under Log format, select JSON. See Akamai’s documentation on data set parameters.
  • Select New Relic from the Destination drop-down menu, and configure the destination with these values:
  • Select Validate & Save to validate the connection to the destination and save the details you provided.
  • After you confirm your push frequency, you'll be able to save the stream and activate the connection on Akamai’s network.
  1. Enable or edit a job in Akamai.
  • After your DataStream is created, select Proceed to Property Manager > Default Rules to edit and enable the DataStream behavior for each property.
    • Select DataStream 2 for the Stream version.
    • Toggle Enable to On.
    • Select the Stream names you created in the last step.
    • Specify the percentage of logs data from this property that you wish to stream to New Relic next to Sampling rate.
    • Select Save.
    • Go to the Activate tab and select the version to activate on Akamai’s network.
  1. Install the Akamai quickstart.
  • Open New Relic and navigate to Add data to install the Akamai DataStream 2 quickstart to view a pre-built dashboard, auto-populated with key insights from your log stream data.

Head to the Akamai documentation to learn about additional options in the Akamai DataStream 2 UI to create a custom header, increase or decrease push frequency, and modify the DataStream behavior in Property Manager.

UI for DataStream 2 integration

Cloudflare integration

Cloudflare uses its expansive network to make everything you connect to the internet secure, private, fast, and reliable while protecting them from malicious attacks like DDoS. Integrating Cloudflare Logpush with New Relic provides insights into key metrics around web traffic and security, including saved bandwidth, recent threat counts, requests and errors by status, and a broad selection of monitoring features. 

The Cloudflare Network Logs quickstart populates this Cloudflare Logpush data on a New Relic dashboard, providing you with an overview of some of the most important performance metric logs from all your websites and applications.

Install the Cloudflare Network Logs quickstart for a pre-built interactive dashboard showing key performance metrics.

How to set up the Cloudflare integration

Follow these instructions or read the ​​docs to learn how to send your Cloudflare logs to New Relic and get pre-built visualizations of your CDN performance.

  1. To create a job, make a POST request to the Cloudflare Logpush jobs endpoint. 
  • Configure your request in Cloudflare with these fields:
    • name: (optional) Use your domain name as the job name.
    • logpull_options: (optional) To configure fields, sample rate, and timestamp format, refer to the Logpush API options. To query Cloudflare logs, New Relic requires fields to be sent as a UNIX timestamp.
    • destination_conf: A log destination consisting of an endpoint URL, a license key, and a format in the following string format:
      • <NR_ENDPOINT_URL>: Enter New Relic HTTP log ingest endpoint.
        • US: 
        • EU:
      • <NR_LICENSE_KEY>: Replace this with your New Relic license key, which you can retrieve from the UI or API. 
      • format:  cloudflare
      • max_upload_records: (optional) The maximum number of log lines per batch. This must be at least 1,000 lines or more. Note that there is no way to specify a minimum number of log lines per batch. This means that log files may contain many fewer lines than specified.
      • max_upload_bytes: (optional) This must be at least 5 MB. Note that there is no way to set minimum file size. 
      • dataset: Refer to Cloudflare log fields documentation for the full list of supported datasets.
  1.  Enable or update a job in Cloudflare.
  • To enable a job, make a PUT request to the Logpush jobs endpoint. Use the job ID returned from the previous step in the URL and send {"enabled": true} in the request body.
  1. Install the Cloudflare quickstart.
  • Navigate to Add data in New Relic and install the Cloudflare Network Logs quickstart to view a pre-built dashboard auto-populated with key insights from your log stream data.

Fastly integration

Fastly's edge cloud platform is designed to take advantage of the modern internet. It’s programmable and supports agile software development with greater visibility and minimal latency—empowering developers to innovate with performance and security. The Fastly real-time analytics API can send aggregates of metrics including response size, request size, cache hits and misses, and a count of each status code, returning a new set of results with each query. 

Our Fastly CDN quickstart auto-populates your data into a user-friendly overview within New Relic. It also comes with two alert configurations that will notify you of excessive error counts and slow response times.

Demo: Set up and deploy the Fastly CDN quickstart in minutes.

How to set up the Fastly integration

Watch the video or follow the following instructions:

  1. To create a job, make a POST request to the Fastly endpoint.
  • Create a New Relic logs endpoint in the Fastly Service configuration. Use these endpoint fields:
  • From Region controls, select the region to stream logs to. 
  • Select Create to create the new logging endpoint.
  1. Enable the job in Fastly.
  • Select Activate to deploy your configuration changes.
  1. Install the Fastly quickstart.
  • Navigate to Add data in New Relic and install the Fastly CDN quickstart to view a pre-built dashboard auto-populated with key insights from your log stream data. Note: This quickstart integration is built on Fastly's expanded log format.

Check out the Fastly documentation for more information on adding New Relic logs as a logging endpoint, including recommended formatting with examples.

Fastly CDN logs UI