Log streaming: New Relic Logs

Fastly's Real-Time Log Streaming feature can send log files to New Relic Logs.


Fastly does not provide direct support for third-party services. Read Fastly's Terms of Service for more information.


Before adding New Relic Logs as a logging endpoint for Fastly services, you will need to:

Adding New Relic Logs as a logging endpoint

Follow these instructions to add New Relic Logs as a logging endpoint:

  1. Deliver services
  2. Compute services
  1. Review the information in our guide to setting up remote log streaming.
  2. In the New Relic Logs area, click Create endpoint.
  3. Fill out the Create a New Relic Logs endpoint fields as follows:
    • In the Name field, enter a human-readable name for the endpoint.
    • In the Placement area, select where the logging call should be placed in the generated VCL. Valid values are Format Version Default, waf_debug (waf_debug_log), and None. Read our guide on changing log placement for more information.
    • In the Log format field, optionally enter an Apache-style string or VCL variables to use for log formatting. Consult the example format section for details.
    • In the License key / Insert key field, enter your New Relic license key or Insert API key.
    • From the Region controls, select the region to stream logs to.
  4. Click Create to create the new logging endpoint.
  5. Click Activate to deploy your configuration changes.

Example format

Data sent to New Relic Logs must be serialized as a JSON object. Here's the recommended example format string for sending data to New Relic Logs:

2 "timestamp": %{time.start.msec}V,
3 "cache_status":"%{regsub(fastly_info.state, "^(HIT-(SYNTH)|(HITPASS|HIT|MISS|PASS|ERROR|PIPE)).*", "\\2\\3") }V",
4 "client_ip":"%h",
5 "client_device_type":"%{client.platform.hwtype}V",
6 "client_os_name":"%{client.os.name}V",
7 "client_os_version":"%{client.os.version}V",
8 "client_browser_name":"%{client.browser.name}V",
9 "client_browser_version":"%{client.browser.version}V",
10 "client_as_name":"%{client.as.name}V",
11 "client_as_number":"%{client.as.number}V",
12 "client_connection_speed": "%{client.geo.conn_speed}V",
13 "client_port": %{client.port}V,
14 "client_rate_bps":%{client.socket.tcpi_delivery_rate}V,
15 "client_recv_bytes":%{client.socket.tcpi_bytes_received}V,
16 "client_requests_count":%{client.requests}V,
17 "client_resp_body_size_write": %{resp.body_bytes_written}V,
18 "client_resp_header_size_write": %{resp.header_bytes_written}V,
19 "client_resp_ttfb": %{time.to_first_byte}V,
20 "client_rtt_us":%{client.socket.tcpi_rtt}V,
21 "content_type":"%{Content-Type}o",
22 "domain": "%{Fastly-Orig-Host}i",
23 "fastly_datacenter": "%{server.datacenter}V",
24 "fastly_host": "%{server.hostname}V",
25 "fastly_is_edge": %{if(fastly.ff.visits_this_service == 0, "true", "false")}V,
26 "fastly_region": "%{server.region}V",
27 "fastly_server": "%{json.escape(server.identity)}V",
28 "host": "%v",
29 "origin_host":"%v",
30 "origin_name":"%{req.backend.name}V",
31 "request":"%{req.request}V",
32 "request_method":"%m",
33 "request_accept_charset":"%{json.escape(req.http.Accept-Charset)}V",
34 "request_accept_language":"%{json.escape(req.http.Accept-Language)}V",
35 "request_referer":"%{json.escape(req.http.Referer)}V",
36 "request_user_agent":"%{json.escape(req.http.User-Agent)}V",
37 "resp_status":"%s",
38 "response": "%{resp.response}V",
39 "service_id":"%{req.service_id}V",
40 "service_version": "%{req.vcl.version}V",
41 "status":"%s",
42 "time_start":"%{begin:%Y-%m-%dT%H:%M:%SZ}t",
43 "time_end":"%{end:%Y-%m-%dT%H:%M:%SZ}t",
44 "time_elapsed":%D,
45 "tls_cipher":"%{json.escape(tls.client.cipher)}V",
46 "tls_version":"%{json.escape(tls.client.protocol)}V",
47 "url":"%{json.escape(req.url)}V",
48 "user_agent":"%{json.escape(req.http.User-Agent)}V",
49 "user_city":"%{client.geo.city.utf8}V",
50 "user_country_code":"%{client.geo.country_code}V",
51 "user_continent_code":"%{client.geo.continent_code}V",
52 "user_region":"%{client.geo.region}V"

Logging a timestamp

If a timestamp field is present in the Fastly log, it must be specified as milliseconds since Epoch to override the New Relic timestamp. If not included, Fastly will generate a timestamp.

Using New Relic Instant Observability's prebuilt Fastly dashboard

New Relic I/O is an open source ecosystem of community-contributed quickstarts for hundreds of tools and technologies. We've worked with New Relic to develop a prebuilt dashboard that highlights certain key metrics we think are important and useful. Setting up the dashboard is easy and the code is open source in case you want to customize it.

Since the prebuilt dashboard expects certain fields to be present, we encourage using the recommended logging format. That said, there is nothing to stop you from adding fields for your own purposes or to maintain backward compatibility with existing dashboards you've built. The dashboard won't break if you don't send some fields, but certain charts won't have data.

Install the Fastly dashboard

Follow these instructions to install the Fastly dashboard quickstart:

  1. Select the Fastly dashboard quickstart from the New Relic marketplace.

    New Relic Marketplace

    Or navigate directly to the Fastly dashboard page.

  2. Click Install quickstart.

    New Relic Fastly Dashboard Page

  3. Click Begin installation.

    New Relic Fastly Dashboard Install Step 1

  4. Click Done or Skip this step.

    New Relic Fastly Dashboard Install Step 2

  5. Click See your data.

    New Relic Fastly Dashboard Install Step 3

The Fastly dashboard appears.

New Relic Fastly Dashboard

Was this guide helpful?

Do not use this form to send sensitive information. If you need assistance, contact support. This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.