Introducing Edgio Applications v7Find out what's new.

New Relic Log Delivery

RTLD may automatically deliver compressed log data to your New Relic account by submitting HTTPS POST requests to it. Each request represents a compressed JSON or CSV document that uniquely identifies a set of log data and describes one or more log entries.
Key information:
  • The format for log data delivered to New Relic is JSON Array. This log format does not provide information that uniquely identifies a set of log data. As a result, there is no way to check for gaps in sequence numbers when attempting to identify missing log data.
  • You must define an event type when setting up a log delivery profile. Query delivered log data by constructing a NRQL that selects data using this event type label (e.g., SELECT \* FROM Event Type).
  • RTLD authorizes requests to New Relic through an Inserts insight API key. Due to security best practices, we recommend using a dedicated API key for RTLD requests.
  • The set of available log fields varies by RTLD module: RTLD CDN | RTLD WAF | RTLD Rate Limiting | RTLD Bot
  • RTLD CDN and RTLD Rate Limiting support delivery to the New Relic destination.
To set up New Relic log delivery
  1. Optional. Register an Inserts insight API key that is dedicated for RTLD log delivery.
    View New Relic documentation on how to register an Inserts insight API key.
  2. Upon completing the above step, you should create a log delivery profile for New Relic.
To set up a log delivery profile
  1. From the Real-Time Log Delivery page, click + New Log Delivery Profile and then select the desired type of log field.
    1. Open the desired property.
      1. Select either your private space or a team space.
      2. Click on the desired property.
    2. From the left pane, click on the desired environment.
    3. From the left pane, click Realtime Log Delivery.
    4. Click + New Log Delivery Profile and then select either CDN, WAF, Rate Limiting, or Bot.
  2. From the Profile Name option, assign a name to this log delivery profile.
  3. From the Log Delivery Method option, select New Relic.
  4. Define how RTLD will communicate with New Relic.
    1. Set the Account ID option to your New Relic account ID.
    2. Set the Event Type option to a label that identifies log data delivered to New Relic as a result of this profile. Specify a label that solely consists of alphanumeric characters, underscores, and colons.
    3. Set the Insert Key option to an Inserts insight API key.
  5. From the Log Format option, select whether to format log data using our standard JSON format, as a JSON array, as JSON lines, or as a CSV (RTLD CDN only).
    Learn more about these formats: RTLD CDN | RTLD WAF | RTLD Rate Limiting | RTLD Bot
  6. From the Downsample the Logs option, determine whether to reduce the amount of log data that will be delivered. For example, you may choose to only deliver 1% of your log data.
    • All Log Data: Verify that the Downsample the Logs option is cleared.
    • Downsampled Log Data: Downsample logs to 0.1%, 1%, 25%, 50%, or 75% of total log data by marking the Downsample the Logs option and then selecting the desired rate from the Downsampling Rate option.
      Use this capability to reduce the amount of data that needs to be processed or stored within your web server(s).
      RTLD CDN Only: Downsampling log data also reduces usage charges for this service.
  7. Determine whether log data will be filtered.
  8. By default, all log fields are enabled on a new log delivery profile. Clear each field for which log data should not be reported. Adjust the set of log fields that will be included within this log delivery profile from within the Fields section.
    Log fields are categorized. You may add or remove individual fields by expanding a category and then marking or clearing specific log fields. Alternatively, add or remove all of the log fields associated with a category by marking or clearing the desired category.
    RTLD CDN Only: You may also log request headers, response headers, and cookies by adding them through the Custom Request Headers, Custom Response Headers, and Custom Cookies options. You may either select the name of the desired header or cookie, or type its name and then press `ENTER`. Click on the list to add additional headers or cookies. Remove a header or cookie by clicking on its `x`.
    Although other settings take effect quickly, it may take up to 90 minutes to log data for custom request/response headers and cookies.
    Learn more about log fields: RTLD CDN | RTLD WAF | RTLD Rate Limiting | RTLD Bot
  9. Click Create Log Delivery Profile.